Re: git-cl upload has stopped working (so has patchy)

[Trevor Daniels]

James Lowe wrote Friday, May 29, 2015 8:08 AM

> On 28/05/15 18:18, Trevor Daniels wrote:
> 
>> Given this problem I thought it prudent to see if I could still import the 
>> Issues DB from GoogleCode to Allura in SourceForge.  I started the import at 
>> 12 noon today (28 May) and after a disconcertingly long pause before 
>> anything happened it now seems to be proceeding normally.
> 
> I haven't really been following the back-and-forth here, but are we now
> 'decided' on which tracker website we are using?

Seems not yet.

Allura at SourceForge works and looks viable.  It appears to be reasonably 
actively maintained there.  A more-or-less up-to-date copy of our Issues DB is 
already loaded.

Savannah may be prepared to install, maintain and host Allura, or they may be 
prepared to let us install and maintain it.  Don't know who 'us' would be - not 
me, I have no *nix experience.  David says he'll contact them to ask.

The third option is to install and maintain Allura on a server of our own.  I 
believe there may be LilyPond users willing to provide or pay for server 
resources, but we'd need to provide the effort to install and maintain both the 
server code and Allura.  Given the problems Google seem to have had that might 
not be trivial.

AFAIK there is no alternative to Allura on the table, so that seems a de facto 
decision.

And of course the scripts still have to be re-engineered to make life easier, 
whichever option is chosen (or forced on us).

Trevor