Hi Renato, Moving this thread to dev@
On Tue, Mar 5, 2013 at 5:45 PM, <[email protected]> wrote: > > Community strategy > 268 by: Renato Marroquín Mogrovejo > > Hi all, > > While discussing new committers issues with Lewis, some interesting > points appeared. For example, to become an Apache Committer is an > honour but also a responsibility that we all understand. And as we > can't push a group of volunteers to do more or less work on a project, > we should probably have a community strategy as the number of new > committers engaged per year, or relationships with other projects, > etc. > This would help us on building a better, and stronger community around > our project. > I was about to steal the voting thread, but I found creating a new one > a better thing to do (: what do you guys think. I have a number of points to make here. These relate not only directly to my interest to grow the Gora community but also indirectly to my general interest in how communities can grow around good software. * I've really been trying to push the GSoC agenda last year and this year. We were lucky to have you step aboard last year, not only to play (very well) the role of student within the effort but also to take the purpose of GSoC to the next level and present on Gora @ApacheConEU... this is exactly the type of exposure we need. If we are lucky enough to be accepted (as an Apache project) this year into GSoC then I will (or would encourage) mentor and student to present the work either at ApacheConEU/NA or indeed at any other platform which Gora is suitable for. This year we already have one proposal for GSoC for an Oracle backend... this is excellent and proves that the work we did last year was not in vain. * I would like to point you to this resource [0] please head to the #Responsibilities subheading. Really, (although it is up to individuals what they want to do) minimal participation in a project involves (N.B. Please note I did not use the word requires... we don't require much and certainly do not request it either) generally keeping up to track with project direction. Any one PMC member, at any time has the ability to voice concerns over Gora. This level of equality and transparency is an excellent environment for us to grow Gora out... in my opinion, it seems to be working. * Building from the note above, at any time existing PMC members who are maybe not as active as they once were have the ability and the right to declare themselves emeritus[1]. IIRC Julien did this some time ago (although I we still associate him dearly with the project :0)). In my opinion we should proudly maintain all PMC and Committers as their merit never expires. Our goal is to source and engage with other willing to contribute the same way as others have up until now. This way we will grow out. * Because of the distributed nature of Gora backends (some within TheASF, some outside) we have an excellent platform within Gora to reach out to other communities when making releases. In the past, I've posted out releases to Accumulo, Avro, Cassandra, HBase and Hector Client. With the release of Gora 0.3 however we can also reach out to the Amazon community and in the future (once the MongoDB patch is reviewed and integrated) we can reach out to MongoDB users. The list will grow as more traction picks up. These are some of my ideas and efforts to try and further expose Gora, please comment where you wish and even add to the list... all contributions welcome. Thanks for bringing this up. Lewis [0] http://apache.org/dev/new-committers-guide.html [1] http://apache.org/dev/pmc.html#emeritus
