I agree. We have to plan a little bit what has to be done and to take some
decisions about which features should be implemented in the next droids
releases. Once the targets are set we can create jira (improvement, bug,
...) tickets to fullfill the targets. Personally I think Jira is a really
good tool. Unfortunately at the moment we don't really use it to schedule
the changes and set priorities.

IMHO one of the primary requirements is to clean the trunk: for exemple, the
work which has been done in the droids-crawler project has to be integrated
with the droids-core project. Then making some refactoring and implementing
some new features will be much easier.


On Thu, Nov 18, 2010 at 3:48 PM, Paul Rogalinski <[email protected]> wrote:

> Hello,
>
> this would make two of us. We do also use Droids for an Internet (not
> Intranet) crawler project and would agree to contribute reference
> impelmentation and improvements to the API to fix some shortcomings of the
> current version.
>
> Right now I am ending up with overwriting many core classes to fix issues
> with caching, proxy support, url acceptance / rejection vs. filter chains
> and more. I would like to discuss if those changes would make sense in the
> Droids-core or if they are supposed to be implemented on top of the Droids
> API and reference crawler implementation. This has a lot to do with the
> project philosophy and is not for me to decide.
>
> So yes, I am offering my help - but Droids still needs an active project
> maintainer role. Opening Jira tasks and committing patches won't do any good
> until then and feels like wasted energy to me. Please correct me if I am
> wrong.
>
> Kind Regards,
> Paul.
>
>
> tobr wrote:
>
>> Hi,
>>
>> In our company, we are using droids as a crawler for intranet and extranet
>> applications.
>> We are also highly interested in supporting the project.
>> But with the lack of community support by not answering questions on the
>> mailing list,
>> we recently did not even know, if the project is still alive.
>>
>> Tobias
>
>

Reply via email to