Request to be made maintainer of ant-plugin

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

Request to be made maintainer of ant-plugin

Jesse Glick-4
See: https://github.com/jenkins-infra/repository-permissions-updater/pull/1240

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0TDQ0o42j756tkYzC2dQ%3Do45XdfiKTC%3DzwozReMcT2Ow%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Request to be made maintainer of ant-plugin

Oleg Nenashev
I am +1 about it.
Taking the state of the plugin, I would not expect any issues with the transfer. 
But we still need an approval

On Tuesday, August 13, 2019 at 6:17:07 PM UTC+2, Jesse Glick wrote:
See: <a href="https://github.com/jenkins-infra/repository-permissions-updater/pull/1240" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater%2Fpull%2F1240\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEw19DIaIkcIZ6qNI95_8hrdteLxw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater%2Fpull%2F1240\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEw19DIaIkcIZ6qNI95_8hrdteLxw&#39;;return true;">https://github.com/jenkins-infra/repository-permissions-updater/pull/1240

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/47f1a82a-512d-431d-9ce5-bb30b6fa82aa%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Request to be made maintainer of ant-plugin

Mark Waite-2
+1 from me as well.  I assume the approval that is needed is from the current maintainer, or we wait the two week expiration period.  Is that correct?

On Fri, Aug 16, 2019 at 5:37 AM Oleg Nenashev <[hidden email]> wrote:
I am +1 about it.
Taking the state of the plugin, I would not expect any issues with the transfer. 
But we still need an approval

On Tuesday, August 13, 2019 at 6:17:07 PM UTC+2, Jesse Glick wrote:
See: https://github.com/jenkins-infra/repository-permissions-updater/pull/1240

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/47f1a82a-512d-431d-9ce5-bb30b6fa82aa%40googlegroups.com.


--
Thanks!
Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtE8TiE6%3Dj68%2B5rSonmSdvntwvq8rUj8LvVB7_xRb2BvKg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Request to be made maintainer of ant-plugin

Jesse Glick-4
On Fri, Aug 16, 2019 at 9:13 AM Mark Waite <[hidden email]> wrote:
> I assume the approval that is needed is from the current maintainer, or we wait the two week expiration period.  Is that correct?

That is the rule, yes.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1Fc8djtWV0Z__WCUB7J04g%3DqSdiLBB3NLPVMugjYYqhA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Request to be made maintainer of ant-plugin

Oleg Nenashev
Will transfer ownership on Aug 27 if there is no response from the maintainer

On Friday, August 16, 2019 at 4:37:58 PM UTC+2, Jesse Glick wrote:
On Fri, Aug 16, 2019 at 9:13 AM Mark Waite <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="2Lw6h60qFQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">mark.e...@...> wrote:
> I assume the approval that is needed is from the current maintainer, or we wait the two week expiration period.  Is that correct?

That is the rule, yes.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ae5e2923-fe3b-4107-8ad9-f5b369db7263%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Request to be made maintainer of ant-plugin

Francisco Javier Fernandez
I would be interested in becoming co-maintainer if possible

El viernes, 23 de agosto de 2019, 10:05:03 (UTC+2), Oleg Nenashev escribió:
Will transfer ownership on Aug 27 if there is no response from the maintainer

On Friday, August 16, 2019 at 4:37:58 PM UTC+2, Jesse Glick wrote:
On Fri, Aug 16, 2019 at 9:13 AM Mark Waite <[hidden email]> wrote:
> I assume the approval that is needed is from the current maintainer, or we wait the two week expiration period.  Is that correct?

That is the rule, yes.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cd65a792-156d-4d66-9b0f-dcdfcb1ebeac%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Request to be made maintainer of ant-plugin

Jesse Glick-4
On Fri, Aug 23, 2019 at 5:25 AM Francisco Javier Fernandez
<[hidden email]> wrote:
> I would be interested in becoming co-maintainer if possible

+1 as far as I am concerned.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1-9641sw%3Duuo02JL-%3D6GMbZZcpTCqOZvZndcsSJb2RnA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Request to be made maintainer of ant-plugin

