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

Next IG meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 03 Sep '19

03 Sep '19

Dear all, Thanks for filling in the doodle! Our next meeting will take place on September 3rd, 11:00-12:00 PST, 14:00-15:00 EST, 20:00-21:00 CEST. I will send a hangouts link half an hour before we start. Best wishes, Martina

2 3

Re: [Tei-council] let's talk about food
by James Cummings 03 Sep '19

03 Sep '19

I believe invited experts are invited and thus earn any meals through their participation. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Martin Holmes <mholmes(a)uvic.ca> Sent: Monday, September 2, 2019 10:28:08 PM To: tei-council(a)lists.tei-c.org <tei-council(a)lists.tei-c.org> Subject: Re: [Tei-council] let's talk about food I eat everything (although I'm not sure whether I'm entitled to any food since I'm not elected :-)). Cheers, Martin On 2019-09-02 2:24 p.m., James Cummings wrote: > Hi Martina, > > No pertinent allergies. And I eat most things, those which I don't like > rarely seem to come up in Styrian cuisine. > > Many thanks, > James > > -- > Dr James Cummings, James.Cummings(a)newcastle.ac.uk > School of English Literature, Language, and Linguistics, Newcastle > University > > ------------------------------------------------------------------------ > *From:* Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of > Scholger, Martina (martina.scholger(a)uni-graz.at) > <martina.scholger(a)uni-graz.at> > *Sent:* Monday, September 2, 2019 9:34:06 PM > *To:* TEI Council <tei-council(a)lists.tei-c.org> > *Subject:* [Tei-council] let's talk about food > > Dear all, > > Planning ahead for our F2F meeting, I wanted to ask about your dietary > requirements. Please let me know if you have any restrictions or allergies. > > Best, > > Martina > > > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council > _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

3 2

Re: [Tei-council] let's talk about food
by James Cummings 02 Sep '19

02 Sep '19

Hi Martina, No pertinent allergies. And I eat most things, those which I don't like rarely seem to come up in Styrian cuisine. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: Monday, September 2, 2019 9:34:06 PM To: TEI Council <tei-council(a)lists.tei-c.org> Subject: [Tei-council] let's talk about food Dear all, Planning ahead for our F2F meeting, I wanted to ask about your dietary requirements. Please let me know if you have any restrictions or allergies. Best, Martina

2 1

let's talk about food
by Scholger, Martina (martina.scholger＠uni-graz.at) 02 Sep '19

02 Sep '19

Dear all, Planning ahead for our F2F meeting, I wanted to ask about your dietary requirements. Please let me know if you have any restrictions or allergies. Best, Martina

1 0

Re: [Tei-council] Issue 1908
by James Cummings 19 Aug '19

19 Aug '19

Yes, the real difference is that for teidata.enumerated then you should have a valList in your ODD enumerating the specific values for your project. Indeed... if we wanted to add checks into an ODD editor like Roma, one could have it check through all classes and elements included in the ODD and find any attributes with teidata.enumerated and check that they have a valList, and if not prompt a user to enter one. That would, however, be quite strict, so maybe only in a future checker 'strict' mode (otherwise just a warning). ;-) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Raffaele Viglianti <raffaeleviglianti(a)gmail.com> Sent: 19 August 2019 19:38 To: James Cummings <James.Cummings(a)newcastle.ac.uk> Cc: tei-council(a)lists.tei-c.org <tei-council(a)lists.tei-c.org> Subject: Re: [Tei-council] Issue 1908 Sounds fine to me. It looks like teidata.enumerated is just a wrapper for teidata.word anyway...? Raff On Mon, Aug 19, 2019 at 2:20 PM James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>> wrote: https://github.com/TEIC/TEI/issues/1908 https://jenkins.tei-c.org/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/rel… Although I fixed the corrigible error for this ticket 25 days ago (within minutes of it being submitted ;-)) I noticed that the datatype for the @role attribute on <org> is teidata.word. For another issue I was looking at the @role attribute usage in other places and it is usually teidata.enumerated and that would make sense with this attribute as well. Any objections if I modified tei:org/@role to be teidata.enumerated instead of teidata.word? (This has no backwards compatibility issues as far as I'm aware, but means that a project _should_ document this list of possible values... which is a good thing.) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

Issue 1908
by James Cummings 19 Aug '19

19 Aug '19

https://github.com/TEIC/TEI/issues/1908 https://jenkins.tei-c.org/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/rel… Although I fixed the corrigible error for this ticket 25 days ago (within minutes of it being submitted ;-)) I noticed that the datatype for the @role attribute on <org> is teidata.word. For another issue I was looking at the @role attribute usage in other places and it is usually teidata.enumerated and that would make sense with this attribute as well. Any objections if I modified tei:org/@role to be teidata.enumerated instead of teidata.word? (This has no backwards compatibility issues as far as I'm aware, but means that a project _should_ document this list of possible values... which is a good thing.) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University

3 2

Call in 20 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 Aug '19

19 Aug '19

Dear all, our call starts in 20 minutes: https://docs.google.com/document/d/1SwwoO1XHVGIvRsSOKov3fzz9qkhFnUg80BWrU_k… Best, Martina

2 1

Stylesheets meeting in just over 4 hours
by Syd Bauman 16 Aug '19

16 Aug '19

We're planning to meet at 20:00Z (13:00 PDT, 16:00 EDT, 21:00 BST, 22:00 CEST). Main topic of discussion will be ticket 370. Google Hangouts, I presume, but feel free to tell me to use Skype or Google Whatever instead.

