December 2015 - Tei-council

Build failed in Jenkins: TEIP5-Pure-ODD #5
by Victoria TEI Jenkins 08 Jan '16

08 Jan '16

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/5/changes> Changes: [lou.burnard] add draft spec for anyxml element ------------------------------------------ [...truncated 161 lines...] dpkg-source -i.svn -I.svn --after-build debian-tei-p5-database dpkg-buildpackage: binary only upload (no source included) BUILD: make Debian tei-p5-doc package (cd debian-tei-p5-doc; debclean;debuild -eXSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/../../../Stylesheet…> -eVCS=git -eINJENKINS=true --no-lintian -nc -b -i.svn -I.svn -uc -us) Cleaning in directory . dh_testdir dh_testroot rm -f build-stamp configure-stamp dh_clean dpkg-buildpackage -rfakeroot -D -us -uc -nc -b -i.svn -I.svn dpkg-buildpackage: source package tei-p5-doc dpkg-buildpackage: source version 2.9.2a dpkg-buildpackage: source distribution debian dpkg-buildpackage: source changed by TEI <editors(a)www.tei-c.org> dpkg-source -i.svn -I.svn --before-build debian-tei-p5-doc dpkg-buildpackage: host architecture amd64 debian/rules build dh_testdir touch configure-stamp dh_testdir touch build-stamp fakeroot debian/rules binary dh_testdir dh_testroot dh_installdirs install -d <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/debian-tei-p5-doc/d…> (cd ..; make VCS=git INJENKINS=true XSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/../../../Stylesheet…> PREFIX=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/debian-tei-p5-doc/d…> install-doc) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5'> BUILD: Make distribution directory for doc rm -rf release/tei-p5-doc* mkdir -p release/tei-p5-doc/share/doc/tei-p5-doc/en cp VERSION release/tei-p5-doc/share/doc/tei-p5-doc BUILD: Make web pages for release notes for i in ReleaseNotes/readme*xml; do \ ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -f <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/../../../Stylesheet…> -lib Utilities/lib/saxon9he.jar -Dprofiledir=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/../../../Stylesheet…> -Dprofile=readme \ -DinputFile=`pwd`/$i -DoutputFile=`pwd`/release/tei-p5-doc/share/doc/tei-p5-doc/`basename $i .xml`.html; \ done [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 10 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds BUILD: Make web guidelines in all supported languages make html-web ALLLANGUAGES="en es de ja ko fr it zh-TW" make[2]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5'> BUILD: Making HTML Guidelines for language en rm -rf Guidelines-web perl -p -e \ "s+http://www.tei-c.org/release/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/../../../Stylesheet…;> \ s+/usr/share/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/../../../Stylesheet…;"> \ Utilities/guidelines.xsl.model > Utilities/guidelines.xsl if [ -n ] ; then curl -s http://www.tei-c.org/index.xml | sed 's/content="text\/html"/content="text\/html; charset=utf-8"/' | xmllint --html --noent --dropdtd --xmlout - > Utilities/teic-index.xml;fi for i in en es de ja ko fr it zh-TW ;do \ mkdir -p Guidelines-web/$i/html; \ cp odd.css guidelines.css guidelines-print.css Guidelines-web/$i/html; \ (cd Source/Guidelines/en; tar --exclude .svn -c -f - Images) | (cd Guidelines-web/$i/html; tar xf - );\ (cd webnav; tar --exclude .svn -c -f - .) | (cd Guidelines-web/$i/html; tar xf - ); \ done echo '<project basedir="." default="html" name="buildweb"><import file="antbuildweb.xml"/><target name="html">' \ > buildweb.xml for i in en es de ja ko fr it zh-TW ;do \ echo "<buildweb lang=\"$i\"/>" >> buildweb.xml; \ done echo '</target></project>' >> buildweb.xml ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/jing.jar:Utilities/lib/saxon9he.jar -f buildweb.xml -DgoogleAnalytics= [echo] Make Guidelines web pages for language en [echo] Make Guidelines web pages for language es [echo] Make Guidelines web pages for language de [echo] Make Guidelines web pages for language ja [echo] Make Guidelines web pages for language ko [echo] Make Guidelines web pages for language fr [echo] Make Guidelines web pages for language it [echo] Make Guidelines web pages for language zh-TW BUILD SUCCESSFUL Total time: 9 minutes 13 seconds # commented out for DEBUGing: rm -f buildweb.xml Utilities/teic-index.xml touch html-web.stamp make[2]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5'> (cd Guidelines-web; tar --exclude .svn -c -f - . ) | (cd release/tei-p5-doc/share/doc/tei-p5-doc; tar xf - ) BUILD: make PDF version of Guidelines make pdf make[2]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5'> check if XeLaTeX exist /usr/bin/xelatex perl -p -e \ "s+http://www.tei-c.org/release/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/../../../Stylesheet…;> \ s+/usr/share/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/../../../Stylesheet…;"> \ Utilities/guidelines-latex.xsl > Utilities/guidelines.xsl BUILD: build Lite version of Guidelines, then LaTeX version of Guidelines from Lite, then run to PDF using XeLaTeX Make sure you have Junicode, Arphic and Mincho fonts installed ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/../../../Stylesheet…> -DXELATEX=xelatex pdfonce [echo] make LaTeX and PDF BUILD FAILED <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5/antbuilder.xml>:161: exec returned: 1 Total time: 2 minutes 15 seconds make[2]: *** [Guidelines.pdf] Error 1 make[2]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5'> make[1]: *** [dist-doc.stamp] Error 2 make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Pure-ODD/ws/P5'> make: *** [install] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 debuild: fatal error at line 1364: dpkg-buildpackage -rfakeroot -D -us -uc -nc -b -i.svn -I.svn failed make: *** [deb] Error 29 Build step 'Execute shell' marked build as failure Archiving artifacts

