Define a set of Labels

[uliska]

The default Issue Labels that github offers aren't very suitable for our purpose which seems to differ from software development in this respect. So we should think about a set of Labels that seem to make sense for us.

• I added a todo Label, meant for smaller things that just have to be done and that aren't real "issues". The issue tracker then can be used to assign/track these task to specific people.
• Is duplicate really useful for LilyPond work (contrasting software development)?
• bug is too generic, I think. But as one can combine different Labels it should do.
• As for more fine-grained bug categories I suggest:
  • musicalcontent for anything relating to musical errors (like wrong notes, bad voice assignment etc.)
  • engraving for anything related to issues with LilyPond's output, i.e. things that have to be tweaked manually
  • Should these be represented by even more Labels or should one keep the number of Labels lower?
• Issue Labels can be relevant for different things:
  • musical input
  • problems with LilyPond's output
  • arrangement of the source tree as a whole

I think there are more useful Labels to find. For now we should agree upon a set, but stay free to add more in later stages of the project.

[jan-warchol]

I think we shouldn't add too many labels, unless we'd start a really huge project. For now going above 10 seems like too much for me.

Nevertheless, i think it would be good to add a regression label. And perhaps some label for library work (like "the arpeggios are too short, do something about it"), or developing functions ("there are loads of bad slurs of this kind, a special function to handle them would be nice").

[uliska]

OK, I updated the labels list to the following:

• bug / enhancement: To be used as a general category
• invalid: I suggest removing this one too. As we have a small project and especially we don't have contact with 'end-users' submitting reports we don't need it.
• documentation: In our project this somewhat specifically refers to the overall project description
• engraving: Anything related to necessary improvements to LilyPond's default
• generaldiscussion: As this project is about a general discussion/experiment I thought this would be good to have. But it could also be merged with documentation
• library: is probably a subset of engraving and refers to tweaks that should/could be pulled out of the music source to some kind of library. For example the need to write functions.
• musicalcontent: Anything related to actual music. Wrong notes, missing articulation, inappropriate voice distribution etc.
• projectstructure: the logical distribution of music/functions to variables and include files. I'm not completely sure if we need an explicit label for this. Maybe it can be merged with generaldiscussion
• regression: Anything that has become worse or is broken through new activities
• todo: Well, any issue is a 'todo'. But this label is useful to make the next steps/tasks explicit, keep track of them and assign them to specific collaborators.

BTW: Is there a way to manually sort the labels?

[jan-warchol]

On Mon, Jun 4, 2012 at 11:28 AM, uliska reply@reply.github.com wrote:

OK, I updated the labels list to the following:

• bug / enhancement: To be used as a general category

i don't think we need a label for that. General things don't get any label.

• invalid: I suggest removing this one too.

+1

• documentation: In our project this somewhat specifically refers to the overall project description
• engraving: Anything related to necessary improvements to LilyPond's default
• generaldiscussion: As this project is about a general discussion/experiment I thought this would be good to have. But it could also be merged with documentation
• library: is probably a subset of engraving and refers to tweaks that should/could be pulled out of the music source to some kind of library. For example the need to write functions.
• musicalcontent: Anything related to actual music. Wrong notes, missing articulation, inappropriate voice distribution etc.
• projectstructure: the logical distribution of music/functions to variables and include files. I'm not completely sure if we need an explicit label for this. Maybe it can be merged with generaldiscussion

probably.

• regression: Anything that has become worse or is broken through new activities
• todo: Well, any issue is a 'todo'. But this label is useful to make the next steps/tasks explicit, keep track of them and assign them to specific collaborators.

aren't milestones and assigning to collaborators independent from labelling? I think we don't need this one.

BTW: Is there a way to manually sort the labels?

I don't know any.

[colinghall]

I have to say that you guys seem to be going way over the top on this. It feels like you are inventing a huge project.

I'm happy to do some hacking around.

My main interest was to see how we could handle merge conflicts, because the rest of this is the same as any other software collaboration.

I must say that the tools provided by GitHub seem fantastic compared to what I used to use!

Cheers Colin.

[uliska]

;-) That may well be true. In fact we are in the middle of a rather huge project (100 pages of late romantic songs with very complex piano part). And all this is somewhat floating through our minds these days. So this project looks small to us but may look 'frightening' to others ...

And I have to admit that I see this as a first shot at some other projects. They will perhaps be huge and hopefully very profitable, for me and for LilyPond ;-)

So don't feel irritated, just do something ...

[colinghall]

On Wed, Jun 06, 2012 at 04:00:10PM -0700, uliska wrote:

;-) That may well be true.

In fact we are in the middle of a rather huge project (100 pages of late romantic songs with very complex piano part). And all this is somewhat floating through our minds these days. So this project looks small to us but may look 'frightening' to others ...

It's not "frightening", Urs, it's just that I thought we were doing a quick sprint of coding something up collaboratively.

Cheers, Colin.

Colin Hall

[jan-warchol]

On Thu, Jun 7, 2012 at 1:13 AM, colinghall reply@reply.github.com wrote:

On Wed, Jun 06, 2012 at 04:00:10PM -0700, uliska wrote:

In fact we are in the middle of a rather huge project (100 pages of late romantic songs with very complex piano part). And all this is somewhat floating through our minds these days. So this project looks small to us but may look 'frightening' to others ...

It's not "frightening", Urs, it's just that I thought we were doing a quick sprint of coding something up collaboratively.

I'm surprised at how this project turns out, too!

Janek