[tei-council] state of play

[Martin Holmes]

I've also left open some tickets assigned to me that are mostly 
completed, to remind me to do some follow-up task, such as writing a 
section in the "How to Edit the Guidelines" document.

The problem with some semi-automated system of ticket assignment would 
be that most of us would end up getting tickets that are outside are 
areas of competence; I think that would lead to even more tickets being 
neglected in the long run. At least if you volunteer to take a ticket, 
you're doing so because you understand it fully, or because you feel it 
will be valuable for you to do the necessary background work to get to 
that point.

How about this: once every couple of weeks, James goes through the 
unassigned tickets and makes a determined effort to get someone to take 
each one on. That would also mean that when we get to the ftf, every 
ticket would have one person who's at least looked at it or done some 
work on it.

Cheers,
Martin

On 12-06-17 11:49 AM, Sebastian Rahtz wrote:
>
> On 17 Jun 2012, at 19:33, Lou Burnard wrote:
>
>> What's a
>> bit more worrying is the relatively high number to which no-one has been
>> assigned.
>
> unless we have a round-robin system, on what basis
> can they be semi-automatically assigned? I agree its
> depressing how many we don't seem to look at.
>
> I just did a little trawl and killed half a dozen.
>
> I note some categories of stayer-around:
>
>     - Kevin's corrections to Tite
>     - Roma bug reports
>     - vague "rewrite the whole chapter" requests
>
> which are understandably still open.
> --
> Sebastian Rahtz
> Head of Information and Support Group
> Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
>
>
>
>
>