Hello all, I monitor the droids project since a long time now without contributing for nothing. My first goal was to find an inspiration source to design a robot. At that time, I already had a simple implementation inspired by the source code published by Andreas Hess.
I really think that the project is a solid foundation for designing powerful crawlers. >From my point of view, few use cases using the core API should be published, starting by the documentation. Some old web crawler implementation not using the core API should be removed because it makes things difficult to understand. I will publish some documentation on how I used the droid core API for my use case, which is interfacing droids with the java ROME library. Regards, Sylvain On Tue, Nov 23, 2010 at 10:36 AM, Thorsten Scherler <[email protected]> wrote: > On Mon, 2010-11-22 at 10:46 +0100, florent andré wrote: >> Hi all, >> >> We are many to be interesting in this great Droids project and have many >> ideas for the future (recent mails show this). >> >> Thorsten, thanks to him, leads this project till now, but don't have >> still much time for it (and we understand him ! :) ) >> >> So, I think it could be cool if someone (or two, three,...) with enough >> karma, can charge of taking the lead of this project. >> >> Have a lead is a requirement to ensure a good growing of "baby Droids" >> imho. > > Like Ross said we do not have and do not need an official leader in a > healthy Apache project since is based on the community! > > I investigated Droids as a labs project and people started to use it. > Then it came into incubation and I did not found the time anymore to > review all the code changes and keep up with the enhancement suggestion > on the list (e.g. Ming Fai). > > Matter of fact is that there are many things to do where you do not need > any karma: > - review patches > - discuss code enhancements > - prepare releases > - writing documentation > - answering eMails > - etc. > > That can be done by the whole community (with and without commit > rights). > > We have successfully celebrated community days where we reviewed and > committed the patch stack and seeing the recent threads it can be seen > that there are a lot of people either using or monitoring Droids. > > IMO the best way to proceed is to pin down a release and then move > forward designing a new version which incorporates the most common use > cases. Further we should review the architecture regarding the different > componentes, so Droids can run in different environment like GAE [1], > Android, .... > > I am happy to see that there IS a community of followers and hope that > together we can: > a) do a release > b) leave the incubator > c) create a "community" version of Droids where we review the > architecture > > Last but not least I never said I will leave the project, nor that I > will not spent any time on it. I am happy to be part of the community > and help where I can, but I cannot do it by myself anymore. > > So if you find a "junior programming error" then please submit a patch > to fix it rather then just pointing it out, that helps the project. > > If you just started with Droids and the first steps you took to get > coding are still in the back of your head, write documentation, that > helps the project. > > If somebody ask a question on the ml, try to answer it even if you do > not know the solution, that helps the project. > > I believe that Apache Droids is very useful and can be very successful > if we all work together. > > salu2 > > [1] http://search-lucene.com/m/h2isH1e495V/v=threaded > -- > Thorsten Scherler <thorsten.at.apache.org> > codeBusters S.L. - web based systems > <consulting, training and solutions> > http://www.codebusters.es/ > >
