Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-14 Thread Trevor Daniels
Assaf Gordon wrote Saturday, March 14, 2015 12:59 AM > On 03/13/2015 07:33 PM, Trevor Daniels wrote: >> All the text in the issues can be extracted as a 5MB JSON file, but the file >> does not include the images. At present I know of no way to extract the >> images in bulk. Individual ones c

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-13 Thread Werner LEMBERG
> assume that the Savane installation on Savannah will eventuall > move to FusionForge). > > There are no such plans at present. Hmm. How does the development of Savannah's bug tracking system work, then? > I would be glad if we could use Savannah > > Ok, I'll look into the image

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-13 Thread Assaf Gordon
On 03/13/2015 07:33 PM, Trevor Daniels wrote: All the text in the issues can be extracted as a 5MB JSON file, but the file does not include the images. At present I know of no way to extract the images in bulk. Individual ones can be downloaded of course. I can send you a copy of the JSON fi

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-13 Thread Noeck
Am 14.03.2015 um 00:33 schrieb Trevor Daniels: > At present I know of no way to extract the images in bulk. As a last resort, a recursive wget could help downloading everything and then use find to see where the pictures are and collect them. Joram ___

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-13 Thread Trevor Daniels
Karl Berry wrote Friday, March 13, 2015 11:03 PM > If it turns out to be useful, we could set up a lilypond-tmp project at > savannah just for purposes of working on the 4000-issue-import. Which > sounds like by far the biggest hurdle to me. Can you dump the current > issues into something read

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-13 Thread Karl Berry
assume that the Savane installation on Savannah will eventuall move to FusionForge). There are no such plans at present. I would be glad if we could use Savannah Ok, I'll look into the image-displaying feature. Unless by some miracle "someone" else gets there first :). while g

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-13 Thread Assaf Gordon
On 03/12/2015 06:11 PM, Werner LEMBERG wrote: Savannah supports web-based 'trackers' (for bugs, supports, tasks, <...> and also using a DebBugs server, for example: However, one extremely important feature is sorely missing from Savannah's bug tracker: the ability to directly display images,

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-13 Thread Noeck
Dear Shane, of those 4311 issues, 1012 are still open all others closed. I can't tell how often they happen but there is a certain classification of severity in the type: 10 Crash 2 Critical (both regressions) 37 Build 212 Defect 196 Ugly 362 Enhancement 71 Documentation 38 Maintai

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-12 Thread Werner LEMBERG
> How many of those issues are the sort that affect users every second > Tuesday after a a blue moon versus critical bugs? I don't understand what you are trying to ask. Please have a look at https://code.google.com/p/lilypond/issues/list to see how we are collecting reports. Note that we

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-12 Thread Werner LEMBERG
> Patches are always welcomed, but I do not know if anyone is > interested in hacking on the current php code to add such a > feature. > > Right, I'm not exactly "interested", but if that single feature > makes the difference between lilypond moving to savannah or > , I'd at least try

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-12 Thread Werner LEMBERG
>> However, one extremely important feature is sorely missing from >> Savannah's bug tracker: the ability to directly display images, >> [...] Are there plans to implement image support? > > Realistically, no. Hmm. Perhaps it's time to open an issue in FusionForge (at least I assume that the Sa

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-12 Thread Shane Brandes
How many of those issues are the sort that affect users every second Tuesday after a a blue moon versus critical bugs? Shane On Thu, Mar 12, 2015 at 6:11 PM, Werner LEMBERG wrote: > >> Issues: >> Savannah supports web-based 'trackers' (for bugs, supports, tasks, >> etc.), for example: >> https

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-12 Thread Karl Berry
Patches are always welcomed, but I do not know if anyone is interested in hacking on the current php code to add such a feature. Right, I'm not exactly "interested", but if that single feature makes the difference between lilypond moving to savannah or , I'd at least try to look at it. Of

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

2015-03-12 Thread Werner LEMBERG
> Issues: > Savannah supports web-based 'trackers' (for bugs, supports, tasks, > etc.), for example: > https://savannah.nongnu.org/bugs/?group=lwip > and also using a DebBugs server, for example: > http://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs However, one extremely important feature