Oleg Nenashev
Permissions have been transferred.
Jesse and Francisco, could you please agree about a default assignee for the component?

On Friday, August 23, 2019 at 7:21:22 PM UTC+2, Jesse Glick wrote:
On Fri, Aug 23, 2019 at 5:25 AM Francisco Javier Fernandez
<<a href="javascript:" target="_blank" gdf-obfuscated-mailto="n5XkUFmoAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">fjfer...@...> wrote:
> I would be interested in becoming co-maintainer if possible

+1 as far as I am concerned.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/342757d2-a431-4edb-937b-817d7615f5e0%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Request to be made maintainer of ant-plugin

Jesse Glick-4
On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev <[hidden email]> wrote:
> a default assignee for the component

As always, I prefer there to be no default assignee for a JIRA
component. It is not a helpful concept IMO. If and when I decide to
tackle an issue, I will assign it to myself.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

[DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

Baptiste MATHUS
I fully agree with Jesse's take. IMO for most plugins where the maintainer is not going to have time to jump on new reports right away, this sends a wrong message that issues will be analyzed and fixed by the assignee.
This sends a second bad message: that an issue being already assigned, this is not necessary that someone steps up to work on a fix proposal.

AIUI, the default assignee is often used by maintainers as a nice way to be notified when a new issue arises, but on average not meaning that that given maintainer will commit to address in a timely manner anything new that comes in.

IOW, my main point is that I think we should allow maintainers to be made default assignee, but we should default to having no default assignee.

Le mar. 27 août 2019 à 15:14, Jesse Glick <[hidden email]> a écrit :
On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev <[hidden email]> wrote:
> a default assignee for the component

As always, I prefer there to be no default assignee for a JIRA
component. It is not a helpful concept IMO. If and when I decide to
tackle an issue, I will assign it to myself.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

Matt Sicker
That makes tons of sense to me. You should only assign tickets to
yourself that you're currently working on or at least intend to work
on in the near future.

On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus <[hidden email]> wrote:

>
> I fully agree with Jesse's take. IMO for most plugins where the maintainer is not going to have time to jump on new reports right away, this sends a wrong message that issues will be analyzed and fixed by the assignee.
> This sends a second bad message: that an issue being already assigned, this is not necessary that someone steps up to work on a fix proposal.
>
> AIUI, the default assignee is often used by maintainers as a nice way to be notified when a new issue arises, but on average not meaning that that given maintainer will commit to address in a timely manner anything new that comes in.
>
> IOW, my main point is that I think we should allow maintainers to be made default assignee, but we should default to having no default assignee.
>
> Le mar. 27 août 2019 à 15:14, Jesse Glick <[hidden email]> a écrit :
>>
>> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev <[hidden email]> wrote:
>> > a default assignee for the component
>>
>> As always, I prefer there to be no default assignee for a JIRA
>> component. It is not a helpful concept IMO. If and when I decide to
>> tackle an issue, I will assign it to myself.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox7Xqp9gzdht-R7GYHjs%2B%3DUdw2Yk32H91pnvyUw9axRZw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

halkeye
Does jira have a concept of auto watch like GitHub does? So an issue could still notify people but not be claimed?

On Thu., Sep. 5, 2019, 11:35 a.m. Matt Sicker, <[hidden email]> wrote:
That makes tons of sense to me. You should only assign tickets to
yourself that you're currently working on or at least intend to work
on in the near future.

On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus <[hidden email]> wrote:
>
> I fully agree with Jesse's take. IMO for most plugins where the maintainer is not going to have time to jump on new reports right away, this sends a wrong message that issues will be analyzed and fixed by the assignee.
> This sends a second bad message: that an issue being already assigned, this is not necessary that someone steps up to work on a fix proposal.
>
> AIUI, the default assignee is often used by maintainers as a nice way to be notified when a new issue arises, but on average not meaning that that given maintainer will commit to address in a timely manner anything new that comes in.
>
> IOW, my main point is that I think we should allow maintainers to be made default assignee, but we should default to having no default assignee.
>
> Le mar. 27 août 2019 à 15:14, Jesse Glick <[hidden email]> a écrit :
>>
>> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev <[hidden email]> wrote:
>> > a default assignee for the component
>>
>> As always, I prefer there to be no default assignee for a JIRA
>> component. It is not a helpful concept IMO. If and when I decide to
>> tackle an issue, I will assign it to myself.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox7Xqp9gzdht-R7GYHjs%2B%3DUdw2Yk32H91pnvyUw9axRZw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuvBB0ye4y%2Bg2_F8MjwgbMPutgUbuiFTA0d0fjVnYX4xcw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

slide
In reply to this post by Matt Sicker
We should add a field in the HOSTING Jira that allows people to specify if they want to be set as the default assignee, then the bot can check that field before setting up the default assignee for the component. We would need someone with admin access on Jira to add the field. I can create a PR for the bot once the field is setup.

On Thu, Sep 5, 2019, 11:35 Matt Sicker <[hidden email]> wrote:
That makes tons of sense to me. You should only assign tickets to
yourself that you're currently working on or at least intend to work
on in the near future.

On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus <[hidden email]> wrote:
>
> I fully agree with Jesse's take. IMO for most plugins where the maintainer is not going to have time to jump on new reports right away, this sends a wrong message that issues will be analyzed and fixed by the assignee.
> This sends a second bad message: that an issue being already assigned, this is not necessary that someone steps up to work on a fix proposal.
>
> AIUI, the default assignee is often used by maintainers as a nice way to be notified when a new issue arises, but on average not meaning that that given maintainer will commit to address in a timely manner anything new that comes in.
>
> IOW, my main point is that I think we should allow maintainers to be made default assignee, but we should default to having no default assignee.
>
> Le mar. 27 août 2019 à 15:14, Jesse Glick <[hidden email]> a écrit :
>>
>> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev <[hidden email]> wrote:
>> > a default assignee for the component
>>
>> As always, I prefer there to be no default assignee for a JIRA
>> component. It is not a helpful concept IMO. If and when I decide to
>> tackle an issue, I will assign it to myself.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox7Xqp9gzdht-R7GYHjs%2B%3DUdw2Yk32H91pnvyUw9axRZw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVduNcw%3DWYb6%2BHNebzarAoQCt%2Bg6bQuFgitVP%3DuC3O2Bww%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

Jesse Glick-4
In reply to this post by halkeye
On Thu, Sep 5, 2019 at 2:36 PM Gavin <[hidden email]> wrote:
> Does jira have a concept of auto watch like GitHub does? So an issue could still notify people but not be claimed?

Good question. That would be very useful.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3SkUwcr4D4mDfqgF2axjWFv42J-2_zRcBgF%2BNOXsK%3DLQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

Oleg Nenashev
There are ways to do so. The most straightforward way is to create a filter (or to use a public one), go to "Details" and then to subscribe to notifications there.
E.g. this is how I get notifications about INFRA, Java 11 and JCasC compatibility issues nowadays

image.png


On Fri, Sep 6, 2019 at 12:56 AM Jesse Glick <[hidden email]> wrote:
On Thu, Sep 5, 2019 at 2:36 PM Gavin <[hidden email]> wrote:
> Does jira have a concept of auto watch like GitHub does? So an issue could still notify people but not be claimed?

Good question. That would be very useful.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/sl9eTjIA8F0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3SkUwcr4D4mDfqgF2axjWFv42J-2_zRcBgF%2BNOXsK%3DLQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBjcFw2zoWu7yrz9RuxoVa_Bgr5v0c%3Dnto6uMx7xa9SQg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

Ulli Hafner
In reply to this post by slide
Making it an optional field in the HOSTING report seems to be a good compromise, so +1 from me for such a change.

(I understand that developers do not want to be assignee for issues they are never going to fix. On the other hands, for a user that reports an issue it is somewhat disappointing that no one actually cares about his new issue. This will indicate that it is not worth to report an issue at all.)
 

Am 05.09.2019 um 20:40 schrieb Slide <[hidden email]>:

We should add a field in the HOSTING Jira that allows people to specify if they want to be set as the default assignee, then the bot can check that field before setting up the default assignee for the component. We would need someone with admin access on Jira to add the field. I can create a PR for the bot once the field is setup.

On Thu, Sep 5, 2019, 11:35 Matt Sicker <[hidden email]> wrote:
That makes tons of sense to me. You should only assign tickets to
yourself that you're currently working on or at least intend to work
on in the near future.

On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus <[hidden email]> wrote:
>
> I fully agree with Jesse's take. IMO for most plugins where the maintainer is not going to have time to jump on new reports right away, this sends a wrong message that issues will be analyzed and fixed by the assignee.
> This sends a second bad message: that an issue being already assigned, this is not necessary that someone steps up to work on a fix proposal.
>
> AIUI, the default assignee is often used by maintainers as a nice way to be notified when a new issue arises, but on average not meaning that that given maintainer will commit to address in a timely manner anything new that comes in.
>
> IOW, my main point is that I think we should allow maintainers to be made default assignee, but we should default to having no default assignee.
>
> Le mar. 27 août 2019 à 15:14, Jesse Glick <[hidden email]> a écrit :
>>
>> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev <[hidden email]> wrote:
>> > a default assignee for the component
>>
>> As always, I prefer there to be no default assignee for a JIRA
>> component. It is not a helpful concept IMO. If and when I decide to
>> tackle an issue, I will assign it to myself.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox7Xqp9gzdht-R7GYHjs%2B%3DUdw2Yk32H91pnvyUw9axRZw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVduNcw%3DWYb6%2BHNebzarAoQCt%2Bg6bQuFgitVP%3DuC3O2Bww%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/EA39641E-B166-4453-8D2C-45C841F3D684%40gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

domi@fortysix.ch
My first thought was that I would like to keep the default assignee - but after reading all the comments, I have to agree, that my only reason for this is so that I get notified by new issues. Although Oleg shoed it is possible to create a filter and get notified about this things, It seems quite complicated and many maintainers will not do it and therefore not get any info about new issues. So I think there should be some kind of easy way to at least inform the official maintainer - maybe we can even create these filters automatically…
/Domi


On 6 Sep 2019, at 01:37, Ullrich Hafner <[hidden email]> wrote:

Making it an optional field in the HOSTING report seems to be a good compromise, so +1 from me for such a change.

(I understand that developers do not want to be assignee for issues they are never going to fix. On the other hands, for a user that reports an issue it is somewhat disappointing that no one actually cares about his new issue. This will indicate that it is not worth to report an issue at all.)
 

Am 05.09.2019 um 20:40 schrieb Slide <[hidden email]>:

We should add a field in the HOSTING Jira that allows people to specify if they want to be set as the default assignee, then the bot can check that field before setting up the default assignee for the component. We would need someone with admin access on Jira to add the field. I can create a PR for the bot once the field is setup.

On Thu, Sep 5, 2019, 11:35 Matt Sicker <[hidden email]> wrote:
That makes tons of sense to me. You should only assign tickets to
yourself that you're currently working on or at least intend to work
on in the near future.

On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus <[hidden email]> wrote:
>
> I fully agree with Jesse's take. IMO for most plugins where the maintainer is not going to have time to jump on new reports right away, this sends a wrong message that issues will be analyzed and fixed by the assignee.
> This sends a second bad message: that an issue being already assigned, this is not necessary that someone steps up to work on a fix proposal.
>
> AIUI, the default assignee is often used by maintainers as a nice way to be notified when a new issue arises, but on average not meaning that that given maintainer will commit to address in a timely manner anything new that comes in.
>
> IOW, my main point is that I think we should allow maintainers to be made default assignee, but we should default to having no default assignee.
>
> Le mar. 27 août 2019 à 15:14, Jesse Glick <[hidden email]> a écrit :
>>
>> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev <[hidden email]> wrote:
>> > a default assignee for the component
>>
>> As always, I prefer there to be no default assignee for a JIRA
>> component. It is not a helpful concept IMO. If and when I decide to
>> tackle an issue, I will assign it to myself.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox7Xqp9gzdht-R7GYHjs%2B%3DUdw2Yk32H91pnvyUw9axRZw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVduNcw%3DWYb6%2BHNebzarAoQCt%2Bg6bQuFgitVP%3DuC3O2Bww%40mail.gmail.com.


--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/EA39641E-B166-4453-8D2C-45C841F3D684%40gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/32589E24-7C06-452F-9582-008BD975710F%40fortysix.ch.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

Olblak-2
I totally agree with the general opinion that an issue should only be assigned to someone if that person is effectively ready to work on it otherwise it just bring confusion about either the assignee will effectively works on it or not.
And I also understand that people use default assignee to get notify when a new issue is created.

What I propose is to set 'default assignee' to 'unassigned' by default and add a notification rule saying each time a ticket is (re)-open, or close, we notify component lead. (btw I just created that rule now :p)

Regarding filters, I think it really depends how much time we spend on Jira, personally I heavily rely on them but I don't expect every contributor to configure their own filters

---
-> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---




On Fri, Sep 6, 2019, at 7:38 AM, domi wrote:
My first thought was that I would like to keep the default assignee - but after reading all the comments, I have to agree, that my only reason for this is so that I get notified by new issues. Although Oleg shoed it is possible to create a filter and get notified about this things, It seems quite complicated and many maintainers will not do it and therefore not get any info about new issues. So I think there should be some kind of easy way to at least inform the official maintainer - maybe we can even create these filters automatically…
/Domi


On 6 Sep 2019, at 01:37, Ullrich Hafner <[hidden email]> wrote:

Making it an optional field in the HOSTING report seems to be a good compromise, so +1 from me for such a change.

(I understand that developers do not want to be assignee for issues they are never going to fix. On the other hands, for a user that reports an issue it is somewhat disappointing that no one actually cares about his new issue. This will indicate that it is not worth to report an issue at all.)
 

Am 05.09.2019 um 20:40 schrieb Slide <[hidden email]>:

We should add a field in the HOSTING Jira that allows people to specify if they want to be set as the default assignee, then the bot can check that field before setting up the default assignee for the component. We would need someone with admin access on Jira to add the field. I can create a PR for the bot once the field is setup.

On Thu, Sep 5, 2019, 11:35 Matt Sicker <[hidden email]> wrote:
That makes tons of sense to me. You should only assign tickets to
yourself that you're currently working on or at least intend to work
on in the near future.

On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus <[hidden email]> wrote:
>
> I fully agree with Jesse's take. IMO for most plugins where the maintainer is not going to have time to jump on new reports right away, this sends a wrong message that issues will be analyzed and fixed by the assignee.
> This sends a second bad message: that an issue being already assigned, this is not necessary that someone steps up to work on a fix proposal.
>
> AIUI, the default assignee is often used by maintainers as a nice way to be notified when a new issue arises, but on average not meaning that that given maintainer will commit to address in a timely manner anything new that comes in.
>
> IOW, my main point is that I think we should allow maintainers to be made default assignee, but we should default to having no default assignee.
>
> Le mar. 27 août 2019 à 15:14, Jesse Glick <[hidden email]> a écrit :
>>
>> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev <[hidden email]> wrote:
>> > a default assignee for the component
>>
>> As always, I prefer there to be no default assignee for a JIRA
>> component. It is not a helpful concept IMO. If and when I decide to
>> tackle an issue, I will assign it to myself.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].


