You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by Mohamed-Tayeb BENTERKI <ta...@apache.org> on 2021/03/29 10:16:44 UTC
[PROPOSAL] Moving to Github issues
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
Re: [PROPOSAL] Moving to Github issues
Posted by Mohamed-Tayeb BENTERKI <ta...@apache.org>.
Hello,
Thank you JB for the point, the explanation and also Serge's clarification.
My point was just to move the tickets to be closest to the code. Indeed, we
have to stay in the same workspace (tickets, code and CI).
But as you said, we can stay with our nice Jira board for the moment.
Thank you
Cheers
On Mon, Mar 29, 2021 at 3:29 PM Jean-Baptiste Onofre <jb...@nanthrax.net>
wrote:
> NB: we already have a PR (I already sent an example while ago).
>
> > Le 29 mars 2021 à 15:25, Jean-Baptiste Onofre <jb...@nanthrax.net> a écrit
> :
> >
> > 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 <sh...@apache.org> 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 <jb...@nanthrax.net>
> >> 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 <ta...@apache.org> 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
> >>>
> >>>
> >
>
>
Re: [PROPOSAL] Moving to Github issues
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
NB: we already have a PR (I already sent an example while ago).
> Le 29 mars 2021 à 15:25, Jean-Baptiste Onofre <jb...@nanthrax.net> a écrit :
>
> 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 <sh...@apache.org> 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 <jb...@nanthrax.net>
>> 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 <ta...@apache.org> 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
>>>
>>>
>
Re: [PROPOSAL] Moving to Github issues
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
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 <sh...@apache.org> 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 <jb...@nanthrax.net>
> 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 <ta...@apache.org> 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
>>
>>
Re: [PROPOSAL] Moving to Github issues
Posted by Serge Huber <sh...@apache.org>.
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 <jb...@nanthrax.net>
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 <ta...@apache.org> 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
>
>
Re: [PROPOSAL] Moving to Github issues
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
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 <ta...@apache.org> 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