On 1/17/06, Patrick Lightbody <[EMAIL PROTECTED]> wrote: > * Jive Forums certainly can filter the email, and I may turn that on, but > then I've bypassed > the team rather than working with them. I don't like that approach at all.
I think most of the "old-school" committers would have gone ahead and setup the filters. Then, once the filters were up and running, it would be easy for everyone to see that they are a good idea. Much of this viewpoint stems from the ASF notion of "Revolutions". Our "Rules for Revolutionaries" were first documented in an email by the then PMC Chair of Jakarta during the Tomcat Wars. Many of us have referred to that email so many times since, that it has become part of the incubator documentation. * http://incubator.apache.org/learn/rules-for-revolutionaries.html Committers often do things on our own, as a whiteboard, and then share them with the group when ready. When Don started Ti, he did it on his own instance of Trac. Nial had up a a site for LazyDynaActionForms for a long time before we made them part of the distribution. Hubert has several Struts extensions going, some that he might contribute some time, others that he may not. To get everyone onboard with Subversion, I had a test conversion done at WUSH.NET first, so that the committers could see exactly how great it would be. We don't consider any of this bypassing the team, we consider it Darwin in action. In concert with the Rules, most projects now have sandboxes where any committer can try something new. Along with Jive Forums, I would also like to use Confluence as our wiki. Right now, the infrastructure team is not up to the challenge of maintaining a Confluence instance. Eventually, I'm sure that circumstance will change, but, in the meantime, Atlassian has graciously offered Confluence space to any ASF project that wants to use it. * http://opensource2.atlassian.com/confluence/oss/dashboard.action One day, we hope to move these wikis to a ASF server. But, in the meantime, we're not breaking any rules or traditions. In fact, we are realizing one of our dearest rules: The Rule of Revolution. I think it would be great if we could do the same thing with Jive. I don't know if Jive would be willing to sponsor it for us, the way Atlassian did or not. But, I would be happy to help administer a Jive instance, the way I help with the Confluence instance. Ideally, after testing the idea at Open Symphony, we would want to open the Jive forums up to any other ASF projects that were interested. I'm sure many of my favorite projects, like iBATIS, MyFaces, and Roller, would also love to have Jive forums, especially for the User lists. So my suggestion would be to: * Setup a set of five Jive forums for our five email sources: User posts, Dev posts, Wiki posts, Issue posts, and Repository posts. * Use filters to separate some of these from the monolithic dev@ email source. * See if we can setup a shared Jive instance for any ASF project to use, perhaps sponsored by Jive Forms or Contegrix. When the time is right, we can propose moving Jive to an ASF server. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
