Re: Wrapping up Bugzilla migration

Thanks Bartłomiej for this! And apologies to everyone I couldn't migrate their BZs in the past. On Mon, 17 May 2021 at 16:45, Bartłomiej Piotrowski wrote: > Hi all, > > I have been looking at Bugzilla migration requests today and have some > related announcements. > > First of all, if for some

Re: Request For Items: September Monthly GNOME Updates

This is an excellent idea, thanks Christopher for putting this together! On Wed, 2 Sep 2020 at 10:24, Christopher Davis wrote: > This marks the first trial of #71 > > for Monthly "What's Happening in GNOME" posts.

Re: Matrix IRC bridge considered harmful

ong massively as a first class native Matrix GTK > client (assuming they want to use it! :) > > So, TL;DR: we've had a solution to much of the Matrix<->IRC problems since > April 2019, we just need to actually use it. > > I'm sorry this has taken so long to sort out - I genuinely hadn

Re: Matrix IRC bridge considered harmful

Hi folks, We been in contact with Matthew from Matrix for some time already. I lately didn't have much time to invest on this, so we had have some delays on answering. However, it's our expectation that with the set up that we have right now the IRC bridge should perform as its best, as we are

Re: Windows runner for CI now generally available!

On Tue, 19 Nov 2019 at 10:48, Carlos Soriano wrote: > Hi everyone, > > Good news! Thanks to OpenAtMicrosoft and our staff we have set up a > Windows runner for the GNOME/ group. Right now it's a single runner with > the "windows" tag attached, feel free to use it as you

Windows runner for CI now generally available!

Hi everyone, Good news! Thanks to OpenAtMicrosoft and our staff we have set up a Windows runner for the GNOME/ group. Right now it's a single runner with the "windows" tag attached, feel free to use it as you see fit. *How to use it* Here's is an example on how to use a specific runner with a

GitLab news & updates

Hi everyone, Just an FYI on latest GitLab news. - *Multiple Issue Boards* is now part of the community edition (despite the documentation saying otherwise). If you ever wanted to try a

Re: Please run for the board!

And in case you missed it in planet.gnome.org, I made a write up on how the board works nowadays, why you should and why you definitely can run for the board, read it! https://csoriano.pages.gitlab.gnome.org/csoriano-blog/post/2019-05-27-why-you-can-and-should-apply-for-the-board/ On Wed, 29 May

Re: Please run for the board!

And in case you missed it in planet.gnome.org, I made a write up on how the board works nowadays, why you should and why you definitely can run for the board, read it! https://csoriano.pages.gitlab.gnome.org/csoriano-blog/post/2019-05-27-why-you-can-and-should-apply-for-the-board/ On Wed, 29 May

Hickups with GitLab during weekend

Hi all, Just a heads up that we had some upstream issue in GitLab that made all events get stuck during the weekend. We applied a workaround for it. This means that you will receive now events that should have been processed on the weekend,

Re: [GSoC] Time to choose students. Deadline next Tuesday.

us or send an email to soc-adm...@gnome.org ASAP. Cheers On Thu, 25 Apr 2019 at 16:05, Carlos Soriano wrote: > A short follow up, regardless of the deadline do this ASAP. > > There are two reasons to do it even today if possible. One is that it's a > first come first serve s

Re: [GSoC] Time to choose students. Deadline next Tuesday.

. In the regular case this will be done with more than a few days time, even though we sent the email a bit late and that's why we extended our internal deadline a bit more. Thanks! On Thu, 25 Apr 2019 at 09:56, Carlos Soriano wrote: > Hello all, > > GNOME has been accepted in GSoC one more

Re: Proposal: Replace all references to master/slave in GNOME modules

Hi, IMHO an smart stance to take in this topic is to focus on the actual impact in practice that this change has, and otherwise just do it if a reasonable amount of people and outside projects think there is a valid reason to do it - we don't need to understand if the reasons are fully valid or

[GSoC] Time to choose students. Deadline next Tuesday.

Hello all, GNOME has been accepted in GSoC one more year! \o/ In order to get the students you want in the accepted slots, you need to complete these steps before next *Tuesday 30th April *(with a day for us as a buffer). Go to https://summerofcode.withgoogle.com/ and search for the proposals

Re: New Matrix IRC bridge server