3 4

Build failed in Jenkins: Stylesheets-dev #1
by mholmes＠uvic.ca 15 Aug '19

15 Aug '19

See <https://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/1/display/redirect> Changes: ------------------------------------------ Started by an SCM change Running as SYSTEM Building in workspace <https://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/> No credentials specified Cloning the remote Git repository Cloning repository https://github.com/TEIC/Stylesheets.git > git init <https://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/> # timeout=10 Fetching upstream changes from https://github.com/TEIC/Stylesheets.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/TEIC/Stylesheets.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > 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 fetch --tags --progress https://github.com/TEIC/Stylesheets.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse refs/remotes/origin/dev^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/dev^{commit} # timeout=10 Checking out Revision e2d67981faa8d51f3c6a4c529d73783d9c01fd1c (refs/remotes/origin/dev) > git config core.sparsecheckout # timeout=10 > git checkout -f e2d67981faa8d51f3c6a4c529d73783d9c01fd1c # timeout=10 Commit message: "incrementing post-release version 7.48.0a" First time build. Skipping changelog. > git tag -a -f -m Jenkins Build #1 jenkins-Stylesheets-dev-1 # timeout=10 FATAL: Could not apply tag jenkins-Stylesheets-dev-1 hudson.plugins.git.GitException: Command "git tag -a -f -m Jenkins Build #1 jenkins-Stylesheets-dev-1" returned status code 128: stdout: stderr: *** Please tell me who you are. Run git config --global user.email "you(a)example.com" git config --global user.name "Your Name" to set your account's default identity. Omit --global to set the identity only in this repository. fatal: unable to auto-detect email address (got 'jenkins(a)teijenkins.(none)') at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2248) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2244) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1777) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1789) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.tag(CliGitAPIImpl.java:1658) Caused: hudson.plugins.git.GitException: Could not apply tag jenkins-Stylesheets-dev-1 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.tag(CliGitAPIImpl.java:1660) at hudson.plugins.git.GitAPI.tag(GitAPI.java:274) at hudson.plugins.git.extensions.impl.PerBuildTag.onCheckoutCompleted(PerBuildTag.java:30) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1256) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Archiving artifacts

1 1

Next call: Monday, August 19
by Scholger, Martina (martina.scholger＠uni-graz.at) 13 Aug '19

13 Aug '19

Dear all, Our next meeting is on Monday, August 19 (EDT 9:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30). This is the agenda - please add topics: https://docs.google.com/document/d/1SwwoO1XHVGIvRsSOKov3fzz9qkhFnUg80BWrU_k… Hugh, could you please start the call? If you have time, please have a look at the open tickets from the Washington meeting (see table in the agenda). Best, Martina

1 0

Next IG meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Aug '19

06 Aug '19

Dear all, Here is a reminder for the Doodle for our next Infrastructure Group meeting: https://doodle.com/poll/rxxdrnkkmd9ywdbg. I added the first week of September to increase our chance to meet. Best, Martina

1 0

Re: [Tei-council] Enable CORS on the TEI Vault
by Raffaele Viglianti 28 Jul '19

28 Jul '19

