Re: [Gimp-developer] Getting involve in gimp development
On 3 February 2012 00:25, Michael Natterer wrote: > On Thu, 2012-02-02 at 22:47 +0200, Nadav Vinik wrote: > >> I can obligate for two hours each day (Sunday to Thursday) for a long >> time. (as long the development cycle won't take for -five years as >> this it) > > I have nothing to add to what Alexandre already said, but to get you > started, you should come to IRC, that's where most things are happening. What is the best hours to be there? > > --mitch > > -- הבלוג שלי: http://nadavvin.com ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Getting involve in gimp development
On Thu, 2012-02-02 at 22:47 +0200, Nadav Vinik wrote: > I can obligate for two hours each day (Sunday to Thursday) for a long > time. (as long the development cycle won't take for -five years as > this it) I have nothing to add to what Alexandre already said, but to get you started, you should come to IRC, that's where most things are happening. --mitch ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Getting involve in gimp development
On Fri, Feb 3, 2012 at 12:47 AM, Nadav Vinik wrote: > I suggest to do this: > UI in JavaScript, as it gnome3. only this will cause many programmers to join. :) Dear Nadav, I kindly suggest you to think in terms of priorities. Here is our TOP5, from most important to less important: 1. Finalize and release v2.8. 2. Merge GSoC2011 projects, adjust libgimp, release v2.10. 3. Finish the existing port to GTK+3. This is what we need to do _urgently_ to clear up the backlog of already implemented features and bring back a working support for Wacom tablets. Rewriting UI in another language simply has no place there. 4. Finalize move to GEGL for high bit depth support. 5. Implement non-destructive editing. Both of these features demand people willing to work on the image processing core which you want to be written in C anyway, and _this_ is where we still miss contributors _most_. Simply put, language for programming UI is not such an issue for the project (Martin will probably object here). OTOH, I certainly like the "I can spend this much time on it to help you" attitude that you demonstrated. I wish we had more of that. Alexandre Prokoudine http://libregraphicsworld.org ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] Getting involve in gimp development
Hello Gimp is a good software but due to its very slow development, It will be very sad that other free software will achieve it and Gimp become irrelevant. Since there are a few developers and it`s not fascinate the community to join, I don't fix that it good strategy to write it only in C. I suggest to do this: UI in JavaScript, as it gnome3. only this will cause many programmers to join. core parts which not demand a lot CPU in Vala high DEMAND CPU in C Since Vala is still in development language, I suggest firstly focus the UI javascript. I can obligate for two hours each day (Sunday to Thursday) for a long time. (as long the development cycle won't take for -five years as this it) Nadav -- הבלוג שלי: http://nadavvin.com ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