ems to be working right now! > > El vie., 5 abr. 2019 a las 10:11, Carlos Soriano () > escribió: > >> Hey, not yet, they need some more time. >> >> On Thu, 4 Apr 2019 at 15:30, Zeeshan Ali wrote: >> >>> Hi Carlos, >>> >>> Is this sor

[GitLab] 11.10 is here

Hello all, New version is on our instance, just a few highlights that might be interesting for us. - Link - You can provide *multi-line suggestions in MRs* now. That is, you can

Re: [GSoC] Mentors registration

A small correction, the mentor's mailing list changed this year to https://mail.gnome.org/mailman/listinfo/mentors-list, thanks Alberto Fanjul for the heads up! On Tue, 2 Apr 2019 at 08:46, Carlos Soriano wrote: > Hello everyone, > > It's time for mentors to register for GSoC! > &

Re: [GSoC] Mentors registration

Garnacho - Federico Mena Quintero - Buildstream maintainers? On Fri, 5 Apr 2019 at 10:14, Carlos Soriano wrote: > I worded it wrong, fixed it now. It should be the titles of the ideas, > feel free to update it :-) > > On Thu, 4 Apr 2019 at 15:29, Zeeshan Ali wrote: > >> Hi

Re: [GSoC] Mentors registration

e. > > On Tue, 2 Apr 2019, 08:47 Carlos Soriano, wrote: > >> Hello everyone, >> >> It's time for mentors to register for GSoC! >> >> Please fill this form <https://forms.gle/UA5CPqAroRqbS1gW7> and we will >> invite you to the GSoC program in Goog

Re: New Matrix IRC bridge server

Hey, not yet, they need some more time. On Thu, 4 Apr 2019 at 15:30, Zeeshan Ali wrote: > Hi Carlos, > > Is this sorted yet? > > On Tue, 19 Mar 2019, 17:28 Carlos Soriano, wrote: > >> Whoops, seems this is still not fully set up, stand by for the >> announcement

[GSoC] Mentors registration

Hello everyone, It's time for mentors to register for GSoC! Please fill this form and we will invite you to the GSoC program in Google's website. It's a Google Form, if you want to provide the information in some other way let us know and we will figure

[GitLab] Enabled issue/MR reply and issue/MR creation by email

Hello all, We have just set up (thanks to the foundation staff, Bartolomej and Andrea) a feature of GitLab that allows to comment on issues/MR by simply replying to the notification email. It also allows issue and MR creation by sending an email to a specific address. Please *read the

Re: [GitLab] Akismet enabled, report if you get constant ReCaptchas

n't catch them immediately. They are pretty "smart"... Keep us updated on the regularity you get these recaptchas and if they become too invasive. On Sat, 30 Mar 2019 at 19:17, Michael Catanzaro wrote: > > > On 03/28/2019 05:45 AM, Carlos Soriano wrote: > > Hi all, > &g

[GitLab] Akismet enabled, report if you get constant ReCaptchas

Hi all, Just a quick heads up, spam bots have started to put comments in issues, so we are trying to enable again a quite strong spam protection called Akismet. In the past we disabled it because false positives fire a ReCaptcha, and for some people those were happening constantly. So now that

[GitLab] Some changes and updates

Hi all, We have made a few changes recently that might be of interest: * All GNOME developers (gnomecvs LDAP group) have now reporter access to Teams/Translation, so you are free to move issues between GNOME/ and Translation/. * Abuse reports now go to a shared private mailing list where me and

Re: [GitLab] Another batch migration coming this week

All done, feel free to reenable your notifications On Tue, 19 Mar 2019 at 17:20, Carlos Soriano wrote: > I forgot an important one, i18n (cced now) and all their products will > also be migrated. > > On Tue, 19 Mar 2019 at 11:17, Carlos Soriano wrote: > >> Hey all, >

Re: New Matrix IRC bridge server

Whoops, seems this is still not fully set up, stand by for the announcement :-) On Tue, 19 Mar 2019 at 16:02, Carlos Soriano wrote: > Hello all, > > As you might know we have IRC bridge for Matrix > <https://matrix.org/blog/home/> that we use for newcomers > <https://

Re: [GitLab] Another batch migration coming this week

I forgot an important one, i18n (cced now) and all their products will also be migrated. On Tue, 19 Mar 2019 at 11:17, Carlos Soriano wrote: > Hey all, > > As the subject says, whenever I manage to make the tool work I will do > another batch migration. If you want to avoid the

New Matrix IRC bridge server

