<tzviya> pass code: Guest Passcode: 743 924 7118

<tzviya> https://mtginfo.pgi.com/globalcallmanagement.asp?bwebid=9820041&cid=da6ee6bfd7ec5a15d77bfcef4d4a&confid=da6ee6bdd7ee5a11d778fcee4d4f82df4254&brandid=1

<tzviya> look up your country

<Tobias> what's the meeting link again?

<Tobias> cannot login

<tzviya> webex is not working

<tzviya> please go to https://mtginfo.pgi.com/globalcallmanagement.asp?bwebid=9820041&cid=da6ee6bfd7ec5a15d77bfcef4d4a&confid=da6ee6bdd7ee5a11d778fcee4d4f82df4254&brandid=1

<tzviya> look up your country

<tzviya> pass code: 743 924 7118

<dauwhe> dial the number, enter the passcode

<dauwhe> https://mtginfo.pgi.com/globalcallmanagement.asp?bwebid=9820041&cid=da6ee6bfd7ec5a15d77bfcef4d4a&confid=da6ee6bdd7ee5a11d778fcee4d4f82df4254&brandid=1

<tzviya> 743 924 7118

<dauwhe> find your country there, call the number, enter the code that tzviya just posted

scribe wolfgang

<tzviya> scribenick: wolfgang

tzviya: none of us did their homework

<Julian_Calderazi> hi all. Can someone post the webex link pls?

only Tobias and Romain were working

what could we do to clean up the site?

tzviya: what could be done?

*congrats and all the best!

Tobias: 4.1 milestones had precedence

Romain: CPO of Daisy, very busy

<tzviya> https://github.com/IDPF/epubcheck/wiki/TestSuiteCleanup

Tzviya: new dir structure on the wiki

*but where is the physical location of the new dirs?

<Julian_Calderazi> here I am (#7) ;)

<Rachel> as someone who is new to this I could use a quick review if there's time

Tobias: from mid-September a demo clean-up as pull request

tzviya: instructions a bit confusing, but you need to be comfortable with github and epub

Julian: familiar with Github

tzviya: Romain and Tobias will be ready to help
... tests assigned to individuals.

brady found out that tests were interdependent on each other

<rdeltour> brady said:

<rdeltour> Regrets, I will still be riding around in a convertible. I poked a bit at my assignment, but haven't actually done much. Looking at one of my files, it turns out is fairly related to all the files in the directory, and really should be condensed into some unit tests. For instance, two of the files differ only in the way times are specified for clips in MO (and the other two files are based on those two with only minor changes). So not only are there two

<rdeltour> full MO files around just to check time formats, they don't really do a very good job of it; there are bunch of correct values, with essentially no variation and no edge case tests. Ugh. I think they should just be deleted and replaced with unit tests.

Tobias: as non-developer it's a task that may be too hard.

Romain: historically, epubcheck uses integration tests rather than single unit tests.
... clean up the extant integration tests and not set up new unit tests.
... Brady used scripts to distribute the work. Manually or via script? Create issues on the tracker in case of problems.

Actual distribution of the work? Related tests should be kept together.

+1 for Rachels proposal

tzviya: people should work on what they are interested in

wait for sample pull request

and each should look at 5 tests he/she is interested in

meet at the end of September and check whether this works

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: tzviya dauwhe wolfgang Rachel rdeltour
Found ScribeNick: wolfgang
Inferring Scribes: wolfgang

WARNING: No "Topic:" lines found.


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 31 Aug 2017
Guessing minutes URL: http://www.w3.org/2017/08/31-epubcheck-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report