Re: [tei-council] Reorganizing labels on GitHub

Well, sorry Raff, but I disagree. Every change to TEI P5 potentially affects both the schema and the Guidelines prose, and I think separating out these two aspects would just encourage us to fix one but not the other. But I do agree that "enforcing this would be crazy"! On 14/12/15 15:40, Raffaele Viglianti wrote:

On Mon, Dec 14, 2015 at 10:30 AM, Lou Burnard wrote:

...

On 14/12/15 13:30, James Cummings wrote:

...

On 14/12/15 13:07, Raffaele Viglianti wrote:

...

That is what we meant. What would be a good short label for this?

What about Component: TEI Guidelines vs Component: TEI Schema?

Except that any issue affecting the "TEI schema" (whatever that is) ought ipso facto to be affecting the TEI Guidelines prose (tho admittedly not necessarily vice versa)! When we e.g. add a new element, which is that? Or is it both i.e. two issues? I can see the advantage of distinguishing issues that relate purely to P5 from those that relate to (say) bugs in Roma, but I don't see the advantage of distinguishing aspects of P5.

I agree that issues affecting the TEI schema and the TEI Guidelines are often related, but that doesn't mean that they'll always be in the same ticket. As you said there are Guidelines issues that do not effect the schema, and I'd say that the opposite is true as well: it happens that the Guidelines say something and the schema doesn't do it (because of an oversight).

I would also argue for creating two tickets when a change in both the schema and the guidelines is required. It is two different actions (even when strictly related) and may very well be done in two commits. Now, enforcing this would be crazy, but it makes perfect sense to just stick both labels to one issue when this happens. And I'd say that this would not happen very often, but if facts will prove me wrong, we can always merge the two labels into one later on.

...

...

...

Isn't that handled by having the different repositories?

Only the stylesheets, but not other "tools" like Jenkins and Roma. I'd still keep a label for Stylesheets as a signifier that the issue should be moved.

Agreed that this is useful.

...

Then I'd say something just like the name of the repository it should be moved to.

Oh, and there is a Roma repository (and maybe there should be a jenkins one?)

Agree with Jas here.

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived