I've fixed the tickets with even numbers and committed to SVN - hopefully that was fine and I haven't broken anything :) Raff On Thu, Jan 22, 2015 at 4:28 AM, Majewski Stefan wrote:

Hi Martin, dear fellow council members,

thanks that was somewhat what I was hoping for; some bugs that are easy to start with to get into the project specific workflows. It might well be that I am coming back to my mentor -- also thanks for this -- with a few questions. But first of all I'll dive into the docs.

kind regards and thanks,

Stefan

Am 22.01.2015 05:30, schrieb Martin Holmes:

Hi all,

...

Jens Østergaard Petersen just read the CH-LanguagesCharacterSets.xml prefatory chapter:

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CH.html

and as he often does, took the trouble to report a bunch of minor issues and typos. I was going to trawl through these tonight, but it crossed my mind that they might be useful for the new Council members to do their first Guidelines edits with. Raffaele and Stefan, what do you think? These are the bugs that are straightforward fixes:

http://sourceforge.net/p/tei/bugs/707/ http://sourceforge.net/p/tei/bugs/708/ http://sourceforge.net/p/tei/bugs/709/ http://sourceforge.net/p/tei/bugs/711/ http://sourceforge.net/p/tei/bugs/712/ http://sourceforge.net/p/tei/bugs/714/ http://sourceforge.net/p/tei/bugs/716/ http://sourceforge.net/p/tei/bugs/717/

There are a few others, but they need at least a look; the final one calls for a complete section to be deleted or revised, and I tend to agree with him, but it'll need some discussion.

Raffaele and Stefan, if you think it would be useful to try editing the Guidelines with some straightforward bugs like this, I'd suggest Raffaele take the even-numbered ones and Stefan the odd-numbered ones, so you don't step on each other's feet, and have a go. Below is a copy of the instructions I sent around in December.

If you don't think it's of value to do this, just post to the list and I'll make these fixes.

--------------------------------------------------------------- 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.) ---------------------------------------------------------------

Cheers, Martin

-- Mag. Stefan Majewski Projektmanager Abteilung Forschung und Entwicklung Österreichische Nationalbibliothek

Josefsplatz 1, 1015 Wien Tel.: (+43 1) 534 10-434 E-Mail: stefan.majewski@onb.ac.at Skype: stefan.majewski.onb.ac.at

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

Once the build is complete (as it is now), you can check out your changes in the "last successful build" area of Jenkins: http://teijenkins.hcmc.uvic.ca/job/TEIP5/lastSuccessfulBuild/artifact/releas... Cheers, Martin On 15-01-22 08:12 AM, Martin Holmes wrote:

On 15-01-22 07:08 AM, Raffaele Viglianti wrote:

...

I've fixed the tickets with even numbers and committed to SVN - hopefully that was fine and I haven't broken anything :)

Everything looks good. Mr Jenkins is working away:

http://teijenkins.hcmc.uvic.ca/

If anything were to go wrong, you should see it on Jenkins (a red ball on one of the three tasks at the bottom), and you would get an email (sent by Jenkins to your SourceForge address).

The only thing I would suggest is that when you're closing a bug, it's conventional to add a note giving the revision number at which you committed the change. That's been handy for us in the past.

I'll write to Jens and thank him for his careful proofing. He's submitted dozens of these tickets over the past few years.

Cheers, Martin

...

Raff

On Thu, Jan 22, 2015 at 4:28 AM, Majewski Stefan wrote:

...

Hi Martin, dear fellow council members,

thanks that was somewhat what I was hoping for; some bugs that are easy to start with to get into the project specific workflows. It might well be that I am coming back to my mentor -- also thanks for this -- with a few questions. But first of all I'll dive into the docs.

kind regards and thanks,

Stefan

Am 22.01.2015 05:30, schrieb Martin Holmes:

Hi all,

...

Jens Østergaard Petersen just read the CH-LanguagesCharacterSets.xml prefatory chapter:

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CH.html

and as he often does, took the trouble to report a bunch of minor issues and typos. I was going to trawl through these tonight, but it crossed my mind that they might be useful for the new Council members to do their first Guidelines edits with. Raffaele and Stefan, what do you think? These are the bugs that are straightforward fixes:

http://sourceforge.net/p/tei/bugs/707/ http://sourceforge.net/p/tei/bugs/708/ http://sourceforge.net/p/tei/bugs/709/ http://sourceforge.net/p/tei/bugs/711/ http://sourceforge.net/p/tei/bugs/712/ http://sourceforge.net/p/tei/bugs/714/ http://sourceforge.net/p/tei/bugs/716/ http://sourceforge.net/p/tei/bugs/717/

There are a few others, but they need at least a look; the final one calls for a complete section to be deleted or revised, and I tend to agree with him, but it'll need some discussion.

Raffaele and Stefan, if you think it would be useful to try editing the Guidelines with some straightforward bugs like this, I'd suggest Raffaele take the even-numbered ones and Stefan the odd-numbered ones, so you don't step on each other's feet, and have a go. Below is a copy of the instructions I sent around in December.

If you don't think it's of value to do this, just post to the list and I'll make these fixes.

--------------------------------------------------------------- 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.) ---------------------------------------------------------------

Cheers, Martin

-- Mag. Stefan Majewski Projektmanager Abteilung Forschung und Entwicklung Österreichische Nationalbibliothek

Josefsplatz 1, 1015 Wien Tel.: (+43 1) 534 10-434 E-Mail: stefan.majewski@onb.ac.at Skype: stefan.majewski.onb.ac.at

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

2015-01-22 17:12 GMT+01:00 Martin Holmes :

On 15-01-22 07:08 AM, Raffaele Viglianti wrote:

...

I've fixed the tickets with even numbers and committed to SVN - hopefully that was fine and I haven't broken anything :)

Everything looks good. Mr Jenkins is working away:

http://teijenkins.hcmc.uvic.ca/

If anything were to go wrong, you should see it on Jenkins (a red ball on one of the three tasks at the bottom), and you would get an email (sent by Jenkins to your SourceForge address).

Great, I have also fixed my lot. Looks good, I validated it locally after committing my fixes. I wondered, is there a way to just use the bug/issue tracker number of the bug in the commit message and by some magic behind the scenes (e.g. triggered by a keyword FIXED or similar) close the bug and add the message as comment? Thanks and kind regards, Stefan

I thought it *must* be there and was looking for it during the last Council meeting but apparently failed. There is no such feature like we have with GitHub [1] ;) Best Peter [1] https://help.github.com/articles/closing-issues-via-commit-messages/

Am 22.01.2015 um 19:16 schrieb Martin Holmes :

Hi Stefan,

On 15-01-22 09:27 AM, Stefan Majewski wrote:

...

Great, I have also fixed my lot. Looks good, I validated it locally after committing my fixes. I wondered, is there a way to just use the bug/issue tracker number of the bug in the commit message and by some magic behind the scenes (e.g. triggered by a keyword FIXED or similar) close the bug and add the message as comment?

That would be nice, eh? I haven't found any documentation for any such feature in SourceForge. Does anyone else know of anything like this?

Cheers, Martin

...

Thanks and kind regards, Stefan

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

That answers my last question! :-) And I also see Martin gave you and Stefan how-to-check info. Good.

I've fixed the tickets with even numbers and committed to SVN - hopefully that was fine and I haven't broken anything :)