Ezio and Nick,
Thanks for the feedback on the tracker. A couple of more thoughts on
"personal tags" which hopefully will clarify and save work and time.
FWIW, I believe the data to determine easily the state of an issue, the
next action required on the issue, and if the issue is free to work on
are most important to a new contributor.
A simple "star/favorite" issue toggle was really the extent of what I
was thinking would have been helpful.
For folks with greater Roundup-fu than me: how hard does the "personal tags"
idea sound? Alternatively, the front end could be more like a personal set
of "issue lists".
"a way to easily tag issues to return to as
promising possibilities", then a star/favorite feature might cover
case 2) and solve the issue, and even if it's not as fine grained as
a full personal tags system, it should be simpler to implement.
Ezio's links to his experiments with alternate displays of information
reminded me of something that I thought about when searching for a
suitable new contributor issue.
http://wolfprojects.altervista.org/patches.html (requires js)
When I was looking for an issue to work on, I tried a number of search
criteria (easy, new, documentation, testing). It's possible that my
"search"-fu is lacking, yet I had a difficult time identifying a "bite
sized" issue related to documentation, testing, or development in either
C or Python that didn't appear to be actively worked on or very old. I
suspect there were a number of suitable issues yet it felt like
searching for a needle in a very large haystack.
At the time I wondered if it just wouldn't be easier to grab the entire
"csv" file of issues and use ipython notebook with numpy/pandas to run
interactive searches for issues. Instead, I wound up just randomly
reading issues from the tracker which was why a "star/tag" would have
been helpful.
In hindsight, I suspect if I used the entire csv file with appropriate
search criteria in numpy/pandas that I would have greatly simplified my
search for an issue. I may do this now so I can see if I can find search
criteria that would be useful for new contributors to identify suitable
issues for:
* documentation
* increasing test coverage[pulling from the coverage site]
* triaging[identifying specific tasks that someone without developer
status can do to add value]).
Thanks,
Carol
--
Carol Willing
Developer
Willing Consulting
_______________________________________________
core-workflow mailing list
core-workflow@python.org
https://mail.python.org/mailman/listinfo/core-workflow
This list is governed by the PSF Code of Conduct:
https://www.python.org/psf/codeofconduct
