Thanks Alex, that makes it clearer. Just one thing. Could you please Copy&Paste this text to Gimp.org? You've put a lot of effort into it and it would be pity not to share it with the world. Here it will be forgotten (lost) very soon. On Wed, Jan 8, 2020, 18:04 Alexandre Prokoudine via gimp-developer-list < gimp-developer-list@xxxxxxxxx> wrote: > On Wed, Jan 8, 2020 at 7:17 PM Michal Vašut wrote: > > > > > By priority I meant that Gimp team is pushing new features (that don't > look > > like prerequisites for that manager) > > > Over the years, I've heard a lot of interesting ideas that suggest that > GIMP team members can replace each other or work on each other's tasks. > > You seem to be under the same kind of impression. Perhaps we should > communicate our roles and interests better. > > - Mitch knows GIMP in and out, can hack both back-end and front-end code, > but currently focuses on refactoring, all things color management, and > reviewing patches coming from other people. > > - Jehan has a wide range of interests mostly stemming from stuff his wife > needs for their animation project. He does both back-end and front-end work > related to painting and animation. But since plugins management is pain, > that's also among things he wants to improve. While he has a long history > of fixing bugs, he mostly works on new features. > > - Ell focuses on performance and new features that involve interaction on > the canvas. He understands the back-end very well and contributes to GEGL > as well. > > - Pippin has a comparatively light footprint in GIMP's source code, GEGL > and babl are the libraries where his contributions mostly go. Hence his > work directly affects how GIMP pushes pixels around and whether pixels get > pushed where they ought to be. > > - Thomas Manni works mostly on GEGL operations and also has a light > footprint in GIMP's code. But his work helps GIMP provide sensible, useful, > and fast filters for end-users. > > That's 5 top contributors in terms of code. Every one of them has his own > interests and specialization — an area where they shine. > > There are more contributors, like Massimo and Elle. Maybe they are supposed > to work towards plugin management. Well, nope. Let me tell you about them. > > Massimo is a prolific contributor of small sane patches that apply cleanly > and work very well. He mastered this art, and we treasure him for sticking > around and doing just that. We'd never expect him to do some massive work > involving redesigning GIMP, because, as far as I can tell, he's not exactly > interested in big stuff. > > Elle is amazing at what she understands very well — color science. Color > space converison, LAB/xyY/etc. spaces support in the color picker and > sample points — that's the kind of work she does. > > So when you are looking at Ell adding a 3D Transform tool or Thomas adding > a new GEGL filter, or Elle adding Yu'v' (CIE 1976 UCS) support to GIMP > color picker, please do not expect them to drop everything and start > hacking on something that is out of scope of their interest. This is not > how it works. > > I hoped I cleared this up a little. If you have more questions, shoot :) > > P.S. You did not say anything of the kind, but since this is related and > still preying on my mind, to everyone who thinks contributors should have > worked on CMYK support or non-destructive image editing instead of > designing the greyscale icon theme I'll just say this: Pffffffff :) > > Alex > _______________________________________________ > gimp-developer-list mailing list > List address: gimp-developer-list@xxxxxxxxx > List membership: > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
