Re: GitLab postmortem

2019-01-15 Thread Will Thompson
On Tue, 15 Jan 2019, at 10:04, Bastien Nocera wrote:
> On Tue, 2019-01-15 at 10:58 +0100, Emilio Pozuelo Monfort wrote:
> > It should still be easy to fork the project, push a branch to your
> > namespace,
> > and then submit a MR. Or did I misunderstand?
> 
> Too many trips to the web browser, too many re-clones of the repo (or
> esoteric git command-lines), and too many left-over repos in your own
> namespace. It's a problem I have with github as well, it's the same
> workflow.

I have found the 'hub' and 'lab' tools very useful for avoiding trips to the 
web browser.

https://github.com/github/hub
https://github.com/zaquestion/lab
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: GitLab postmortem

2019-01-15 Thread Bastien Nocera
On Tue, 2019-01-15 at 10:58 +0100, Emilio Pozuelo Monfort wrote:
> On 15/01/2019 10:48, Bastien Nocera wrote:
> > On Tue, 2018-12-11 at 14:22 +0100, Carlos Soriano wrote:
> > > Hey,
> > > 
> > > It has been a few months since we moved to GitLab. Apart of
> > > spurious
> > > issues, specific annoyances and frustrations, seems it has been
> > > generally good. I would like to gather some general feeling about
> > > it.
> > > Things that really made a constant impact to you and your work,
> > > both
> > > bad or good. Feel free to provide feedback about the transition
> > > or
> > > the administration of GitLab instance too. Free form.
> > > 
> > > Please keep the mail chain one way from you towards the world, so
> > > we
> > > don't get trapped on specifics, we can address stuff raised here
> > > individually out of list. Personally, I'll ping you on IRC or so
> > > if I
> > > can do something to help.
> > > 
> > > Of course, feel free to msg me directly on IRC/email too.
> > 
> > My main problem is/was that contributing by pushing a branch is
> > super-
> > easy, but you can't contribute by pushing a branch if you're not
> > allowed to push a branch. So this isn't a problem when you're in
> > @GNOME, and the project is as well, but I've not bothered pushing
> > small
> > fixes to non-GNOME group modules.
> 
> It should still be easy to fork the project, push a branch to your
> namespace,
> and then submit a MR. Or did I misunderstand?

Too many trips to the web browser, too many re-clones of the repo (or
esoteric git command-lines), and too many left-over repos in your own
namespace. It's a problem I have with github as well, it's the same
workflow.

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: GitLab postmortem

2019-01-15 Thread Emilio Pozuelo Monfort via desktop-devel-list
On 15/01/2019 10:48, Bastien Nocera wrote:
> On Tue, 2018-12-11 at 14:22 +0100, Carlos Soriano wrote:
>> Hey,
>>
>> It has been a few months since we moved to GitLab. Apart of spurious
>> issues, specific annoyances and frustrations, seems it has been
>> generally good. I would like to gather some general feeling about it.
>> Things that really made a constant impact to you and your work, both
>> bad or good. Feel free to provide feedback about the transition or
>> the administration of GitLab instance too. Free form.
>>
>> Please keep the mail chain one way from you towards the world, so we
>> don't get trapped on specifics, we can address stuff raised here
>> individually out of list. Personally, I'll ping you on IRC or so if I
>> can do something to help.
>>
>> Of course, feel free to msg me directly on IRC/email too.
> 
> My main problem is/was that contributing by pushing a branch is super-
> easy, but you can't contribute by pushing a branch if you're not
> allowed to push a branch. So this isn't a problem when you're in
> @GNOME, and the project is as well, but I've not bothered pushing small
> fixes to non-GNOME group modules.

It should still be easy to fork the project, push a branch to your namespace,
and then submit a MR. Or did I misunderstand?

Emilio
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: GitLab postmortem

2019-01-15 Thread Bastien Nocera
On Tue, 2018-12-11 at 14:22 +0100, Carlos Soriano wrote:
> Hey,
> 
> It has been a few months since we moved to GitLab. Apart of spurious
> issues, specific annoyances and frustrations, seems it has been
> generally good. I would like to gather some general feeling about it.
> Things that really made a constant impact to you and your work, both
> bad or good. Feel free to provide feedback about the transition or
> the administration of GitLab instance too. Free form.
> 
> Please keep the mail chain one way from you towards the world, so we
> don't get trapped on specifics, we can address stuff raised here
> individually out of list. Personally, I'll ping you on IRC or so if I
> can do something to help.
> 
> Of course, feel free to msg me directly on IRC/email too.

My main problem is/was that contributing by pushing a branch is super-
easy, but you can't contribute by pushing a branch if you're not
allowed to push a branch. So this isn't a problem when you're in
@GNOME, and the project is as well, but I've not bothered pushing small
fixes to non-GNOME group modules.

Per-commit reviews are absolutely head-against-the-desk because the UI
is really bad, and the diff tool is sluggish. I miss splinter if I have
more than one commit to review.

All-in-all, it's still a better, and known, workflow for people who
didn't want to, or couldn't learn about git-bz, and having a CI
available is awesome. Don't even need to spend a second reviewing
patches that don't build ;)

Good job :)

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list