Re: Fwd: Using MSH Paris Nord server
Il giorno lun, 30/07/2012 alle 15.21 +0100, Graham Percival ha scritto: Ok. I just want to emphasize that you could easily spend 20 hours setting this up, but then have the response be no, we prefer the old system. I got it :-P oh, logins just occurred to me. Can gerrit let people log in with their google accounts (IIRC there's an api for that), or would we all need to make new accounts on the gerrit server? The two options are * using OpenId, see http://openid.net/get-an-openid/ (with the suboption of restricting it to logins through HTTPS, or to Google accounts) * setting up HTTP(S) authentification, requiring all of us to make new accounts on that server. I'm currently setting up the server with the default (OpenId), but I don't mind changing it if there are strong wishes for the other option. John ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Using MSH Paris Nord server
Il giorno mar, 31/07/2012 alle 12.12 +0200, John Mandereau ha scritto: I'm currently setting up the server with the default (OpenId), but I don't mind changing it if there are strong wishes for the other option. Uh oh, OpenId login hits on the firewall (I haven't requested outgoing HTTPS connexions to be accepted), and the network administrator is on vacation until August 8th, so don't hold your breath. I could mess with setting up HTTP Authenication and an account management service (not included in Gerrit), but this would take me oodles of time (taking into account security to a reasonable extent) as I've never done it. Best, John ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Using MSH Paris Nord server
On Mon, Jul 30, 2012 at 01:48:15PM +0200, John Mandereau wrote: From: John Mandereau john.mander...@gmail.com 2012/7/30 David Kastrup d...@gnu.org: Here is what I see as the required steps: -snip steps- At this point of time, it becomes feasible to sensibly test one setup against the other for a typical developer. Yes. However, a Gerrit setup for LilyPond alone will certainly help having a global eye on submitted patches, and avoid creating Google Code issues for patches that are not bug fixes. I'm not convinced that this is an advantage. I'd rather have one central place to look for patches and their status (currently google code, filtered by has:Patch and sorted based on patch status[1]). If not bug fixes patches aren't listed in the same place as bug fix patches, then we'll have two websites to check and keep up-to-date. In short: we already have a global eye on submitted patches, provided that people use git-cl. If they don't use git-cl, then it doesn't matter whether the backend is rietveld or gerrit; the patch will be lost in limbo on lilypond-devel until some kind developer steps in. Don't get me wrong: I have nothing against switching the backend from rietveld to gerrit. I just want to keep the google code frontend. [1] sorry, icky url: http://code.google.com/p/lilypond/issues/list?can=2q=has:Patchsort=patch IMO all developers should have this bookmarked. Of course, if we later find that everybody finds Gerrit too cumbersome to use, or if we get serious protests against reviews being even placed there, the work invested up to that point may be wasted. Wasting time setting up Gerrit was my concern, but now it's no longer. I'll chime in back when I have done steps a) and b). Ok. I just want to emphasize that you could easily spend 20 hours setting this up, but then have the response be no, we prefer the old system. oh, logins just occurred to me. Can gerrit let people log in with their google accounts (IIRC there's an api for that), or would we all need to make new accounts on the gerrit server? - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Using MSH Paris Nord server
On 30/07/2012 16:21, Graham Percival wrote: oh, logins just occurred to me. Can gerrit let people log in with their google accounts (IIRC there's an api for that), or would we all need to make new accounts on the gerrit server? IIRC, gerrit works with any openID service... A while ago I set up gerrit on my server to evaluate it (I even posted it here), but I have meanwhile removed the installation again, as it seemed no one was really interested. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://www.kainhofer.com * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * Edition Kainhofer, Music Publisher, http://www.edition-kainhofer.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Using MSH Paris Nord server
Reinhold Kainhofer reinh...@kainhofer.com writes: On 30/07/2012 16:21, Graham Percival wrote: oh, logins just occurred to me. Can gerrit let people log in with their google accounts (IIRC there's an api for that), or would we all need to make new accounts on the gerrit server? IIRC, gerrit works with any openID service... A while ago I set up gerrit on my server to evaluate it (I even posted it here), but I have meanwhile removed the installation again, as it seemed no one was really interested. Without test-patchy understanding Gerrit URLs, there is really no way in which one can actually test this in connection with LilyPond development. In addition I would have needed a login IIRC. I agree with Graham that a transition is not feasible unless we can continue working with the Google Code frontend. A frontend move would be much more of a non-reversible change than supporting another backend. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Using MSH Paris Nord server
2012/7/30 Graham Percival gra...@percival-music.ca: I'm not convinced that this is an advantage. I'd rather have one central place to look for patches and their status (currently google code, filtered by has:Patch and sorted based on patch status[1]). If not bug fixes patches aren't listed in the same place as bug fix patches, then we'll have two websites to check and keep up-to-date. I have never meant this. I meant that if we decide to adopt Gerrit, then *all* pending patches will be on Gerrit, but patches that don't come from bug reports on Google Code tracker needn't be added there. In short: we already have a global eye on submitted patches, provided that people use git-cl. Gerrit can provide this as well, and might offer a better global eye than a generic issue tracker, be it an excellent one like Google Code. Don't get me wrong: I have nothing against switching the backend from rietveld to gerrit. I just want to keep the google code frontend. We certainly agree on this as long as we use Rietveld for patches review, but if we find a better tool that provides a good frontend for patches review that can also integrate with Google code, then there's no reason to keep Google code as the frontend. Ok. I just want to emphasize that you could easily spend 20 hours setting this up, but then have the response be no, we prefer the old system. I've already evaluated this, so I don't mind :-) John ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: Using MSH Paris Nord server
John Mandereau john.mander...@gmail.com writes: 2012/7/30 Graham Percival gra...@percival-music.ca: I'm not convinced that this is an advantage. I'd rather have one central place to look for patches and their status (currently google code, filtered by has:Patch and sorted based on patch status[1]). If not bug fixes patches aren't listed in the same place as bug fix patches, then we'll have two websites to check and keep up-to-date. I have never meant this. I meant that if we decide to adopt Gerrit, then *all* pending patches will be on Gerrit, but patches that don't come from bug reports on Google Code tracker needn't be added there. In short: we already have a global eye on submitted patches, provided that people use git-cl. Gerrit can provide this as well, and might offer a better global eye than a generic issue tracker, be it an excellent one like Google Code. There is no point arguing this. We can't do a reasonable side-by-side comparison and/or transition if we don't work with the same frontend. The decision to change the frontend would be a rather invasive one, and one can't use more than one frontend in parallel since the point of the frontend is to provide a _complete_ overview over existing issues. We certainly agree on this as long as we use Rietveld for patches review, but if we find a better tool that provides a good frontend for patches review that can also integrate with Google code, then there's no reason to keep Google code as the frontend. Again: wrong time to argue this. One thing after the other. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
