Re: [Gimp-developer] Please migrate to GitHub/CMake

On Mon, May 8, 2017 at 6:05 PM, gregory grey wrote: > Cool. So basically you confirmed what I wrote before. I have to be > deemed worthy to get a response more detailed that "No". If that's what you choose to believe. > Your makefiles are special makefiles, unique in their awesomeness. See

Re: [Gimp-developer] Please migrate to GitHub/CMake

Cool. So basically you confirmed what I wrote before. I have to be deemed worthy to get a response more detailed that "No". Your makefiles are special makefiles, unique in their awesomeness. Good luck building user community, I'll go commit to Spark meanwhile. 2017-05-08 15:25 GMT+02:00 Alexandre

Re: [Gimp-developer] Please migrate to GitHub/CMake

> Von: "gregory grey" > In my experience "ain't broke" is a standard mantra of organizations > stuck in the past. GNOME *is* currently pondering to move to a different infrastructure - in particular to get issue tracking, revision management and continuous integrate more

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Mon, May 8, 2017 at 3:47 PM, gregory grey wrote: > @Alexandre - what exactly is your point here? That you have no experience releasing GIMP whatsoever. That you don't know our procedure. That you can't estimate how much time it takes to actually cut a release. That you don't know what you are

Re: [Gimp-developer] Please migrate to GitHub/CMake

On 8 May 2017 at 09:47, gregory grey wrote: I can get why are you trying to poke Alexandre on that - you are on an absolute "shoot the messenger" weird thing there. > In my experience "ain't broke" is a standard mantra of organizations > stuck in the past. > > It's a

Re: [Gimp-developer] Please migrate to GitHub/CMake

In my experience "ain't broke" is a standard mantra of organizations stuck in the past. It's a tent-pole phrase that does not explain anything, and justifies whatever practices you want it to justify. I say waiting 3 weeks for build under some platform is broken as hell, given you shoot for

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 4:07 PM, Liam R E Quin wrote: > Please remember that English is not the first language of everyone on > this list, and people come from a wide range of cultures. I don't think > Alexandre meant to be dismissive or rude with his "No" (and I think > Carol's

Re: [Gimp-developer] Please migrate to GitHub/CMake

First, to all - Please remember that English is not the first language of everyone on this list, and people come from a wide range of cultures. I don't think Alexandre meant to be dismissive or rude with his "No" (and I think Carol's comment was meant ironically although I'm not certain). GIMP

Re: [Gimp-developer] Please migrate to GitHub/CMake

I find conversation typically more friendly on IRC. Also, it's really awesome to be able to chat with project devs and others in the community in near real-time capacity. It's also easier to joke and share stuff without the need to spam the whole mailing list (not that anyone is doing that). My

Re: [Gimp-developer] Please migrate to GitHub/CMake

