labeling issues as easy-fix
Hi, At https://github.com/scipy/scipy/issues I've just added an easy-fix label, to guide newcomers to issues that don't require too much scipy background or hard debugging. I had planned to do that for a while, and the upcoming EuroSciPy sprint is a good motivation to get it done. Any help would be much appreciated. Maybe module maintainers could go through their module? Adding labels requires commit rights, but anyone without those who wants to help out can either just leave a comment on the ticket or send me the issue ID. Ralf
On 07/29/2013 09:13 PM, Ralf Gommers wrote:
Hi,
At https://github.com/scipy/scipy/issues I've just added an easy-fix label, to guide newcomers to issues that don't require too much scipy background or hard debugging. I had planned to do that for a while, and the upcoming EuroSciPy sprint is a good motivation to get it done.
Any help would be much appreciated. Maybe module maintainers could go through their module? Adding labels requires commit rights, but anyone without those who wants to help out can either just leave a comment on the ticket or send me the issue ID.
Ralf
As a newcomer myself, I think this is indeed highly valuable. First thing I did when wondering how could I contribute to SciPy was looking for some sort of easy-fix label - probably because I had already seen it in Astropy. Talking about maintainers, I just saw that each module's issues are linked in Trac. Is it desirable to replace the links with the new GitHub ones? Juan Luis
On Fri, Aug 2, 2013 at 2:38 PM, Juan Luis Cano <juanlu001@gmail.com> wrote:
On 07/29/2013 09:13 PM, Ralf Gommers wrote:
Hi,
At https://github.com/scipy/scipy/issues I've just added an easy-fix label, to guide newcomers to issues that don't require too much scipy background or hard debugging. I had planned to do that for a while, and the upcoming EuroSciPy sprint is a good motivation to get it done.
Any help would be much appreciated. Maybe module maintainers could go through their module? Adding labels requires commit rights, but anyone without those who wants to help out can either just leave a comment on the ticket or send me the issue ID.
Ralf
As a newcomer myself, I think this is indeed highly valuable. First thing I did when wondering how could I contribute to SciPy was looking for some sort of easy-fix label - probably because I had already seen it in Astropy.
Talking about maintainers, I just saw that each module's issues are linked in Trac. Is it desirable to replace the links with the new GitHub ones?
Yes, a PR for that would be great. Ralf
On 08/02/2013 02:52 PM, Ralf Gommers wrote:
Talking about maintainers, I just saw that each module's issues are linked in Trac. Is it desirable to replace the links with the new GitHub ones?
Yes, a PR for that would be great.
Ralf
Here it is! https://github.com/scipy/scipy/pull/2679
On a related note, do you need to have commit rights to label issues? Is there a way to allow the person who created the issue to label it? On Fri, Aug 2, 2013 at 10:30 AM, Juan Luis Cano <juanlu001@gmail.com> wrote:
On 08/02/2013 02:52 PM, Ralf Gommers wrote:
Talking about maintainers, I just saw that each module's issues are
linked in Trac. Is it desirable to replace the links with the new GitHub ones?
Yes, a PR for that would be great.
Ralf
Here it is!
https://github.com/scipy/scipy/pull/2679
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
On Sat, Aug 3, 2013 at 1:55 AM, Blake Griffith <blake.a.griffith@gmail.com>wrote:
On a related note, do you need to have commit rights to label issues? Is there a way to allow the person who created the issue to label it?
There isn't, and I think that's a feature not a limitation. It makes the labels more accurate and consistent. On Trac it was possible for users to set labels, and there it was common that issue submitters would set priorities and milestones (usually prio high and next release of course) which was unhelpful and had to be undone most of the time. On Github this would be worse, since it's not possible to see who labeled an issue. Ralf
On Fri, Aug 2, 2013 at 10:30 AM, Juan Luis Cano <juanlu001@gmail.com>wrote:
On 08/02/2013 02:52 PM, Ralf Gommers wrote:
Talking about maintainers, I just saw that each module's issues are
linked in Trac. Is it desirable to replace the links with the new GitHub ones?
Yes, a PR for that would be great.
Ralf
Here it is!
https://github.com/scipy/scipy/pull/2679
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
On 08/02/2013 05:30 PM, Juan Luis Cano wrote:
On 08/02/2013 02:52 PM, Ralf Gommers wrote:
Talking about maintainers, I just saw that each module's issues are linked in Trac. Is it desirable to replace the links with the new GitHub ones?
Yes, a PR for that would be great.
Ralf
Here it is!
I saw that these two links to RSS feeds: http://new.scipy.org/scipy-chatter.xml http://new.scipy.org/scipy-pull.xml are broken, and I could not locate any old version of those files digging into the repositories. These could be remade, and the RSS feeds for the individual modules could be replaced by ones using the GitHub API. The latter are easy, but I don't know exactly what the former contained.
On 08/03/2013 03:18 PM, Juan Luis Cano wrote:
I saw that these two links to RSS feeds:
http://new.scipy.org/scipy-chatter.xml http://new.scipy.org/scipy-pull.xml
are broken, and I could not locate any old version of those files digging into the repositories. These could be remade, and the RSS feeds for the individual modules could be replaced by ones using the GitHub API. The latter are easy, but I don't know exactly what the former contained.
Well, proof it was easy is that I already did it, being clueless: https://github.com/Juanlu001/scipy-feeds
participants (3)
-
Blake Griffith -
Juan Luis Cano -
Ralf Gommers