Re: [tei-council] co-operative stylesheet education session #8

I'm happy to reschedule to any weekday. I've got nothing going on at 6 in the morning. :-) Cheers, Martin On 2017-04-15 12:04 PM, Scholger, Martina (martina.scholger@uni-graz.at) wrote:

Hi,

great idea! I would appreciate more practice with forking and pulling. However, I wasn't bored and learned a lot during the last sessions.

Concerning the schedule: I don't have fixed dates in the afternoon (CET) except on Tuesdays.

Best, Martina

-----Ursprüngliche Nachricht----- Von: tei-council-bounces@lists.tei-c.org [mailto:tei-council-bounces@lists.tei-c.org] Im Auftrag von Elisa Beshero-Bondar Gesendet: Samstag, 15. April 2017 17:57 An: tei-council@lists.tei-c.org Betreff: Re: [tei-council] co-operative stylesheet education session #8

I just realized that I skipped over the end-of-April/start-of-May meeting. As far as I know, I should be okay to attend on Thurs. May 4. I probably won't have had time to experiment much with code ahead of that meeting, however--it's the very end of my campus's semester and I'll just be emerging then from under a mountain of grading.

For my part, Thurs. May 4 is a good moment to *begin* a forking and pulling experiment, and also probably just about the moment when I'll attend to my mountain of delayed action on TEI tickets. I realize you can't schedule these things around me, but I do like the idea of an active experimentation as the best way to learn one's way around the Stylesheets, and I really hope to participate. I wonder if anyone else's schedules are stacked like mine?

Elisa

On Sat, Apr 15, 2017 at 11:50 AM, Elisa Beshero-Bondar wrote:

...

Hi Council and Stylesheets crew-- I wish I'd been able to attend the last Stylesheets meeting--I've been learning much from you (Martin) and Syd in the preceding sessions, but I'll agree that the passive watching of two very active participants can only go so far. I like your idea to have us fork the Stylesheets repo, create fixes, and submit them by pull requests, since this will be a good way to encourage active learning.

Here's a problem for me: If we adhere to the current Stylesheets meeting schedule, I'm probably about to miss the *next* Stylesheets meeting, too (and possibly others of us will, as well), because of the STS conference hosted by MITH on Wed. May 31 - Fri. June 2. I'm actually scheduled to present on Thurs. June 1 at 9am EST, which I think is exactly when the next Stylesheets meeting is supposed to be, right? I don't really want to be missing these, and especially not two in a row, but I don't think I'll have much choice if we stick to the usual schedule.

Since this particular conference is likely a schedule handicap for others among us, and since scheduling is about to get weird for June and July as well, I wonder if we should revisit our calendars?

Thanks, Elisa

On Fri, Apr 14, 2017 at 9:20 PM, Martin Holmes wrote:

...

Hi all,

Syd and I were talking today about how the last meeting went, and thinking that it was rather too much of him and me editing code and nobody else doing anything, which is perhaps boring and unhelpful. We thought we might try something else next time:

Assuming we can identify a relatively small issue that's isolated and looks fixable without major work, we thought we could ask everyone in the group ahead of time to do this:

- Fork the repo

- Create and test a fix in their fork

Then at the group meeting, everyone who thinks they've successfully solved the problem could walk the group through their solution. At the end, if we can agree that someone has a good solution with no bad side-effects, that person could issue a pull request.

That would give everyone a bit of experience working in branches and testing fixes, and give everyone more chance for participation in the meeting.

Does this sound like a good idea?

Cheers, Martin

On 2017-03-31 11:25 AM, Syd Bauman wrote:

...

We are planning to meet next Thu, 04-06 at 13:00Z, i.e.:

Thu 2017-04-06 06:00 PDT (poor Martin) Thu 2017-04-06 09:00 EDT Thu 2017-04-06 14:00 BST Thu 2017-04-06 15:00 CEST

Martin will be sending out details on 2 more issues we thought might be worth addressing. They are https://github.com/TEIC/Stylesheets/issues/246 and another (that I don't think has a ticket yet) which is an error in common/common_figures.xsl (roughly lines 226-240): the stylesheet makes the erroneous assumption that if there is a @width attribute, then there will be a @height attribute.

Moreover, there are still the agenda items from our last meeting, most of which are still to be addressed. They include:

* table review (http://wiki.tei-c.org/index.php/Mapping_ODD_processing) - we still need rows for TEI ODD -> documentation * generation of PDF from within oXygen framework * stylesheet re-write project * re-working the Stylesheet/Test/ suite (see Martin's Test2/, which uses 'ant') * ticket: https://github.com/TEIC/Stylesheets/issues/227

I can try to be the one to establish a Google Hangout and invite people, but I have been remarkably unsuccessful at this in the past. So if anyone would like to volunteer ...

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

-- 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@pitt.edu Development site: http://newtfire.org

-- 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@pitt.edu Development site: http://newtfire.org -- 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