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

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 22 Jul '19

22 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 21 Jul '19

21 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