Hello all, As you might know we have IRC bridge for Matrix that we use for newcomers and other people of the community in an unofficial way. There has been quite a few complains about the performance of the IRC

[GitLab] Another batch migration coming this week

Hey all, As the subject says, whenever I manage to make the tool work I will do another batch migration. If you want to avoid the mass mailing, feel free to turn off Bugzilla notifications. The projects on the batch are these

Re: Deprecating nautilus-sendto

Created also https://gitlab.gnome.org/GNOME/gnome-build-meta/merge_requests/246 On Wed, 27 Feb 2019 at 13:56, Bastien Nocera wrote: > Hey, > > 15 years ago, in another age, nautilus-sendto was created so that one > could easily send files from nautilus via email. Then via email and > Gaim. Via

Re: [GSoC] Call for ideas

admins at soc-adm...@gnome.org or any of us on irc if you are unsure about them. Thanks! On Tue, 12 Feb 2019 at 12:55, Carlos Soriano wrote: > I just realized my second email mentioning the date didn't went through... > > So just a heads up, we will need as many ideas as we can by to

Re: [GSoC] Call for ideas

I just realized my second email mentioning the date didn't went through... So just a heads up, we will need as many ideas as we can by today 15:00 UTC. So please add them ASAP. Thanks! On Sun, 10 Feb 2019 at 09:29, Carlos Soriano wrote: > Dear GNOME hackers, > > It's this time of

[GSoC] Call for ideas

Dear GNOME hackers, It's this time of the year again, GSoC is here! It's time for potential mentors to add their project ideas to the wiki . Ideally we would have a sensible list of ideas during next week, so Google accept us as an

Re: GNOME 3.32 milestone review

On Wed, 30 Jan 2019 at 10:20, Allan Day wrote: > Great initiative, Carlos! > Thanks Allan for the answer! > Carlos Soriano wrote: > ... > > gnome-screenshot, retire app menu - Part of the GNOME initiative to > remove app menus. There is a MR, needs some review. Deadli

Re: GNOME 3.32 milestone review

s to be > reviewed and if everything is right merge it. :) > > Best regards, > > [0] https://gitlab.gnome.org/GNOME/evince/merge_requests/119#note_422389 > > > El mié., 30 ene. 2019 a las 9:23, Carlos Soriano () > escribió: > >> Hi all, >> >> We are quit

GNOME 3.32 milestone review

Hi all, We are quite close to 3.32 freezes! I thought it would be helpful for some maintainers and projects to summarize their 3.32 pressing issues that they could do with some help and see if someone in ddl would like to give a hand. I basically went through the 3.32 milestone at GitLab,

Re: GitLab postmortem

Now that it has settled down, thanks all for the feedback! It's really useful for me (and I believe for everyone else) to have a general feeling and what things are in common as biggest struggles and positives. Cheers On Wed, 2 Jan 2019 at 16:22, Germán Poo-Caamaño wrote: > On Wed, 2019-01-02

Re: [GitLab] What 11.6 brings to us

It's all enabled now \m/ Please provide feedback about the duplicate issues feature either to me or upstream. On Wed, 2 Jan 2019 at 21:49, Carlos Soriano wrote: > > On Thu, 27 Dec 2018 at 10:04, Abderrahim Kitouni > wrote: > >> Hi, >> >> Le dim. 23 déc

Re: EU security bug bounty, anyone has more info or contact?

Thanks for the pointer! Will contact her then. Cheers On Thu, 3 Jan 2019 at 10:21, Luca Cavalli wrote: > Hi Carlos, > > you can try to contact Julia Reda, @Senficon on Twitter. > > Cheers, > > Luca > > Il giorno mer 2 gen 2019, 21:46 Carlos Soriano ha > scritto

Re: [GitLab] What 11.6 brings to us

On Thu, 27 Dec 2018 at 10:04, Abderrahim Kitouni wrote: > Hi, > > Le dim. 23 déc. 2018 à 13:36, Carlos Soriano a écrit > : > > > > 11.6 is here, there are a few nice things for us. > > > > Run CI/CD for merge requests > > CI are not only for bran

EU security bug bounty, anyone has more info or contact?

Hello all, I just read this post , seems the EU is putting money on some FOSS software for improving security and finding vulnerabilities through bounties. I was wondering if glib, gnome-keyring, etc. could fall in this programme.

[GitLab] What 11.6 brings to us

