[Python-Dev] Re: 🍝 New keyword in bpo: `newcomer friendly`

2019-07-27 Thread Kyle Stanley 
Not sure if this would be the right place to mention it,
but the side menu url/button "Easy issues" in bpo
should probably be renamed to "Newcomer friendly"
and the "dispname" property in the url could also be
similarly updated. This could be done by changing the
url from: 

[current](https://bugs.python.org/issue?status=1&@sort=-activity&@columns=id%2Cactivity%2Ctitle%2Ccreator%2Cstatus&@dispname=Easy%20issues&@startwith=0&@group=priority&keywords=6&@action=search&@filter=&@pagesize=50&nosy=31554)
 
=>
[updated](https://bugs.python.org/issue?status=1&@sort=-activity&@columns=id%2Cactivity%2Ctitle%2Ccreator%2Cstatus&@dispname=Newcomer%20friendly&@startwith=0&@group=priority&keywords=6&@action=search&@filter=&@pagesize=50&nosy=31554)

Apologies if this should be posted somewhere other
than the mailing list, but I figured there probably
wouldn't be an issue tracker for the issue tracker, 
that would be some serious BPO inception and
quite the paradox.
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/GDPOWKDKOBVRUAG5EHGVC5E6EKRCYEP5/

[Python-Dev] Re: 🍝 New keyword in bpo: `newcomer friendly`

2019-07-27 Thread Kyle Stanley 
Clarification: The url change is only for updating the
"dispname" property, which is shown at the top of 
the page. It would change the header from:

"List of issues - Easy issues"
=>
"List of issues - Newcomer friendly"

Also, I realized that I accidentally included the "nosy"
property at the end, which sets it to only show
anything that I'm on the nosy list for. The "keywords"
property would also have to be updated, it looks like
6 currently represents Easy, not sure what the
value for Newcomer friendly would be.

If the Easy keyword is going to stick around, it might
be better to just have a separate Newcomer friendly
link on the side menu.
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/AEOGHA2EJ4QOFXAC4CO5OHK4AWO6XLRR/

[Python-Dev] Re: 🍝 New keyword in bpo: `newcomer friendly`

2019-07-27 Thread Steve Dower 
On 26Jul.2019 1909, Guido van Rossum wrote:
> See the thread 'The trouble with "Easy" issues' in
> [email protected] .
> Essentially those "easy" issues aren't so easy, and we're starting over.

Couldn't that be achieved just as easily by removing the "Easy" and
"Easy (C)" tags from everything and coming up with a better definition?

I agree they haven't been a great source of bugs for the sprints I've
helped coordinate, but I don't think the problem is the label. But I
assume the bikeshedding over the name has been done on the private list.

Most of the trouble is there are many pending PRs that have not been
merged, and so maybe 3/4 of the issues are not actually available. (My
suspicion is that the delay in CLA handling is a significant factor
here, as many PRs can't be merged during the sprint itself, and we're
not so good at following up later.)

(As an aside, the best first issue is usually the one the new
contributor cares about most, regardless of difficulty. Finding
something "suitable" for someone with no preferences or interests is
never going to be easy.)

Cheers,
Steve
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/44HUPDKAQIR5YU4UPEZS26PBSCXFYSJ5/

[Python-Dev] Re: 🍝 New keyword in bpo: `newcomer friendly`

2019-07-27 Thread Guido van Rossum 
On Sat, Jul 27, 2019 at 8:46 PM Steve Dower  wrote:

> On 26Jul.2019 1909, Guido van Rossum wrote:
> > See the thread 'The trouble with "Easy" issues' in
> > [email protected] .
> > Essentially those "easy" issues aren't so easy, and we're starting over.
>
> Couldn't that be achieved just as easily by removing the "Easy" and
> "Easy (C)" tags from everything and coming up with a better definition?
>
> I agree they haven't been a great source of bugs for the sprints I've
> helped coordinate, but I don't think the problem is the label. But I
> assume the bikeshedding over the name has been done on the private list.


Hardly. But a new label is easier to set up, and doesn't erase any
information.

>
> Most of the trouble is there are many pending PRs that have not been
> merged, and so maybe 3/4 of the issues are not actually available. (My
> suspicion is that the delay in CLA handling is a significant factor
> here, as many PRs can't be merged during the sprint itself, and we're
> not so good at following up later.)
>
> (As an aside, the best first issue is usually the one the new
> contributor cares about most, regardless of difficulty. Finding
> something "suitable" for someone with no preferences or interests is
> never going to be easy.)


That's so true!

--Guido
-- 
--Guido (mobile)
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/VAEEHYOOSX7U4GMAPUWK4I5HEITYT5VR/