[ANNOUNCE] JIRA permissions changed: Only committers can assign somebody to a ticket

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[ANNOUNCE] JIRA permissions changed: Only committers can assign somebody to a ticket

Robert Metzger
Hi all,

The permissions for the FLINK Jira project have been changed [1], to *only
allow committers and PMC members to assign somebody to a Jira ticket.*

Anybody with a Jira account can be assigned to a ticket. There is no need
for "Contributor" permissions.

This has been discussed in this mailing list thread [2]. More information
on the contribution process is available on the Flink website [3].
The goal of this change is to ensure that discussions happen in the JIRA
ticket, before implementation work has started.
I'm encouraging all committers to monitor the Jira tickets created in
"their" components, drive discussions to a consensus and then assign
somebody to the ticket (indicating that this change has been agreed upon
and that somebody will review and merge it).

Best,
Robert



[1] https://issues.apache.org/jira/browse/INFRA-18644
[2]
https://lists.apache.org/thread.html/b39e01d636cffa74c85b2f7405a25ec63a38d47eb6e0133d22873478@%3Cdev.flink.apache.org%3E
[3] https://flink.apache.org/contributing/contribute-code.html
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCE] JIRA permissions changed: Only committers can assign somebody to a ticket

bowen.li
shall we announce in user ML too? Users who are used to assign tickets to
themselves should also be aware of this change

On Thu, Jul 18, 2019 at 3:06 AM Robert Metzger <[hidden email]> wrote:

> Hi all,
>
> The permissions for the FLINK Jira project have been changed [1], to *only
> allow committers and PMC members to assign somebody to a Jira ticket.*
>
> Anybody with a Jira account can be assigned to a ticket. There is no need
> for "Contributor" permissions.
>
> This has been discussed in this mailing list thread [2]. More information
> on the contribution process is available on the Flink website [3].
> The goal of this change is to ensure that discussions happen in the JIRA
> ticket, before implementation work has started.
> I'm encouraging all committers to monitor the Jira tickets created in
> "their" components, drive discussions to a consensus and then assign
> somebody to the ticket (indicating that this change has been agreed upon
> and that somebody will review and merge it).
>
> Best,
> Robert
>
>
>
> [1] https://issues.apache.org/jira/browse/INFRA-18644
> [2]
>
> https://lists.apache.org/thread.html/b39e01d636cffa74c85b2f7405a25ec63a38d47eb6e0133d22873478@%3Cdev.flink.apache.org%3E
> [3] https://flink.apache.org/contributing/contribute-code.html
>
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCE] JIRA permissions changed: Only committers can assign somebody to a ticket

Robert Metzger
I thought about this, but decided against it. I would hope that everybody
who's involved with the development in a way that they assign issues to
themselves is also active on this list.
Users who just report a bug should not just assign themselves.
If you disagree with me, feel free to forward the email to the user@ list.
It is okay for me if you do that :)

On Thu, Jul 18, 2019 at 9:47 PM Bowen Li <[hidden email]> wrote:

> shall we announce in user ML too? Users who are used to assign tickets to
> themselves should also be aware of this change
>
> On Thu, Jul 18, 2019 at 3:06 AM Robert Metzger <[hidden email]>
> wrote:
>
> > Hi all,
> >
> > The permissions for the FLINK Jira project have been changed [1], to
> *only
> > allow committers and PMC members to assign somebody to a Jira ticket.*
> >
> > Anybody with a Jira account can be assigned to a ticket. There is no need
> > for "Contributor" permissions.
> >
> > This has been discussed in this mailing list thread [2]. More information
> > on the contribution process is available on the Flink website [3].
> > The goal of this change is to ensure that discussions happen in the JIRA
> > ticket, before implementation work has started.
> > I'm encouraging all committers to monitor the Jira tickets created in
> > "their" components, drive discussions to a consensus and then assign
> > somebody to the ticket (indicating that this change has been agreed upon
> > and that somebody will review and merge it).
> >
> > Best,
> > Robert
> >
> >
> >
> > [1] https://issues.apache.org/jira/browse/INFRA-18644
> > [2]
> >
> >
> https://lists.apache.org/thread.html/b39e01d636cffa74c85b2f7405a25ec63a38d47eb6e0133d22873478@%3Cdev.flink.apache.org%3E
> > [3] https://flink.apache.org/contributing/contribute-code.html
> >
>