11.6 is here, there are a few nice things for us. *Run CI/CD for merge requests * CI are not only for branches, but also for MR. Variables, etc. can be put to adjust the CI to do X or Y things on MR or regular

Re: This Week in GNOME

> > Is there a way we (developers) could mark issues/MR to be picked up in > the weekly report? FWIW I created "9. Engagement Material" label back then for this use. I think a good idea would be for us to use a label and his scripts to query that. On Thu, 13 Dec 2018 at 13:27, Felipe Borges

GitLab postmortem

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

Re: getting commit rights for / maintaining Dia ?

FWIW the process will eventually be https://wiki.gnome.org/AccountsTeam/NewAccounts. On Thu, 6 Dec 2018 at 10:15, Tomas Pospisek wrote: > Am 04.12.18 um 22:53 schrieb mcatanz...@gnome.org: > > You should have gotten an email about this from Zander. He will help > > manage this! > Cool, I'll get

Re: [GitLab] Fast CI is now available for all projects under gitlab.gnome.org

2018 at 13:24, Carlos Soriano wrote: > So that's it, we got fast CI for all projects now, including GNOME/ World/ > and all forks. > > This is thanks to donations from Packet.net and Oregon State University > Open Source Lab. We will check if they want some PR and do so soon. We wil

[GitLab] Fast CI is now available for all projects under gitlab.gnome.org

So that's it, we got fast CI for all projects now, including GNOME/ World/ and all forks. This is thanks to donations from Packet.net and Oregon State University Open Source Lab. We will check if they want some PR and do so soon. We will also update https://wiki.gnome.org/GitLab/CI with the info

Re: GitLab minor-reorganization to Community group

for > clarification > > On Mon, Sep 24, 2018 at 9:21 AM Carlos Soriano wrote: > >> This is done now, please check everything is alright. >> >> Left to be done: >> - The translation team, whether they want a group, projects, or something >> else. To be discu

Re: GitLab minor-reorganization to Community group

This is done now, please check everything is alright. Left to be done: - The translation team, whether they want a group, projects, or something else. To be discussed. - The DeveloperPortal, since they weren't part of the disscussion afaik so I want to double check with them. - Creating

Re: GitLab minor-reorganization to Community group

Since there hasn't been any complains I'm going ahead with Britt reorganizacion proposal. Let me know if any issue arises. If permissions are the problem, check the owners of their respective groups/subgroups/projects and check with them or fallback to contact me or Andrea Veri. Cheers On Sun,

Re: [GitLab] Gravatar vs libravatar

8 at 18:03, Carlos Soriano wrote: > I'm not sure, contact Andrea Veri for more. We definitely got dissapointed > by finding this suddenly, and we should have investigated a bit more before > hand. So for now sysadmins wants it disabled. > > On Thu, 20 Sep 2018 at 17:26, Alexandre Franke

Re: [GitLab] Gravatar vs libravatar

I'm not sure, contact Andrea Veri for more. We definitely got dissapointed by finding this suddenly, and we should have investigated a bit more before hand. So for now sysadmins wants it disabled. On Thu, 20 Sep 2018 at 17:26, Alexandre Franke wrote: > On Thu, Sep 20, 2018 at 3:52 PM Car

Re: [GitLab] Gravatar vs libravatar

Right we read that too, although it doesn't give very high hopes. The main problem is the second point, it just redirects stuff to Gravatar, so not much point (and quite shady imho) On Thu, 20 Sep 2018 at 15:50, Matthias Klumpp wrote: > Am Do., 20. Sep. 2018 um 15:48 Uhr schrieb Carlos Sori

Re: [GitLab] Gravatar vs libravatar

ontact libravatar developers feel free to do so. Cheers On Thu, 20 Sep 2018 at 15:33, Carlos Soriano wrote: > Done, enjoy! > > On Thu, 6 Sep 2018 at 10:03, Carlos Soriano wrote: > >> There has been indeed many things I didn't realize back then! >> >> This has got an ove

Re: [GitLab] Gravatar vs libravatar

Done, enjoy! On Thu, 6 Sep 2018 at 10:03, Carlos Soriano wrote: > There has been indeed many things I didn't realize back then! > > This has got an overwhelming positive outcome, so seems replacing Gravatar > by libravatar is the way forward. We will replace it in two weeks if

Re: [GitLab] Gravatar vs libravatar

