Re: [Gimp-developer] finalizing the task list
Hi Bill, On Sat, 2007-12-15 at 18:18 +, William Skaggs wrote: I think I probably would be able to come pretty close to turning the list that Chris Mohler created into a more-or-less complete 2.6 roadmap I don't think that a roadmap for 2.6 is what we are aiming for, at least not for publishing on the website. What we actually need is a not-too-long list of interesting tasks that shows where GIMP is heading. These tasks should be things that we agreed on, things that we are sure we want to see implemented sooner or later. Some of the items on this list can be marked as scheduled for 2.6, but most things on it will probably be open. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] finalizing the task list
I think I probably would be able to come pretty close to turning the list that Chris Mohler created into a more-or-less complete 2.6 roadmap, with one exception: I haven't been following the developments concerning gegl. I wonder, then, whether the people involved in developing gegl and applying it to gimp could comment on whether the following is okay: GEGL integration - write adapter/proxy functions/objects which enable GEGL graphs to read/write from/to GIMP PixelRegions - remove all color correction code from app/base and use GEGL operators instead - if feasible in the time frame, abstract some common color correction base API out of the above step and implement a simple color correction paint tool - look for more isolated spots that would allow us to get rid of legacy code in favor of GEGL operators. --- -- Bill ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] finalizing the task list
On Nov 26, 2007 1:58 AM, Sven Neumann [EMAIL PROTECTED] wrote: Hi, On Sun, 2007-11-25 at 18:52 -0600, Chris Mohler wrote: On Nov 22, 2007 1:03 AM, Sven Neumann [EMAIL PROTECTED] wrote: This is a nice start, but I think we need a lot more information in the short description. So one row per task is certainly not going to be sufficient. But it's probably a good idea to finalize the structure and layout before we go into filling in all the details. I trolled through Bugzilla and added anything with a 2.6 milestone. I *think* this is now a list of all possible tasks for 2.6. Eeek, no! I thought I had tried to make the purpose of this list clear. We already have Bugzilla and its milestones for the purpose of reminding us what needs to be done for 2.6. The task list is supposed to list a few tasks that we consider important and that show where GIMP development is heading. Your list now has about five times too many items. It will be rather difficult to get to the final list from there. OK - I thought it was too long also. Ignore the third version. I'm beginning to see the light - we need a short list of the most important items, with a nice description for each... I'll try again tonight. Chris ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] finalizing the task list
On Nov 22, 2007 1:03 AM, Sven Neumann [EMAIL PROTECTED] wrote: This is a nice start, but I think we need a lot more information in the short description. So one row per task is certainly not going to be sufficient. But it's probably a good idea to finalize the structure and layout before we go into filling in all the details. I trolled through Bugzilla and added anything with a 2.6 milestone. I *think* this is now a list of all possible tasks for 2.6. So now I need some feedback on what ought to be bumped to Future or 2.8, and also how this could be better organized. The meta tasks at the bottom are pretty much useless: if someone wants to propose specific areas to move forward with Cairo/GEGL I'm more than happy to add/outline them. http://cr33dog.fedorapeople.org/misc/gimp_task_list_03.html http://cr33dog.fedorapeople.org/misc/gimp_task_list_03.ods I will add a longer description for each task later (hopefully after shortening the list :) Chris ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] finalizing the task list
Hi, On Sun, 2007-11-25 at 18:52 -0600, Chris Mohler wrote: On Nov 22, 2007 1:03 AM, Sven Neumann [EMAIL PROTECTED] wrote: This is a nice start, but I think we need a lot more information in the short description. So one row per task is certainly not going to be sufficient. But it's probably a good idea to finalize the structure and layout before we go into filling in all the details. I trolled through Bugzilla and added anything with a 2.6 milestone. I *think* this is now a list of all possible tasks for 2.6. Eeek, no! I thought I had tried to make the purpose of this list clear. We already have Bugzilla and its milestones for the purpose of reminding us what needs to be done for 2.6. The task list is supposed to list a few tasks that we consider important and that show where GIMP development is heading. Your list now has about five times too many items. It will be rather difficult to get to the final list from there. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] finalizing the task list
On Nov 22, 2007 1:03 AM, Sven Neumann [EMAIL PROTECTED] wrote: Hi, On Wed, 2007-11-21 at 18:32 -0600, Chris Mohler wrote: On Nov 20, 2007 7:26 PM, Chris Mohler [EMAIL PROTECTED] wrote: Does this sound reasonable? Is there anything I missed? Any volunteers to work on this list? Formatted it a bit better: http://cr33dog.fedorapeople.org/misc/gimp_task_list_02.html http://cr33dog.fedorapeople.org/misc/gimp_task_list_02.ods This is a nice start, but I think we need a lot more information in the short description. So one row per task is certainly not going to be sufficient. But it's probably a good idea to finalize the structure and layout before we go into filling in all the details. OK. Should these tasks be added perhaps? http://wiki.gimp.org/gimp/ToDo I won't have much time to work on the list today, but I can make changes tomorrow or over the weekend. Chris ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] finalizing the task list
Hi, On Thu, 2007-11-22 at 10:55 -0600, Chris Mohler wrote: OK. Should these tasks be added perhaps? http://wiki.gimp.org/gimp/ToDo They should be considered, and as far as I can see, this has happened. But they don't belong on the task list unless we decide that they should go there. This list on the Wiki is a list of user wishes, added by less than a handful of users. It is very important that we listen to such requests. But our challenge is to use this information to identify the problems that the users are trying to address here. Then we can look for solutions that fit into the bigger picture. The bigger picture which is defined by our product vision and by the wishes and requests of all users. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] finalizing the task list
On Nov 20, 2007 7:26 PM, Chris Mohler [EMAIL PROTECTED] wrote: Does this sound reasonable? Is there anything I missed? Any volunteers to work on this list? Formatted it a bit better: http://cr33dog.fedorapeople.org/misc/gimp_task_list_02.html http://cr33dog.fedorapeople.org/misc/gimp_task_list_02.ods I will try to make time to hunt for BZ numbers and look at the UI spec this weekend. I may also go through the list again and see what I missed. Chris ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] finalizing the task list
Hi, On Wed, 2007-11-21 at 18:32 -0600, Chris Mohler wrote: On Nov 20, 2007 7:26 PM, Chris Mohler [EMAIL PROTECTED] wrote: Does this sound reasonable? Is there anything I missed? Any volunteers to work on this list? Formatted it a bit better: http://cr33dog.fedorapeople.org/misc/gimp_task_list_02.html http://cr33dog.fedorapeople.org/misc/gimp_task_list_02.ods This is a nice start, but I think we need a lot more information in the short description. So one row per task is certainly not going to be sufficient. But it's probably a good idea to finalize the structure and layout before we go into filling in all the details. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] finalizing the task list
Hi, since I don't seem to be getting to do it myself, I want to propose the details of the task list / roadmap that I would like to see published on www.gimp.org. Perhaps with your help it can be done... We discussed the roadmap here over the last few weeks and during that discussion a lot of development tasks have been proposed. I think many of them are in a state where we can say that we definitely want to implement this feature or do this change at some point. In my opinion it would be nice if we could collect these tasks into a list. This task list can then also serve the role of a roadmap. I imagine a list of tasks with short descriptions and a pointer to a bug report with more details. If no bug report exists yet, we should either create one or add a note that it still needs to be created. We should also mention if a UI specification is needed for a task. If it has even been written already, we should link to it. For the tasks where this is applicable, the list should also mention a tentative milestone. If someone is already working on it or has expressed to do so in this development cycle, his/her name should be added. Does this sound reasonable? Is there anything I missed? Any volunteers to work on this list? I hope that such a public task list can help to attract new developers. And I hope that it can show that development is active and into which direction it is steering. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] finalizing the task list
Does this sound reasonable? Is there anything I missed? Any volunteers to work on this list? Sounds reasonable to me. Since I never get around to contributing anything, I took a few minutes to copy-paste some items from the mailing list that came up this past month. It needs work - I haven't searched BZ or the UI spec yet to match up items either. Hopefully it can be a start at least. http://cr33dog.fedorapeople.org/misc/gimp_task_list.html http://cr33dog.fedorapeople.org/misc/gimp_task_list.ods Chris ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
