I did a search on issues updated in the past 6 month, and here is the list:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CHUKWA+AND+resolution+in+%28Unresolved%2C+Fixed%2C+%22Won%27t+Fix%22%29+AND+updated+%3E%3D+-180d+ORDER+BY+reporter+ASC%2C+key+DESC The community is moving forward with development even without my involvement. I have only written code for 4 of 29 JIRAs. I don't think I am only one that is involved in this project. There are others that are working on this project at their own pace. Some people may have been turn away from this project because the assumption that this project would be retired soon. I am not sure how to fix this mental block that was implanted previously by past concerns. If Chukwa is here to stay in Apache, I would recommend to make new releases of Chukwa to improve the community involvement. In terms of new features, there are some data analysis examples of collected logs could also show developers how to use Chukwa and Hadoop related technologies together to generate insights from collected logs. I volunteer to make releases and let the community contributors steer the direction of the development. Of course, this plan can only carry out base on the voting result in general@incubator. regards, Eric On Mon, Nov 26, 2012 at 12:53 PM, Alan Cabrera <l...@toolazydogs.com> wrote: > > On Nov 26, 2012, at 12:21 PM, Jukka Zitting wrote: > > > Hi, > > > > On Mon, Nov 26, 2012 at 4:52 PM, Alan Cabrera <l...@toolazydogs.com> > wrote: > >> Even by the PPMC's comments they obliquely acknowledge that there's not > much > >> activity and expressed an interested in simply keeping it around with > the hopes > >> that something would happen; there were no concrete ideas or plans on > how to > >> grow the community because, by their own admission, no one has the time > to > >> work much on the project. > > > > That lack of concrete plans is a good place to start. Anyone from the > > community who opposes retirement should take it up on themselves to > > provide such a concrete plan for example in time for next month's > > report. Just like the caster of a technical veto should come up with > > an alternative implementation. :-) > > > As I mentioned in an earlier email, we did have this conversation seven > months ago. We came to a consensus to give it another try. We even added > a few committers a "bit early" with the hopes that they would infuse the > project with more energy. > > The vote came after many discussions over the year. The Chukwa podling, > which was started back in 2010, was given its second chance. Unless > there's something glaring that was overlooked, I'm not prepared to change > my mind about its retirement. > > > Regards, > Alan > >