There has been indeed many things I didn't realize back then! This has got an overwhelming positive outcome, so seems replacing Gravatar by libravatar is the way forward. We will replace it in two weeks if no blocker appears. Thanks all! On Tue, 4 Sep 2018 at 18:00, Tobias Mueller wrote: >

Re: [GitLab] Gravatar vs libravatar

is well supported by us and we start using it it looks like an easy win-win for privacy-aware tools and people. On Mon, 3 Sep 2018 at 20:13, Carlos Soriano wrote: > Hello all, > > There is a request to replace Gravatar <https://en.gravatar.com/> by > libravatar <https

[GitLab] Gravatar vs libravatar

Hello all, There is a request to replace Gravatar by libravatar on our GitLab instance. Both are supported in GitLab. The reasoning to replace it is that Gravatar seems to have privacy issues . So I would like to

Re: [GitLab] Group runners: And why CI is slow in forks

rience for CI for the whole GNOME, so that means we need to have them centralized. This is useful to play with it to see costs and how much donation could be made. Cheers On Tue, 24 Jul 2018 at 10:08, Carlos Soriano wrote: > That sounds great! Seems you know how to set up this which is wonderuf

Re: [GitLab] Group runners: And why CI is slow in forks

Support from the Engagement Team to create a social media strategy, > etc. > > Warm Regards. > > On Mon, Jul 23, 2018 at 7:28 AM Carlos Soriano wrote: > > > > Hello all, > > > > In case you missed my treasurer report talk at GUADEC, our annual costs >

[GitLab] Bugs migrations status

Just a heads up, for those projects waiting for me to migrate bugs apologies I have been slow, the baseline time requirement of GitLab as admin is not trivial yet and real work is knocking the door :) Said that, I'll try to do a migration batch this week for those projects without special request

[GitLab] Updated to 11.1

*What's important for us?* - Performance improvements - Rewrite of the MR backend . Should be much smoother and

[GitLab] Group runners: And why CI is slow in forks

Hello all, In case you missed my treasurer report talk at GUADEC, our annual costs for CI is around $22.000. This is okay since we are lucky to have GitLab Inc. as the main sponsor of that. However, we cannot offload all of our needs on them, even more in the long-term. So we need to 1) find

Re: CI/CD workshop with GitLab developer

end it? > Thanks. > > 2018-06-21 9:16 GMT-03:00 Carlos Soriano : > >> Hello all, >> >> We will have a workshop with a GitLab developer at GUADEC 9th July about >> CI/CD. We are creating the agenda, and I would like to ask what points >> would you like to see? >

CI/CD workshop with GitLab developer

Hello all, We will have a workshop with a GitLab developer at GUADEC 9th July about CI/CD. We are creating the agenda, and I would like to ask what points would you like to see? The current agenda is: *Introduction to GitLab CI/CD* - Concepts - Why use GitLab CI/CD? - Overview *Setup CI* -

Migration of GNOME to GitLab is now completed

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

IMPORTANT Mass migration to GitLab starts

. Hope the ride goes well for everyone! Cheers, Carlos Soriano ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: IMPORTANT: Mass migration to GitLab update

whoops good catch! Thanks Alberto. On 21 May 2018 at 07:18, Alberto Fanjul Alonso wrote: > Glade is already migrated with bugs https://gitlab.gnome.org/GNOME/glade, > the pending migration is for glade-web https://gitlab.gnome.org/ > Infrastructure/GitLab/issues/232,

Re: IMPORTANT: Mass migration to GitLab update

Here you are, I created an issue to not forget again https://gitlab.gnome.org/Infrastructure/GitLab/issues/240. Thanks for sending a new email! On 20 May 2018 at 23:17, Tim-Philipp Müller wrote: > Hi Carlos, > > > Exceptions are possible but discouraged due to overhead, please

IMPORTANT: Mass migration to GitLab update

rminal - gnome-online-accounts - totem - rhythmbox - cogl Please let me know any thoughts, questions or concerns you might have! Cheers, Carlos Soriano ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: BUG REPROT: Bug tracker URLs not talking with Canonical's Launchpad

Hey Jeb, I'm confident Canonical and Ubuntu are aware of this limitation, they are also GNOMER's around here. Not sure if they will be able to implement that feature, but there's nothing we can do from here I'm afraid. Cheers On 3 May 2018 at 16:08, Jeb Eldridge wrote: >

Re: Protected branches in GNOME's GitLab

