On Tue 31 Mar 2009 21:34, Henri Yandell <[email protected]> wrote:
> Use community@ - if people get annoyed they'll voice that and the
> correct context list can be created. Community gets used so rarely
> that I don't have a filter for it, so there's nothing to complain
> about yet and you're making make work.
+1 for using community@
gene...@jakarta used to be like that. Some people loved it. Some
people didn't. Personally, I think we as a foundation have lost
"something" as Jakarta has disbanded. A lively general discussion list
is useful. And members@ is too closed.
The trouble with a general@ list is that it's hard to build a specific
community there. Just because there are occasional good threads about,
say, osgi on a general@ list, why would a non-ASF committer subscribe to
general@ instead of existing osgi specific mailing lists?
So I think you have to consider your goal:
If you want to create a public community for discussing a specific
topic, then specific interest lists are appropriate, either here or
outside the ASF, such as Google Groups.
If you want to bounce ideas around other people already inside the ASF,
then use a general list like commun...@. You can always move the
discussion elsewhere if necessary.
--
J Aaron Farr jadetower.com [US] +1 724-964-4515
馮傑仁 cubiclemuses.com [HK] +852 8123-7905
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
