Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, Jun 08, 2016 at 01:46:56PM +, Luca Filipozzi wrote: > Let me rephrase, then: can we have a plan that addresses alioth / git / > gitolite / gitlab / stuff rather than standing up yet another SCM/PM tool > because it's shiny? > > This has more to do with delivering sustainable services

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

Hi, Am 8. Juni 2016 22:47:24 MESZ, schrieb Julien Cristau : >On Wed, Jun 8, 2016 at 15:56:31 +0200, Joachim Breitner wrote: > >> We’ll have to allow for some diversity, if only to try new paths (and >> then, eventually, cut off old ones). Especially as long as there is >>

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, Jun 8, 2016 at 15:56:31 +0200, Joachim Breitner wrote: > We’ll have to allow for some diversity, if only to try new paths (and > then, eventually, cut off old ones). Especially as long as there is > motivation.  > I haven't seen much motivation to maintain alioth (especially the

Re: why, nicely explained (Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, Jun 8, 2016 at 12:39 PM, Milan Kupcevic wrote: > On 06/08/2016 02:55 PM, Michael Lustfield wrote: > > On Wed, 8 Jun 2016 15:47:46 +, Holger Levsen > > > wrote: > >>Thanks for this nice summary. It helped me

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On 06/08/2016 02:08 PM, Milan Kupcevic wrote: > On 06/08/2016 11:19 AM, Felipe Sateler wrote: >> >> So, say I want to contribute to a project I don't normally work in. Steps >> in alioth: >> > > [...] > > Well, I would go this route: > > - git clone > - hack > - git commit -a -v > - git

Re: why, nicely explained (Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On 06/08/2016 02:55 PM, Michael Lustfield wrote: > On Wed, 8 Jun 2016 15:47:46 +, Holger Levsen > > wrote: >>Thanks for this nice summary. It helped me understand things better. > > I'm... actually gonna save this for later because it helps

Re: why, nicely explained (Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, 8 Jun 2016 15:47:46 +, Holger Levsen wrote: >Thanks for this nice summary. It helped me understand things better. I'm... actually gonna save this for later because it helps me understand the alioth workflow. I'm still relatively fresh to Debian dev and can

Re: why, nicely explained (Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, 8 Jun 2016 15:47:46 +, Holger Levsen wrote: >Thanks for this nice summary. It helped me understand things better. What Holger says +1. I must say that I like the discussion style shown in this thread up to now. Please more of this friendly constructivism.

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On 06/08/2016 11:19 AM, Felipe Sateler wrote: [...] > > So, say I want to contribute to a project I don't normally work in. Steps > in alioth: > [...] Well, I would go this route: - git clone - hack - git commit -a -v - git format-patch -1 --to=proj...@lists.alioth.debian.org | mailx -t

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, Jun 08, 2016 at 05:16:54PM +0100, Ian Jackson wrote: > Luca Filipozzi writes ("Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: > Next steps for gitlab.debian)"): > > On Wed, Jun 08, 2016 at 03:19:09PM +, Felipe Sateler wrote: > > > That speaks more to the need of actually

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, 2016-06-08 at 20:29 +0530, Balasankar C wrote: > Tell me an "easy" way to do merging in alioth, I think perhaps it hasn't been made clear to folks on this thread that gitlab is more like a github style thing (with a webui for PRs and whatnot) rather than a more "traditional"/"simple" git

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

Luca Filipozzi writes ("Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)"): > On Wed, Jun 08, 2016 at 03:19:09PM +, Felipe Sateler wrote: > > That speaks more to the need of actually dropping the not-shiny-anymore > > services rather than block adding a new

why, nicely explained (Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, Jun 08, 2016 at 03:19:09PM +, Felipe Sateler wrote: > Git is not only for code hosting. It is also a tool for collaborating, > even with people not formally affiliated with your project. > > So, say I want to contribute to a project I don't normally work in. Steps > in alioth: > >

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, Jun 08, 2016 at 03:19:09PM +, Felipe Sateler wrote: > >> But that doesn't mean we as a project have to run and keep maintaining > >> all the things that were once shiney. > > > > +1 > > That speaks more to the need of actually dropping the not-shiny-anymore > services rather than

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, 08 Jun 2016 15:14:36 +0100, Iain R. Learmonth wrote: > Hi All, > > On 08/06/16 15:10, Peter Palfrader wrote: >> On Wed, 08 Jun 2016, Marco d'Itri wrote: >>> Since usability is the main reason many people hate using alioth, > > Do people really hate Alioth if they're just using it for

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On ബുധന്‍ 08 ജൂണ്‍ 2016 07:44 വൈകു, Iain R. Learmonth wrote: > Do people really hate Alioth if they're just using it for git hosting? > You do some ssh and make a repo and then you just pull and push as you > would with anything else. > Tell me an "easy" way to do merging in alioth, and then

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, Jun 08, 2016 at 03:14:36PM +0100, Iain R. Learmonth wrote: > Hi All, > > On 08/06/16 15:10, Peter Palfrader wrote: > > On Wed, 08 Jun 2016, Marco d'Itri wrote: > >> Since usability is the main reason many people hate using alioth, > > Do people really hate Alioth if they're just using

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

Hi All, On 08/06/16 15:10, Peter Palfrader wrote: > On Wed, 08 Jun 2016, Marco d'Itri wrote: >> Since usability is the main reason many people hate using alioth, Do people really hate Alioth if they're just using it for git hosting? You do some ssh and make a repo and then you just pull and

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, 08 Jun 2016, Marco d'Itri wrote: > On Jun 08, Luca Filipozzi wrote: > > > Let me rephrase, then: can we have a plan that addresses alioth / git / > > gitolite / gitlab / stuff rather than standing up yet another SCM/PM tool > > because it's shiny? > Since usability

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

Hi, Am Mittwoch, den 08.06.2016, 13:46 + schrieb Luca Filipozzi: > On Wed, Jun 08, 2016 at 03:17:44PM +0200, Joachim Breitner wrote: > > > Let me rephrase, then: can we have a plan that addresses alioth / git / > gitolite / gitlab / stuff rather than standing up yet another SCM/PM tool >

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Jun 08, Luca Filipozzi wrote: > Let me rephrase, then: can we have a plan that addresses alioth / git / > gitolite / gitlab / stuff rather than standing up yet another SCM/PM tool > because it's shiny? Since usability is the main reason many people hate using alioth,

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

On Wed, Jun 08, 2016 at 03:17:44PM +0200, Joachim Breitner wrote: > Am Mittwoch, den 08.06.2016, 10:21 +0100 schrieb Jonathan Dowland: > > On Tue, Jun 07, 2016 at 10:25:07AM +0530, Pirate Praveen wrote: > > > Thanks for the offer. It would be great if I have more hands to help with > > > migrating

Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

Hi, Am Mittwoch, den 08.06.2016, 10:21 +0100 schrieb Jonathan Dowland: > On Tue, Jun 07, 2016 at 10:25:07AM +0530, Pirate Praveen wrote: > > Thanks for the offer. It would be great if I have more hands to help with > > migrating git.debian.org > > Whoah there. Running an official Debian gitlab