A small correction from Florian's asnwer: We had a period that some branches were protected by default because I didn't know how to deactivate that. But it shouldn't be the case for new projects or new migrated projects. Cheers On 30 April 2018 at 19:19, Florian Müllner

Re: GNOME 3.28.1 tarballs due

I'll put a banner in GitLab. Cheers. On 7 April 2018 at 19:50, wrote: > Hi developers, > > It looks like our automated reminder mails are not working properly > currently. (Does anybody know how to help fix this?) 3.28.1 tarballs are > due Monday. You all know the drill.

[GitLab] Duplicates handling, feedback for meeting with GitLab

Hello all, I'm having a meeting with GitLab on Friday about what we are missing for duplicates handling as part of one of the high priority items . I identified the following points (upstream comment

Re: [GitLab] Easter gift, GitLab Pages are now enabled

sier to contribute and maintain than the wiki, with all the custom styling we do in the wiki I'm starting to think that it could be. On the other hand it's not very obvious the end result of the Hugo website is when looking at these templates. Ultimately it depends on how we see it... the proposal is

Re: [GitLab] Easter gift, GitLab Pages are now enabled

your nautilus-web example is ultimately going to be merged > into nautilus' git repo? Or I didn't understood? That would be awesome! > > Regards, > Xavier Claessens. > > Le jeudi 29 mars 2018 à 19:54 +0200, Carlos Soriano a écrit : > > As the subject says, we have now supp

[GitLab] Easter gift, GitLab Pages are now enabled

As the subject says, we have now support for GitLab Pages , thanks to Andrea. Take a look to the example I did for Nautilus with Hugo, which renders to this result

[GSoC] Mentors: Time to review students proposals

Hello GSoC Mentors, Students have already added their final proposals to the GSoC website and we cleaned up everything so you can search for the ones that you are interested in. In order to get the students who you want into the accepted slots, go to https://summerofcode.withgoogle.com/ and

Re: [GitLab] IMPORTANT: Mass migration plan

Just issue and MR descriptions. Not sure I understood your idea though, what would you put in a comment? On 24 March 2018 at 14:39, Alexandre Franke <afra...@gnome.org> wrote: > On Fri, Mar 23, 2018 at 11:56 AM, Carlos Soriano <csori...@gnome.org> > wrote: > > Proper forma

Re: [GitLab] IMPORTANT: Mass migration plan

Milan, Proper formatting from users is what issue templates are for. You can take a look at the blog post I did where we take into account crashes, and definitely worth saying "select the backtrace and click the button 'code'" or similar (which is not in my current proposal, but I ll add it). On

[GitLab] We are on GitLab Libre 10.6

Short update: We are now on GitLab Libre (renamed from CE) 10.6, and therefore now we can rebase and modify non-dev branches , make sure to ask contributors to enable that. Cheers ___

Re: [GitLab] IMPORTANT: Mass migration plan

Oh got it Phillip, apologies for the noise, I'm starting to forget the details here and there... On 21 March 2018 at 22:49, Alexandre Franke wrote: > On Wed, Mar 21, 2018 at 10:37 PM, Shaun McCance wrote: > > And in constructing this example for this email,

Re: Migration of non-core apps Was: Re: [GitLab] IMPORTANT: Mass migration plan

intainer of the Gnome Commander > repo at GitLab somewhere? > > Best wishes and thank you for all your efforts so far! > Uwe > > Am Tue, 20 Mar 2018 18:01:35 +0100 schrieb Carlos Soriano: > > Hello community, > > > > After a few months of manually migrating projects

Re: [GitLab] IMPORTANT: Mass migration plan

I personally prefer the result of the migration with impersonation too. Anyway, Philip let's go with impersonation, would you be able to take care of that? On 21 March 2018 at 21:52, Carlos Soriano <csori...@gnome.org> wrote: > Hey Shaun, > > It wouldn't be a problem per se, a

Re: [GitLab] IMPORTANT: Mass migration plan

org> wrote: > On Tue, 2018-03-20 at 18:01 +0100, Carlos Soriano wrote: > > - Cgit will be phased out and removed by June 1st 2018. > > How tremendously difficult would it be to set up 302 redirects so that > links to commits/branches/etc go to the right place in GitLab? I don

Re: [GitLab] IMPORTANT: Mass migration plan

Just a very quick thing, please don't rename projects :D We have git management on disk, not only in GitLab. Not sure if our hooks would protect against that, but better to not test them for now... On Wed., 21 Mar. 2018, 17:57 Mathieu Bridon via desktop-devel-list, <

