> I don't see why the ASF *has* to support water-cooler conversations. It > just doesn't coincide with our mission.
Why do you keep assuming it is for chit chat? If it were [EMAIL PROTECTED] and it was clear (community imposed/whatever) to be about Java @ ASF, wouldn't that make sense? Aren't there issues (i.e. supporting JDK1.5, not supporting JDK 1.2, that are good cross-project topics?) I'm not suggesting ASF host forums, but a list to discuss language issues/tips-tricks and help w/ fixes/changes, whatever. Sure, only a few folks responded, but that is all the more reason for allow them to communicate with each other. Otherwise ASF projects that need Python skills/experience are starved of a valuable (possibly amenable) source -- i.e. other ASFers. I think we need some "AOI" -- aspect oriented infrastructure. ;-) This is a project "cross cutting concern". No one project needs it (nor could support it) standalone, but a bunch could benefit from it... I know infra@ are overloaded, I wish I could help with that (but believe that is out of my control). That said, in this day and age mailing lists ought not be so heavyweight; I definitely agree with Brian there. Hmm ... perhaps create a 'community PMC' that deals w/ oversight of community related lists, and so forth. Make community communications a project if that helps it fit into ASF... regards, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
