Re: thinking twice about the new issue tracker

Il giorno sab 5 set 2015 alle 2:59, Han-Wen Nienhuys ha scritto: On Wed, Sep 2, 2015 at 6:11 AM, Trevor Daniels wrote: This is on the GC FAQ covering migration to GitHub: Error "Project cannot be migrated because it has too many issues."

Re: thinking twice about the new issue tracker

On Wed, Sep 2, 2015 at 6:11 AM, Trevor Daniels wrote: > This is on the GC FAQ covering migration to GitHub: > >> Error "Project cannot be migrated because it has too many issues." >> There is a hard limit on the number of issues that can be exported >> by the tool, per

Re: thinking twice about the new issue tracker

Il giorno gio 3 set 2015 alle 11:03, Trevor Daniels ha scritto: It works quite well. Status and labels are migrated correctly. Attachments are saved on Github server and displayed inline if they are images (Type-Ugly issues usually have image attachments). Are you

Re: thinking twice about the new issue tracker

Il giorno mer 2 set 2015 alle 18:52, Federico Bruni ha scritto: Il giorno mer 2 set 2015 alle 12:51, Federico Bruni ha scritto: I'm running the import on github. It takes more time, even if I've been whitelisted by github team. I'm currently at: Issue:

Re: thinking twice about the new issue tracker

Il giorno gio 3 set 2015 alle 11:07, David Kastrup ha scritto: "Trevor Daniels" writes: Federico, you wrote Thursday, September 03, 2015 9:24 AM It took about 10 hours. You can see the result here: https://github.com/fedelibre/lilyissues/issues

Re: thinking twice about the new issue tracker

Federico, you wrote Thursday, September 03, 2015 9:24 AM > It took about 10 hours. You can see the result here: > https://github.com/fedelibre/lilyissues/issues It's a pity you didn't do this a couple of months ago so we could have compared Github with Allura properly. It's a bit late now. >

Re: thinking twice about the new issue tracker

"Trevor Daniels" writes: > Federico, you wrote Thursday, September 03, 2015 9:24 AM > >> It took about 10 hours. You can see the result here: >> https://github.com/fedelibre/lilyissues/issues > > It's a pity you didn't do this a couple of months ago so we could > have

Re: thinking twice about the new issue tracker

Federico Bruni writes: > Github, unlike Bitbucket, does not put any restriction to the number > of contributors. And public repositories are free of charge. So IMO > this could have been a possible interim solution. "Free of charge" also means they reserve the right to dump

Re: thinking twice about the new issue tracker

Federico Bruni writes: > Il giorno gio 3 set 2015 alle 11:07, David Kastrup ha > scritto: >> "Trevor Daniels" writes: >> >>> Federico, you wrote Thursday, September 03, 2015 9:24 AM >>> It took about 10 hours. You can see the

Re: thinking twice about the new issue tracker

Federico Bruni wrote Thursday, September 03, 2015 10:21 AM > > Il giorno gio 3 set 2015 alle 11:03, Trevor Daniels > ha scritto: >> >>> It works quite well. Status and labels are migrated correctly. >>> Attachments are saved on Github server and displayed inline if they

Re: thinking twice about the new issue tracker

Federico Bruni writes: > Hi folks > > I know that a lot of time has been invested on Allura, especially by > Trevor. So I feel uneasy in writing this email, but I have the > feeling that the time costraint didn't help to make the best decision > for the new issue tracker.

Re: thinking twice about the new issue tracker

Am 2. September 2015 07:30:09 MESZ, schrieb Federico Bruni : >Hi folks > >I know that a lot of time has been invested on Allura, especially by >Trevor. >So I feel uneasy in writing this email, but I have the feeling that the > >time >costraint didn't help to make the best

Re: thinking twice about the new issue tracker

Il giorno mer 2 set 2015 alle 9:33, David Kastrup ha scritto: I think that on the "evaluate other alternatives" angle it would likely make more sense to go through with getting Allura up and running. As we are so close to get Allura up and running, of course it makes sense.

Re: thinking twice about the new issue tracker

David Kastrup writes: > The main problem I see is that questions like the usefulness of the > documentation, scalability under duress, helpfulness of community, > design of the codebase don't really gain a reliable answer before > taking a full plunge. I was missing a clear

Re: thinking twice about the new issue tracker

Am 02.09.2015 um 09:33 schrieb David Kastrup: Federico Bruni writes: Hi folks I know that a lot of time has been invested on Allura, especially by Trevor. So I feel uneasy in writing this email, but I have the feeling that the time costraint didn't help to make the best

Re: thinking twice about the new issue tracker

Federico Bruni wrote Wednesday, September 02, 2015 6:30 AM > What if we take some time to evaluate other alternatives and in the We don't really have time, unless you don't mind having an hiatus in the historical record of the LilyPond Tracker. I do, which is why I've invested the time and

Re: thinking twice about the new issue tracker

Il giorno mer 2 set 2015 alle 10:09, Urs Liska ha scritto: Am 2. September 2015 07:30:09 MESZ, schrieb Federico Bruni : Hi folks I know that a lot of time has been invested on Allura, especially by Trevor. So I feel uneasy in writing this email, but

Re: thinking twice about the new issue tracker

