Update RoadMap page
This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
Update RoadMap page | Massimo Fidanza via gimp-developer-list | 27 Jun 23:53 |
Update RoadMap page | Alexandre Prokoudine via gimp-developer-list | 28 Jun 07:24 |
Update RoadMap page | Massimo Fidanza via gimp-developer-list | 29 Jun 12:54 |
Update RoadMap page | Alexandre Prokoudine via gimp-developer-list | 29 Jun 12:56 |
Update RoadMap page | Andrew Pullins via gimp-developer-list | 29 Jun 13:46 |
Update RoadMap page | Alexandre Prokoudine via gimp-developer-list | 29 Jun 14:11 |
Update RoadMap page | JLuc | 29 Jun 16:40 |
Update RoadMap page | Alexandre Prokoudine via gimp-developer-list | 29 Jun 19:56 |
Update RoadMap page | Andrew Pullins via gimp-developer-list | 30 Jun 12:32 |
Update RoadMap page | Alexandre Prokoudine via gimp-developer-list | 30 Jun 12:44 |
Update RoadMap page | Andrew Pullins via gimp-developer-list | 01 Jul 13:43 |
Update RoadMap page | Alexandre Prokoudine via gimp-developer-list | 01 Jul 13:48 |
Update RoadMap page | Andrew Pullins via gimp-developer-list | 02 Jul 20:03 |
Update RoadMap page | Alexandre Prokoudine via gimp-developer-list | 03 Jul 10:07 |
Update RoadMap page | JLuc | 03 Jul 10:00 |
Update RoadMap page
Hi,
Can roadmap page https://wiki.gimp.org/wiki/Roadmap be updated with current project status and references to Gitlab?
Il mer 27 giu 2018, 23:12 Ofnuts ha scritto:
This seems due to the script importing another module:
Traceback (most recent call last): File "E:\Gimp\Arakne\arakne-path-shape-creator8.py", line 35, in
import gtk, gimpui, pnt2d, drawUI ImportError: No module named pnt2d
In other words, the plugin main module is making the assumption that it is in the python path, so any module in the same directory can be imported. This doesn't seem to be true for the Windows version (the plugin works OK in Linux 2.10). This is possibly a bug in the Windows version.
On 06/25/18 07:26, Paco Garcia via gimp-developer-list wrote:
The scripts are working fine until the last gimp release, two of the scripts failing are:
http://www.arakne.es/en/dessign/gimp-guideslab-edit-guides-numerically/ and
http://www.arakne.es/en/programming/python/gimp-plugin-shape-creator-v8/Calling gimp with the verbose option don't give more clues about the
error:
Querying plug-in: 'C:\Users\yo\Desktop\gimp_plugins\pnt2d.py' gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error Querying plug-in: 'C:\Users\yo\Desktop\gimp_plugins\drawUI.py' gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error Querying plug-in:
'C:\Users\yo\Desktop\gimp_plugins\araknepathshapecreatorshapes.py' gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error Querying plug-in: 'C:\Users\yo\Desktop\gimp_plugins\arakne-stitch3b.py' Querying plug-in:
'C:\Users\yo\Desktop\gimp_plugins\arakne-path-shape-creator8.py' gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error Querying plug-in: 'C:\Users\yo\Desktop\gimp_plugins\arakne-guide-lab.py' gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error Querying plug-in: 'C:\Program Files\GIMP2\lib\gimp\2.0\plug-ins\gimpfu3.py'
Any help is welcome
2018-06-23 18:29 GMT+02:00 Carol Spears via gimp-developer-list < gimp-developer-list@gnome.org>:
On Sat, Jun 23, 2018 at 10:23 AM, Carol Spears wrote:
On Sat, Jun 23, 2018 at 8:25 AM, Ofnuts wrote:
On 06/19/18 21:43, Paco Garcia via gimp-developer-list wrote:
Is there any way to get more information about the gimp_wire_read () error
that occurs when loading python scripts? Many scripts that worked in previous versions of gimp fail in the new one without apparent cause. Spanish version:
¿Hay alguna forma de obtener mas información sobre el error gimp_wire_read() que se produce al cargar scripts de python?. Muchos scripts que funcionaban en versiones anteriores de gimp fallan en la nueva
sin causa aparente.
_______________________________________________I have seen plenty of such errors and they don't make the registration fail. In 2.10 for Windows, scripts that import pygtk can have problems
(you
have to make sure you import gimpfu first). Would you have the URL to
such
a script?
That's right. I've seen that error before though, but I write crappy python also. Maybe it is missing its beginning:
#!/usr/bin/env python # -*- coding: utf-8 -*-
or pygtk is not installed. Or maybe the script is a template and
broken
from the fill ins.
My earlier suggestion to poke around with it was not wrong, however.
Maybe the file is base64 or whatever that format was for mail in the
1980s.
carol
_______________________________________________ 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-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-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
Update RoadMap page
Yes, thanks for reminding :)
Alex
чт, 28 июн. 2018 г., 2:54 Massimo Fidanza via gimp-developer-list < gimp-developer-list@gnome.org>:
Hi,
Can roadmap page https://wiki.gimp.org/wiki/Roadmap be updated with current
project status and references to Gitlab?Il mer 27 giu 2018, 23:12 Ofnuts ha scritto:
This seems due to the script importing another module:
Traceback (most recent call last): File "E:\Gimp\Arakne\arakne-path-shape-creator8.py", line 35, in
import gtk, gimpui, pnt2d, drawUI ImportError: No module named pnt2d
In other words, the plugin main module is making the assumption that it is in the python path, so any module in the same directory can be imported. This doesn't seem to be true for the Windows version (the plugin works OK in Linux 2.10). This is possibly a bug in the Windows version.
On 06/25/18 07:26, Paco Garcia via gimp-developer-list wrote:
The scripts are working fine until the last gimp release, two of the scripts failing are:
http://www.arakne.es/en/dessign/gimp-guideslab-edit-guides-numerically/
and
http://www.arakne.es/en/programming/python/gimp-plugin-shape-creator-v8/
Calling gimp with the verbose option don't give more clues about the
error:
Querying plug-in: 'C:\Users\yo\Desktop\gimp_plugins\pnt2d.py' gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error Querying plug-in: 'C:\Users\yo\Desktop\gimp_plugins\drawUI.py' gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error Querying plug-in:
'C:\Users\yo\Desktop\gimp_plugins\araknepathshapecreatorshapes.py' gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error Querying plug-in: 'C:\Users\yo\Desktop\gimp_plugins\arakne-stitch3b.py' Querying plug-in:
'C:\Users\yo\Desktop\gimp_plugins\arakne-path-shape-creator8.py' gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error Querying plug-in:'C:\Users\yo\Desktop\gimp_plugins\arakne-guide-lab.py'
gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error Querying plug-in: 'C:\Program Files\GIMP
2\lib\gimp\2.0\plug-ins\gimpfu3.py'
Any help is welcome
2018-06-23 18:29 GMT+02:00 Carol Spears via gimp-developer-list < gimp-developer-list@gnome.org>:
On Sat, Jun 23, 2018 at 10:23 AM, Carol Spears <
wrote:
On Sat, Jun 23, 2018 at 8:25 AM, Ofnuts wrote:
On 06/19/18 21:43, Paco Garcia via gimp-developer-list wrote:
Is there any way to get more information about the gimp_wire_read
()
error
that occurs when loading python scripts? Many scripts that workedin
previous versions of gimp fail in the new one without apparent
cause.
Spanish version:
¿Hay alguna forma de obtener mas información sobre el error gimp_wire_read() que se produce al cargar scripts de python?.Muchos
scripts que funcionaban en versiones anteriores de gimp fallan en
la
nueva
sin causa aparente.
_______________________________________________I have seen plenty of such errors and they don't make the
registration
fail. In 2.10 for Windows, scripts that import pygtk can have
problems
(you
have to make sure you import gimpfu first). Would you have the URL
to
such
a script?
That's right. I've seen that error before though, but I write crappy python also. Maybe it is missing its beginning:
#!/usr/bin/env python # -*- coding: utf-8 -*-
or pygtk is not installed. Or maybe the script is a template and
broken
from the fill ins.
My earlier suggestion to poke around with it was not wrong, however.
Maybe the file is base64 or whatever that format was for mail in the
1980s.
carol
_______________________________________________ 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-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-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-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
Update RoadMap page
Hi Alex,
thank you for updating this. I noticed that others pages on the wiki are outdated.I want to help fix them, but I need to ask information to someone, which one is the best communication channel?
Massimo
2018-06-28 9:24 GMT+02:00 Alexandre Prokoudine via gimp-developer-list < gimp-developer-list@gnome.org>:
Yes, thanks for reminding :)
Alex
чт, 28 июн. 2018 г., 2:54 Massimo Fidanza via gimp-developer-list < gimp-developer-list@gnome.org>:
Hi,
Can roadmap page https://wiki.gimp.org/wiki/Roadmap be updated with current
project status and references to Gitlab?_______________________________________________ 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
Update RoadMap page
On Fri, Jun 29, 2018 at 3:54 PM, Massimo Fidanza wrote:
Hi Alex,
thank you for updating this. I noticed that others pages on the wiki are outdated.I want to help fix them, but I need to ask information to someone, which one is the best communication channel?
We usually use IRC for instant messaging, with a caveat that a person you need might not be online at the moment you join the channel.
Alex
Update RoadMap page
Would it be possible to move the roadmap to the Gnome GitLab milestones? This way the issues on GitLab link to milestones and the progress of that milestone would automatically be updated when issues are updated.
Andrew
--
Jesus is my Lord and Savior. Praise be unto God for giving us a way to live
with him.
On Fri, Jun 29, 2018 at 8:56 AM Alexandre Prokoudine via gimp-developer-list wrote:
On Fri, Jun 29, 2018 at 3:54 PM, Massimo Fidanza wrote:
Hi Alex,
thank you for updating this. I noticed that others pages on the wiki are outdated.I want to help fix them, but I need to ask information to
someone,
which one is the best communication channel?
We usually use IRC for instant messaging, with a caveat that a person you need might not be online at the moment you join the channel.
Alex _______________________________________________ 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
Update RoadMap page
On Fri, Jun 29, 2018 at 4:46 PM, Andrew Pullins wrote:
Would it be possible to move the roadmap to the Gnome GitLab milestones?
I don't understand how this would be done, exactly.
This way the issues on GitLab link to milestones and the progress of that milestone would automatically be updated when issues are updated.
The whole point of the Roadmap page is to tell people we know and care about the most important issues. It isn't meant to have every single issue listed.
Alex
Update RoadMap page
Le 29/06/2018 à 16:11, Alexandre Prokoudine via gimp-developer-list a écrit :
On Fri, Jun 29, 2018 at 4:46 PM, Andrew Pullins wrote:
Would it be possible to move the roadmap to the Gnome GitLab milestones?
I don't understand how this would be done, exactly.
Preventing duplicate milestones management attracted my thoughts :
On https://wiki.gimp.org/wiki/Roadmap there are big versions like "2.10.X" these are similar to gitlab milestones : https://gitlab.gnome.org/GNOME/gimp/milestones
And there are also so-called "features" like "High bit depths" or "UI themes".
As for now, gitlab's "Labels" are used mostly for metadatas aboug issues but a new category and color of labels could be created to follow these roadmap features.
The whole point of the Roadmap page is to tell people we know and care about the most important issues. It isn't meant to have every single issue listed.
The "board" can later be used to follow specific labels or milestone https://gitlab.gnome.org/GNOME/gimp/boards
Another way would be to define subgoal-milestones like "2.10.X.HighBitDepths" or "2.10.X.UIThemes" which would provide a global view in the milestone page. That view would be a bit more detailed.
JL
Update RoadMap page
пт, 29 июн. 2018 г., 19:41 JLuc:
Le 29/06/2018 à 16:11, Alexandre Prokoudine via gimp-developer-list a écrit :
On Fri, Jun 29, 2018 at 4:46 PM, Andrew Pullins wrote:
Would it be possible to move the roadmap to the Gnome GitLab milestones?
I don't understand how this would be done, exactly.
Preventing duplicate milestones management attracted my thoughts :
I feel lost in this discussion.
There is no duplicate management of milestones. The Roadmap page is mostly a PR thing, nothing else. No developers use it. There is no milestone management there.
Alexa
Update RoadMap page
There is no duplicate management of milestones. The Roadmap page is mostly a PR thing, nothing else. No developers use it. There is no milestone management there.
One thing that always frustrated me about the roadmap as a person who occasionally wondered how things were going. Was that some of the roadmap points would have bug reports hyperlinked while the features I was most interested in or did not understand did not. With milestones, every issue that would be attached to that milestone would be displayed. I would say that half the interest in the roadmap is to see how far along development is and the other half is to find out what will be in the next release/to see what the developers are working on.
-- Jesus is my Lord and Savior. Praise be unto God for giving us a way to live with him.
On Fri, Jun 29, 2018 at 4:01 PM Alexandre Prokoudine via gimp-developer-list wrote:
пт, 29 июн. 2018 г., 19:41 JLuc:
Le 29/06/2018 à 16:11, Alexandre Prokoudine via gimp-developer-list a écrit :
On Fri, Jun 29, 2018 at 4:46 PM, Andrew Pullins wrote:
Would it be possible to move the roadmap to the Gnome GitLab
milestones?
I don't understand how this would be done, exactly.
Preventing duplicate milestones management attracted my thoughts :
I feel lost in this discussion.
There is no duplicate management of milestones. The Roadmap page is mostly a PR thing, nothing else. No developers use it. There is no milestone management there.
Alexa
_______________________________________________ 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
Update RoadMap page
сб, 30 июн. 2018 г., 15:33 Andrew Pullins :
There is no duplicate management of milestones. The Roadmap page is mostly
a PR thing, nothing else. No developers use it. There is no milestone management there.
One thing that always frustrated me about the roadmap as a person who occasionally wondered how things were going. Was that some of the roadmap points would have bug reports hyperlinked while the features I was most interested in or did not understand did not. With milestones, every issue that would be attached to that milestone would be displayed. I would say that half the interest in the roadmap is to see how far along development is and the other half is to find out what will be in the next release/to see what the developers are working on.
https://gitlab.gnome.org/GNOME/gimp/milestones
That makes 2.10 only 37% ready (while released), the now obsolete 2.8 only 8% ready, and doesn't even begin to cover the amount of work on 3.0 that is untracked, because mitch et al. keep discovering ugly code as they go.
Given that, all estimations would be a lie.
Alex
Update RoadMap page
Sounds like these issues need to be recategorized then. All the 2.8.X and 2.10.X might need to be moved to the 3.0 release or perhaps removed from milestones.
--
Jesus is my Lord and Savior. Praise be unto God for giving us a way to live
with him.
On Sat, Jun 30, 2018 at 8:45 AM Alexandre Prokoudine via gimp-developer-list wrote:
сб, 30 июн. 2018 г., 15:33 Andrew Pullins :
There is no duplicate management of milestones. The Roadmap page is
mostly
a PR thing, nothing else. No developers use it. There is no milestone management there.
One thing that always frustrated me about the roadmap as a person who occasionally wondered how things were going. Was that some of the roadmap points would have bug reports hyperlinked while the features I was most interested in or did not understand did not. With milestones, every issue that would be attached to that milestone would be displayed. I would say that half the interest in the roadmap is to see how far along development is and the other half is to find out what will be in the next release/to see what the developers are working on.
https://gitlab.gnome.org/GNOME/gimp/milestones
That makes 2.10 only 37% ready (while released), the now obsolete 2.8 only 8% ready, and doesn't even begin to cover the amount of work on 3.0 that is untracked, because mitch et al. keep discovering ugly code as they go.
Given that, all estimations would be a lie.
Alex _______________________________________________ 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
Update RoadMap page
вс, 1 июл. 2018 г., 16:44 Andrew Pullins:
Sounds like these issues need to be recategorized then. All the 2.8.X and 2.10.X might need to be moved to the 3.0 release or perhaps removed from milestones.
And to people who will file bug reports against issues in, say, upcoming in 2.10.4 and hope to see that fixed in 2.10.6 this would be helpful how, exactly?
Alex
Update RoadMap page
And to people who will file bug reports against issues in, say, upcoming in 2.10.4 and hope to see that fixed in 2.10.6 this would be helpful how, exactly?
Ok I guess that makes sense, but what does not make sense is to keep issues
labeled as for 2.8.X, not fix the bug/make the feature then release 2.8.x
or any point release without doing something to the issue. If it is not
crucial to that point release and no one goes to work on the issue than why
is it labeled as being for the point release? Why not move it to future. If
someone works on it in time for the 2.10.6 release great. But if you devs
decide that issue X is not important enough for 3.0 why keep issues open
with 2.8.X, 2.9.X, or 2.10.X? Kinda makes the release look half backed if
there are still issues for the release not finished. That is my point.
--
Jesus is my Lord and Savior. Praise be unto God for giving us a way to live
with him.
On Sun, Jul 1, 2018 at 9:48 AM Alexandre Prokoudine via gimp-developer-list wrote:
вс, 1 июл. 2018 г., 16:44 Andrew Pullins:
Sounds like these issues need to be recategorized then. All the 2.8.X and 2.10.X might need to be moved to the 3.0 release or perhaps removed from milestones.
And to people who will file bug reports against issues in, say, upcoming in 2.10.4 and hope to see that fixed in 2.10.6 this would be helpful how, exactly?
Alex
_______________________________________________ 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
Update RoadMap page
Le 29/06/2018 à 21:56, Alexandre Prokoudine via gimp-developer-list a écrit :
There is no milestone management there.
milestones might not be up to date, but obviously there is some sort of milestone management.
JL
Update RoadMap page
On Mon, Jul 2, 2018 at 11:03 PM, Andrew Pullins wrote:
And to people who will file bug reports against issues in, say, upcoming in
2.10.4 and hope to see that fixed in 2.10.6 this would be helpful how, exactly?
Ok I guess that makes sense, but what does not make sense is to keep issues labeled as for 2.8.X,
You are welcome to join the team, test every 2.8.x bug report in 2.10.x, and update milestones.
If it is not crucial to that point release and no one goes to work on the issue than why is it labeled as being for the point release?
Because we don't always know if we work on a 2.10.x issue or feature request while 2.10.x development is still ongoing.
Kinda makes the release look half backed if there are still issues for the release not finished. That is my point.
It looks like you want to move things around solely for the purpose of the milestones completion chart look cool and be a lie :)
Alex