Hi Mathieu, inline...
Am 11.03.20 um 16:29 schrieb Mathieu Lirzin:
You are right. I should be more constructive than just acknowledging that the requirements I expressed were not properly considered. Let me try joining Pierre's effort by providing a simple but radical proposal for our contribution procedure : - Adopt Github Pull Request (PR) as the unique channel for code contribution
-1I don't see a reason why we should not allow patches also. It will make it easier for people to contribute who are not able (or willing) to run their own GitHub repository.
We should encourage people to use PR's but not force it (at least, not immediately...).
- Require tickets only for bug reports
-1Jira tickets for improvements/new features are extremely helpful to have everything in one place (with the addition to a link to the mailing list discussion), track the efforts, watch issues etc.
How would you manage the work then?
- Replace JIRA with Github issues
-1Why should we have two different issue management systems when we can have everything in one place? What advantages do you see for doing so?
I also would not rely too heavily on GitHub because it is not an official ASF resource and IMO Jira is a huge knowledge base of the project.
- Use Github API to get the stats for OFBiz monthly reports
Can you elaborate what you mean/ how you would do it? Thanks, Michael Brohl ecomify GmbH - www.ecomify.de
smime.p7s
Description: S/MIME Cryptographic Signature