Il giorno mer 2 set 2015 alle 12:51, Federico Bruni ha scritto: I'm running the import on github. It takes more time, even if I've been whitelisted by github team. I'm currently at: Issue: 659/4567 Let's see how it works. Now, after 6 hours, I'm at 3500/4567. A bit slow

Re: thinking twice about the new issue tracker

David Kastrup wrote Wednesday, September 02, 2015 8:33 AM > At the current point of time, we aren't even on Github/Bitbucket. At > any rate, regarding "promising" solutions there is also the SFC-hosted > Kallithea where we likely would get > more than marginal

Re: thinking twice about the new issue tracker

Phil Holmes wrote Wednesday, September 02, 2015 10:31 AM > Finally, FWIW I have no objection to continuing to use SourceForge for issue > hosting. I realise it counts as non-free and has had issues over including > unwanted functionality in downloads, but Google ain't exactly free either, >

Re: thinking twice about the new issue tracker

Il 02/set/2015 13:17, Trevor Daniels ha scritto: > > > David Kastrup wrote Wednesday, September 02, 2015 8:33 AM > > > At the current point of time, we aren't even on Github/Bitbucket.  At > > any rate, regarding "promising" solutions there is also the SFC-hosted > >

Re: thinking twice about the new issue tracker

Simon Albrecht wrote Wednesday, September 02, 2015 9:34 AM > Am 02.09.2015 um 09:33 schrieb David Kastrup: > >> I seem to remember they announced closing that down in 2016 or so. > > That’s only access via VCS – the actual data ‘will remain online for > years into the future’. Which doesn’t

Re: thinking twice about the new issue tracker

David Kastrup wrote Wednesday, September 02, 2015 11:46 AM > "Trevor Daniels" writes: > >> And we'd be limited to 5 developers, unless we pay, it seems. >> Hardly opensource. > > More like "hardly gratis". I've just glanced cursorily at the site but > saw no obvious

Re: thinking twice about the new issue tracker

Am 02.09.2015 um 11:27 schrieb Federico Bruni: Il giorno mer 2 set 2015 alle 11:11, Trevor Daniels ha scritto: meanwhile we use Bitbucket or Github? Not Free services, I know, but at least their business model seems honest. This is on the GC FAQ covering migration

Re: thinking twice about the new issue tracker

Am 02.09.2015 um 11:59 schrieb Federico Bruni: Il giorno mer 2 set 2015 alle 11:41, Simon Albrecht ha scritto: I made the bitbucket repository public: https://bitbucket.org/fedelibre/lilyissues/issues?status=new=open ‘Access denied’ for me… I made the

Re: thinking twice about the new issue tracker

"Trevor Daniels" writes: >> I made the bitbucket repository public: >> https://bitbucket.org/fedelibre/lilyissues/issues?status=new=open > > I don't see how to set up searches; is that possible? > > And we'd be limited to 5 developers, unless we pay, it seems. > Hardly

Re: thinking twice about the new issue tracker

- Original Message - From: "Federico Bruni" I'm not concerned about the https issue. I'm concerned about the Allura usability and the work on the API/patchy stuff which Phil started recently. I think Allura will need some time to get used to, but once we are

Re: thinking twice about the new issue tracker

Il giorno mer 2 set 2015 alle 11:41, Simon Albrecht ha scritto: I made the bitbucket repository public: https://bitbucket.org/fedelibre/lilyissues/issues?status=new=open ‘Access denied’ for me… I made the repository public, not the issue tracker. Now you can see it

Re: thinking twice about the new issue tracker

Federico Bruni wrote Wednesday, September 02, 2015 10:15 AM > Yes, but I was thinking about using an interim solution for some months > to have some more time to evaluate the self-hosted solutions. > Sourceforge would not be the best interim solution. I think you first need to prove our DB

Re: thinking twice about the new issue tracker

Il giorno mer 2 set 2015 alle 11:11, Trevor Daniels ha scritto: meanwhile we use Bitbucket or Github? Not Free services, I know, but at least their business model seems honest. This is on the GC FAQ covering migration to GitHub: Error "Project cannot be migrated

Re: thinking twice about the new issue tracker

Federico Bruni wrote Wednesday, September 02, 2015 10:27 AM > > Il giorno mer 2 set 2015 alle 11:11, Trevor Daniels > ha scritto: > >>> meanwhile we use Bitbucket or Github? Not Free services, I know, but at >>> least their business model seems honest. >> >> This is on

Re: thinking twice about the new issue tracker

Il giorno mer 2 set 2015 alle 12:41, Simon Albrecht ha scritto: As you already said, the quality of the import is completely insatisfactory. Also I find the UI quite crude, with little flexibility – that’s probably what they offer with the advertised JIRA software,

Re: thinking twice about the new issue tracker

"Trevor Daniels" writes: > David Kastrup wrote Wednesday, September 02, 2015 8:33 AM > >> At the current point of time, we aren't even on Github/Bitbucket. At >> any rate, regarding "promising" solutions there is also the SFC-hosted >> Kallithea

thinking twice about the new issue tracker

Hi folks I know that a lot of time has been invested on Allura, especially by Trevor. So I feel uneasy in writing this email, but I have the feeling that the time costraint didn't help to make the best decision for the new issue tracker. Allura doesn't seem a software which is going to have