--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].


--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e7648c68-92d6-4cc0-a96c-6ff5e925f988%40www.fastmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

halkeye
Filterers can be saved and shared, and so a default search could be setup with https://confluence.atlassian.com/jira063/advanced-searching-functions-683542527.html#AdvancedSearchingFunctions-componentsLeadByUser() and then any custom requirements could be forked and tweaked per user.


On Fri., Sep. 6, 2019, 1:35 a.m. Olblak, <[hidden email]> wrote:
I totally agree with the general opinion that an issue should only be assigned to someone if that person is effectively ready to work on it otherwise it just bring confusion about either the assignee will effectively works on it or not.
And I also understand that people use default assignee to get notify when a new issue is created.

What I propose is to set 'default assignee' to 'unassigned' by default and add a notification rule saying each time a ticket is (re)-open, or close, we notify component lead. (btw I just created that rule now :p)

Regarding filters, I think it really depends how much time we spend on Jira, personally I heavily rely on them but I don't expect every contributor to configure their own filters

---
-> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---




On Fri, Sep 6, 2019, at 7:38 AM, domi wrote:
My first thought was that I would like to keep the default assignee - but after reading all the comments, I have to agree, that my only reason for this is so that I get notified by new issues. Although Oleg shoed it is possible to create a filter and get notified about this things, It seems quite complicated and many maintainers will not do it and therefore not get any info about new issues. So I think there should be some kind of easy way to at least inform the official maintainer - maybe we can even create these filters automatically…
/Domi


