Difference between revisions of "Workgroup to revise the Best Practices for TEI in Libraries"
Jump to navigation
Jump to search
m (→Meeting minutes: added placeholder for 2016-03-07) |
Peter Gorman (talk | contribs) (→Members) |
||
Line 26: | Line 26: | ||
* Antonio Rojas () | * Antonio Rojas () | ||
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu]) | * Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu]) | ||
− | * Peter Gorman () | + | * Peter Gorman (peter.gorman@wisc.edu) |
* Andrew Rouner (andrew.rouner@gmail.com) | * Andrew Rouner (andrew.rouner@gmail.com) | ||
Revision as of 16:00, 7 March 2016
Background
Invitation to participate in revision of Best Practices for TEI in Libraries
Logistics
First Monday of each month
9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC in summer in North America)
People with email addresses listed below will have hangout link sent to them for each meeting. We can do up to 10 people with a regular hangout. If we get more people, we'll find someone with a Google Apps for Education account who can support up to 15(?).
If you can't make it, follow along by reviewing minutes (linked below) and/or watching issues on GitHub and adding comments there.
Members
- Kevin Hawkins (kevin.s.hawkins@gmail)
- stuart yeates ()
- stefanie gehrke (stefanie.gehrke9@gmail.com)
- Elli Mylonas (elli_mylonas@brown.edu)
- James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
- Lisa McAulay ()
- Martin Mueller (martinmueller@northwestern.edu)
- Michelle Dalmau ()
- Antonio Rojas ()
- Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
- Peter Gorman (peter.gorman@wisc.edu)
- Andrew Rouner (andrew.rouner@gmail.com)
Suggested meeting procedure
- Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
- Resume discussions postponed from last meeting.
- Go through issues not yet discussed in order of BP revision ticket triage. For each issue, someone volunteers to summarize the issue:
- If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement.
- If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
- If there is consensus, volunteer implements after the meeting.
- If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing.
- After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.
Meeting minutes
- February 1, 2016
- March 7, 2016