[Python-Dev] "Good first issues" on the bug tracker

[Cheryl Sabella]

Hello!

Due to the upcoming sprints at PyCon, there will be issues marked in the
bug tracker as 'Good first issues'.  Please do *not* submit pull requests
for these as it is difficult to find suitable issues.

Instead of working on these issues, I'd like to propose a much more
difficult challenge to current contributors looking for something to work
on.  Please find issues which can be tackled at the sprint!  They are out
there, but the trick is finding them.  :-)

Here's the link to the mentored sprint page to understand the audience:
https://us.pycon.org/2019/hatchery/mentoredsprints/

I don't think this needs to be limited to documentation changes, but those
are the obvious choice (even the devguide suggests it).  The goal is really
workflow, meaning the new contributor doesn't necessarily have to solve the
problem themselves - if an issue says: x function in y module needs to have
z applied, then there's a lot of hurdles there for a newcomer which may not
involve solving the problem.

If you find anything you think is suitable, please add a comment with 'good
first issue' and nosy me or Mariatta on it.  If you're unsure, then nosy us
anyway.  It would be awesome to have too many issues to choose from than
not enough.  If an issue isn't worked on at the sprint, then it would still
be available to new contributors afterwards, so the exercise of flagging
the issues wouldn't be wasted effort.

Thanks!
Cheryl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20190221/f4821020/attachment.html>