?? ... press@ can't be found at http://www.apache.org/mail/ neither eyebrowse. Where can i find the archive (log), by the way?
press@ is not a public list. It is the place where PR firms can (and do) contact us. Yet, the content of those messages are not public information.
'Public Relations Committee': 1. website (www.apache.org/ "site" module) maintenance and improvements/suggestions of userfriendliness of each $tlp sites.
I believe the website needs to be ultimately controlled by the infrastructure committee. We used to have a separate list for doing the 'site' module (site-dev@), but people found it too cumbersome and it was shut down and all discussion was moved back to [EMAIL PROTECTED] So, we've tried having 'site' split off and that failed. And, I also believe that each PMC needs to be responsible for their own site.
2. press@
AFAICT, press@ is doin' just fine. I don't see a need to usurp this into a committee. Plus, the main person to talk to here is Sally. She's pretty much only on press@, AFAIK.
3. apache@ (and hidden mail address :-)
AFAIK, Ken Coar is the one who responds to these. He has, on several occasions, declined offers of assistance - this has been a semi-frequent topic of discussion on infrastructure@, but the outcome has always been the same. Perhaps he'd be willing to change his mind now...
4. [EMAIL PROTECTED] 5. [EMAIL PROTECTED]
I think these two represent a poor trend in that they'd move away from TLP control to centralized control. I can't disagree with that enough. The PMC needs to responsible for this type of stuff.
6. Marketing 7. (Newsletter)
If you want to group these two together, that'd be fine. Call it 'Publicity'.
'Communications Committee': 1. apmail@ 2. supervise of [EMAIL PROTECTED] lists 3. supervise of [EMAIL PROTECTED] lists (community, committer, announce, etc.)
Absolutely not. This is the infrastructure committee's responsibility. Proper operation of the website and mailing lists is the responsibility of that committee. It currently delegates these responsibilities into root@ and apmail@ participants. I don't think you've made a compelling argument that the current situation is broken and worth splitting up into new committees.
4. Coaching (mentoring?) of developers/committers/members
Perhaps incubator, but I'm not clear what you mean. -- justin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
