Hi, I understand the point, but honestly, I’m not sure using GitHub issues will improve the current state.
For instance, if we have lot of PR without Jira attached, I doubt they will have GitHub issue either ;) So, my point is more to "drive" people to first create Jira before doing the PR. A possible improvement would be to use a PR template. It’s simply a file located in .github/PULL_REQUEST_TEMPLATE.md where we can have something like: **Please** add a meaningful description for your change here ------------------------ Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] [**Choose reviewer(s)**](https://unomi.apache.org/contribute/#make-your-change) and mention them in a comment (`R: @username`). - [ ] Format the pull request title like `[UNOMI-XXX] Fixes bug in ApproximateQuantiles`, where you replace `UNOMI-XXX` with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue. - [ ] Update `CHANGES.md` with noteworthy changes. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). See the [Contributor Guide](https://unomi.apache.org/contribute) for more tips on [how to make review process smoother](https://unomi.apache.org/contribute/#make-reviewers-job-easier). As reminder: if using the right format, PR and Jira can be linked easily. Regards JB > Le 29 mars 2021 à 15:16, Serge Huber <[email protected]> a écrit : > > Actually this was something I suggested to Taybou as we are currently > struggling to keep up with tickets and PRs, as a lot of committers are not > following the procedures because they involve extra "meta" work that is not > in the flow of coding with modern tools. > > Going full github seems like things are better integrated but indeed the > reliance on such tools can be problematic from an Apache point of view. > Thanks for bringing that up JB. For continuous integration I guess it is > acceptable to migrate to github as its just transient data but for issues I > could understand that it could be a problem despite the fact that they are > still sent in the mailing lists. > > Regards, > Serge... > > On Mon, Mar 29, 2021 at 2:37 PM Jean-Baptiste Onofre <[email protected]> > wrote: > >> Hi, >> >> What’s the point about moving to GitHub issues ? >> >> I’m -1 about this generally speaking as we "could" lose the governance. >> Jira is managed by Apache infra, GitHub is not. >> >> It’s exactly the same between GitBox vs GitHub (and reason why GitHub is a >> mirror of GitBox). >> >> Regards >> JB >> >>> Le 29 mars 2021 à 12:16, Mohamed-Tayeb BENTERKI <[email protected]> a >> écrit : >>> >>> Hello, >>> >>> I propose to move the project management tool from Jira to Github issues, >>> the idea behind this, to centralize all tickets and or issues in one >> place >>> as code and simplify the process of agile ticket creation and handling. >>> >>> Note: >>> - There is no impact on the Unomi code base. >>> - If you like the idea and the benefits, I will take care of migrating >> the >>> current Jira board tickets to Github issues. >>> >>> Thoughts? >>> Regards >> >>
