On Thu, Mar 6, 2008 at 7:04 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> On Thursday 06 March 2008, Martin Ritchie wrote: > <snip> > > We are > > again working as a community to provide a M2.1 release that will inter > > operate at AMQP 0-9 with other AMQP products outside the Apache world. > > I for one am looking forward to our future releases where we can again > > move the entire project on to the wholly different AMQP 0-10. > > And nothing stops you from doing all of that while still in the incubator > while working on trying to furthur diversify your community. Working > with other AMQP products could be a perfect opportunity to find other > interested people and get them involved with Qpid. Why rush? +1 > From experience with CXF, after we got 2.0 and 2.0.1 out the door, we > thought the same way. "Hey, we worked hard to get the TCK passing, > integrated with Geronimo, and two releases out, we're ready to go!" but > Jim (one of our mentors) still had concerns about diversity. Thus, we > stuck with it and worked hard on getting other people more involved. > It has paid off as we have added several very good folks that have > brought fresh ideas and perspectives to the project. If we HAD > graduated, I'm not sure if we would have spent the time/effort on the > mentoring and such that was required to bring them on board. We've > learned a lot in the process. In hind sight, Jim was completely > correct. Part of the "Apache way" you talk about is being concious of > things like that. > IMHO community building is by far the toughest skill in open source. for a project to be viable in the long run, it needs to learn to recruit and mentor new developers. this takes effort but it's rewarding to see other people with fresh ideas pick up a project and take it forward. it's great to see someone you helped take the first steps here at apache progress all the way to member. prefecting this may well take a lifetime but the basics can be learn by some hard work. engaging a wider audience and community then inducting them to share in the development of a project is the major reason why closed source projects should choose to open up at apache. the IPMC has failed unless we equip projects with the lessons needed to thrive in an open development environment. the reason why we examine projects which arrive from a closed source background more closely is that they have not had the chance to develop these skills before arrival. these cannot easily to learnt by reading but only by doing. so we ask projects to learn by doing: go out and diversify. - robert
