GitLab update: Moving to the next step

[Carlos Soriano]

Hello community,

I have good news, after few meetings and discussions with GitLab we reached
an agreement on a way to bring the features we need and to fix our most
important blockers

in a reasonable time and in a way that are synced with us. Their team will
fix our blockers in the next 1-2 months, most of them will be fix in the
release of 22th of December and the rest if everything goes well in the
release of 22th of January. The one left that will be an ongoing effort out
of those 2 months is a richer UI experience for duplicates, which is going
to be an ongoing effort.

Apologies for the blockage for those that regularly asked to migrate their
project, I wanted to make sure we are doing things in the right steps. I
also wanted to make sure that I get feedback and comments about the
initiative all around in my effort to make a representation of the
community for taking these decisions. Now it's the point where I'm
confident, the feedback and comments both inside and outside of our core
community has been largely that we should start our path to fully migrate
to GitLab.

So starting today we move forward to the next step, this means that all
projects that want to migrate are free to migrate. I'm also coordinating
with some core apps for a migration in the upcoming month (e.g. Documents,
Photos, Boxes), with other core projects to be migrated once we have in
GitLab the features we need (i.e. Software, Shell, Mutter), and more
platform-ish core projects like gtk+, glib etc. to be taken their time to
ensure their migration is smooth. All depends individually of the project
and the maintainer, of course.

With this change comes other news: We did our first batch migration of 8
projects today, totaling 21 projects that have moved by now. Also, the
Engagement team has started using GitLab for better tracking and
collaboration with the rest of the community, don't hesitate to check it out
 if you want to make
publicity of some feature or if you want to collaborate!

To make the transition easier, I created a general documentation for using
GitLab for GNOMER's, check it out here  (feel
free to edit).
If you want to help, get in touch with me or check out our task list
.
If you want your project to be moved, get in touch with me or create an
issue like this one
.

As always, I'm there for your questions and feedback. You can do so in this
mail chain, in irc, in private messages to me or by filling issues in the GNOME
infrastructure project
. I just
want to ask, please keep in mind that I'm doing this entirely in my free
time, so be considerate, I don't have unlimited energy :)

Also thanks to all that helped so far, specially Phillip, Emmanuele and
Alberto.

Hope you enjoy the news and the work we have done.

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

Re: GitLab update: Moving to the next step

[Milan Crha]

On Wed, 2017-12-06 at 18:49 +0100, Carlos Soriano wrote:
> I have good news, after few meetings and discussions with GitLab we
> reached an agreement on a way to bring the features we need and to
> fix our most important blockers in a reasonable time and in a way
> that are synced with us.

Hi,
I only recently noticed that there is no option to send mail
notifications from Gitlab as text/plain only, while this could be
changed in bugzilla. I agree it's no blocker, it's just nice to have.
For me personally, I do not care of fancy fonts and whatever in
text/plain+text/html messages they send, I prefer text/plain for
bugzilla mail, because I care of the information, not the form (and
less data being transferred and stored as well). In case I didn't
overlook the option in the Gitlab preferences, could you ask them/add
it to the list, please?
Thanks and bye,
Milan
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab update: Moving to the next step

[Carlos Soriano]

Hey Milan,

To explain it better, my discussions with them are for high impact changes.
My bandwidth is fully in there.

We however maintain our own list
 in
a way for us to keep an eye for improvements we want to see and also
because there are GitLab people looking at it, but I want to keep the focus
on our major issues for the direct discussions, and leave everything else
for a more regular flow discussion with upstream issues, etc.

For your issue, could you please create an issue upstream
 and add it in a comment to our
list? You are the best person to explain why you need that option.


Best
--
Carlos Soriano
GNOME Foundation
Treasurer, Board of Directors

On Wed, Dec 6, 2017 at 7:05 PM, Milan Crha  wrote:

> On Wed, 2017-12-06 at 18:49 +0100, Carlos Soriano wrote:
> > I have good news, after few meetings and discussions with GitLab we
> > reached an agreement on a way to bring the features we need and to
> > fix our most important blockers in a reasonable time and in a way
> > that are synced with us.
>
> Hi,
> I only recently noticed that there is no option to send mail
> notifications from Gitlab as text/plain only, while this could be
> changed in bugzilla. I agree it's no blocker, it's just nice to have.
> For me personally, I do not care of fancy fonts and whatever in
> text/plain+text/html messages they send, I prefer text/plain for
> bugzilla mail, because I care of the information, not the form (and
> less data being transferred and stored as well). In case I didn't
> overlook the option in the Gitlab preferences, could you ask them/add
> it to the list, please?
> Thanks and bye,
> Milan
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list
>
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: GitLab update: Moving to the next step

[philip . chimento]

On Wed, Dec 6, 2017 at 9:49 AM Carlos Soriano  wrote:

> Hello community,
>
> I have good news, after few meetings and discussions with GitLab we
> reached an agreement on a way to bring the features we need and to fix our
> most important blockers
> 
> in a reasonable time and in a way that are synced with us. Their team will
> fix our blockers in the next 1-2 months, most of them will be fix in the
> release of 22th of December and the rest if everything goes well in the
> release of 22th of January. The one left that will be an ongoing effort out
> of those 2 months is a richer UI experience for duplicates, which is going
> to be an ongoing effort.
>

Sounds like fantastic news!

Apologies for the blockage for those that regularly asked to migrate their
> project, I wanted to make sure we are doing things in the right steps. I
> also wanted to make sure that I get feedback and comments about the
> initiative all around in my effort to make a representation of the
> community for taking these decisions. Now it's the point where I'm
> confident, the feedback and comments both inside and outside of our core
> community has been largely that we should start our path to fully migrate
> to GitLab.
>
> So starting today we move forward to the next step, this means that all
> projects that want to migrate are free to migrate. I'm also coordinating
> with some core apps for a migration in the upcoming month (e.g. Documents,
> Photos, Boxes), with other core projects to be migrated once we have in
> GitLab the features we need (i.e. Software, Shell, Mutter), and more
> platform-ish core projects like gtk+, glib etc. to be taken their time to
> ensure their migration is smooth. All depends individually of the project
> and the maintainer, of course.
>
> With this change comes other news: We did our first batch migration of 8
> projects today, totaling 21 projects that have moved by now. Also, the
> Engagement team has started using GitLab for better tracking and
> collaboration with the rest of the community, don't hesitate to check it
> out  if you want to
> make publicity of some feature or if you want to collaborate!
>
> To make the transition easier, I created a general documentation for using
> GitLab for GNOMER's, check it out here  (feel
> free to edit).
> If you want to help, get in touch with me or check out our task list
> 
> .
> If you want your project to be moved, get in touch with me or create an
> issue like this one
> 
> .
>
> As always, I'm there for your questions and feedback. You can do so in
> this mail chain, in irc, in private messages to me or by filling issues in
> the GNOME infrastructure project
> . I just
> want to ask, please keep in mind that I'm doing this entirely in my free
> time, so be considerate, I don't have unlimited energy :)
>

Thank you for all the coordination and work you have done so far.

Also thanks to all that helped so far, specially Phillip, Emmanuele and
> Alberto.
>
> Hope you enjoy the news and the work we have done.
>

I am already getting a lot more contributions to GJS in GitLab, without
even asking for them, than I did in Bugzilla. It's fantastic!

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