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

I've just test-migrated my CodeSharing project from SF to GH
by Martin Holmes 05 Aug '15

05 Aug '15

Hi all, especially Raff, our migration manager. I just migrated my project from SF to GitHub in the following steps: === 1. PREPARATION === Do a freeze (not a problem for my tiny project). Make sure you have complete backups and checkouts. Prepare a JSON file called users_sf2gh.json which consists of the equivalent user names from SF and GitHub, like this: { "martindholmes" : "martindholmes", "stadlerpeter" : "peterstadler" } (Obviously this needs a bit of research.) === 2. GETTING TICKETS ETC. OUT OF SF ========================== Do a full export of the SF project from here: https://sourceforge.net/p/[proj]/admin/export This is not instant; you'll get an email when it's complete and you can download it as a zip. That produced these files for me: admin.json discussion.json tickets.json wiki.json It doesn't include the code, of course. === MOVING CODE TO GITHUB ===================================== Go here: https://import.github.com/new/ and follow the instructions to import your code. This was quick for my tiny project, but would take a long time for the TEI codebase. The commit history is preserved correctly, as far as I can see. I provided the https URL for the SF repo: https://svn.code.sf.net/p/[proj] While that's going on, or after it's finished, you're offered the option to provide the list of SF/GitHub user equivalences you've already specified in the JSON file, through a web form (you'll use the JSON file itself later, when importing tickets). === MOVING TICKETS TO GITHUB ================================= I used this PERL script for this: https://github.com/cmungall/gosf2github Beware: there is a typo (occurring in two places) which omits a quotation mark in the example; I've added a patch and sent a pull request to fix it. There are several stages to this: 1. Set up an OAUTH token for the Git repo here: https://github.com/settings/tokens 2. Get a list of the project collaborators in JSON format from github like this: curl -H "Authorization: token YOURTOKEN" https://api.github.com/repos/[entity]/[project]/collaborators > [project]-collab.json 3. Run the PERL script, which pulls down each ticket from SF and pushes it up to GitHub -- this is my command line: perl gosf2github.pl -a martindholmes -u users_sf2gh.json -c codesharing-collab.json -r martindholmes/CodeSharing -s codesharing/tickets -t [MYTOKEN] tickets.json You can run it with the -k flag first to do a dry-run and see the curl statements that would be addressed to github without sending them. This successfully imported the two tickets I had created as a test, one open and one closed, with embedded XML code successfully preserved. Hope this helps. It's nice to be on vacation. There's time to actually do stuff. :-) Cheers, Martin

4 7

Test GLs repo on GitHub
by Hugh Cayless 03 Aug '15

03 Aug '15