On 6 Sep 2019, at 01:37, Ullrich Hafner <[hidden email]> wrote:

Making it an optional field in the HOSTING report seems to be a good compromise, so +1 from me for such a change.

(I understand that developers do not want to be assignee for issues they are never going to fix. On the other hands, for a user that reports an issue it is somewhat disappointing that no one actually cares about his new issue. This will indicate that it is not worth to report an issue at all.)
 

Am 05.09.2019 um 20:40 schrieb Slide <[hidden email]>:

We should add a field in the HOSTING Jira that allows people to specify if they want to be set as the default assignee, then the bot can check that field before setting up the default assignee for the component. We would need someone with admin access on Jira to add the field. I can create a PR for the bot once the field is setup.

On Thu, Sep 5, 2019, 11:35 Matt Sicker <[hidden email]> wrote:
That makes tons of sense to me. You should only assign tickets to
yourself that you're currently working on or at least intend to work
on in the near future.

On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus <[hidden email]> wrote:
>
> I fully agree with Jesse's take. IMO for most plugins where the maintainer is not going to have time to jump on new reports right away, this sends a wrong message that issues will be analyzed and fixed by the assignee.
> This sends a second bad message: that an issue being already assigned, this is not necessary that someone steps up to work on a fix proposal.
>
> AIUI, the default assignee is often used by maintainers as a nice way to be notified when a new issue arises, but on average not meaning that that given maintainer will commit to address in a timely manner anything new that comes in.
>
> IOW, my main point is that I think we should allow maintainers to be made default assignee, but we should default to having no default assignee.
>
> Le mar. 27 août 2019 à 15:14, Jesse Glick <[hidden email]> a écrit :
>>
>> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev <[hidden email]> wrote:
>> > a default assignee for the component
>>
>> As always, I prefer there to be no default assignee for a JIRA
>> component. It is not a helpful concept IMO. If and when I decide to
>> tackle an issue, I will assign it to myself.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].


--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].


--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e7648c68-92d6-4cc0-a96c-6ff5e925f988%40www.fastmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duv4Xufjmjk02R2%3D2biCxE3ZR1hX60Rx0BwyZwTh%2BhEdsA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

Jesse Glick-4
In reply to this post by Oleg Nenashev
On Thu, Sep 5, 2019 at 7:01 PM Oleg Nenashev <[hidden email]> wrote:
> create a filter (or to use a public one), go to "Details" and then to subscribe to notifications there.

I tried this, but it does not do what I need: it just sends, say, a
daily list of all issues matching that filter. To replace the
notification function of default assignee, I would want something that
only send me _changes_ in issues matching the filter.

I suppose a workaround would be to create a filter matching all issues
from some component which I am not watching, and then send a digest of
that; then I would need to click on everything newly appearing and
watch it, and rely on the watches for notifications. Seems pretty
clumsy though.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2kBsSjX50OWKTX1P6EwWPj-KQ_QiufssxjBzi-%3DX3XWg%40mail.gmail.com.
12