Hi all,
I did a quick bugfix for this ticket:
<http://sourceforge.net/p/tei/bugs/724/>
back in July, but I'm now dealing with the ramifications of getting it
onto tei-c.org, and in the process, noticing that the project was moved
from SF to GitHub without some key code changes being made to handle the
changelog; I think the same issues will apply to P5, so I think we could
use Roma as a good testcase for handling the change.
When you run "make dist" or "make install" in the Roma source, one of
the things that should happen is that the latest changes are added to
the ChangeLog file. That's done by calling a PERL script called
gnuify-changelog, which seems to be fairly widely used; but it is
explicitly customized for the project and its contributors, all of whom
are listed explicitly. What it does is to call svn log to get the latest
commits, then converts them into a GNU-style changelog by substituting
more detailed user info for user names.
There are four problems with this:
1. gnuify-changelog.pl no longer exists in the Roma source, since it's
been pulled out of the P5 tree.
2. We're now using git, not svn, so the log info is differently formatted.
3. The script requires a hard-coded list of contributors to be maintained.
However, git log seems to be more friendly than svn log, in that it
includes user name and email:
---------------
$> git log -n 1 --name-status
commit 18cc86ddcd79b409a9bfa406426fe4685c37fa8a
Author: martindholmes <mholmes(a)uvic.ca>
Date: Mon Jul 27 14:05:29 2015 -0700
Fix for http://sourceforge.net/p/tei/bugs/724/. I'm doing a
string-replace which catches the specific bug reported (double quotes)
in the title and author fields, but doesn't make any attempt to do more
comprehensive escaping, since that would need a significant rewrite of
large blocks of the code, I think.
M VERSION
M roma/romadom.php
---------------
git log can also be massaged to output stuff in XML, by defining an XML
format. So I'd like to suggest the following, to be piloted and tested
with Roma, but then implemented for P5 (and any other projects which
happen to be using gnuify-changelog.pl in our setup:
Replace that call with an ant task which reads the existing XML log file
(if it exists), calls git log to output anything subsequent to the last
entry in XML, calls Saxon to XSLT it to whatever we want and insert it
into the existing XML log file, then calls Saxon again to XSLT the
now-updated XML log file into the GNU-preferred text format.
Alternatively, if those of you who love PERL would like to simply update
gnuify-changelog.pl so that it can use the git log output format, you're
welcome to do that; it's a bit urgent because I don't think a build will
work properly otherwise.
Another option is to rely (for P5 builds) on having an svn checkout
which can generate an svn log in the expected format, and using that;
and then re-inserting gnuify-changelog.pl into the Roma tree, changing
the Makefile to point to it, and doing other updates (adding and
removing potential contributors) to both PERL files. I think the
ant/XSLT solution is better in the long term, and removes one more PERL
dependency, but I suspect I'm in a minority there.
Cheers,
Martin
Hi all,
A reminder that the Doodle poll for our August telecon needs your input, if
you haven't already filled it out: http://doodle.com/5ks6ma5f3fez838c
Right now, August 31 looks like the best date.
I expect the agenda will focus mainly on the migration and on the logistics
of a Fall release. It would be really nice to be able to discuss some
tickets too though!
All the best,
Hugh
Hello TEITechnicalCouncil,
We wanted to let you know that your GitHub password was changed.
If you did not perform this action, you can recover access by entering tei-council(a)lists.tei-c.org into the form at https://github.com/password_reset.
To see this and other security events for your account, visit https://github.com/settings/security.
If you run into problems, please contact support by visiting https://github.com/contact or replying to this email.
Hello TEITechnicalCouncil,
We wanted to let you know that your GitHub password was changed.
If you did not perform this action, you can recover access by entering james+teitechnicalcouncil(a)blushingbunny.net into the form at https://github.com/password_reset.
To see this and other security events for your account, visit https://github.com/settings/security.
If you run into problems, please contact support by visiting https://github.com/contact or replying to this email.
Re: discussion Gabby & Martin are having on TEI-L
I think this is evidence in support for a linked data block element
that is a child of <text> but not in <front>, <body>, or <back> that
is specifically for this kind of stuff (<relation>s).
Hey, we want to verify that you are indeed "TEITechnicalCouncil". Verifying this address (tei-council(a)lists.tei-c.org) will let you receive notifications and password resets from GitHub. If you wish to continue, please follow the link below:
https://github.com/users/TEITechnicalCouncil/emails/16451158/confirm_verifi…
If you’re not TEITechnicalCouncil or didn’t request verification, you can ignore this email.
Hiya,
I'm starting to look at creating individual spec files for the
processing model documentation additions to the Guidelines and
when I loaded up some random spec files (e.g. in SF svn:
P5/Source/Specs/affiliation.xml) to use as a model I notice it
didn't validate.
We added an xml-model of:
<?xml-model
href="http://tei.it.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/relea…"
type="application/xml"
schematypens="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"?>
to these some time back. (And part of me wants to point out that
maybe this should be http://bits.nsms.ox.ac.uk:8080/ or we should
set up jenkins really to run on tei.it rather than use some URL
rewrites...)
However, the error message I'm getting in oXygen is:
"Attribute @xsl:dummy-for-xmlns is not allowed on element
<xsl:stylesheet>"
I can't find where this is being caused. It doesn't seem to be
in our p5odds.rng or p5odds.isosch files.
Any suggestions?
-James
--
Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT
Services, University of Oxford
Forwarding this reminder to tei-council to remind them that they
need to keep a watching eye on such pull requests. (Once set up,
we should get notifications sent to tei-council if possible)
-James
-------- Forwarded Message --------
Subject: Re: editing the TEI stylesheets
Date: Wed, 19 Aug 2015 09:43:31 +1200
From: Stuart A. Yeates <syeates(a)gmail.com>
To: James.Cummings(a)it.ox.ac.uk <James.Cummings(a)it.ox.ac.uk>
CC: Sebastian Rahtz <sebastian.rahtz(a)it.ox.ac.uk>
OK, so I sent a pull request almost a week ago
https://github.com/TEIC/Stylesheets/pull/114
Do I need to notify someone? Or has feedback gone somewhere I'm
missing...
cheers
stuart
--
...let us be heard from red core to black sky
On Wed, Aug 12, 2015 at 10:01 PM, James Cummings
<James.Cummings(a)it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk>>
wrote:
Hi Stuart,
The TEI Technical Council is currently reviewing how it uses
GitHub as part of examining whether it is a suitable
replacement for SourceForge in moving Guidelines development
there. As you know, it moved the Stylesheets (and other
software) building there some time ago. Although you (and
various others) are members of the Stylesheets repository I
believe the correct github etiquette is to fork, then issue a
pull request. However, I think as long as you are flagging
that you are making the change (or open an issue and then
make the change as a result of that) it should probably be
fine. (Though when you say 'regularise the display of
attribute values' I'd be interested to know what you mean by
regularise. There are some options and logic already in
there.) The change in your forked version won't get looked at
by Jenkins. We're also looking at whether some of the GitHub
hosted alternative continuous integration systems might
replace Jenkins. So, to be honest, you could do either, but
fork+change+pull-request will ensure that it gets other eyes
on it before going into the system. Jenkins uses the most
up-to-date stylesheets when next building the Guidelines. I
know it used to email when doing commits to the Guidelines SF
SVN repository that broke something (or more accurately when
someone committing around the same time as you broke
something ;-) ) and I'm assuming that is still the case. I
don't think it emailed just when it was running a job based
on your commits...just when that job failed and your commit
was one of those possible causes.
That is my understanding at least, some of our council github
gurus may correct me.
-James
On 12/08/15 10:26, Stuart A. Yeates wrote:
I've got a change I'd like to make to the stylesheets
used to generate the HTML version of the standard (a
minor change to regularise the display of attribute
values), but I'm not quite sure how to go about it.
Do I just push a change request to
https://github.com/TEIC/Stylesheets ? Or fork it? Does
that get tested by jenkins?
Jenkins used to send me emails when it ran a job based on
my commits, but I've not seen one for a couple of recent
commits, is that because I'm not on the council any more?
cheers
stuart
--
...let us be heard from red core to black sky
--
Dr James Cummings, James.Cummings(a)it.ox.ac.uk
<mailto:James.Cummings@it.ox.ac.uk>
Academic IT Services, University of Oxford
--
Dr James Cummings, Academic IT Services, University of Oxford TEI
Consultations: tei(a)it.ox.ac.uk
