[tei-council] f2f agenda

[James Cummings]

On 01/11/13 10:47, Sebastian Rahtz wrote:
>> You'll also note that I've put in a skeleton schedule that
>> alternates between general discussion sessions where you should
>> put topics (I've not moved any of the ones from the bottom of the
>> page yet) and SourceForge Tickets sessions.
> Are you suggesting we add topics to the end, and you will spread them out
> across the available slots; or are you suggesting we edit the slots and add
> yet more topics?

The former. (Though if things need to be discussed on a 
particular day, do let me know or slot it in.)

> I think you need to triage the ones at the bottom to assign a length of time to each,
> and then apportion them across the days. I suspect we already have more
> topics than time, so you may well need to attach indicators of importance to topics.

Precisely what is on my to-do list for early next week.

> We also need a triage of the outstanding SF tickets, and tagging their status.
> A quick glance through suggests that there are a not a few quite general ones in there
> (eg "Need for consistency in terminology relating to TEI conformance”)
> which we could spend a lot of time just wondering about; and some which are really
> just one of us making reminder notes (e.g. "Need for some way to test the oxygen-tei
> package before release”). These are perfectly valid issues, but not at the same point
> on the resolvability scale as (e.g.) "<num> not a part of att.segLike (and thus of att.fragmentable)”.
> I’d volunteer to do the triaging myself, but them i18n efforts in the last few days have put me
> way behind in real work.

Also something on the to-do list for early next week. I was going 
to go through them classifying the unclassified ones as 
red/amber/green as previously but also using the 'priority' field 
to categorise how important they are.

http://wiki.tei-c.org/index.php/TEI-Council-FAQ#What_does_Red.2C_Amber.2C_and_Green_mean_in_classifying_a_ticket.3F

> It would obviously be helpful if everyone scanned the tickets for ones in which
> they have a particular hand and tried to sort them out one way or another.

Yes!

And as a reminder for new council members, please let me have 
your sourceforge username. I can then make you 'developers' on 
the project and thus assign tickets for you to oversee.  Existing 
members, please 'take' tickets by assigning them to yourselves if 
it is one you wish to oversee.  If I give you a ticket that you 
really really don't want, tell me or find someone to swap with. 
As part of the meeting I'll be assigning tickets and since some 
of them will be done next year some will be assigned to new 
members of the council as well!

Please also see
http://wiki.tei-c.org/index.php/TEI-Council-FAQ#How_are_tickets_assigned_in_SourceForge.3F

-James

-- 
Dr James Cummings, James.Cummings at it.ox.ac.uk
Academic IT Services, University of Oxford