Re: [GitLab] IMPORTANT: Mass migration plan

their own modules and reporting issues. On 21 March 2018 at 09:27, Germán Poo-Caamaño <g...@gnome.org> wrote: > On Wed, 2018-03-21 at 08:53 -0400, Carlos Soriano wrote: > > > Should issues be filed against Infrastructure/GitLab? > > > > Yeah please > > > >

Re: [GitLab] IMPORTANT: Mass migration plan

fications would be send massively, and I don't know how to prevent that. So that's basically a no-no from the start. Maybe some trick can be done, but no idea. On 21 March 2018 at 07:07, Alexandre Franke <afra...@gnome.org> wrote: > On Wed, Mar 21, 2018 at 11:28 AM, Carlos Soriano <csori.

Re: [GitLab] IMPORTANT: Mass migration plan

ting bugs is a big work load. On 21 March 2018 at 05:50, Alexandre Franke <afra...@gnome.org> wrote: > On Tue, Mar 20, 2018 at 6:01 PM, Carlos Soriano <csori...@gnome.org> > wrote: > > Hello community, > > Hi, > > > After a few months of manually migrating pr

Re: [GitLab] IMPORTANT: Mass migration plan

Hey all, Tim-Philipp I'll discuss today with Andrea what to do here, in any case don't worry, we will find a solution with either staying in Bugzilla or making sure you can migrate to fdo (I'll run a migration test). Arnaud, if you want a rename it's totally doable, several modules already took

Re: [GitLab] IMPORTANT: Mass migration plan

By request, cc'ing this list. On 20 March 2018 at 18:01, Carlos Soriano <csori...@gnome.org> wrote: > Hello community, > > After a few months of manually migrating projects we have moved already > over 60, most of them were core modules to make sure the most important > p

[GitLab] IMPORTANT: Mass migration plan

Hello community, After a few months of manually migrating projects we have moved already over 60, most of them were core modules to make sure the most important projects were migrated before the mass migration happens. We are now at the point where a mass migration makes more sense than

Re: [GSoC] Call for ideas

lternative email for communication (optional) and phone number. Carlos Soriano GNOME Board of Directors On 12 March 2018 at 09:38, Carlos Soriano <csori...@gnome.org> wrote: > Hello all, > > As you may know GNOME was again accepted for GSoC! > > Thanks to the mentors who've al

[GSoC] Call for ideas

Hello all, As you may know GNOME was again accepted for GSoC! Thanks to the mentors who've already listed GSoC project ideas! There is still time to add more ideas and they are more than welcome. If you are interested, please add your idea to the wiki

Re: [GitLab] Projects moved, general comments, tips of the week, question of the week

> I apologize, if I sounded inappropriate earlier. No worries, it was fine. I probably wasn't clear in the past what people need to do to discuss these priorities and it's a very valid question. Cheers Carlos Soriano GNOME Board of Directors On 28 February 2018 at 17:38, Milan Crha

Re: [GitLab] Projects moved, general comments, tips of the week, question of the week

one all left GNOME projects will be migrated to GNOME's gitlab instance and bugzilla will be switched to read-only mode, or? The plan is to migrate already, our blockers were fixed in the past already. And yeah, after mass migration BZ will be put into read-only mode. Best, Carlos Soriano On 2

Re: [GitLab] Projects moved, general comments, tips of the week, question of the week

all can comment there, that's why it's public :) Cheers On 28 February 2018 at 13:03, Milan Crha <mc...@redhat.com> wrote: > On Fri, 2018-02-23 at 21:40 +0100, Carlos Soriano wrote: > > If you have some issue or feature request that might impact GNOME as > > a whole and you

Re: Let's kill gnome-common!

Thanks Bastien. > Or better port to meson. Yeah that sounds like a better task. Carlos Soriano GNOME Board of Directors On 13 February 2018 at 10:20, Bastien Nocera <had...@hadess.net> wrote: > On Tue, 2018-02-13 at 10:08 +0100, Carlos Soriano wrote: > > Hi Michael, >

Re: Let's kill gnome-common!

Hi Michael, Could you give some context and explanation on this? I could take the gnome-autoar, but need to know why this is wanted and the alternative to gnome-common. Cheers On 13 February 2018 at 02:08, wrote: > Hi, > > I want to remove gnome-common from our

  1   2   3   >