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.
>From the peanut gallery, I'd echo Tony's suggestion earlier. I'd suggest that the Droids team could boost their participation level immensely by providing a simple bootstrapping/quickstart document. Something like Apache Click[1] where, in a couple simple steps you can download a jar, write a handful of code, and see "something." Something doesn't have to be useful - it has to be simple enough to entice me to learn more on my own - pointing to the test code isn't going to drive much adoption I think. --tim [1] - http://click.apache.org/