2 7

Build failed in Jenkins: Stylesheets (Pure ODD branch) #1
by Victoria TEI Jenkins 08 Jan '16

08 Jan '16

See <http://teijenkins.hcmc.uvic.ca/job/Stylesheets%20(Pure%20ODD%20branch)/1/> ------------------------------------------ Started by user Martin Holmes Building in workspace <http://teijenkins.hcmc.uvic.ca/job/Stylesheets%20(Pure%20ODD%20branch)/ws/> Cloning the remote Git repository Cloning repository https://github.com/TEIC/Stylesheets.git > git init <http://teijenkins.hcmc.uvic.ca/job/Stylesheets%20(Pure%20ODD%20branch)/ws/> # timeout=10 Fetching upstream changes from https://github.com/TEIC/Stylesheets.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/TEIC/Stylesheets.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://github.com/TEIC/Stylesheets.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/TEIC/Stylesheets.git # timeout=10 Fetching upstream changes from https://github.com/TEIC/Stylesheets.git > git -c core.askpass=true fetch --tags --progress https://github.com/TEIC/Stylesheets.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/pureodd^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/pureodd^{commit} # timeout=10 Checking out Revision b7ee9fa3d851dbd2ce3d560a1718b4aec40588f6 (refs/remotes/origin/pureodd) > git config core.sparsecheckout # timeout=10 > git checkout -f b7ee9fa3d851dbd2ce3d560a1718b4aec40588f6 First time build. Skipping changelog. > git tag -a -f -m Jenkins Build #1 jenkins-Stylesheets_(Pure_ODD_branch)-1 # timeout=10 [workspace] $ /bin/bash -xe /tmp/hudson3612594154646683956.sh + make clean test deb dist (for i in css/*; do rm -f `basename $i`;done) echo "" > test~ rm -f profile1.html profile2.html profile.xml find . -name "*~" | xargs rm rm -f tei-xsl-*.zip rm -rf tei-xsl_* rm -f Documentation/stylebear Documentation/style.xml Documentation/customize.xml Documentation/teixsl.html Documentation/index.xml rm -rf release dist (cd Test; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/Stylesheets%20(Pure%20ODD%20branch)/ws/T…'> (cd ..; for i in css/*; do rm -f `basename $i`;done) rm -f test*.odd.rnc test*epub test*pdf test*rdf test*text test*.xml.docx test*.xml.odt test*.tex test*.fo *.html *.xhtml *~ dummy* test.html test3.html test4.html *aux *vrb *out *log *nav *ent *snm *toc *.end *.1 *.2 test.xsd test.zip test*.dtd test-indexes.xml test37.xml test38.xml test39.xml test40.xml rm -f test*.rnc test*.json test*.rnc test*.combined.odd test*listing* test*.tei test*.rng test*.html5 test*.processedodd *.isosch rm -f oddbyexample.* index*div*html rm -f testdrama.compiled.xml rm -f test5.odt test7.xml test18.xml test19.xml test-index.xml test7.zip test11.xml test9.docx test9.odt content.xml.odt.listing content.xml.odt test.xml.docx.core test7.docx rm -f A54031.xml dcr.result test-rtf2tei.xml test29.xml rm -f xml.result rm -rf charts/ embeddings/ media/ _rels/ \[Content_Types\].xml rm -rf temp-dir-for-ant Pictures OEBPS META-INF mimetype files rm -f test.xlsx.xml *.result.tex *.result.pdf _slidelogo.png rm -f content.xml rm -f cocoatest*.xml make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/Stylesheets%20(Pure%20ODD%20branch)/ws/T…'> rm -rf tei-p5-xsl_* rm -rf tei-p5-xsl2_* (cd debian-tei-xsl/debian; rm -rf tei-xsl) rm -f teioo.jar rm -rf docx/ImageInfo/bin rm -f names.xml licensekey.txt runDoc.sh (for i in sciencejournal/*.html; do rm -f sciencejournal/`basename $i`;done) (for i in sciencejournal/*.xml; do rm -f sciencejournal/`basename $i`;done) BUILD Copy main XSL files test -d release/xsl/xml/tei/stylesheet || mkdir -p release/xsl/xml/tei/stylesheet/ for i in bibtex cocoa common csv docx dtd docbook epub epub3 fo html wordpress markdown html5 json latex latex nlm odd odds odt p4 pdf profiles/default rdf relaxng rnc schematron simple slides tbx tcp tite tools txt html xsd xlsx pdf verbatimxml ; do \ tar cf - $i | (cd release/xsl/xml/tei/stylesheet; tar xf - ); \ done java -jar lib/saxon9he.jar -it:main tools/getnames.xsl > names.xml BUILD Copy common files and documentation test -d release/xslcommon/xml/tei/stylesheet || mkdir -p release/xslcommon/xml/tei/stylesheet cp names.xml catalog.xml VERSION css/*.css i18n.xml release/xslcommon/xml/tei/stylesheet sh ./tools/mydch debian-tei-xsl/debian/changelog update debian changelog with 7.40.1 BUILD Run tests (cd Test; make) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/Stylesheets%20(Pure%20ODD%20branch)/ws/T…'> ../bin/teitorelaxng --odd test.odd test.rng Convert test.odd to <http://teijenkins.hcmc.uvic.ca/job/Stylesheets%20(Pure%20ODD%20branch)/ws/T…> (tei to relaxng) using profile default [echo] Do ODD expand processing (schema ) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 17 seconds perl -i -p -e 's/generated from ODD source.*//' test.rng xmllint --format test.rng > temp; mv temp test.rng perl -i -pe 'BEGIN{undef $/;} s/<!--\n ?Schema[^>]+>//smg' test.rng diff test.rng expected-results/test.rng (cd ..; for i in css/*; do test -f `basename $i` || ln -s $i `basename $i`;done) BUILD: testing html java -Djava.awt.headless=true -jar ../lib/saxon9he.jar test.xml ../html/html.xsl cssFile=../tei.css useFixedDate=true | xmllint --format - > test.html diff test.html expected-results/test.html 797d796 < make[1]: *** [test-to-html] Error 1 make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/Stylesheets%20(Pure%20ODD%20branch)/ws/T…'> make: *** [test] Error 2 Build step 'Execute shell' marked build as failure Archiving artifacts

