- Tei-council - lists.tei-c.org

adding @source to att.global.responsibility
by James Cummings 05 Jan '16

05 Jan '16

Hi Council, As you'll remember from issue 536 I'm tasked with adding @source to att.global.responsibility and am preparing to do so (even though I voted against this madness). I'm presuming I should wait until Pure ODD is settled in 'dev' before branching off that. I've added a comment to the issue at https://github.com/TEIC/TEI/issues/536#issuecomment-168669886 where I list all the things I think need to do to implement this but since it is a significant change I thought people might want to look at it before I start breaking things (and this will break things) and let me know if there are major things I'm forgetting in my todo list on the ticket? Mostly the problem isn't in adding a @source attribute to att.global.responsibility (that is straightforward) it is in removing all the existing uses of source for example in att.readFrom and att.source. The latter has members that are classes (att.editLike, att.interpLike, att.textCritical, as well as abbr abstract egXML handShift note orig provenance q quote respons rs seg sic space witDetail writing). The adding of @source to new elements is an example in customising ODDs, and discussions of quotations, etc. wherever it is in a specList this needs to change from att.source to att.global.responsibility, etc. Many thanks, -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

2 1

do we have git doc yet?
by Syd Bauman 03 Jan '16

03 Jan '16

I can never figure out how to do this, and my local GitAlmostExpert is not around. I want to muck with the GLs in a new branch. So I want to make a new branch called 'sydb-WHATEVER'. It should track a branch of the same name in GitHub (in remotes/origin/, I guess, but I'm not sure that's the right nomenclature). I want to create it on my own commandline locally, check it out, make same changes checking in as needed, and then when done for the day push it up to GitHub so I can check fetch it and then check it out and work some more when I get home. Pretty reasonable request, IMHO. But I don't want to have to go to the GitHub website to do this. I just want to type at my coammandline. Do we have doc on how to do this already, and I've just missed it? If not, anyone want to tell me what the BLEEP to type? (I can give you a sizable list of `git branch` commands that *don't* do what I want. :-) Thanks.

2 2

Pure ODD Stylesheets progress
by Hugh Cayless 31 Dec '15

31 Dec '15

I think I’ve fixed DTD creation—I can build valid exemplar DTDs anyway. The Stylesheets tests are now foundering on a new reef: ODD by Example. Possibly not surprising that would be broken… Still, progress has been made.

2 3

Scheduling
by Hugh Cayless 30 Dec '15

30 Dec '15

Hello All, I have three scheduling items for your consideration: January telecon: http://doodle.com/poll/h9c4wu85pqqvbcbe If we can, I’d like to schedule a regular monthly day / time for our meetings, say the third or fourth week of every month. To that end, please give me an idea of what days/times are *in general* possible or impossible for you this upcoming semester and beyond: http://doodle.com/poll/d3nyte4wuiiqt9r4 Spring F2F: http://doodle.com/poll/cd9n3d47e5ezfkit I’ve put together a set of options between mid-April and mid-May. How do people feel about working weekends? I’d prefer weekdays as a general rule, but I can compromise if need be. The current poll includes some Saturday dates, but not Sundays. We can change that of course if you need different dates. We can move earlier or later if need be. Scheduling these is usually a pain, and usually requires a couple of iterations. I hope you’ve all been enjoying whatever holidays you celebrate (or just some well-earned time off work) and I wish you a happy new year! Hugh

5 8

Roma documentation
by Martin Holmes 29 Dec '15

29 Dec '15

I've created a TCW here: <http://www.tei-c.org/Activities/Council/Working/tcw29.xml> explaining how Roma is deployed on tei-c, and how to deploy a new version. If you believe this is the wrong place for this information, feel free to move it to wherever it belongs. Cheers, Martin

1 0

Where should we document Roma configuration?
by Martin Holmes 28 Dec '15

28 Dec '15

HI all, Today the Roma install got updated to 4.18, which includes the bugfix I added for quotation marks in titles. That's a minor thing, but in the process, over the last couple of months, Ian Rifkin and I have been working out a setup which enables us to deploy and test new versions on tei-c without needing his intervention, and enables us to get him to switch from an old to a new version when we're ready just by changing a pointer. This all needs documenting, but the question is where should it go? It has slightly gnarly stuff like Apache rewrite rules and tei-c.org filesystem paths, so I'm not sure whether it belongs on the wiki, or in a TCW, or somewhere slightly more private. I think probably a TCW, but I thought I should check first. What do you think? Cheers, Martin

2 3

Oxgarage is out of date
by Martin Holmes 21 Dec '15

21 Dec '15

Hi all, If you convert an ODD file to a RelaxNG schema using OxGarage right now, you'll see this at the top of your file:  OxGarage hasn't been updated to use 2.9.1. I don't know what's actually involved here; perhaps OxGarage uses the P5 and Stylesheets versions from the debs, and the server hasn't been updated since 2.9.1 was released. Does anyone know how this works? Cheers, Martin

6 13

TEI Templates missing from Oxygen?
by Martin Holmes 20 Dec '15

20 Dec '15

Hi all, I just updated my Oxygen to the latest release, and I can't see any TEI P5 templates other than the JTEI template. This is an install which doesn't have the bleeding-edge version of the plugin installed. In the Framework folder I see all the relevant files, but I don't see anything other than JTEI when I go to File / New / Framework Templates. Can anyone else who's got the latest Oxygen check what you see? Thanks, Martin

3 3

GitHub Labels re-organized
by Raffaele Viglianti 18 Dec '15

18 Dec '15

Deal all, As promised at the F2F, Elli and I have re-organized the GitHub labels before the year end. You can see the current labels here: https://github.com/TEIC/TEI/labels Thank you for your feedback earlier this week - we took it into account, but made some executive decisions. None of this is set in stone, however, as changing and adjusting the labels is easy. Let's give this setup a test drive and see how it works for us. I've also gone through the issues that are currently open and made sure they all have at least one label for *Status:**, *TEI:** or *Tool*:*, and *Type:**. Best, Raff

1 0

Git question
by James Cummings 18 Dec '15

18 Dec '15

Hiya, Is there a way to copy the changes I've made on one branch to another? Or move one branch (off another branch) to be tracking a different branch instead? (e.g. I made the 'processing-model' branch off of Lou's original lb42-pureodd branch and I want to move it to his current one.) Suggestions? Or do I have to go do all the changes again? -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

4 18