Yes, this will be a great task.
1. I agree with Jim that the Priority labels are pretty darn useless.
People will always solve issues they are comfortable with, *high priority*
or not.
2. Also, I am not too comfortable with the difficulty labels as they tend
to be subjective. What is
On Friday, April 17, 2015 at 8:17:56 AM UTC-5, Harsh Gupta wrote:
Great initiative, I suggest adding `needs decision` to the classifier tag.
It is for the issues for which we are not sure if they are valid or not.
`Needs Decision` already exists, and is a special (pink) tag. The reason
for
Great initiative, I suggest adding `needs decision` to the classifier tag.
It is for the issues for which we are not sure if they are valid or not.
--
Harsh
--
You received this message because you are subscribed to the Google Groups
sympy group.
To unsubscribe from this group and stop
Am 17.04.2015 um 07:40 schrieb James Crist:
- Brief discussion on labeling system.
Actually I think what you're proposing is fine.
If it's found lacking, we can easily fix it.
- Help labeling.
I haven't found a way to enable tagging for people that do not have full
write access to the
Also maybe a small gripe about organizing by submodule.
I did this because this seemed to be the easiest way to ensure that like
issues were grouped together, in a way with consistent naming. There were
`integration` and `Integration` labels before, as well as many tags for
things that were
Glad to see you taking this on. Quite a few issues are either
duplicate or already fixed, so there is definitely some cleanup
possible.
On Fri, Apr 17, 2015 at 12:40 AM, James Crist crist...@umn.edu wrote:
As of this writing, SymPy has 1648 issues open. That's more than numpy,
scipy, or pandas
Also maybe a small gripe about organizing by submodule. Evalf labeled
issues don't have to be something that is happening in the core (you
renamed it to core.evalf). I also like to encourage creating issues
for things that come up a lot, even if they aren't submodules (the
Noncommutative label is
On Friday, April 17, 2015 at 1:34:55 PM UTC-5, Joachim Durchholz wrote:
- Help labeling.
I haven't found a way to enable tagging for people that do not have full
write access to the repository. I suspect GitHub does not offer any.
This is also the reason why tagging does not happen very
That's at least a little nicer. How about the following for status tags:
- Needs Decision : community hasn't decided how to handle this
- Needs Work : PR needs work to meet standards
- Needs Review : PR needs review by someone before being merged
Seems to cover all the bases, but I'm still not
Hi,
`Needs better patch`: could be useful to indicate PR status to devs, but
mostly I feel that it comes off as rude to the person making the PR. I'd
like to remove it unless someone makes a strong argument to the contrary.
Perhaps, we can reword it. How about Needs changes or Waiting
One thing I saw proposed elsewhere is to group labels, by naming them
group:label.
Am 17.04.2015 um 07:40 schrieb James Crist:
*Submodule tags (html #FF, blue):*
Everything after `sympy.` for the specific submodule. Keep the naming and
casing consistent with the sympy namespace. If the
That's just a name change for each label (one-to-one correspondance with
existing labels), which can be done easily later. I'm just going to keep
doing what I've been doing, and if we want to change the names later we can.
- Jim
On Fri, Apr 17, 2015 at 2:47 PM, Joachim Durchholz
Don't the colors already serve to group the labels?
Jason
moorepants.info
+01 530-601-9791
On Fri, Apr 17, 2015 at 2:11 PM, James Crist crist...@umn.edu wrote:
That's just a name change for each label (one-to-one correspondance with
existing labels), which can be done easily later. I'm just
On Fri, Apr 17, 2015 at 2:05 PM, James Crist crist...@umn.edu wrote:
On Friday, April 17, 2015 at 1:34:55 PM UTC-5, Joachim Durchholz wrote:
- Help labeling.
I haven't found a way to enable tagging for people that do not have full
write access to the repository. I suspect GitHub does not
On Fri, Apr 17, 2015 at 11:13 AM, Aaron Meurer asmeu...@gmail.com wrote:
Glad to see you taking this on. Quite a few issues are either
duplicate or already fixed, so there is definitely some cleanup
possible.
On Fri, Apr 17, 2015 at 12:40 AM, James Crist crist...@umn.edu wrote:
As of this
Also, did you kill the Alternate Python label? That was useful.
Aaron Meurer
On Fri, Apr 17, 2015 at 11:19 AM, Aaron Meurer asmeu...@gmail.com wrote:
Also maybe a small gripe about organizing by submodule. Evalf labeled
issues don't have to be something that is happening in the core (you
On Fri, Apr 17, 2015 at 11:33 AM, James Crist crist...@umn.edu wrote:
Also maybe a small gripe about organizing by submodule.
I did this because this seemed to be the easiest way to ensure that like
issues were grouped together, in a way with consistent naming. There were
`integration` and
Do people still use this?
Many recent beginner PRs have been tagged with it. If no one is attached,
I'd like to remove it.
- Jim
On Fri, Apr 17, 2015 at 6:28 PM, Aaron Meurer asmeu...@gmail.com wrote:
On Fri, Apr 17, 2015 at 2:05 PM, James Crist crist...@umn.edu wrote:
On Friday, April 17,
18 matches
Mail list logo
