Re: Fwd: Google Code shutting down
On 13/03/15 12:51, David Kastrup wrote: GitLab (like GitHub) does not run on free software. They have some community version of their software freely available at least. Gitorious was eating its own dog food with regard to running on their free software version, but they have just been acquired by GitLab, and due to licensing differences, Gitorious software will not be mixed with either version of GitLab. So the outlook for further company development of Gitorious is somewhat dim. Now Savannah is running on a continuation of the last free version of SourceForge if I remember correctly, so that would not be a real showstopper for picking up there. But the situation overall is a nuisance. Might be worth keeping a weather eye on Launchpad, as this is free software and is currently in the process of gaining git support: https://help.launchpad.net/Code/Git It's been a while since I last used it, but it has a nice combination of issue tracking, code review and hosting features. AFAICS it'll also support file attachments to issues, so should be able to support copying the .png's from Lilypond's current issue tracker. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Google Code shutting down
On Fri, Mar 13, 2015 at 4:40 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
have a look at
https://code.google.com/p/support-tools/wiki/IssueExporterTool
That is quite useful, thanks. I've exported the LilyPond Issues
DB to a JSON file on my laptop. 5Mb. It seems complete as far
as the text goes, but images do not seem to be included, as least
for the one issue I've inspected in detail (Issue 4005). All
the JSON file says for the image is:
attachments : [ {
attachmentId : 40050007000,
fileName : Screenshot.png,
fileSize : 137527,
mimetype : image/png
} ]
but I don't see any attachments anywhere in the download.
I'll send mail to the folks handling this to mention this, but you can
do it manually:
You can extract the attachments from the HTML sources:
wget --quiet -O-
'https://code.google.com/p/lilypond/issues/detail?id=4316'|grep
/attachatt.txt
$ grep 2-19-16.png att.txt|head -1
a
href=//lilypond.googlecode.com/issues/attachment?aid=4316000amp;name=atest-2-19-16.pngamp;token=ABZ6GAcfLZCKQxStq2tURaM_f0RSDPjJFw%3A142633422
this is the URL, minus the protocol part. For some reason, the in
the URL has been escaped.
$ wget $(echo
'https://lilypond.googlecode.com/issues/attachment?aid=4316000amp;name=atest-2-19-16.pngamp;token=ABZ6GAeDaPOMP8ZuFedDBpB7Z3xy01aM0g%3A1426334055154amp;inline=1'
| sed 's/amp;/\/g')
--2015-03-14 13:00:10--
https://lilypond.googlecode.com/issues/attachment?aid=4316000name=atest-2-19-16.pngtoken=ABZ6GAeDaPOMP8ZuFedDBpB7Z3xy01aM0g%3A1426334055154inline=1
Resolving lilypond.googlecode.com (lilypond.googlecode.com)...
74.125.136.82, 2a00:1450:4013:c01::52
Connecting to lilypond.googlecode.com
(lilypond.googlecode.com)|74.125.136.82|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1749 (1.7K) [image/png]
Saving to:
‘attachment?aid=4316000name=atest-2-19-16.pngtoken=ABZ6GAeDaPOMP8ZuFedDBpB7Z3xy01aM0g%3A1426334055154inline=1’
attachment?aid=4316000name=atest-2-19-
100%[=]
1.71K --.-KB/s in 0s
2015-03-14 13:00:11 (24.3 MB/s) -
‘attachment?aid=4316000name=atest-2-19-16.pngtoken=ABZ6GAeDaPOMP8ZuFedDBpB7Z3xy01aM0g%3A1426334055154inline=1’
saved [1749/1749]
You can loop over the issues (4000-something), extract a ID = URL
mapping and then download them. If you do this, you may need to rate
limit this so you don't get anti-robot captchas.
Trevor
--
Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Fwd: Google Code shutting down
I guess most of you have seen this by now. I can click the export button so all the issues are migrated to github. Thoughts, ideas? Didn't someone setup a lilypond organization at github? -- Forwarded message -- From: google-code-nore...@google.com Date: Fri, Mar 13, 2015 at 2:11 AM Subject: Google Code shutting down To: hanw...@gmail.com Code Hello, Earlier today, Google announced we will be turning down Google Code Project Hosting. The service started in 2006 with the goal of providing a scalable and reliable way of hosting open source projects. Since that time, millions of people have contributed to open source projects hosted on the site. But a lot has changed since 2006. In the past nine years, many other options for hosting open source projects have popped up, along with vibrant communities of developers. It’s time to recognize that Google Code’s mission to provide open source projects a home has been accomplished by others, such as GitHub and Bitbucket. We will be shutting down Google Code over the coming months. Starting today, the site will no longer accept new projects, but will remain functionally unchanged until August 2015. After that, project data will be read-only. Early next year, the site will shut down, but project data will be available for download in an archive format. As the owner of the following projects, you have several options for migrating your data. lilypond The simplest option would be to use the Google Code Exporter, a new tool that will allow you to export your projects directly to GitHub. Alternatively, we have documentation on how to migrate to other services — GitHub, Bitbucket, and SourceForge — manually. For more information, please see the Google Open Source blog or contact google-code-shutd...@google.com. -The Google Code team Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043 You have received this mandatory email service announcement to update you about important changes to Google Code Project Hosting. -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Google Code shutting down
On Fri, Mar 13, 2015 at 11:33:22AM +0100, Han-Wen Nienhuys wrote: I can click the export button so all the issues are migrated to github. Thoughts, ideas? Didn't someone setup a lilypond organization at github? There was some discussion about that, which spilled over to gnu-hackers or gnu-devel or whatever it's called. Pending some investigation about the javascript libraries or scripts used on github.com, it's tentatively seen as reluctantly acceptable to host GNU software there. A few people spoke highly in favor of gitlab, but I'm not familiar with them so I can't say anything one way or the other. In addition to moving the issues, the issue handling scripts would need to be updated. Things like git-cl, patchy, and the whole patch-submission system. That will be a non-trivial effort. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Google Code shutting down
On Fri, Mar 13, 2015 at 12:04 PM, David Kastrup d...@gnu.org wrote: I suspect that there will not be much hope for transferring the Rietveld reviews over into something Git-based and reasonably equivalent, but they are less important than getting everything out of the issue tracker. Rietveld is not part of google code. It would appear that we have until August to move. -- David Kastrup -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Google Code shutting down
Am 13.03.2015 um 11:33 schrieb Han-Wen Nienhuys: I guess most of you have seen this by now. I can click the export button so all the issues are migrated to github. Thoughts, ideas? Didn't someone setup a lilypond organization at github? Yes, that was Janek. But it was considered problematic due to Github's unpredictable TOS. Apart from that: As much as I like working with Github, and especially the Pull Request workflows are way more convenient than our Rietveld on IMO, the lightweight issue tracker is much too lightweight compared to our current Google tracker. Urs -- Forwarded message -- From: google-code-nore...@google.com Date: Fri, Mar 13, 2015 at 2:11 AM Subject: Google Code shutting down To: hanw...@gmail.com Code Hello, Earlier today, Google announced we will be turning down Google Code Project Hosting. The service started in 2006 with the goal of providing a scalable and reliable way of hosting open source projects. Since that time, millions of people have contributed to open source projects hosted on the site. But a lot has changed since 2006. In the past nine years, many other options for hosting open source projects have popped up, along with vibrant communities of developers. It’s time to recognize that Google Code’s mission to provide open source projects a home has been accomplished by others, such as GitHub and Bitbucket. We will be shutting down Google Code over the coming months. Starting today, the site will no longer accept new projects, but will remain functionally unchanged until August 2015. After that, project data will be read-only. Early next year, the site will shut down, but project data will be available for download in an archive format. As the owner of the following projects, you have several options for migrating your data. lilypond The simplest option would be to use the Google Code Exporter, a new tool that will allow you to export your projects directly to GitHub. Alternatively, we have documentation on how to migrate to other services — GitHub, Bitbucket, and SourceForge — manually. For more information, please see the Google Open Source blog or contact google-code-shutd...@google.com. -The Google Code team Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043 You have received this mandatory email service announcement to update you about important changes to Google Code Project Hosting. -- Urs Liska www.openlilylib.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Google Code shutting down
Graham Percival gra...@percival-music.ca writes: On Fri, Mar 13, 2015 at 11:33:22AM +0100, Han-Wen Nienhuys wrote: I can click the export button so all the issues are migrated to github. Thoughts, ideas? Didn't someone setup a lilypond organization at github? There was some discussion about that, which spilled over to gnu-hackers or gnu-devel or whatever it's called. Pending some investigation about the javascript libraries or scripts used on github.com, it's tentatively seen as reluctantly acceptable to host GNU software there. A few people spoke highly in favor of gitlab, but I'm not familiar with them so I can't say anything one way or the other. GitLab (like GitHub) does not run on free software. They have some community version of their software freely available at least. Gitorious was eating its own dog food with regard to running on their free software version, but they have just been acquired by GitLab, and due to licensing differences, Gitorious software will not be mixed with either version of GitLab. So the outlook for further company development of Gitorious is somewhat dim. Now Savannah is running on a continuation of the last free version of SourceForge if I remember correctly, so that would not be a real showstopper for picking up there. But the situation overall is a nuisance. In addition to moving the issues, the issue handling scripts would need to be updated. Things like git-cl, patchy, and the whole patch-submission system. That will be a non-trivial effort. You bet. It would appear like Rietveld will stick around for longer, but of course moving away from this Subversion-centric piece of our infrastructure would also make sense. But at least we have a different time frame for that. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Google Code shutting down
David Kastrup wrote Friday, March 13, 2015 11:51 AM Subject: Re: Fwd: Google Code shutting down Graham Percival gra...@percival-music.ca writes: In addition to moving the issues, the issue handling scripts would need to be updated. Things like git-cl, patchy, and the whole patch-submission system. That will be a non-trivial effort. You bet. It would appear like Rietveld will stick around for longer, but of course moving away from this Subversion-centric piece of our infrastructure would also make sense. But at least we have a different time frame for that. AFAIK the issues database and associated comments are the only part of Google Code that we, the LilyPond community, use. It is vital we don't lose this. Two questions: (a) how do we take a copy of this data base to keep it safe, including all the follow-up discussions? Making a CSV copy just seems to download the index. (b) Is Google Code open-source or proprietary? Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Google Code shutting down
Han-Wen Nienhuys hanw...@gmail.com writes: I guess most of you have seen this by now. Not really. I can click the export button so all the issues are migrated to github. Thoughts, ideas? I don't really want LilyPond to move to GitHub. I prefer figuring out what resources we would need from Savannah and work out what it takes to get the stuff set up properly and our workflows go at least as smoothly as we have them now. And of course we don't want to lose all of our issue database. I suspect that there will not be much hope for transferring the Rietveld reviews over into something Git-based and reasonably equivalent, but they are less important than getting everything out of the issue tracker. It would appear that we have until August to move. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Google Code shutting down
Trevor Daniels t.dani...@treda.co.uk writes:
Han-Wen, you wrote Friday, March 13, 2015 1:45 PM
On Fri, Mar 13, 2015 at 1:37 PM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Two questions:
(a) how do we take a copy of this data base to keep it safe,
including all the follow-up discussions? Making a CSV
copy just seems to download the index.
have a look at
https://code.google.com/p/support-tools/wiki/IssueExporterTool
That is quite useful, thanks. I've exported the LilyPond Issues
DB to a JSON file on my laptop. 5Mb. It seems complete as far
as the text goes, but images do not seem to be included, as least
for the one issue I've inspected in detail (Issue 4005). All
the JSON file says for the image is:
attachments : [ {
attachmentId : 40050007000,
fileName : Screenshot.png,
fileSize : 137527,
mimetype : image/png
} ]
but I don't see any attachments anywhere in the download.
5Mb would certainly not cut it for including the attachments: they
were/are sort of a running quota problem.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Google Code shutting down
On Fri, Mar 13, 2015 at 1:37 PM, Trevor Daniels t.dani...@treda.co.uk wrote: David Kastrup wrote Friday, March 13, 2015 11:51 AM Subject: Re: Fwd: Google Code shutting down Graham Percival gra...@percival-music.ca writes: In addition to moving the issues, the issue handling scripts would need to be updated. Things like git-cl, patchy, and the whole patch-submission system. That will be a non-trivial effort. You bet. It would appear like Rietveld will stick around for longer, but of course moving away from this Subversion-centric piece of our infrastructure would also make sense. But at least we have a different time frame for that. Rietveld is open source https://cloud.google.com/appengine/articles/rietveld that said, it is not very reliable or oriented towards git. Most of the git work at google (eg. Android) today actually uses Gerrit, which a Git-only code review system which is more reliable and performant. Gerrit is open-source, and GNU/FSF could host an instance too. There are hosted versions of these as well, eg. http://gerrithub.io/ AFAIK the issues database and associated comments are the only part of Google Code that we, the LilyPond community, use. It is vital we don't lose this. Two questions: (a) how do we take a copy of this data base to keep it safe, including all the follow-up discussions? Making a CSV copy just seems to download the index. have a look at https://code.google.com/p/support-tools/wiki/IssueExporterTool (b) Is Google Code open-source or proprietary? It's proprietary. It runs on a host of Google production technologies, such as Bigtable, to be able to scale, and integrates with a bunch of other technologies (Google login, e-mail, etc.) -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Google Code shutting down
Han-Wen, you wrote Friday, March 13, 2015 1:45 PM
On Fri, Mar 13, 2015 at 1:37 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
Two questions:
(a) how do we take a copy of this data base to keep it safe,
including all the follow-up discussions? Making a CSV
copy just seems to download the index.
have a look at
https://code.google.com/p/support-tools/wiki/IssueExporterTool
That is quite useful, thanks. I've exported the LilyPond Issues
DB to a JSON file on my laptop. 5Mb. It seems complete as far
as the text goes, but images do not seem to be included, as least
for the one issue I've inspected in detail (Issue 4005). All
the JSON file says for the image is:
attachments : [ {
attachmentId : 40050007000,
fileName : Screenshot.png,
fileSize : 137527,
mimetype : image/png
} ]
but I don't see any attachments anywhere in the download.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
