On 14/12/15 01:36, Raffaele Viglianti wrote:
What does "component" mean here? The "core" is the name of a TEI module, and <div> is actually not defined there but in textstructure, so I guess you mean "core schema" in some other sense. But what? And what about things that are proposals for new elements or modules? What component do they go in? Point taken. By core we mean "principal", "main", not the module. It is as opposed to any customization schema. We could say "Component: main schema" instead, or "Component: TEI all".
I think it is the 'Component' bit that people might find confusing. TEI all sounds like tei_all the general schema, will that cause confusion. I'm assuming what you mean is "The component this bug/fr is talking about is the main TEI scheme generally".
"Status: Needs Discussion" Is this the same as the old Red/Amber/Green ? If so, why change it? It is, and we changed these names during out F2F, in fact. I think they are clearer than Red/Amber/Green, but I'm also fine with keeping the old names.
I don't mind the rename, but would suggest we keep the colours associated with this (i.e. 'Needs Discussion' should be an amber coloured label, 'Blocked' should be red, 'Go' should be green, etc.) I believe this was your intention, I just thought I'd reiterate it.
- "SIG": identifies tickets about SIG organization (maybe we need a
category for less technical discussions, "meta"?). SIG is fine by me. "Meta" has a different signification for me: I'd expect it to label tickets which are about ODD for example.
SIG for any SIG related activities, including looking at proposals from a SIG.
Then we have a couple of specific questions for you:
- Should we keep labels specific to each chapter in the guidelines? (e.g. MS, ND, PH, etc). We think they should go away. But if we keep them we can get group them under "Component: Guidelines", e.g. "Component: Guidelines: MS".
Those labels were created during the run up to P5. They weren't used much then, and I don't think they're much use now. Nuke em. Agreed - Nuke'em.
By component we mean one of our points of focus for development; e.g. the Guidelines (prose issues, mostly), the "main" schema development (things that we'd fix in the ODD, mostly), tools (things that should be moved to the Stylesheet repo, or are related to some other tool we maintain). Thanks again for your comments - looking forward to more discussion. Best, Raff
Isn't that handled by having the different repositories? Re: sf_creator* Embed in prose, remove categories. Hope that helps, -James -- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford