Re: [Gimp-developer] Code for editing in non-sRGB color spaces
Hi Elle, On 13.4.2016 at 11:18 PM Elle Stone wrote: On 04/13/2016 03:16 PM, Sven Claussner wrote: thank you for your contribution and sorry for not replying earlier. I didn't have the time yet to read all your lines yet, but how about pushing your work to separate branches in babl, GEGL and GIMP? Currently I don't have commit rights. But when I finish the new patches, it would be nice to be able to upload them to branches where people can test, review, etc. We could review and refine them there and make builds on Jenkins for testing. When they have matured for integration they should go then into the master branches. If you need help with development let us know. Perhaps someone could set up suitable branches of babl/GEGL/GIMP? It's best to set them up yourself, because even if we did you'd had to pull them and apply your patches there. Setting up branches is easy and perhaps you've already done it in your local workspace: git checkout -b $mybranch Instead of $mybranch use wip-not-only-sRGB or what fits best. To get your branches upstream, follow this: https://wiki.gnome.org/Git/Developers#Pushing_your_changes_upstream To get a GNOME Git account just follow this tutorial: https://wiki.gnome.org/action/show/AccountsTeam/NewAccounts?action=show=NewAccounts In step 1 'Explanation why you think you should get an account' write that you need it to contribute to babl, GEGL and GIMP. I cc'ed to Mitch (or Pippin, too) so he can give his OK on admins request. Greetings Sven ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] Enhancement request policy
Hi, in the light of current events one problem comes up again: how do we deal with enhancement requests reported in Bugzilla? Currently we count 1'193 open GIMP bugs, of which 607 are enhancement requests. We're drowning in them. In 2015 Jim DeLaHunt pointed out a discrepancy between the website and the documentation, see https://mail.gnome.org/archives/gimp-developer-list/2015-February/msg3.html Unfortunately the topic wasn't discussed, but still persists and is in a current case time consuming and going blue. In the past I already closed bugs as INVALID until they are agreed upon on the mailing list, but it wasn't considered the best solution. Actually we put the bug on hold, but Bugzilla has no bug state for this. How about this: 1. On enhancement requests we check for Bugzilla duplicates and former mailing list discussions. On duplicates and formerly disagreed requests we close the bug with a suitable reason as DUPLICATE or WONTFIX. 2. If the request is not a duplicate we answer with an friendly stock answer and ask to bring the topic to the developer mailing list. If it's a pure GUI topic, then to the gimp-gui mailing list. Until the topic is discussed with a clear result, we set the bug into NEEDINFO state. 3. On agreement we set the bug into state NEW, otherwise close it as WONTFIX. If the reporter refuses to post the request to the mailing list, then either we post it there if we think it's useful, otherwise we close it as INVALID. If no further discussion is ongoing we close the bugs after an agreed period of time, e.g. 3 weeks since reporting. The goals are getting useful feedback, while keeping the bug base small. It would be nice if we found a final solution now and made it clear at the website and in the documentation. Greetings Sven ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Code for editing in non-sRGB color spaces
Hi Elle, On 9.4.2016 at 10:32 PM Elle Stone wrote: I made the assumption that the very talented babl/GEGL/GIMP developers are capable of writing code that can send colorant information from GIMP to babl. On the basis of this assumption, I made a list of all the code files in babl/GEGL/GIMP that would require patching: http://ninedegreesbelow.com/files/patch-gimp/user-chosen-rgb/hard-coded-srgb.ods Then I wrote some "proof of concept" patches for providing GIMP users with the ability to edit in RGB working spaces other than sRGB: http://ninedegreesbelow.com/files/patch-gimp/user-chosen-rgb/proof-of-concept-patches.tar.gz I also wrote an overview of the task of patching babl/GEGL/GIMP to allow for editing in a user-chosen RGB working space: Modifying bab/GEGL/GIMP for editing in user-chosen RGB working spaces http://ninedegreesbelow.com/photography/gimp-edit-in-user-chosen-rgb-working-space.html thank you for your contribution and sorry for not replying earlier. I didn't have the time yet to read all your lines yet, but how about pushing your work to separate branches in babl, GEGL and GIMP? We could review and refine them there and make builds on Jenkins for testing. When they have matured for integration they should go then into the master branches. If you need help with development let us know. Greetings Sven ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