All, I've pushed up a copy of the my own synced git-svn copy of the Guidelines at https://github.com/TEIC/Guidelines-TEST. It's got issues and a wiki enabled, so we can try those out as we like. Commits to SF should be synced periodically by my server, but changes you push here will not automatically be sent back to SourceForge (so you can try it out, with the foreknowledge that they'll probably be deleted). Currently in-use branches have been copied, but I've not bothered to create the old ones (the history is there, but they're not visible as branches). I've also not bothered to create any tags. This may be something that has to be done manually, as git tags are not branches, unlike svn tags. I bet there's a script for it somewhere. If not, I don't think writing one would be hard. Request for everyone: can you try out cloning and messing with this? In particular I'd like to know what *doesn't* seem to work, and what the pain points are. All of them. We will obviously need to develop new tutorials/documentation for this, so I very much want to know what's confusing, up to and including "I don't even know where to start with this git thing". Please don't be shy or embarrassed—you will not be judged. This is a new thing to many of us and will be to new members of Council in the future. GUI clients for those who prefer them are available at https://windows.github.com and https://mac.github.com. I've zero experience with them, but they may be nicer to work with if you're less comfortable in the command line.

5 19

Why are we using a pantor.com namespace?
by Martin Holmes 31 Jul '15

31 Jul '15

In Utilities/guidelines.xsl.model, I see this: xmlns:pantor="http://www.pantor.com/ns/local" and something similar in the following files: Query/simplify.xsl Utilities-1/colorsvg.xsl Utilities-1/divsplit.xsl Utilities-1/generate-label.xsl Utilities-1/guidelines-latex.xsl Utilities-1/guidelines-print.xsl Utilities~1/guidelines.xsl.model Utilities~1/odd2ebnf.xsl Utilities~1/odd2exodd.xsl Utilities~1/rng2ebnf.xsl Utilities~1/split.xsl Utilities/guidelines-print.xsl Sometimes it maps to the prefix "pantor" and sometimes to the prefix "local". pantor.com seems to be some kind of electronic stock trading platform: <http://www.pantor.com/> The Stylesheets repo contains a file called RngToRnc.xsl, which is an ancient stylesheet apparently dating back to 2002, last edited by Syd in 2010. But this does not appear to use the pantor: or local: prefixes, and neither prefix seems to be actually used anywhere. Does anyone have any recollection of what was going on here? If we're not using this namespace, it would be good to get rid of it, especially since it's usually rather confusingly mapped to the prefix "local". Cheers, Martin

2 3

svn:keywords
by Peter Stadler 29 Jul '15

29 Jul '15

It just occurred to me that GitHub won’t support svn:keywords such as $Date$ or $Rev$. Humans will probably adjust themselves but I don’t know whether any software piece in our (some) processing pipeline relies on this information? Best Peter

5 5

SF restore is not complete yet
by Martin Holmes 29 Jul '15

29 Jul '15

Hi all, Just an update on the SF situation: I just tried to upload a new release of Roma to the Files area and that functionality is not yet working; it fails when you try to do it over SSH from the command line, and the GUI which is supposed to be available to admins on the website is not there yet. That means we cannot yet release updated versions of anything. Me no like. I'm copying Kevin on this in case he knows anything about the bandwidth expectations/agreements/limits that might pertain to our shared hosting with ADHO; it seems to me that we might well want to serve our files from our own server if we can. We had 1117 downloads of P5 (which is about 256MB) from SF in the last year, which would amount to less than 300GB per year. Could our hosting deal handle that? Cheers, Martin

2 3

July Telecon
by Hugh Cayless 28 Jul '15

28 Jul '15

Hi all, A reminder that we need to schedule our July telecon in a week or so. Please fill out the poll at http://doodle.com/xy2hqrpk9swnzhzd <http://doodle.com/xy2hqrpk9swnzhzd> if you haven’t yet. I’ve been traveling for a while, so I’m running a little behind on organization, but I’ll try to have an agenda up this week. Possible agenda Items: Source Control and administration discussion Fall F2F App validation? Ticket review What else? /** * Hugh A. Cayless, Ph.D * Chair, TEI Technical Council * Duke Collaboratory for Classics Computing (DC3) * hugh.cayless(a)duke.edu * http://blogs.library.duke.edu/dcthree/ **/

9 16

Re: [tei-council] Something weird about tei-c.org
by Martin Holmes 28 Jul '15

28 Jul '15

Hi Kevin, Sebastian et al, I've just done a quick bugfix for the Roma PHP webapp: <https://sourceforge.net/p/tei/bugs/724/> and tested it locally and it seems to work fine. As far as I can tell from browsing around the projects/tei/web/Vault directory, the current deployed version of Roma on tei-c is 4.15; the new build is 4.18. The system looks similar to the setup for P5, where the "current" symlink points to whatever should be the current version. I think (but I'm not sure) that we can get a new version deployed like this: - Create new 4.18 directory - Get the latest build from Jenkins: <http://teijenkins.hcmc.uvic.ca/job/Roma/lastSuccessfulBuild/artifact/tei-ro…> and unzip it into there. - Change the "current' symlink to point at it. However, there's something slightly odd going on. As far as I understand it, tei-roma/roma.php requires a file called config.php in the same directory. That file is (I thought) created by copying the file config-dist.php to config.php and then customizing it as necessary for the local install. roma/roma.php contains this: require_once( 'config.php' ); so it it's definitely expected to be available. But in current/tei-roma/roma, there is no config.php; there are various versions of config-dist.php resulting from what appears to be an svn conflict, where the differences amount only to the version number and date. So my question is: am I wrong about the fact that config.php is expected to be created from config-dist.php? That is what I did on my local test install, and it worked fine. If I'm right, that would seem to suggest that Roma on tei-c.org has been running slightly misconfigured, and managing without the missing config.php somehow (perhaps error messages are being suppressed). Does anybody know anything about this? I'm not seeing any documentation on how to deploy the PHP Roma, so I've started a new section on the wiki page: <http://wiki.tei-c.org/index.php/Roma#Getting_the_Roma_server_running> Cheers, Martin On 15-07-27 01:44 PM, Kevin Hawkins wrote: > As you've probably seen by now, we did in fact get a notification from > Uptime Robot, and it's already back up. > > This is the first time I've seen the TEI site go down while I'm at my > computer. The ADHO site remained up during that time, and given how > often I've seen notifications that that site goes down while the TEI > site stays up, it appears that these two sites function independently > despite sharing a hosting service. > > Nick, I'm going to turn off the Uptime Robot notifications for the ADHO > site for now. > > Kevin > > On 7/27/15 3:42 PM, Martin Holmes wrote: >> Hi Kevin, >> >> I was just working on Roma on tei-c when it stopped responding. I then >> went to try tei-c.org, and the site doesn't seem to be responding. If >> you ping it, the ping is returned by digitalhumanities.org, so tei-c >> appears to be up for services like isup.me, but wget requests never get >> a response, and I see this proxy error message eventually in my browser: >> >> Proxy Error >> >> The proxy server received an invalid response from an upstream server. >> The proxy server could not handle the request GET /index.xml. >> >> Reason: Error reading from remote server >> >> Additionally, a 502 Bad Gateway error was encountered while trying to >> use an ErrorDocument to handle the request. >> >> Just letting you know, because I don't know whether uptimerobot will >> notice it. >> >> Cheers, >> Martin

3 3

Looks like the SF svn repo is back up
by Martin Holmes 26 Jul '15

26 Jul '15

<http://sourceforge.net/blog/category/sitestatus/> I was able to do an svn update successfully on the TEI repo and my own CodeSharing repo. Cheers, Martin

1 0

F2F in Lyon in Oct
by Syd Bauman 24 Jul '15

24 Jul '15

Hugh -- Do we have definitve dates for the F2F in Lyon in 2015-10 yet? James and I are supposed to be at a meeting in Germany on Thu 10-22, Fri 10-23, and maybe Sat 10-24. The pre-conference workshops will be Mon 10-26, Tue 10-27, and Wed morning 10-28; conference proper from Wed afternoon 10-28 through Sat 10-31.

3 2

ODD question
by Hugh Cayless 22 Jul '15

22 Jul '15

Hello all, Hope your trips home went well (or are going well). I’m having a hard time defining a new spec for <secl>. Does anybody know why https://github.com/hcayless/TEI-Guidelines/blob/secl/P5/Source/Specs/secl.x… <https://github.com/hcayless/TEI-Guidelines/blob/secl/P5/Source/Specs/secl.x…> wouldn’t be picked up by any of the build processes I’m running? It’s as though the file is invisible. There’s clearly some incantation I’m not including, but I don’t know what it is… Thanks, Hugh /** * Hugh A. Cayless, Ph.D * hugh.cayless(a)duke.edu * Duke Collaboratory for Classics Computing (DC3) * http://blogs.library.duke.edu/dcthree/ **/

9 36