[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: The purpose of the dev@ list (was: svn list -R with directories only)

From: Talden <talden_at_gmail.com>
Date: 2007-01-08 01:26:07 CET

There should definitely be separation between user and dev lists. Good
separation makes both lists assets to Subversions constant
improvement, bad separation will hamper it.

It would help to have a page at tigris that explains this separation.
Referencing this when suggesting people go back to the user list for
such questions might help smooth ruffled feathers by showing it as
official policy and not personal opinion.

In would think that people should always ask on the user list for "how
do I..." questions and if they are informed of a technical limitation
then they should consider whether to move the discussion to the dev
list as a discussion of new features.

NB: Polling the user list occassionally with stagnant or newly
proposed features might help identify the degree of acceptance and
demand - it might also help encourage those with the time and skills
to put design and implementation effort in when they see features
they'd like proposed but stagnant.

--
Talden
On 1/8/07, Branko Èibej <brane@xbc.nu> wrote:
> Maybe it's just me, but I see a marked increase of users@-type messages
> on this list, many of which show a distinct lack of RTFMing, and are
> actually responded to instead of being gently redirected to the
> correct list.
>
>
> Now I wouldn't like us to appear unhelpful, but this list has way too
> much legitimate traffic as it is. I suggest we try to be a bit more
> pedantic about what we discuss on dev@.
>
> -- Brane
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
Received on Mon Jan 8 01:26:20 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.