-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jukka Zitting wrote: > Hi, > > At the ApacheCon we discussed about introducing some generic > topic-based mailing lists at Apache. Currently inter-project > cooperation is a bit difficult as joining another dev@ or user@ > mailing list can be a pretty overwhelming experience due to the heavy > volume of project-specific discussion. To avoid this problem we could > introduce some generic mailing lists that cover technologies or other > topics that are of interest to multiple Apache projects. Such lists > could be osgi-interest@, http-interest@, xml-interest@, > rest-interest@, jcr-interest@, build-interest@, etc. Whatever topic > where two more projects have a shared interest and believe that they > could benefit from a low volume forum where they could coordinate > their efforts and exchange experience and code. > > WDYT?
a good start :-) i think these issues are definitely in the air ATM, so i would like to hijack this thread to start to talk about a related issue i think we need to start thinking about how apache - as an organisation - - can re-invent the social integration that jakarta did so well (see http://www.jroller.com/robertburrelldonkin/entry/apache_the_foundation_needs_themes). though mailing lists are a reasonable start, documentation will be needed to write up what happens on list and to share presentations and other material. it's now hard for people to find which projects have interesting code related to a topic which doesn't directly map to a particular top level project. so, a directory role is also needed. i would like to see a new organisational unit introduced to focus integration efforts (both social and developmental) that cross-cut project boundaries. i think a 'theme' would be a good name. i see this as a way to meet an emerging grassroots need. for example, lots of projects are now starting to take OSGi tooling seriously. felix is the emerging hub but - as a conventional project - it is not really the right long term organisational vehicle. i also see this as a way to allow apache to push broader strategy. for example, starting a Cloud Computing theme would be a way to crystalise and evangelise efforts in this area which are compatible with the foundation's aims. here's my current thinking (in organisational terms): 1. themes would be grassroots, self organised committees like projects with a management committee and committers, and not top down appointed committees (like legal, infra) 2. unlike projects they would not be allowed to host code or make releases. they would be allowed the other infrastructure of a project (versioned documentation, a website, mailing lists, issue tracking, wiki's). opinions? - - robert -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkncao0ACgkQQ617goCdfgP7xQCfdgxSqDayPmvPWOD6oy7+vraI wCMAoKKhqukXWx+cfH9rKbGW3Ou4RhfX =Nhhc -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: community-unsubscr...@apache.org For additional commands, e-mail: community-h...@apache.org