Thanks Luis, I'm glad you were able to figure something out! I just tested and it all seems to be working. All the best, Raff On Fri, Jul 26, 2019 at 4:05 PM Luis Meneses <ldmm(a)uvic.ca> wrote: > Hi Raff, > > I found a way to enable it without impacting security. > You should be good to go. > > Cheers, > ----- > -Luis > > On Jul 26, 2019, at 11:54 AM, Raffaele Viglianti < > raffaeleviglianti(a)gmail.com> wrote: > > Hi Luis, > > Any more thoughts on this? (Or from other council members?) For the time > being I'm switching to https://vault.tei-c.de which enables CORS for all > domains. > > Raff > > On Wed, Jul 24, 2019 at 1:28 PM Raffaele Viglianti < > raffaeleviglianti(a)gmail.com> wrote: > >> Hi Luis, >> >> Looping in the council list again. >> >> Why does it sound like a bad idea? What are your concerns and how could >> we address them while allowing full access to static data? >> >> One way could be making sure the header is only added to the /Vault >> location in Apache or Nginx. >> >> Raff >> >> >> On Wed, Jul 24, 2019, 1:06 PM Luis Meneses <ldmm(a)uvic.ca> wrote: >> >>> Hi Raff, >>> >>> Enabling CORS for all sites does sound like a bad idea. >>> I can set a rule to allow it for some sites, but now all of them. >>> >>> Is this something that we can try to do? >>> >>> Best, >>> ----- >>> -Luis >>> >>> On Jul 24, 2019, at 7:10 AM, Raffaele Viglianti < >>> raffaeleviglianti(a)gmail.com> wrote: >>> >>> Hi Luis, >>> >>> We had CORS allowed from all domains before and the Council saw that as >>> a good idea. We should make it as simple as possible to obtain static files >>> from the Vault. I don't believe this will expose the server to any new >>> forms of attacks because this would simply allow GET requests of static >>> files from a browser JavaScript source. Since any other system can already >>> send unlimited requests of this type, limiting JavaScript does not make the >>> server more secure. In other words, the JavaScript won't be interacting >>> with an API, but simply GETting static files, so there shouldn't be any >>> risk involved in turning CORS on. >>> >>> Thanks, >>> Raff >>> >>> On Tue, Jul 23, 2019 at 6:45 PM Luis Meneses <ldmm(a)uvic.ca> wrote: >>> >>>> Hi Raff, >>>> >>>> Would it be sufficient to allow requests from a smaller set of domains? >>>> >>>> For example: roma2.tei-c.org where the Roma tool lives? >>>> >>>> Making the other change can introduce some new attack vectors for the >>>> site. >>>> >>>> Best, >>>> ----- >>>> -Luis >>>> >>>> On Jul 22, 2019, at 6:28 AM, Raffaele Viglianti < >>>> raffaeleviglianti(a)gmail.com> wrote: >>>> >>>> Hi Luis, >>>> >>>> Thanks for the quick reply! The idea is that the server that serves the >>>> data from tei-c.org/Vault needs to add the Access-Control-Allow-Origin >>>> to the response so that browsers know they're allowed to grab data from >>>> different domains. If the server is Apache, it should enough to add the >>>> line below to <VirtualHost> or <Location> (depending on the set up) >>>> >>>> Header set Access-Control-Allow-Origin "*" >>>> >>>> If the server is nginx, you should add this under the right location >>>> stanza; >>>> >>>> add_header 'Access-Control-Allow-Origin' '*'; >>>> >>>> Let me know if I can help further, and thanks! >>>> Raff >>>> >>>> >>>> On Sun, Jul 21, 2019 at 10:12 PM Luis Meneses <ldmm(a)uvic.ca> wrote: >>>> >>>>> Hi Raff, >>>>> >>>>> Sorry to hear about that you have an issue. >>>>> Can you give me more details on it? >>>>> >>>>> I am just not too sure about what I need to do to fix it. >>>>> >>>>> Best, >>>>> -Luis >>>>> >>>>> >>>>> On Jul 21, 2019, at 1:02 PM, Raffaele Viglianti < >>>>> raffaeleviglianti(a)gmail.com> wrote: >>>>> >>>>> Dear Luis, >>>>> >>>>> Sorry to add even more to your plate, but could you enable CORS on the >>>>> TEI Vault? The new version of Roma written in JavaScript needs it to access >>>>> ODD customizations and p5subet. Example: fetch >>>>> https://tei-c.org/Vault/P5/current/xml/tei/odd/p5subset.json >>>>> The response needs to contain the header >>>>> Access-Control-Allow-Origin: * >>>>> >>>>> Thanks! >>>>> Raff >>>>> >>>>> >>>>> >>>> >>> >

1 0

Re: [Tei-council] Enable CORS on the TEI Vault
by Raffaele Viglianti 27 Jul '19

27 Jul '19

Hi Luis, Looping in the council list again. Why does it sound like a bad idea? What are your concerns and how could we address them while allowing full access to static data? One way could be making sure the header is only added to the /Vault location in Apache or Nginx. Raff On Wed, Jul 24, 2019, 1:06 PM Luis Meneses <ldmm(a)uvic.ca> wrote: > Hi Raff, > > Enabling CORS for all sites does sound like a bad idea. > I can set a rule to allow it for some sites, but now all of them. > > Is this something that we can try to do? > > Best, > ----- > -Luis > > On Jul 24, 2019, at 7:10 AM, Raffaele Viglianti < > raffaeleviglianti(a)gmail.com> wrote: > > Hi Luis, > > We had CORS allowed from all domains before and the Council saw that as a > good idea. We should make it as simple as possible to obtain static files > from the Vault. I don't believe this will expose the server to any new > forms of attacks because this would simply allow GET requests of static > files from a browser JavaScript source. Since any other system can already > send unlimited requests of this type, limiting JavaScript does not make the > server more secure. In other words, the JavaScript won't be interacting > with an API, but simply GETting static files, so there shouldn't be any > risk involved in turning CORS on. > > Thanks, > Raff > > On Tue, Jul 23, 2019 at 6:45 PM Luis Meneses <ldmm(a)uvic.ca> wrote: > >> Hi Raff, >> >> Would it be sufficient to allow requests from a smaller set of domains? >> For example: roma2.tei-c.org where the Roma tool lives? >> >> Making the other change can introduce some new attack vectors for the >> site. >> >> Best, >> ----- >> -Luis >> >> On Jul 22, 2019, at 6:28 AM, Raffaele Viglianti < >> raffaeleviglianti(a)gmail.com> wrote: >> >> Hi Luis, >> >> Thanks for the quick reply! The idea is that the server that serves the >> data from tei-c.org/Vault needs to add the Access-Control-Allow-Origin >> to the response so that browsers know they're allowed to grab data from >> different domains. If the server is Apache, it should enough to add the >> line below to <VirtualHost> or <Location> (depending on the set up) >> >> Header set Access-Control-Allow-Origin "*" >> >> If the server is nginx, you should add this under the right location >> stanza; >> >> add_header 'Access-Control-Allow-Origin' '*'; >> >> Let me know if I can help further, and thanks! >> Raff >> >> >> On Sun, Jul 21, 2019 at 10:12 PM Luis Meneses <ldmm(a)uvic.ca> wrote: >> >>> Hi Raff, >>> >>> Sorry to hear about that you have an issue. >>> Can you give me more details on it? >>> >>> I am just not too sure about what I need to do to fix it. >>> >>> Best, >>> -Luis >>> >>> >>> On Jul 21, 2019, at 1:02 PM, Raffaele Viglianti < >>> raffaeleviglianti(a)gmail.com> wrote: >>> >>> Dear Luis, >>> >>> Sorry to add even more to your plate, but could you enable CORS on the >>> TEI Vault? The new version of Roma written in JavaScript needs it to access >>> ODD customizations and p5subet. Example: fetch >>> https://tei-c.org/Vault/P5/current/xml/tei/odd/p5subset.json >>> The response needs to contain the header >>> Access-Control-Allow-Origin: * >>> >>> Thanks! >>> Raff >>> >>> >>> >> >

