Hello- Life has swooped up most of my time (baby, work etc)... so I have not been able to focus on droids at all. Earlier this year, i think we added two more committers, but i think things have been pretty quiet since then:
http://search-lucene.com/m/49fNpCl04N http://search-lucene.com/m/Via2e2c1VPF In general, patches are *the* way to get karma and move the project forward. It is easy for us to talk about wanting the project to improve, but without action not much will happen. For people who want to help keep droids alive, patches are the best way to help. ryan On Mon, Nov 22, 2010 at 1:48 PM, Richard Frovarp <[email protected]> wrote: > On 11/22/2010 08:48 AM, Ross Gardler wrote: >> >> A patch that fixes this, and just this would be easy to review and apply. >> >> If you have the energy and desire then go for it. If not - fair enough >> let's allow Droids to go to sleep. >> >> This was suggested recently, people said "no", we need to see community >> and code if the project is to stay alive. >> >> I don't use it. I don't care one way or the other - if others cars then >> I'll apply appropriate parches until someone earns sufficient merit. >> >> Ross >> > > Thank you Ross. > > I think what we're seeing here is that there is a community interested in > using Droids. However, either they're not sure on how to use it > (documentation), or not sure if they're contributions back will be > committed. > > To the community: > > For documentation, it is true that many of us don't like writing > documentation. Perhaps it might be useful if people started asking questions > about how to do X. That can help guide where the documentation needs to go. > Others on this list may have answers to your questions. > > If you have patches or enhancements, offer them up. Put them into Jira so > that we can all see them and make sure they get applied. > > Richard >