1 9

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

and now...
by Lou Burnard 15 Dec '15

15 Dec '15

If we're reaching consensus on the meta-question of how issues should be labelled, could we now collectively consider at least some of the urgent outstanding issues themselves? In particular, I am still waiting for an explicit green light from at least one other council member who has successfully built using the lb42-pure-odd-2 branch? Martin set up a Jenkins job to do this, but it seems to have fallen over at the penultimate hurdle, and I don;'t know enough about Jenkins to see why. If we get that, then I could maybe issue a pull request (whatever that is) and get this stuff merged in... If we're looking for jobs for new council members to cut their teeth on, I'd be delighted to propose trying to build this branch! Much more fun than fixing a tedious bit of prose. I'd also appreciate some feedback on my ticket proposing a new anyXML element... L

5 13

Reorganizing labels on GitHub
by Raffaele Viglianti 14 Dec '15

14 Dec '15

Dear all, Elli and I spent some time this morning going through the labels on the TEI repository and discussed a new, simpler, system for organizing our tickets. Here is a spreadsheet with current labels and their proposed new name: https://docs.google.com/spreadsheets/d/1VhBYft_85F6x8J0YpGvqn-ZfIHbXqk9j8QV… We propose to have 4 higher level label categories: *component* or *tool*, *type*, *priority*, and *status. * When creating a new issue, one label from each category should be chosen. For example a new ticket about a badly misguiding example for the the "div" element would probably get these labels: "Component: Core schema" "Type: Bug" "Priority: High" "Status: Needs Discussion" There are a couple of extra labels that don't fit this system: - "sf-automigrated": identifies tickets migrated from SF. We suggest to keep it. - "SIG": identifies tickets about SIG organization (maybe we need a category for less technical discussions, "meta"?). 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". - "sf_creator-*" tickets were introduced to facilitate finding migrated tickets by their original SF creator. Since that information is also recorded in the text of the ticket, we think they should go away. Thoughts? Many thanks for your comments - after we make some decisions here, we will also check labels in the Spreadsheets repository and implement a similar system. Best, Raff

