On 11/5/06, Blair Zajac <email@example.com> wrote:
> On Nov 5, 2006, at 9:23 AM, Erik Huelsmann wrote:
> > Every now and then on IRC we see requests for help with the bindings.
> > Almost never do those requests come on #svn, but almost always on
> > #svn-dev.
> > While it is implicit that bindings usage questions be asked on users@,
> > the list traffic does not give any indication bindings questions run
> > any chance of being answered.
> > While all that is true but never seems to have bothered anybody, it
> > didn't result in a lively community of bindings users either. With the
> > instantiation of a bindings-users@ list, I'd like to give a little
> > push in the right direction.
> > Comments?
> I think the bindings could use more love and given the discussion at
> the summit of having a common object model for all the bindings, I
> propose to keep any binding discussions on the main dev list. Moving
> them off to a separate list would, I'm afraid, even give them less
Ah, but note that I didn't propose to divert the posts about
development of the bindings themselves, rather only the posts about
developing with the bindings, ie scripts etc. It's just that the
description of dev@ and users@ to posts of people trying to develop
with the bindings are not really clear where to go. In this case, I
don't think we're splitting something into its own list: what I want
currently doesn't exist: traffic about using the bindings.
Also, note that some of the Subversion devs have said to be unable to
keep up with the tremendous volume of users@ mail. Posts from bindings
users benefit - even more so than other users posts - from being read
by developers. Also, if we are to give them more love - a good idea -
it would be good to know what our users are doing with them (without
having to wade through 100s of messages each day on users...?).
That is nothing irreversible though, we could always pull the plug on
the bindings-users mailing list if it doesn't do what we want...
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Nov 5 19:59:56 2006