Hello, On Sun, 7 May 2017 16:33:49 +0300 Shlomi Fish wrote: > Dear Alexandre, > [snip] > As a side note regarding IRC - old does not necessarily imply it is bad (see > http://www.shlomifish.org/humour/fortunes/show.cgi?id=two-kinds-of-fools ) and > one can normally

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 9:13 PM, Boudewijn Rempt wrote: > And didn't take a lot of time. In 2006, that is, more than eleven years ago. That's the ticket :) Inkscape developers would tell a different story, and their one is fairly recent. Alex ___

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, 7 May 2017, Øyvind Kolås wrote: > If cmake (or perhaps meson http://mesonbuild.com/ ?) truely is so easy > to use and provides big benefits, a patch that should be simple to > make that uses this or a script that automigrates contents from > autofoo files demonstrating the cross platform

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 6:25 PM, Chris Moller wrote: > Yes, that's it. Some cool stuff on it, especially the "Future" section, but > it's not clear what's most important to you right now. All the stuff in the "Future" section is unprioritized. It's too far off to deal with it now. Pretty much

Re: [Gimp-developer] Please migrate to GitHub/CMake

Yes, that's it. Some cool stuff on it, especially the "Future" section, but it's not clear what's most important to you right now. --cm On 05/07/17 11:13, Alexandre Prokoudine wrote: On Sun, May 7, 2017 at 6:01 PM, Chris Moller wrote: As to your item 2. "There has been a problem to attract

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 6:01 PM, Chris Moller wrote: > As to your item 2. "There has been a problem to attract new developers and > contributors," I'd personally be glad to pitch in--I'm a retired IBM and Red > Hat developer and have been coding for a third of a century--but it's not at > all

Re: [Gimp-developer] Please migrate to GitHub/CMake

Any piece of code more complex than "Hello, World!" can asymptotically approach perfection, but it will never get there. In a sense, all code is always broken, so the questions are whether it's broken enough to warrant fixing, and the benefits versus the cost in labour of fixing it. I'd

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 12:31 PM, Ivano Arrighetta wrote: > I would like to suggest to migrate to GitHub for version control, and to > use CMake for creating build projects for Windows and Mac OS, other than > Makefiles for *nix. If cmake (or perhaps meson

Re: [Gimp-developer] Please migrate to GitHub/CMake

Le 07/05/2017 14:04, gregory grey a écrit : > It's not about Github necessarily, it's about the response tone etc. > You made a blog post, saying how small is the team and how much work you all > do. > Now, a person says "I'd like to suggest" and your reply is basically > "f*** off". Don't

Re: [Gimp-developer] Please migrate to GitHub/CMake

Le 07/05/2017 13:31, gregory grey a écrit : > Guys, I respect your work and I like Gimp a lot but this > >>> I would like to suggest to migrate to GitHub for version control >> >> No. > > is how you end up being a dead project. I won't say a dead project, but I can see your are unhappy by the

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 5:06 PM, Shlomi Fish wrote: > I see some problems with GIMP development: > > 1. It's been taking too long to release new major versions. > > 2. There has been a problem to attract new developers and contributors. > > 3. GIMP is lacking many features that are present in

Re: [Gimp-developer] Please migrate to GitHub/CMake

Hi Chris, On Sun, 07 May 2017 09:31:29 -0400 Chris Moller wrote: > There's an American expression, "If it ain't broke, don't fix it." > You can find a rebuttal of this phrase, in a different context here:

Re: [Gimp-developer] Please migrate to GitHub/CMake

Why do people wants to centralize over github ? I am seeing that question on many projects. Github has been unfriendly over free/libre software See: https://mikegerwitz.com/about/githubbub and the new TOS give them some strange copyright over your copyleft software (if you did put a copyleft

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 4:32 PM, gregory grey wrote: > Using Github is infrastructure decision if there is one. > > Why did you respond to question about it then? Because if nobody replied your emails _at all_, _that_ could be considered rude and unfriendly. > I have experience releasing

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 4:33 PM, Shlomi Fish wrote: > Dear Alexandre, > > I agree with Gregory that your original reply to the original suggestion was > phrased too laconically, and came across as rude, impolite, and unfriendly. > You > should try to improve such replies in the future, in order to

Re: [Gimp-developer] Please migrate to GitHub/CMake

There's an American expression, "If it ain't broke, don't fix it." GIMP development has been working well for a lot of years and I see exactly zero reason to change something that works well. I don't always agree with minor bits of what the devs decide to do, but THEY'RE doing the work and

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 07, 2017 at 02:04:04PM +0200, gregory grey wrote: > It's not about Github necessarily, it's about the response tone etc. [...] > and your reply is basically "f*** off". [..] > who knows better than behaving like a jerk. Who is the jerk here? -- Marco Ciampa I know a joke about

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 3:54 PM, gregory grey wrote: >>> Now, a person says "I'd like to suggest" and your reply is basically >>> "f*** off". >> >> It's an interesting way to interpret a simple 'no'. >> > > Turning tables much? You should interpret the number of developers on > the projects into

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 3:04 PM, gregory grey wrote: > It's not about Github necessarily, it's about the response tone etc. > You made a blog post, saying how small is the team and how much work you all > do. > Now, a person says "I'd like to suggest" and your reply is basically > "f*** off".

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 8:04 AM, gregory grey wrote: > . There is plethora > of other image editors, I can't see why I should not help someone else > who knows better than behaving like a jerk. > Oh gosh, and they are so much worse in real life!! carol

Re: [Gimp-developer] Please migrate to GitHub/CMake

It's not about Github necessarily, it's about the response tone etc. You made a blog post, saying how small is the team and how much work you all do. Now, a person says "I'd like to suggest" and your reply is basically "f*** off". I wrote 2 emails saying I can help with build infra, which is

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 07, 2017 at 01:42:57PM +0300, Alexandre Prokoudine wrote: > On Sun, May 7, 2017 at 1:40 PM, Ivano Arrighetta wrote: > > Hello there. > > My name is Ivano Arrighetta and I'm Italian. > > I would like to suggest to migrate to GitHub for version control > > No. > > > and to use > >

Re: [Gimp-developer] Please migrate to GitHub/CMake

On Sun, May 7, 2017 at 1:40 PM, Ivano Arrighetta wrote: > Hello there. > My name is Ivano Arrighetta and I'm Italian. > I would like to suggest to migrate to GitHub for version control No. > and to use > CMake for creating build projects for Windows and Mac OS, other than > Makefiles for *nix.

[Gimp-developer] Please migrate to GitHub/CMake

Hello there. My name is Ivano Arrighetta and I'm Italian. I would like to suggest to migrate to GitHub for version control, and to use CMake for creating build projects for Windows and Mac OS, other than Makefiles for *nix. GitHub also offers a WebSite builder and a Wiki for each repository,