Re: Fwd: Manipulating instrument names and staff group names

[Jonas Hahnfeld]

Am Sonntag, dem 07.11.2021 um 11:07 -0500 schrieb Kieren MacMillan:
> > > 2. Is there a tag/label on GitLab which identifies all and only
> > > those issues which don’t (or at least shouldn’t likely) require
> > > any C++ work?
> > 
> > There isn't. We had Frog in the past (good for beginners,
> > not language-specific), but it was practically unused and
> > the issues tagged were not actually so easy. Feel free to
> > propose something on the devel list though.
> 
> My goal is to be able to search the issues by language(s) required
> [i.e., filter out anything that requires more than Scheme], sort the
> list by difficulty [ascending], and start hacking away from the top.
> In order to do this, I imagine we’d need tags/labels for both
> “language(s)” and “difficulty”. I don’t want to clutter up the
> label-space… but I offer that adding something would help beginners
> like me to feel comfortable jumping in.
> 
> 1. “Language(s)”. While I would love it to be one tag per language
> involved (C++, Scheme, Python) — which would allow really granular
> searching/filtering — that might be overkill for everyone else. Maybe
> just one tag (e.g., “Scripting”) for things that don’t require recompilation?

We have the "Scripts" label that should group everything related to the
Python scripts, plus some more specific labels for ABC2ly, MIDI2ly, and
MusicXML. Likewise "Defect" is for problems within the "core program",
which means either C++ or Scheme. I would argue that those two are not
really separable in most cases, so I don't think a new label is a good
fit here.

> 2. “Difficulty”. Any multi-level (and thus multi-tag) system would be
> fine, as long as it’s at least three levels (e.g., Easy, Medium, Hard);
> optimal would be, say, a scale from 1 to 10 (e.g., Difficulty-1, 
> Difficulty-2, etc.).

As Jean already pointed out, assigning a difficulty is difficult
without having a very close look at the issue at hand. For example, a
small issue requiring only one changed line can at first seem very
similar to a problem that turns out to be related to the entire design
of LilyPond and is actually much harder to solve.

Jonas

signature.asc
Description: This is a digitally signed message part