[Written on behalf of Alberto Ruiz, Carlos Soriano, Andrea Veri, Emmanuele
Bassi and myself.]
Dear community,
Over the years, many of us have become increasingly frustrated about the
state of our development infrastructure, Bugzilla in particular. Pretty
much everyone we’ve spoken to doesn’t like
On 16 May 2017 at 14:22, Allan Day wrote:
> The outcome of this evaluation process is that we are recommending that
> GNOME sets up its own GitLab instance, as a replacement for Bugzilla and
> cgit.
This is great news. Over the last few years I've started most of my
new projects on GitHub and the
On 16/05/17 09:22 AM, Allan Day wrote:
> The outcome of this evaluation process is that we are recommending that
> GNOME sets up its own GitLab instance, as a replacement for Bugzilla and
> cgit.
I'm totally supportive of the idea. While it is a proposal, I just have
a couple of questions about th
On Tue, 2017-05-16 at 14:22 +0100, Allan Day wrote:
> [Written on behalf of Alberto Ruiz, Carlos Soriano, Andrea Veri,
> Emmanuele Bassi and myself.]
Hi !
I'd first like to say that I would love it that we embrace gitlab and
run our own gitlab instance to manage GNOME's gits.
There are some grea
Hello Richard,
Glad to hear that. Could you mention what projects relevant for GNOME (either
part of GNOME already or not) that you are maintainer of would benefit of a
transition to GitLab?
In this way we can evaluate the positive impact this initiative would have.
Cheers,
Carlos Soriano
---
Hello Hubert,
Glad to hear you are supportive of the idea.
Regarding your questions:
1- will URL to cgit be remapped to the gitlab instance?
Last time I checked with Andrea and Alberto that was the plan.
2- what are the migration plans for bugzilla: bugzilla URL, bug numbers and the
actual conten
Hello Tristan,
Glad to hear you are positive about the change!
Regarding your concerns, all of them are currently being work by GitLab. A good
example to know whether GitLab can handle big projects it's to look at GitLab
itself as we mention in the wiki, here:
https://gitlab.com/gitlab-org/git
On Tue, May 16, 2017 at 3:22 PM, Allan Day wrote:
> In recent months we have got together to examine the possibilities for
> GNOME’s development infrastructure. We’ve spent a lot of time on this,
> because we want the community to have faith in our conclusions. If you are
> interested in this, you
On 2017-05-16 09:22 AM, Allan Day wrote:
We are confident that GitLab is a good choice for GNOME, and we can’t
wait for GNOME to modernise our developer experience with it. It will
provide us with vastly more effective tools, an easier landing for
newcomers, and lots of opportunities to improve t
Hi.
I welcome the proposal to modernise our development infrastructure.
On Di, 2017-05-16 at 10:38 -0400, Carlos Soriano via desktop-devel-list
wrote:
> You can take a look at their "changelogs" between releases (one each month).
This seems to be the most risky part about moving to GitLab: Havin
On 16 May 2017 at 15:38, Alexandre Franke wrote:
> On Tue, May 16, 2017 at 3:22 PM, Allan Day wrote:
>> In recent months we have got together to examine the possibilities for
>> GNOME’s development infrastructure. We’ve spent a lot of time on this,
>> because we want the community to have faith i
Alexandre Franke wrote:
> On Tue, May 16, 2017 at 3:22 PM, Allan Day wrote:
> > In recent months we have got together to examine the possibilities for
> > GNOME’s development infrastructure. We’ve spent a lot of time on this,
> > because we want the community to have faith in our conclusions. If
On Tue, 2017-05-16 at 14:22 +0100, Allan Day wrote:
> The outcome of this evaluation process is that we are recommending
> that GNOME sets up its own GitLab instance, as a replacement for
> Bugzilla and cgit.
I 100% support this move. There are inevitably going to be some pain
points, but the end
Hello Alexandre (I got your name right :P),
The team was composed by people with no previous bias, except Alberto who
initially approached us towards GitLab, and me liking Phab more.
Said that, over the testing period of more than 3 months we evaluated both
options as extensively as possible, an
On Tue, May 16, 2017 at 3:51 PM, Shaun McCance wrote:
> On Tue, 2017-05-16 at 14:22 +0100, Allan Day wrote:
> > The outcome of this evaluation process is that we are recommending
> > that GNOME sets up its own GitLab instance, as a replacement for
> > Bugzilla and cgit.
>
> I 100% support this mo
On Tue, 2017-05-16 at 10:51 -0400, Shaun McCance wrote:
> On Tue, 2017-05-16 at 14:22 +0100, Allan Day wrote:
> > The outcome of this evaluation process is that we are recommending
> > that GNOME sets up its own GitLab instance, as a replacement for
> > Bugzilla and cgit.
>
> I 100% support this m
On 16 May 2017 at 16:17, Germán Poo-Caamaño wrote:
> Another potential pain point: in Bugzilla, one can move bugs between
> products. This happen when the bug has been reported to the wrong
> product, or when triaging the bugs the developers know the bug is
> somewhere else in the stack.
>
> Gitl
On Tue, 2017-05-16 at 16:24 +0100, Emmanuele Bassi wrote:
> On 16 May 2017 at 16:17, Germán Poo-Caamaño wrote:
>
> > Another potential pain point: in Bugzilla, one can move bugs
> > between
> > products. This happen when the bug has been reported to the wrong
> > product, or when triaging the bug
On Tue, May 16, 2017 at 9:49 AM, Tobias Mueller
wrote:
Hi.
I welcome the proposal to modernise our development infrastructure.
On Di, 2017-05-16 at 10:38 -0400, Carlos Soriano via
desktop-devel-list
wrote:
You can take a look at their "changelogs" between releases (one
each month).
This s
On Tue, 2017-05-16 at 10:28 -0400, Carlos Soriano via desktop-devel-
list wrote:
> Hello Hubert,
>
> [...]
> 2- what are the migration plans for bugzilla: bugzilla URL, bug
> numbers and the actual content
> In the wiki we outline what our plans are. However this is a moving
> target based on the
On Tue, May 16, 2017 at 6:23 AM Allan Day wrote:
>
> We are confident that GitLab is a good choice for GNOME, and we can’t wait
> for GNOME to modernise our developer experience with it. It will provide us
> with vastly more effective tools, an easier landing for newcomers, and lots
> of opportun
Another issue we haven't discussed yet is commit permissions. Right
now, everyone can commit anything to every repository, but with GitLab
we'll probably eventually want something more fine-grained where
*active* maintainers have more control over who is allowed to commit.
Currently we still ne
On Tue, May 16, 2017 at 11:12 AM, Germán Poo-Caamaño
wrote:
From the migration plan in the wiki:
"Our contention is that copying/moving every existing GNOME issue
to
a new issue tracker is impractical and, in many situations,
undesirable."
May you expand in which many situations
On 16 May 2017 at 15:23, Carlos Soriano wrote:
> Glad to hear that. Could you mention what projects relevant for GNOME
> (either part of GNOME already or not) that you are maintainer of would
> benefit of a transition to GitLab?
Of immediate benefit would be gnome-software as we have lots of
diff
mcatanz...@gnome.org wrote:
> > Does the plan consider a tool like bugzilla2gitlab, but removing
> > the part that copy the accounts?
>
> We need a much better migration plan than that. If we don't have a
> script to migrate Bugzilla issues, comments, and attachments to our
> new GitLab instance
On Tue, May 16, 2017 at 5:36 PM, wrote:
...
> We need a much better migration plan than that. If we don't have a script
> to migrate Bugzilla issues, comments, and attachments to our new GitLab
> instance, then we should not be considering using GitLab's issue tracker at
> all.
>
We're committed
Hi,
On Tue, May 16, 2017 at 12:20 PM wrote:
> Another issue we haven't discussed yet is commit permissions. Right
> now, everyone can commit anything to every repository, but with GitLab
> we'll probably eventually want something more fine-grained where
> *active* maintainers have more control o
On Tue, May 16, 2017 at 12:03 PM, Ray Strode wrote:
Hi,
On Tue, May 16, 2017 at 12:20 PM wrote:
Another issue we haven't discussed yet is commit permissions. Right
now, everyone can commit anything to every repository, but with
GitLab
we'll probably eventually want something more fine-grain
On Tue, May 16, 2017 at 12:23 PM, mcatanz...@gnome.org wrote:
Some maintainers want this, and I think that will be fine in the
future. I don't really care much either way, because I've never seen
any intentional abuse, and if someone commits something wrong to one
of my projects I can simply re
On Tue, May 16, 2017 at 7:03 PM, Ray Strode wrote:
> Hi,
>
> On Tue, May 16, 2017 at 12:20 PM wrote:
>>
>> Another issue we haven't discussed yet is commit permissions. Right
>> now, everyone can commit anything to every repository, but with GitLab
>> we'll probably eventually want something more
Hi,
> It's quite hard to get commit access atm because you have to be
> trusted initially. If a maintainer can give commit access to one repo
> he/she watches anyway there is less trust needed in the beginning. Or
> if a new contributor wants to take over an abandoned project.
>
is that true? I me
I agree with Ray. Open ACLs is a big + for GNOME and there are no
significant evidence of abuse of that. Big NO for the artificial
barriers by fine grained ACLs
On 16 May 2017 at 23:51, Ray Strode wrote:
> Hi,
>>
>> It's quite hard to get commit access atm because you have to be
>> trusted initia
Michael, Ray,
That's a nice discussion to have, but a goal on the initiative was to try to
match what we have now (with the inherited niceties for those workflow/use
cases), with the less disruption possible, while keeping the "nice things we
could do" for a later case-by-case evaluation.
My m
On Tue, May 16, 2017 at 2:38 PM Carlos Soriano
wrote:
> That's a nice discussion to have, but a goal on the initiative was to try
> to match what we have now (with the inherited niceties for those
> workflow/use cases), with the less disruption possible, while keeping the
> "nice things we could
I'm *AGAINST* any initiative about moving GNOME to either GitLab or Phabricator.
> In recent months we have got together to examine the possibilities for
> GNOME’s development infrastructure. We’ve spent a lot of time on this,
> because we want the community to have faith in our conclusions.
> Av
Hi all!
On Tue, 2017-05-16 at 14:22 +0100, Allan Day wrote:
> The outcome of this evaluation process is that we are recommending
> that GNOME sets up its own GitLab instance, as a replacement for
> Bugzilla and cgit.
This is very exciting! I've been following the plans on the wiki and
the discuss
Hello Mattias,
Thanks for sharing your thoughs!
Your concern is about using fast forward merge. Yes, we raised this concern as
the top most important for us, and as we mention in the wiki we have good news,
GitLab team is willing to strongly consider making fast forward merge to CE if
GNOME de
First off, thank you so much for all your contributions as a user and
contributor. I think all of us appreciate that.
On Tue, May 16, 2017 at 1:27 PM Mirko Crowther via desktop-devel-list <
desktop-devel-list@gnome.org> wrote:
> I'm *AGAINST* any initiative about moving GNOME to either GitLab o
Hi Pat!
On Tue, 2017-05-16 at 10:41 -0400, Pat Suwalski wrote:
> I only lurk here, so I don't often offer an opinion, but I do
> maintain the GitLab install at my medium-sized company.
I do the same, but our experiences seems to be pretty different.
> My problem with GitLab is how fluid it is. T
Hi!
On Wed, May 17, 2017 at 12:27 AM, Carlos Soriano via
desktop-devel-list wrote:
> Hello Mattias,
>
> Thanks for sharing your thoughs!
>
> Your concern is about using fast forward merge. Yes, we raised this concern
> as the top most important for us, and as we mention in the wiki we have good
>
On 17 May 2017 at 03:57, Carlos Soriano via desktop-devel-list
wrote:
> Hello Mattias,
>
> Thanks for sharing your thoughs!
>
> Your concern is about using fast forward merge. Yes, we raised this concern
> as the top most important for us, and as we mention in the wiki we have good
> news, GitLab
41 matches
Mail list logo