Hi,
On 15/10/13 13:13, Saint Germain wrote:
Hello,
I am a newcomer to Trac and Apache Bloodhound and it seems that both
projects are very interesting for me.
I would like to know what is the best way to contribute ?
For instance for translation, having discussed with rjollos, it seems
better to translate Trac, as the translation will end up eventually in
Apache Bloodhound.
But I would like to add a feature for internationalization (like Django):
https://docs.djangoproject.com/en/1.5/topics/i18n/translation/#how-django-discovers-language-preference
How should I proceed:
1) Send a patch to Trac and wait for Trac integration and hope that
Apache Bloodhound will import it
2) Send a patch to Trac and Apache Bloodhound, but what happens if
both have different comments or if one accept it and not the other ?
3) Send a patch only to Apache Bloodhound
I know that the subject is a bit difficult, so keep in mind that I'm
just someone willing to contribute to nice open source softwares and
looking for the correct way to do it.
Best regards,
The Apache Bloodhound project is likely to be very open to such
contributions and I should really encourage you to do so. Strictly
speaking all of the ways you list to proceed are likely to benefit
Apache Bloodhound as it would be extremely surprising if Trac accepted
your code and Bloodhound decided not to allow it to be used. However, if
you are interested in contributing beyond this, we are very interested
in getting more Bloodhound developers.
Attempting to contribute to both projects simultaneously might end up
being a little confusing, particularly if both accept the code. There
are a few ways that we could manage the difficulties associated with
that depending on how things go, from disabling Trac's version of the
code to encouraging Trac to accept appropriate patches and providing
additional features through extending the Trac version.
Anyway, thanks a lot for the interest and I hope to hear more from you!
Cheers,
Gary