2 2

Next IG meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 25 Jul '19

25 Jul '19

Dear all, I think it's time to plan the next Infrastructure Group meeting. I am aware that this will not be easy during the summer, but I'll give it a try. In this meeting we should focus on the move to HumaNum - which Luis is planning for the summer - and the requirements of the Technical Council for the new environment to facilitate future release processes. I send this to the Council list as well, in case Council members want to add to the discussion. Please fill in the doodle: https://doodle.com/poll/rxxdrnkkmd9ywdbg Best, Martina

1 0

July ticket triage
by Elisa Beshero-Bondar 23 Jul '19

23 Jul '19

Dear Council, I've just done the July ticket triage round and some of you will have a new ticket in your pile. Feel free to reassign, but we've now at least given all the tickets a home. Cheers, Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu <ebb8(a)pitt.edu> Development site: http://newtfire.org

1 0

Next Stylesheets meeting
by Peter Stadler 22 Jul '19

22 Jul '19

Hi all, my apologies, but I’m on vacation next week thus unavailable for the Stylesheets meeting on Monday. Best Peter

7 8

Enable CORS on the TEI Vault
by Raffaele Viglianti 21 Jul '19

21 Jul '19

Dear Luis, Sorry to add even more to your plate, but could you enable CORS on the TEI Vault? The new version of Roma written in JavaScript needs it to access ODD customizations and p5subet. Example: fetch https://tei-c.org/Vault/P5/current/xml/tei/odd/p5subset.json The response needs to contain the header Access-Control-Allow-Origin: * Thanks! Raff

1 0

oxygen update
by Scholger, Martina (martina.scholger＠uni-graz.at) 20 Jul '19

20 Jul '19