5 19

Building the PureODD branch
by Martin Holmes 13 Dec '15

13 Dec '15

Hi all (but mainly Lou and Hugh), I notice there's a pureodd branch for the Stylesheets. Should my Pure ODD P5 build on Jenkins be using that branch of the Stylesheets rather than the dev branch? Cheers, Martin

2 2

Pure ODD progress
by Lou Burnard 09 Dec '15

09 Dec '15

I am now at the stage of being able to generate web pages in the lb42-pureodd-2 branch. To get there, I have had to comment out of the makefile the two "EXTENDED" test files testp4compat.xsd and testi18n.xsd (the latter was already commented out in fact). Can anyone remember/reconstruct what these tests were intended to do? I am also now using Hugh's latest Stylesheets, so have some further comments to make on them: Firstly, what appears to be a bug: in the pureODD section, I see nothing at all inside the <content> element. e.g. in emph. This looks OK at http://teic.github.io/TEI/ref-emph.html but not in the version I have locally generated, so either the former is not up to date, or I have messed something up. Secondly, I still don't want to see class declarations inside that section Thirdly, I don't want to see element names clickable inside examples. This is not what we currently do; I find it distracting; and it's strictly speaking wrong, since example contents are not in the TEI namespace! :-) [this also doesn't happen in the github.io version]

4 13

anyone for @exclude ?
by Lou Burnard 08 Dec '15

08 Dec '15

Wandering the anyXML rabbit warren, I came upon a new side passage which may be worth considering. This is to define in pure ODD a new attribute @exclude on the <content element, the effect of which is to specify one or more elements which should be excluded from said content model. We could implement this in DTD land (if we still did DTDs) with an exclusion exception; in Relaxng of course it has to be a schematron rule. It would enable us to do two things we currently do rather obscurely (1) prevent <teix:egXML> from containing <teix:egXML> (2) prevent <s> from containing <s>. And there may well be others. Unless anyone can plausibly show that this is bonkers, I will create a ticket.

1 0

Contributors
by Hugh Cayless 07 Dec '15

07 Dec '15

Dear All, Thanks for the productive meeting earlier today. I’d said I wanted to broach the topic of keeping Contributors engaged over email, partly because it’s been a little contentious in the past and partly because I think it’s something that deserves more deliberation than we can give it in a single meeting. I’ll start by setting out how (as I understand it) things work now and then paint a picture of things as I’d like them to be. I mean the latter as something for you all to react to, so don’t hesitate to do so. I’d particularly like reactions from those of you who are new to Council. This is really going to be an ongoing conversation, I believe, and not something we can just fix. Martin has volunteered to be a champion for Contributors and I’m hoping that he and any other outgoing members who want to remain active participants will be vocal about what works and what doesn’t work for them. Council is a highly effective group that does a lot of good work, so we need to find a balance that doesn’t mess with our effectiveness and cohesiveness. The status quo: Engagement with TEI work happens via the TEI and Stylesheets repos on GitHub. Each of these has issue trackers, and there are two teams that have access to make changes to TEI, the Technical Council and "TEI Contributors". Incidentally, if the new folks will send me their github ids, I’ll add you to the Council team. The Tech Council team is for current Council members and the Contributors team is for a) former Council members who wish to remain active and b) anyone else we decide should have the ability to push directly to the TEI repo. This being GitHub, we can also take pull requests from people on neither team. Discussion of TEI stuff happens on this mailing list, on the issue trackers, in our monthly telecons, and in our Face to Face meeting. Only current Council members are on the mailing list, and people are removed as they cycle off Council. Only Council members attend the telecons and the F2F meetings, though occasionally "outside experts" are invited. Council tends to operate on consensus, though from time to time contentious issues are put to a vote. My ideal world: Contributors would be able to be as involved as they want to be in ongoing TEI development. That might include staying on or joining the mailing list, attending telecons, and even F2F meetings (though the TEI wouldn’t be able to pay for them unless they were formally invited of course). The main difference between Council Members and Contributors would be that the former have a vote when things come to a vote and would in general have more responsibility for development and maintenance. I feel that we don’t do enough to foster an active community of people who are TEI experts, and I think part of that is Council being a bit mysterious and exclusionary. It’s hard to get onto Council, especially if you’re not already part of a community of TEI users (so that you have name recognition in the elections) and people who leave have tended to just drift away (often leaving unfinished business). As I mentioned above, we’ve had a version of this discussion before, and I think mine was a minority view then, but I wanted to raise it again now to get the reactions of our incoming members and the perspectives of our outgoing members. What should we do? As you might have guessed, I have strong opinions, so I’m going to shut up for a while in the hope that a productive discussion develops without me driving it :-).

10 17

PDF and Pure ODD...
by Hugh Cayless 03 Dec '15

03 Dec '15

Tried this out, and decided to wait until we’ve got a version that’s current with the HEAD of dev. Right now it won’t build because of expired deprecated stuff that’s been fixed in the dev branch. Hugh

1 0

Telco this morning, right?
by Martin Holmes 03 Dec '15

03 Dec '15

According to my calendar, we have a telco in about 45 minutes. Is that right? Cheers, Martin

7 11

Agenda and Hangout
by Hugh Cayless 03 Dec '15

03 Dec '15

Hi all, Sorry for the delay. Moving offices is a headache. Agenda: https://docs.google.com/document/d/1f27Q0VLFN26oDNKgJ8hIXg97MF_9LeYavb1Wd9h… Hangout: https://talkgadget.google.com/hangouts/_/x3ri7iimwlh5ogr3t265zhe6n4a See you in 15 minutes!

1 0

LearnGit at Codecademy
by Raffaele Viglianti 02 Dec '15

02 Dec '15

Codecademy has just released a free interactive course for learning Git. Some council members may find it useful! It cleared some things up for me as well. (Also interesting how it has you write literature rather than code) https://www.codecademy.com/learn/learn-git Best, Raff

1 0