[tei-council] open issues and planning

[Sebastian Rahtz]

Christian Wittern wrote:
>
> In an ideal world, the specs would have the approval from the Council
> before being handed for translation.  I realize that reality has
> overtaken us here, but it still is a situation that worries me.  Maybe
> we need a status flag on the specs that indicates its state ("proposed",
> "implemented", "tested", "approved") to track its status?
>   
It worries me a little too; but I am also confident that I can work out
for any given spec which of the translations is out of date
at any given time. It isn't completely easy, but doable.
>
>> I did wonder about running trac (http://trac.edgewall.org/) as an aide.
>>     
>
> Do you have experience with this?  It certainly looks good, but we can't
> throw too much ressources on getting this up and runnin
>   
I could justify a bit of work on this (Lou, as part of assessments for
software palette), but there is one flaw - it can't link to the Subversion
on Sourceforge. I *could* set it up to work for 6 months on
its own Subversion, copied from SF, and keep them in sync, but
I am not keen :-} Or we could use it without Subversion.

Is anyone else interested in mechanical assistance like this?
ie taking 50 open issues and managing them in an adhoc
system until they are fixed?


-- 
Sebastian Rahtz      

Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

OSS Watch: JISC Open Source Advisory Service
http://www.oss-watch.ac.uk