Hi,

Piotr Legiecki writes:

I'd like to have a glimpse of what and *when* gimp is going to make next big step (after 2.0 release), or in other words when gimp is going to use gegl?

We are considering a slow migration towards GEGL since we want to avoid another large rewrite of the GIMP that would cause another endless development cycle. So at the moment we consider to start using some parts of GEGL after GIMP-2.0 is out. This does not necessarily mean that GIMP-2.2 will have significantly better support for color spaces or more color precision but it means that the GEGL development will get more momemtum and it will bring us one step closer to these goals.

I have just looked at gegl site and it looks quiet, very quiet. Actually it looks just like a year ago ;-( (I mean those % status). Am I looking at wrong (not updated) places?

Indeed. Websites do rarely say anything useful about the state of development of an open source project. If you had a look at CVS, you'd have noticed that there is indeed development going on.

Sven

Hi,

one more thing: Would you mind to finally add the information to Bugzilla that I keep asking for? You are opening bug reports and people express their interest to implement the features you are asking for. But when asking for more feedback, you keep quiet. This is certainly not a good way to motivate developers.

Sven

On 5 Nov 2003, at 10:35, Piotr Legiecki wrote:

I'd like to have a glimpse of what and *when* gimp is going to make next big step (after 2.0 release), or in other words when gimp is going to use gegl?

I have just looked at gegl site and it looks quiet, very quiet. Actually it looks just like a year ago ;-( (I mean those % status). Am I looking at wrong (not updated) places?

Sometimes Calvin needs to be prodded and poked a little to make him update the web site. I am sure if you asked him politely, he would update the site.

A much better source for checking out what's going on with GEGL (although not for a 'where are we now?' type of overview) is the CVS tree. See for instance

(or other views at ). As you can see from the Changelog, it's mostly one person working at it, although he keeps working at it steadily. There are several other people involved though. They are on this list, so they might tell you more.

Good luck,

On Wed, Nov 05, 2003 at 12:27:04PM +0100, Sven Neumann wrote:

avoid another large rewrite of the GIMP that would cause another endless development cycle. So at the moment we consider to start using some parts of GEGL after GIMP-2.0 is out. This does not necessarily mean that GIMP-2.2 will have significantly better support for color

Looking at the subject, I'd certainly say that the version that a) integrates gegl and b) makes full use of it (La*b*, fixed & floatingpoint etc.) would certainly qualify to be gimp-3.0 (I'd even say a major bump is a must) :)

Hi,

writes:

On Wed, Nov 05, 2003 at 12:27:04PM +0100, Sven Neumann wrote:

avoid another large rewrite of the GIMP that would cause another endless development cycle. So at the moment we consider to start using some parts of GEGL after GIMP-2.0 is out. This does not necessarily mean that GIMP-2.2 will have significantly better support for color

Looking at the subject, I'd certainly say that the version that a) integrates gegl and b) makes full use of it (La*b*, fixed & floatingpoint etc.) would certainly qualify to be gimp-3.0 (I'd even say a major bump is a must) :)

Agreed. However this doesn't keep us from starting to use some GEGL functionality earlier. This is all undecided yet but we consider to start by replacing GimpColor with GeglColor.

Sven

Hi,

I wrote:

we consider to start by replacing GimpColor with GeglColor.

^^^^^^^^^
That should read GimpRGB of course.

Sven

On 5 Nov 2003, Sven Neumann wrote:

Hi,

Piotr Legiecki writes:

Indeed. Websites do rarely say anything useful about the state of development of an open source project. If you had a look at CVS, you'd have noticed that there is indeed development going on.

Which brings up an interesting question -- how can an open source project accurately represent what is going on in developmentland on its web site? It's more of a question to ponder -- I don't have the answer myself. On first thought, a todo list with progress bars and lists of current scarry bugs would be good, and a Kernel Cousin-like newslog could be good, too.

Rockwalrus

Hi,

Nathan Carl Summers writes:

Which brings up an interesting question -- how can an open source project accurately represent what is going on in developmentland on its web site? It's more of a question to ponder -- I don't have the answer myself. On first thought, a todo list with progress bars and lists of current scarry bugs would be good, and a Kernel Cousin-like newslog could be good, too.

http://developer.gimp.org/ChangeLog http://developer.gimp.org/NEWS
http://bugzilla.gnome.org/buglist.cgi?product=GIMP&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED http://bugzilla.gnome.org/buglist.cgi?product=GIMP&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&bug_status=NEEDINFO&bug_severity=enhancement

All these are linked from the gimp.org web-site. We tried the nicer looking TODO.xml (and it's HTML counterpart) for a while but it didn't work and other projects that tried it, abandoned the idea as well.

Sven

Hi,

Nathan Carl Summers writes:

Which brings up an interesting question -- how can an open source project accurately represent what is going on in developmentland on its web site?

One thing I could imagine would be some sort of regular news update on GIMP development. Similar to kernel-cousin (you mentioned that already) or the Abiword Weekly News
(http://www.abisource.com/information/news/).

If someone was willing to do such a thing, that would of course be very much appreciated. I would volunteer to help by reviewing the information and by answering technical questions. This job probably involves following the mailing-lists, following GIMP development in CVS, reading the ChangeLogs and compiling the very latest version (in order to produce nice screenshots of new features). So if there's anyone listening who is doing all this anyway, perhaps that someone wants to become famous for writing a regular summary on GIMP development ?

Sven

Sven Neumann wrote:

Nathan Carl Summers writes:

Which brings up an interesting question -- how can an open source project accurately represent what is going on in developmentland on its web site?

One thing I could imagine would be some sort of regular news update on GIMP development. Similar to kernel-cousin (you mentioned that already) or the Abiword Weekly News
(http://www.abisource.com/information/news/).

Something like that once existed, but sadly it's asleep now: http://kt.zork.net/asleep.html