Re: migrating gtk

On 16 April 2018 at 19:32, Emmanuele Bassi wrote: > > * Migrate what's left at the end >> > > We're in the process of migrating: https://gitlab.gnome.org/ > Infrastructure/GitLab/issues/228 > > This will take a while once it starts; I'll send another email to the list > to

Re: migrating gtk

Hi all; it's time for an update. On 2 February 2018 at 14:04, Matthias Clasen wrote: > Hey Carlos, > > we discussed gitlab migration for gtk here at the hackfest. Our > conclusions were as follows: > > * We want to migrate the git repository as soon as possible >

Re: migrating gtk

On Sat, 2018-02-10 at 16:43 +0100, Salvatore De Paolis wrote: > On Thu, 08 Feb 2018 02:00:16 + > Sriram Ramkrishna wrote: > > > Every contributor who takes an actionable step and reports a bug is > > a > > potential future core contributor. Please remember that. A

Re: migrating gtk

On 10 February 2018 at 21:26, Kristian Rietveld wrote: > >> On 05 Feb 2018, at 11:37, Emmanuele Bassi wrote: >> >> Of course if we get a positive response that the bug is still there >> we're going to migrate it and keep track of it. >> >>> With that in mind,

Re: migrating gtk

> On 05 Feb 2018, at 11:37, Emmanuele Bassi wrote: > > Of course if we get a positive response that the bug is still there > we're going to migrate it and keep track of it. > >> With that in mind, I believe it is much nicer to just leave the old bugs >> there. > > The old

Re: migrating gtk

On Thu, 08 Feb 2018 02:00:16 + Sriram Ramkrishna wrote: > Every contributor who takes an actionable step and reports a bug is a > potential future core contributor. Please remember that. A person who > attempts to fix a bug with a patch is even more valuable. It's a

Re: migrating gtk

On Tue, Feb 6, 2018 at 8:31 AM Matthias Clasen wrote: > I will ignore the childish name-calling here and just state that as far as > I am concerned, > the bugs you file are donations to the project. What we do with them is up > to us. If we decide > to fix them, good

Re: migrating gtk

I will ignore the childish name-calling here and just state that as far as I am concerned, the bugs you file are donations to the project. What we do with them is up to us. If we decide to fix them, good for you. If not, that's tough and annoying, but lets face it: there is an infinite number of

Re: migrating gtk

Hi everyone, can we please stop the ad hominems and stick to constructive suggestions to improve things please? this is becoming disgusting and is a poor display of community dynamics Thank you. 2018-02-05 16:36 GMT+01:00 Morten Welinder : > > Your behaviour on this mailing

Re: migrating gtk

> Your behaviour on this mailing list, and on Bugzilla, has been > consistently rude, inconsiderate, and plain abusive of the patience > and effort that volunteers put in the platform you're consuming. You have absolutely no respect for the work of other volunteers to the gtk+ project or for

Re: migrating gtk

On 5 February 2018 at 14:15, Emmanuele Bassi wrote: > I gained the fact that you read your email and if you're still > experiencing the issue, or if it was accidentally fixed in the ~4 > years between your original report and me going through the open bugs > of

Re: migrating gtk

On 5 February 2018 at 13:19, Morten Welinder wrote: >> Considering that you usually stop short of the first step I have to >> ask you: what kind of "busywork" have you ever experienced? > > Here's a sample: > https://bugzilla.gnome.org/show_bug.cgi?id=694627#c7 > > Yes, that

Re: migrating gtk

> Considering that you usually stop short of the first step I have to > ask you: what kind of "busywork" have you ever experienced? Here's a sample: https://bugzilla.gnome.org/show_bug.cgi?id=694627#c7 Yes, that was you. What did you really gain from asking that question, other than verifying

Re: migrating gtk

Hey Matthias, Sounds good. In the short experience with the migration it looks like it worked well to be as strict as possible, meaning, migrating the only the most relevant bugs. I would also take the opportunity to ack/nack pending patches if that is possible for gtk+. Just to double check,

Re: migrating gtk

On 4 February 2018 at 20:52, Morten Welinder wrote: > As a general principle, you should only ask bug reporters to do work if you > intend to do something with the answer. Or, with other words, it really is > not nice to keep asking "is that bug still there?" until they get

Re: migrating gtk

As a general principle, you should only ask bug reporters to do work if you intend to do something with the answer. Or, with other words, it really is not nice to keep asking "is that bug still there?" until they get tired of the busywork and leave in disgust. With that in mind, I believe it is

Re: migrating gtk

On 2 February 2018 at 15:04, Matthias Clasen wrote: > Hey Carlos, > > we discussed gitlab migration for gtk here at the hackfest. Our conclusions > were as follows: > > * We want to migrate the git repository as soon as possible > * For bugs: > * Do a sweep now, close

migrating gtk

Hey Carlos, we discussed gitlab migration for gtk here at the hackfest. Our conclusions were as follows: * We want to migrate the git repository as soon as possible * For bugs: * Do a sweep now, close all >5 year old bugs, needinfo all >1 old ones * Wait a few weeks, then close the