<div dir="ltr"><div><div>When the default is gonna be unassigned for WFLY and WFCORE, following pages should get better visibility: <br><br></div><div> - <a href="https://issues.jboss.org/projects/WFLY?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page">https://issues.jboss.org/projects/WFLY?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page</a><br> - <a href="https://issues.jboss.org/projects/WFCORE?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page">https://issues.jboss.org/projects/WFCORE?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page</a><br><br></div><div>Reason is to have easy way how to identify component owner when there is lack of activity on the issue.<br></div><div><br></div></div>Rostislav</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 29, 2018 at 5:15 PM, David Lloyd <span dir="ltr"><<a href="mailto:david.lloyd@redhat.com" target="_blank">david.lloyd@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There's nothing stopping leads (or others) from commenting on issues<br>
with questions and/or more information, also. I'm more inclined to do<br>
that when I look at an issue and think "this isn't assigned to me, so<br>
I better make a note for whoever works the issue instead of just<br>
writing it on a forgotten notepad somewhere". Even if it ends up<br>
being me, it's helpful.<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, Mar 29, 2018 at 9:58 AM, Brian Stansberry<br>
<<a href="mailto:brian.stansberry@redhat.com">brian.stansberry@redhat.com</a>> wrote:<br>
> I'm in favor of this change.<br>
><br>
> I think in most cases it's important for people to communicate with<br>
> component leads before they start doing much on an issue. But having the<br>
> issued assigned to the lead hasn't AFAICT help ensure that kind of<br>
> communication.<br>
><br>
> On Thu, Mar 29, 2018 at 9:41 AM, Andrig Miller <<a href="mailto:anmiller@redhat.com">anmiller@redhat.com</a>> wrote:<br>
>><br>
>> Good points. The issue has always been getting component leads to triage<br>
>> their issues on a regular enough basis.<br>
>><br>
>> If this is just hiding that problem, and causing issues with community<br>
>> involvement, I am all for going back to unassigned.<br>
>><br>
>> Andy<br>
>><br>
>> On Thu, Mar 29, 2018 at 8:39 AM, David Lloyd <<a href="mailto:david.lloyd@redhat.com">david.lloyd@redhat.com</a>><br>
>> wrote:<br>
>>><br>
>>> Speaking for myself, I'd rather have issues unassigned because having<br>
>>> it assigned means "do not work on this; someone else is going to".<br>
>>> Then they just sit like that, maybe for years.<br>
>>><br>
>>> I think having a default assignee is hiding the symptom while at the<br>
>>> same time discouraging volunteers from taking issues. It's even worse<br>
>>> now that we have multiple teams within Red Hat itself who want to work<br>
>>> issues. I often get emails like "I see that WFLY-xxx is assigned to<br>
>>> you; is it OK if I take it?" For every one of these, there may be<br>
>>> several (internal or external) where they just give up because the<br>
>>> issue is "assigned", and they just wait forever for someone to deliver<br>
>>> the fix/feature for them.<br>
>>><br>
>>> We see every issue as they are created. If we don't take an issue at<br>
>>> that time, being honest, are we really ever going to do it?<br>
>>><br>
>>> On Thu, Mar 29, 2018 at 9:28 AM, Andrig Miller <<a href="mailto:anmiller@redhat.com">anmiller@redhat.com</a>><br>
>>> wrote:<br>
>>> > This is the way it was a long time ago, and then we moved to default to<br>
>>> > the<br>
>>> > component lead because so many issues were being left in the unassigned<br>
>>> > state.<br>
>>> ><br>
>>> > Perhaps the default assignment just makes thing "look" better, and<br>
>>> > doesn't<br>
>>> > force triage to occur, or perhaps it does?<br>
>>> ><br>
>>> > I think we just think about this a little more, since we made the<br>
>>> > change<br>
>>> > because of such a mountain of issues being in the unassigned state.<br>
>>> ><br>
>>> > Andy<br>
>>> ><br>
>>> > On Thu, Mar 29, 2018 at 8:20 AM, David Lloyd <<a href="mailto:david.lloyd@redhat.com">david.lloyd@redhat.com</a>><br>
>>> > wrote:<br>
>>> >><br>
>>> >> This is something we've talked about before. I think we should move<br>
>>> >> forward on this for the WFLY and WFCORE projects.<br>
>>> >><br>
>>> >> Ideally we'd also have a "responsible person" field which would be<br>
>>> >> populated by the component lead by default. But I don't think this is<br>
>>> >> necessary as long as our component leads are triaging issues in their<br>
>>> >> areas (which they should be).<br>
>>> >><br>
>>> >> I think we should just do it. WDYT?<br>
>>> >><br>
>>> >> --<br>
>>> >> - DML<br>
>>> >> ______________________________<wbr>_________________<br>
>>> >> wildfly-dev mailing list<br>
>>> >> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
>>> >> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > --<br>
>>> > Andrig (Andy) T. Miller<br>
>>> > Global Platform Director, Middleware<br>
>>> > Red Hat, Inc.<br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> - DML<br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Andrig (Andy) T. Miller<br>
>> Global Platform Director, Middleware<br>
>> Red Hat, Inc.<br>
>><br>
>> ______________________________<wbr>_________________<br>
>> wildfly-dev mailing list<br>
>> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Brian Stansberry<br>
> Manager, Senior Principal Software Engineer<br>
> Red Hat<br>
<br>
<br>
<br>
--<br>
- DML<br>
______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>