[tei-council] Useful resources for Council members

[Martin Holmes]

Hi Hugh,

If you have a look through the Jenkins Builder Script:

<http://sourceforge.net/p/tei/code/HEAD/tree/trunk/Documents/Editing/Jenkins/jenkins_builder_script_2012.sh>

you'll probably find the bits you're missing.

Cheers,
Martin

On 14-12-18 06:39 AM, Hugh Cayless wrote:
> Sorting out the details of the build system would be nice. I can't myself
> do a full build—it fails somewhere around PDF generation, possibly because
> I don't have all the right fonts. But it's not at all clear to me what
> those are or how to get them. I've never dug into it because I can generate
> the HTML GLs just fine. Is there documentation about the details anywhere?
>
> On Wed, Dec 17, 2014 at 1:52 PM, Martin Holmes <mholmes at uvic.ca> wrote:
>>
>> On 14-12-17 10:18 AM, Lou Burnard wrote:
>>> Always useful to have such lists. I wonder whether it is stating the
>>> obvious to say that guidelines source documents should always be
>>> validated against the p5oddschema (and indicate where that is)?
>>
>> All the specs and chapter files include this:
>>
>> <?xml-model
>> href="
>> http://tei.it.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/release/xml/tei/odd/p5.nvdl
>> "
>> type="application/xml"
>> schematypens="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"?>
>>
>> which Oxygen will use to validate them.
>>
>>> Personal.ly i always like to do a test build locally before bothering Mr
>>> jenkins. That may just be my age but it might be worth mentioning too
>>
>> That brings up the difficult issue of getting a build environment
>> working on your system. I think anyone just getting started might want
>> not want to open that particular can of worms until they're happy doing
>> things in the normal way.
>>
>> But I think it would be worth putting together a guide to creating a
>> local build environment, in case people want to try it.
>>
>> Cheers,
>> Martin
>>
>>>
>>>
>>>
>>> Sent from my Samsung Galaxy Tab®|PRO
>>>
>>>
>>> -------- Original message --------
>>> From: Martin Holmes
>>> Date:12/17/2014 17:48 (GMT+00:00)
>>> To: TEI Council
>>> Subject: [tei-council] Useful resources for Council members
>>>
>>> Hi all,
>>>
>>> This is a list of useful documents and resources for Council members:
>>>
>>>
>>> ---------------------------------------------------------------
>>> 1. BACKGROUND INFO:
>>> ---------------------------------------------------------------
>>>
>>> TEI Council FAQ:
>>> <http://wiki.tei-c.org/index.php/TEI-Council-FAQ>
>>>
>>> The Council Mailing List archive:
>>> <http://lists.village.virginia.edu/pipermail/tei-council/>
>>> (I don't know if this will change as the lists are migrated at the end
>>> of the week.)
>>>
>>> TEI Council yearly reports:
>>> <http://www.tei-c.org/Activities/Council/Reports/>
>>>
>>> Minutes of previous Council meetings (face-to-face and online):
>>> <http://www.tei-c.org/Activities/Council/Meetings/>
>>>
>>>
>>> ---------------------------------------------------------------
>>> 2. EDITING THE GUIDELINES:
>>> ---------------------------------------------------------------
>>>
>>> Most of the actions taken by Council members involve editing the TEI
>>> Guidelines source code. The process basically works like this:
>>>
>>> 1. Check out the source from Subversion on SourceForge.
>>>
>>> 2. Make changes.
>>>
>>> 3. Commit them back to the repository.
>>>
>>> 4. Wait to see whether our Continuous Integration servers successfully
>>> rebuild the schemas and documentation.
>>>
>>> These are the key URLs for learning how to edit the Guidelines:
>>>
>>> The Sourceforge SVN repository:
>>> <http://sourceforge.net/p/tei/code/HEAD/tree/>
>>> (If you log into the SF website, you will see the option RW for a
>>> read-write checkout; use this option so that you can easily commit
>>> changes back to the repository. All Council members are members of the
>>> Developer group, with write permissions.)
>>>
>>> Bug reports and feature requests (tickets) on SourceForge:
>>> <http://sourceforge.net/p/tei/_list/tickets>
>>>
>>> How to Edit the TEI Guidelines:
>>> <http://www.tei-c.org/Activities/Council/Working/tcw20.xml>
>>> (This is a vital read before attempting to make any changes to the
>>> Guidelines source code.)
>>>
>>> Style Guide for Editing the TEI Guidelines:
>>> <http://www.tei-c.org/Activities/Council/Working/tcw24.xml>
>>> (Another important document to read before making any edits.)
>>>
>>> Currently Unresolved Tickets:
>>> <http://www.tei-c.org/Activities/Council/Working/tcw17.html>
>>> (This is a good way to see what we're currently working on. New members
>>> might find a ticket here that they feel confident about implementing,
>>> and could volunteer to take it and work on it with the help of their
>>> mentor.)
>>>
>>>
>>> ---------------------------------------------------------------
>>> 3. BUILDING A RELEASE:
>>> ---------------------------------------------------------------
>>>
>>> Building a TEI Release:
>>> <http://www.tei-c.org/Activities/Council/Working/tcw22.xml>
>>> (Our current practice is to ask a relatively new member of Council to
>>> act as "Release Technician" for each new release of the Guidelines. A
>>> team of experienced members is always available to monitor and help, but
>>> the idea is that our new member should be able to follow the
>>> documentation in TCW 22 successfully; this helps to confirm that the
>>> documentation is up to date and accurate, and each time we do this, we
>>> clarify and expand TCW 22.
>>>
>>> ---------------------------------------------------------------
>>> If anything crucial is missing from this list, please let me know.
>>>
>>> Cheers,
>>> Martin
>>> --
>>> tei-council mailing list
>>> tei-council at lists.village.Virginia.EDU
>>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>>
>>> PLEASE NOTE: postings to this list are publicly archived
>> --
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>
>> PLEASE NOTE: postings to this list are publicly archived
>>