Hi Luis, Sorry, there is another issue. Could you please make the oxygen plugin file available from the TEI server (http://www.tei-c.org/release/oxygen/updateSite.oxygen) You can find the file here: https://jenkins.tei-c.org/job/oxygen-tei-bleeding/lastSuccessfulBuild/artif… Thanks! Martina Von: Tei-council <tei-council-bounces(a)lists.tei-c.org> Im Auftrag von James Cummings Gesendet: Freitag, 19. Juli 2019 14:42 An: Luis Meneses <ldmm(a)uvic.ca>; Peter Stadler <pstadler(a)mail.uni-paderborn.de> Cc: TEI Council <tei-council(a)lists.tei-c.org>; Elisa Beshero-Bondar <ebb8(a)pitt.edu> Betreff: Re: [Tei-council] ***SPAM Suspected*** Re: ***SPAM Suspected*** Re: Missing newly released TEI Stylesheets on tei-c.org Hi all, Stylesheets were never part of the vault but copy of the release put on website each time so that people could do processing that just imported xslt from server and only had their local xslt overrides locally. (Not saying that is best way to do it in days of github etc.) There are several sites I know of that use the CSS there and then build on that locally (which is sorta how CSS was intended). So we should probably put contents of https://jenkins.tei-c.org/job/Stylesheets/lastSuccessfulBuild/artifact/dist/ in the release. (Or decide we don't want to any more ... ) but release infrastructure when on final server needs to have ability for council to do this without hassling Luis. ;-) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org<mailto:tei-council-bounces@lists.tei-c.org>> on behalf of Luis Meneses <ldmm(a)uvic.ca<mailto:ldmm@uvic.ca>> Sent: Friday, July 19, 2019 1:31:24 PM To: Peter Stadler <pstadler(a)mail.uni-paderborn.de<mailto:pstadler@mail.uni-paderborn.de>> Cc: TEI Council <tei-council(a)lists.tei-c.org<mailto:tei-council@lists.tei-c.org>>; Elisa Beshero-Bondar <ebb8(a)pitt.edu<mailto:ebb8@pitt.edu>> Subject: [Tei-council] ***SPAM Suspected*** Re: ***SPAM Suspected*** Re: Missing newly released TEI Stylesheets on tei-c.org Hi Peter and All, I just copied over the css files into a newly created "stylesheet "folder. https://www.tei-c.org/release/xml/tei/stylesheet/tei.css I don't think they should be in the Vault, but until we find a better solution I am keeping them there. Best, -Luis On Fri, 2019-07-19 at 14:08 +0200, Peter Stadler wrote: Hi Luis, yes: the Stylesheets are not part of the vault (I don't know why, but maybe because they are versioned differently) but only the current version is available from <https://www.tei-c.org/release/xml/tei/stylesheet> https://www.tei-c.org/release/xml/tei/stylesheet Best Peter Am 19.07.2019 um 14:03 schrieb Luis Meneses < <mailto:ldmm@uvic.ca> ldmm(a)uvic.ca<mailto:ldmm@uvic.ca> >: Hi Elisa, I haven't been able to find stylesheets in any of the previous releases on the website. Are they always accessed through this URL? <https://www.tei-c.org/release/xml/tei/stylesheet/tei.css> https://www.tei-c.org/release/xml/tei/stylesheet/tei.css Here are some previous releases: For example: <https://tei-c.org/Vault/P5/3.6.0/xml/tei/> https://tei-c.org/Vault/P5/3.6.0/xml/tei/ <https://tei-c.org/Vault/P5/3.5.0/xml/tei/> https://tei-c.org/Vault/P5/3.5.0/xml/tei/ <https://tei-c.org/Vault/P5/3.4.0/xml/tei/> https://tei-c.org/Vault/P5/3.4.0/xml/tei/ Best, -Luis On Fri, 2019-07-19 at 12:08 +0200, Elisa Beshero-Bondar wrote: Hi Luis (cc: TEI Council), We noticed that the TEI Stylesheets are not available from tei-c.org, and this is because we didn't install them on the scratch-tei-server during our release process (sorry!). But we also think it's probably just as well to get them at this point directly from their GitHub repo (now that we know all the builds pass their tests and the release is official), so here they are: GitHub: <https://github.com/TEIC/Stylesheets/releases> https://github.com/TEIC/Stylesheets/releases Would you make sure these are available on the website? Also, it would be be helpful if Council could see the file directory structure on the tei-c.org website as we used to, so we can tell more quickly when something like this is missing. Thank you! Cheers, Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: <mailto:ebb8@pitt.edu> ebb8(a)pitt.edu<mailto:ebb8@pitt.edu> Development site: <http://newtfire.org> http://newtfire.org _______________________________________________ Tei-council mailing list <mailto:Tei-council@lists.tei-c.org> Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> <http://lists.lists.tei-c.org/mailman/listinfo/tei-council> http://lists.lists.tei-c.org/mailman/listinfo/tei-council

3 2

Re: [Tei-council] ***SPAM Suspected*** Re: ***SPAM Suspected*** Re: Missing newly released TEI Stylesheets on tei-c.org
by James Cummings 19 Jul '19

19 Jul '19

Hi all, Stylesheets were never part of the vault but copy of the release put on website each time so that people could do processing that just imported xslt from server and only had their local xslt overrides locally. (Not saying that is best way to do it in days of github etc.) There are several sites I know of that use the CSS there and then build on that locally (which is sorta how CSS was intended). So we should probably put contents of https://jenkins.tei-c.org/job/Stylesheets/lastSuccessfulBuild/artifact/dist/ in the release. (Or decide we don't want to any more ... ) but release infrastructure when on final server needs to have ability for council to do this without hassling Luis. ;-) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Luis Meneses <ldmm(a)uvic.ca> Sent: Friday, July 19, 2019 1:31:24 PM To: Peter Stadler <pstadler(a)mail.uni-paderborn.de> Cc: TEI Council <tei-council(a)lists.tei-c.org>; Elisa Beshero-Bondar <ebb8(a)pitt.edu> Subject: [Tei-council] ***SPAM Suspected*** Re: ***SPAM Suspected*** Re: Missing newly released TEI Stylesheets on tei-c.org Hi Peter and All, I just copied over the css files into a newly created "stylesheet "folder. https://www.tei-c.org/release/xml/tei/stylesheet/tei.css I don't think they should be in the Vault, but until we find a better solution I am keeping them there. Best, -Luis On Fri, 2019-07-19 at 14:08 +0200, Peter Stadler wrote: Hi Luis, yes: the Stylesheets are not part of the vault (I don’t know why, but maybe because they are versioned differently) but only the current version is available from <https://www.tei-c.org/release/xml/tei/stylesheet> https://www.tei-c.org/release/xml/tei/stylesheet Best Peter Am 19.07.2019 um 14:03 schrieb Luis Meneses < <mailto:ldmm@uvic.ca> ldmm(a)uvic.ca >: Hi Elisa, I haven't been able to find stylesheets in any of the previous releases on the website. Are they always accessed through this URL? <https://www.tei-c.org/release/xml/tei/stylesheet/tei.css> https://www.tei-c.org/release/xml/tei/stylesheet/tei.css Here are some previous releases: For example: <https://tei-c.org/Vault/P5/3.6.0/xml/tei/> https://tei-c.org/Vault/P5/3.6.0/xml/tei/ <https://tei-c.org/Vault/P5/3.5.0/xml/tei/> https://tei-c.org/Vault/P5/3.5.0/xml/tei/ <https://tei-c.org/Vault/P5/3.4.0/xml/tei/> https://tei-c.org/Vault/P5/3.4.0/xml/tei/ Best, -Luis On Fri, 2019-07-19 at 12:08 +0200, Elisa Beshero-Bondar wrote: Hi Luis (cc: TEI Council), We noticed that the TEI Stylesheets are not available from tei-c.org, and this is because we didn't install them on the scratch-tei-server during our release process (sorry!). But we also think it's probably just as well to get them at this point directly from their GitHub repo (now that we know all the builds pass their tests and the release is official), so here they are: GitHub: <https://github.com/TEIC/Stylesheets/releases> https://github.com/TEIC/Stylesheets/releases Would you make sure these are available on the website? Also, it would be be helpful if Council could see the file directory structure on the tei-c.org website as we used to, so we can tell more quickly when something like this is missing. Thank you! Cheers, Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: <mailto:ebb8@pitt.edu> ebb8(a)pitt.edu Development site: <http://newtfire.org> http://newtfire.org _______________________________________________ Tei-council mailing list <mailto:Tei-council@lists.tei-c.org> Tei-council(a)lists.tei-c.org <http://lists.lists.tei-c.org/mailman/listinfo/tei-council> http://lists.lists.tei-c.org/mailman/listinfo/tei-council

2 1

Next Meeting: Friday, July 19
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 Jul '19

19 Jul '19

Dear all, Our next meeting is on Friday, July 19 (EDT 16:00-17:30, GMT 21:00-22:30, CEST 22:00-23:30) This is the rudimentary agenda (tbc): https://docs.google.com/document/d/1RSM_3y_FJmc5Q8VdWF3ZcqX1BCvms26k1bHU2zr… Hugh, could you please start the call? Best, Martina

3 3

Missing newly released TEI Stylesheets on tei-c.org
by Elisa Beshero-Bondar 19 Jul '19

19 Jul '19

Hi Luis (cc: TEI Council), We noticed that the TEI Stylesheets are not available from tei-c.org, and this is because we didn't install them on the scratch-tei-server during our release process (sorry!). But we also think it's probably just as well to get them at this point directly from their GitHub repo (now that we know all the builds pass their tests and the release is official), so here they are: GitHub: https://github.com/TEIC/Stylesheets/releases Would you make sure these are available on the website? Also, it would be be helpful if Council could see the file directory structure on the tei-c.org website as we used to, so we can tell more quickly when something like this is missing. Thank you! Cheers, Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu <ebb8(a)pitt.edu> Development site: http://newtfire.org

3 7

The problem with expected-results and p5subset
by Martin Holmes 18 Jul '19

18 Jul '19

Hi all, I think there's a possible partial solution to the chaos resulting from the fact that Stylesheets tests depend on p5subset.xml, so whenever the Specs change, the expected-results in the Stylesheets tests may also change. This is because we always try to use the same p5subset for every test: the current release. But if we make each test point at a specific version of p5subset.xml in the Vault, then that version will never change; so the Stylesheets output should also never change, unless we change the Stylesheets themselves, in which case we want to see what changes in the expected-results anyway. Anyone see any problem with this? Cheers, Martin

3 4

Release 3.6.0 in progress: Freeze on Release Branches
by Elisa Beshero-Bondar 16 Jul '19

16 Jul '19

Dear Council, Just a quick note to say, please don't push to release branches on Guidelines or Stylesheets...the Potrzebie release 3.6.0 is underway! Cheers, Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu <ebb8(a)pitt.edu> Development site: http://newtfire.org

1 0

Re: [Tei-council] release notes
by James Cummings 16 Jul '19

16 Jul '19

Hi all, isn't that how SF shells always worked? I remember there always being done weirdness around this. I.e. easier to scp the files but getting an actual login was always difficult in some way. In release notes do things like: === A zip file with examples for ODD chaining has been added to the /TEIC/TEI/Documents/pureODD directory (#1882). === really belong since it is for a tutorial outside of the Guidelines that Council isn't writing? (Honest question, I'm not sure either way.) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Martin Holmes <mholmes(a)uvic.ca> Sent: Monday, July 15, 2019 1:40:45 AM To: Elisa Beshero-Bondar <ebb8(a)pitt.edu> Cc: TEI Council <tei-council(a)lists.tei-c.org> Subject: Re: [Tei-council] release notes I can't ssh into SF shell with my keys either, and I certainly used to be able to. Things seem to have changed since the last time I did it, though; the instructions here seem different: <https://sourceforge.net/p/forge/documentation/Shell%20Service/> When I tried what's in TCW22 I was asked for a password, then the shell shut itself down automatically: __________________________________________ Password: PTY allocation request failed on channel 0 Welcome! This is a restricted Shell Account. You can only copy files to/from here. Connection to frs.sourceforge.net closed. __________________________________________ It might be worth considering whether we want to bother with the SF release any more; or whether it should be left until after release day, to simplify things for the release technicians, and then someone could just do it later when there's no time pressure. Cheers, Martin On 2019-07-14 5:22 p.m., Elisa Beshero-Bondar wrote: > Nope-- no luck yet. Same problem as before: I'm prompted for a password > when I attempt SSH access to SourceForge TEI from the scratch-tei server. > And the tei(a)tei-c.org <mailto:tei@tei-c.org> server just times out so I > can't get in there at all. > > Thanks for the troubleshooting help... > > Elisa > > On Mon, Jul 15, 2019 at 2:15 AM Martin Holmes <mholmes(a)uvic.ca > <mailto:mholmes@uvic.ca>> wrote: > > I've added you to the admin group. Can you check again? > > There was a problem with the TEI server yesterday; apparently the db > server became unresponsive, so the site was giving "unable to > connect to > db" errors (why oh why did we go for WordPress? If there's one > community > on the planet who doesn't need a child-friendly interface to make web > pages, it's us, surely?) I emailed Jon and he says it's a problem with > Compute Canada, and they weren't responding to his requests to restart > it, so he's set up a new db server instance and pointed to that > instead. > I don't know whether any of this would affect what needs to happen on > release day, but I hope not; presumably the regular command-line stuff > will be unaffected. But let's keep our fingers crossed. > > Cheers, > Martin > > On 2019-07-14 5:03 p.m., Elisa Beshero-Bondar wrote: > > Thanks, Martin--I see I'm a developer there now. But I'm still being > > prompted for a password when I try this: ssh > > ebeshero,tei(a)frs.sourceforge.net <mailto:tei@frs.sourceforge.net> > <mailto:tei@frs.sourceforge.net <mailto:tei@frs.sourceforge.net>>. I'm > > doing this SSH-ing from a temporary "scratch-tei" server that > Luis set > > up, and I don't know if that has anything to do with it. > > > > I notice I'm unable to SSH into the usual place: ssh > tei(a)tei-c.org <mailto:tei@tei-c.org> > > <mailto:tei@tei-c.org <mailto:tei@tei-c.org>> (That just lags > and times out.) (But I'm able to > > get into the temporary server that Luis set up.) Maybe the > morning will > > bring some answers. > > Elisa > > > > > > > > On Mon, Jul 15, 2019 at 1:46 AM Martin Holmes <mholmes(a)uvic.ca > <mailto:mholmes@uvic.ca> > > <mailto:mholmes@uvic.ca <mailto:mholmes@uvic.ca>>> wrote: > > > > Hi Elisa, > > > > I've added you as a developer; can you see if you have the > permissions > > you'll need? > > > > Cheers, > > Martin > > > > On 2019-07-14 4:29 p.m., Elisa Beshero-Bondar wrote: > > > I like it, too, but I'm also noting that "Potzrebie" is a > Polska > > word! > > > https://en.wikipedia.org/wiki/Potrzebie So it's kind of > perfect > > right > > > now while I'm staying with Magdalena! :-) > > > > > > By the way, I just posted this on Slack, but I think I > need to be a > > > member or developer or something of the TEI Project on > > Sourceforge. I'm > > > ebeshero there, and my public SSH key is in with my > account. Can > > someone > > > add me there, as I'm not apparently on the SourceForge TEI > > > member/developer list? > > > > > > Thanks, > > > Elisa > > > > > > On Mon, Jul 15, 2019 at 1:18 AM Martin Holmes > <mholmes(a)uvic.ca <mailto:mholmes@uvic.ca> > > <mailto:mholmes@uvic.ca <mailto:mholmes@uvic.ca>> > > > <mailto:mholmes@uvic.ca <mailto:mholmes@uvic.ca> > <mailto:mholmes@uvic.ca <mailto:mholmes@uvic.ca>>>> wrote: > > > > > > Since Mad is just publishing its final edition > > > > > > (<https://www.smithsonianmag.com/smart-news/last-laugh-mad-magazine-will-soon…>), > > > > > > I vote for whatmeworry. > > > > > > Cheers, > > > Martin > > > > > > On 2019-07-14 3:01 p.m., Elisa Beshero-Bondar wrote: > > > > However(!) I'm having second thoughts, reviewing the > > measurement > > > ticket > > > > and branch. I'd be happy to call this the > "potrzebie" or the > > > > "whatmeworry" release, in commemoration of the > measurement > > ticket > > > and in > > > > honor of the first Mad Magazine example going into the > > Guidelines > > > BIB > > > > (about the Potrzebie system with its whatmeworry > Mad Magazine > > > fictional > > > > power unit). Magdalena and I will debate it in the > morning and > > > decide on > > > > the codename. :-) > > > > > > > > What, me worry? > > > > Elisa > > > > > > > > On Sun, Jul 14, 2019 at 11:09 PM Elisa Beshero-Bondar > > > <ebb8(a)pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>> <mailto:ebb8@pitt.edu > <mailto:ebb8@pitt.edu> > > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>>> > > > > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>> > > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>>>>> wrote: > > > > > > > > I've checked our minutes from the May F2F > meeting: We'd > > > decided then > > > > to call this the "Rebel Release" and I like it > very much. > > > Also, as > > > > I'm supposed to make the release branch right > now, I think > > > the rebel > > > > associations with Bastille Day still apply. So! > codename > > > "rebel" okay? > > > > > > > > cheers, > > > > Elisa > > > > > > > > On Sun, Jul 14, 2019 at 10:37 PM Syd Bauman > > > > <s.bauman(a)northeastern.edu > <mailto:s.bauman@northeastern.edu> > > <mailto:s.bauman@northeastern.edu > <mailto:s.bauman@northeastern.edu>> > <mailto:s.bauman@northeastern.edu <mailto:s.bauman@northeastern.edu> > > <mailto:s.bauman@northeastern.edu > <mailto:s.bauman@northeastern.edu>>> > > > <mailto:s.bauman@northeastern.edu > <mailto:s.bauman@northeastern.edu> > > <mailto:s.bauman@northeastern.edu > <mailto:s.bauman@northeastern.edu>> > > > <mailto:s.bauman@northeastern.edu > <mailto:s.bauman@northeastern.edu> > > <mailto:s.bauman@northeastern.edu > <mailto:s.bauman@northeastern.edu>>>>> wrote: > > > > > > > > Hi, Martin. Not surprisingly I've already hit > > several of > > > the things > > > > you note, and not others. > > > > > > > > > Looks good. This is a slight typo: > > > > > "An additional information that the unit > > attribute may be > > > > unnecessary > > > > > when the unitRef attribute is present > has been > > given > > > (#1905)." > > > > > It should be either "An additional > warning" or just > > > "Additional > > > > > information". > > > > > > > > Fixed. > > > > > > > > > > > > > Also, I'm confused by this: > > > > > "The factor attribute has been added to the > > unit element, > > > > which shows > > > > > factors of numerical values given in a > > referenced unit > > > element." > > > > > I thought the @formula attribute was the > final > > > decision? And its > > > > > datatype is XPath, surely? > > > > > > > > There is no @factor, so I deleted this > entire bit. > > (I did not > > > > fix the > > > > bit that is in there about @formula, though ... > > hope to > > > do that in a > > > > few.) > > > > > > > > > > > > > For the Japanese translations, I don't > think I > > should be > > > > thanked; it's > > > > > Kiyonori's team that's done the actual > translation, > > > and what > > > > I've been > > > > > doing (which is nowhere near half-done) > is largely > > > > mechanical. Good to > > > > > thank Hanna, but perhaps put her after > Kiyonori. > > > > > > > > Did not touch this. > > > > > > > > > > > > I also commented out two items completely, as I > > consider > > > them too > > > > minor to be in release notes (they are covered > > under the > > > last bullet > > > > point for the Guidelines, "Corrections of > > typographic errors, > > > > improvements on explanations, and > corrections of > > examples > > > have been > > > > conducted in various sections of the > Guidelines", > > which > > > I'm not sure > > > > should be a bullet point, but perhaps a > separate > > paragraph): > > > > > > > > * The description of schema validation of > > co-occurrence > > > > constraints > > > > has been cleaned up slightly (#1770). > [Also, > > this was not > > > > true, we > > > > deleted said description. The section from > > which it > > > was deleted > > > > needs some work, BTW.] > > > > > > > > * The change from http:// to https:// for > > relaxng.rng. > > > > _______________________________________________ > > > > Tei-council mailing list > > > > Tei-council(a)lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org> > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org>> > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org> > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org>>> > > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org> > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org>> > > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org> > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org>>>> > > > > > http://lists.lists.tei-c.org/mailman/listinfo/tei-council > > > > > > > > > > > > > > > > -- > > > > Elisa Beshero-Bondar, PhD > > > > Director, Center for the Digital Text | Associate > > Professor > > > of English > > > > University of Pittsburgh at Greensburg | Humanities > > Division > > > > 150 Finoli Drive > > > > Greensburg, PA 15601 USA > > > > E-mail: ebb8(a)pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>> > > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>>> > > > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>> > > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>>>> > > > > Development site: http://newtfire.org > > <http://newtfire.org/> > > > > > > > > > > > > > > > > -- > > > > Elisa Beshero-Bondar, PhD > > > > Director, Center for the Digital Text | Associate > Professor of > > > English > > > > University of Pittsburgh at Greensburg | Humanities > Division > > > > 150 Finoli Drive > > > > Greensburg, PA 15601 USA > > > > E-mail: ebb8(a)pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>> > > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>>> > > > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>> > > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>>>> > > > > Development site: http://newtfire.org > <http://newtfire.org/> > > > > > > > > _______________________________________________ > > > > Tei-council mailing list > > > > Tei-council(a)lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org> > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org>> > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org> > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org>>> > > > > > http://lists.lists.tei-c.org/mailman/listinfo/tei-council > > > > > > > _______________________________________________ > > > Tei-council mailing list > > > Tei-council(a)lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org> > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org>> > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org> > > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org>>> > > > http://lists.lists.tei-c.org/mailman/listinfo/tei-council > > > > > > > > > > > > -- > > > Elisa Beshero-Bondar, PhD > > > Director, Center for the Digital Text | Associate Professor of > > English > > > University of Pittsburgh at Greensburg | Humanities Division > > > 150 Finoli Drive > > > Greensburg, PA 15601 USA > > > E-mail: ebb8(a)pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>> > > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>>> > > > Development site: http://newtfire.org <http://newtfire.org/> > > _______________________________________________ > > Tei-council mailing list > > Tei-council(a)lists.tei-c.org <mailto:Tei-council@lists.tei-c.org> > <mailto:Tei-council@lists.tei-c.org > <mailto:Tei-council@lists.tei-c.org>> > > http://lists.lists.tei-c.org/mailman/listinfo/tei-council > > > > > > > > -- > > Elisa Beshero-Bondar, PhD > > Director, Center for the Digital Text | Associate Professor of > English > > University of Pittsburgh at Greensburg | Humanities Division > > 150 Finoli Drive > > Greensburg, PA 15601 USA > > E-mail: ebb8(a)pitt.edu <mailto:ebb8@pitt.edu> > <mailto:ebb8@pitt.edu <mailto:ebb8@pitt.edu>> > > Development site: http://newtfire.org <http://newtfire.org/> > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org <mailto:Tei-council@lists.tei-c.org> > http://lists.lists.tei-c.org/mailman/listinfo/tei-council > > > > -- > Elisa Beshero-Bondar, PhD > Director, Center for the Digital Text | Associate Professor of English > University of Pittsburgh at Greensburg | Humanities Division > 150 Finoli Drive > Greensburg, PA 15601 USA > E-mail: ebb8(a)pitt.edu <mailto:ebb8@pitt.edu> > Development site: http://newtfire.org <http://newtfire.org/> _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

7 8

Release in progress! Stylesheets 7.48.0 release branch
by Elisa Beshero-Bondar 15 Jul '19

15 Jul '19

Dear Council (cc: Martin and Lou), I've just created the release branch for the Stylesheets: https://github.com/TEIC/Stylesheets/tree/release-7.48.0 Martin, Peter, Raff--if you'd like to get started with setting Jenkins to monitor that branch, that would be great! :-) I'll make a release branch for the Documentation repo as well, since we've made some significant revisions there since May to TCW20. Magdalena is working on a bit of helpful explanation re #1414 to complete our work on the Guidelines for this release, and she'll be creating the Guidelines release branch when that is ready. We're trying to minimize having to make changes to the release branches in hopes of smooth sailing through this release process. Thanks, all! Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu <ebb8(a)pitt.edu> Development site: http://newtfire.org

2 1