On Sat, 19 Aug 2006, Torsten Curdt wrote:
> Why that combination? ...feels quite unnatural to me - I am sure so it
will
> for the users.
It's our list of small largely inactive subprojects. We know that none of
those are going to go TLP, and their dev lists are quiet by an order of
magnitude compared to an inactive TLP potential project like Slide.
True ...but that grouping is not obvious to the users. Besides conditions
*could* change.
The grouping is 'Jakarta' :)
I'm not sure the obviousness to users is important, this is the dev@
mailing list and not a user@ one.
> Combining mailinglist would definitely get a -1 from me. I don't want the
> few BCEL subscribers left to unsubscribe because they get annoyed
> because they are receiving mails they are not interested in.
>
> We might get away with that at commons - but in general I think it's
> quite a bad idea.
We've a bunch of relatively small codebases and subprojects that on their
own are a stretch to maintain oversight over. It's a match for the Commons
approach of having those communities share the same space and help each
other on general issue topics, such as releases.
Well, oversight does not really apply to the users. Besides developers
could subscribe to all sub projects list. We could even ask comitters or
at least PMC members to subscribe to all of them to achieve the same
kind of oversight. ...it would just be more convenient for the users.
We could - but I don't see any reason why we should have so much make-work
to do as opposed to being on the same dev list.
IMO rather have it too fine grained and combine than too general and you
are stuck with what you don't want.
Too fine grained and combine hasn't been working well up to now. Do you
think the commons-dev merged approach is damaging?
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
