Re: [Gimp-developer] How do I get a plugin into the offical release?
On Tue, 23 Sep 2003, David Neary wrote: > Henrik Brix Andersen wrote: > > According to http://registry.gimp.org/changes?max=15 the last change to > > a plug-in was done only a couple of days ago - so it seems the registry > > works at least for some people. > > Perhaps, but there are several things which should be possible > which aren't. > > First, the majority of the plug-ins in the registry appear to be > abandonware - 1.0 plug-ins that have never been updates to 1.2, > never mind 1.3/2.0. We need a way to clean out the cruft (or at > least hide it away). > > Second, the registry could do with a ranking system to have the > most common and/or popular plug-ins appearing on the top of the > lists of plug-ins. The only sorting system I've seen is > alphabetically, which severely limits the usefullness of the site. > > Third, it is not possible to attach patches for existing > plug-ins to a plug-in without being a plug-in maintainer. It > would be nice if this were easier to do, perhaps with a comment > system? Although I guess an inscription system makes some > sense... This functionality sounds a lot like MozDev, which has a very useful list of active projects, or Sourceforge (or Gnu/Savannah/Whatever). Changing to a full blown project management system might make things easier to manage in the long run. Something to consider at least. - Alan H ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] How do I get a plugin into the offical release?
Carol Spears wrote: http://wiki.gimp.org/ is a nice holding place until the other > stuff gets ironed out, imo. OK, I've put DBP up there because I think it's the most useful. I might add some others later. Let me know (or, I guess, just edit it) if I've done something horribly wrong. -- David Hodson -- this night wounds time ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] How do I get a plugin into the offical release?
David Neary wrote: > Henrik Brix Andersen wrote: >>According to http://registry.gimp.org/changes?max=15 the last change to >>a plug-in was done only a couple of days ago - so it seems the registry >>works at least for some people. > > Perhaps, but there are several things which should be possible > which aren't. > > First, the majority of the plug-ins in the registry appear to be > abandonware - 1.0 plug-ins that have never been updates to 1.2, > never mind 1.3/2.0. We need a way to clean out the cruft (or at > least hide it away). > > Second, the registry could do with a ranking system to have the > most common and/or popular plug-ins appearing on the top of the > lists of plug-ins. The only sorting system I've seen is > alphabetically, which severely limits the usefullness of the site. > > Third, it is not possible to attach patches for existing > plug-ins to a plug-in without being a plug-in maintainer. It > would be nice if this were easier to do, perhaps with a comment > system? Although I guess an inscription system makes some > sense... Fourth, there needs to be a way to recover your password or something! My plugins died in the registry because the ability to update them was locked to an account that I'd forgotten the password to. --Adam -- Adam D. Moss . ,,^^ [EMAIL PROTECTED] http://www.foxbox.org/ co:3 ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] How do I get a plugin into the offical release?
David Neary wrote: I'm not sure the plug-in registry likes anyone :) Who *is* responsible for maintaining it? Ingo is listed as the contact, and his email address is there. I did get a reply from him when I was having problems (in May this year), but we couldn't solve them. (Or maybe I lost interest.) (BTW, sorry I replied to you instead of the list.) -- David Hodson -- this night wounds time ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] How do I get a plugin into the offical release?
Henrik Brix Andersen wrote: > According to http://registry.gimp.org/changes?max=15 the last change to > a plug-in was done only a couple of days ago - so it seems the registry > works at least for some people. Perhaps, but there are several things which should be possible which aren't. First, the majority of the plug-ins in the registry appear to be abandonware - 1.0 plug-ins that have never been updates to 1.2, never mind 1.3/2.0. We need a way to clean out the cruft (or at least hide it away). Second, the registry could do with a ranking system to have the most common and/or popular plug-ins appearing on the top of the lists of plug-ins. The only sorting system I've seen is alphabetically, which severely limits the usefullness of the site. Third, it is not possible to attach patches for existing plug-ins to a plug-in without being a plug-in maintainer. It would be nice if this were easier to do, perhaps with a comment system? Although I guess an inscription system makes some sense... > > In the meantime, as Carol suggested it might be an idea to use > > the wiki to collect these kinds of external resources, in the > > absence of a registry which gets updated. > > Hmmm... another duplication of effort? Why have two places to store user > committed plug-ins? Wouldn't the time be better spent on say, > maintaining registry.gimp.org? Sure - "In the meantime" was meant to be "until the plug-in registry is maintained". I would still like to know who is running the site. Is Ingo still active on it? Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] How do I get a plugin into the offical release?
On Tue, 2003-09-23 at 10:01, David Neary wrote: > I'm not sure the plug-in registry likes anyone :) Who *is* > responsible for maintaining it? According to http://registry.gimp.org/changes?max=15 the last change to a plug-in was done only a couple of days ago - so it seems the registry works at least for some people. > In the meantime, as Carol suggested it might be an idea to use > the wiki to collect these kinds of external resources, in the > absence of a registry which gets updated. Hmmm... another duplication of effort? Why have two places to store user committed plug-ins? Wouldn't the time be better spent on say, maintaining registry.gimp.org? Sincerely, ./Brix -- Henrik Brix Andersen <[EMAIL PROTECTED]> ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] How do I get a plugin into the offical release?
David Hodson wrote: > I really don't have the time to take on a maintenance job - I have > too many of my own projects to finish. Plus, I don't think that the > plugin registry likes me. I have some very old plugins there, but > every time I try to update them I can't get access. I'm not sure the plug-in registry likes anyone :) Who *is* responsible for maintaining it? In the meantime, as Carol suggested it might be an idea to use the wiki to collect these kinds of external resources, in the absence of a registry which gets updated. Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] How do I get a plugin into the offical release?
http://wiki.gimp.org/ is a nice holding place until the other stuff gets ironed out, imo. carol David Hodson wrote: I've got a bunch of plugins on my website, a couple of which are reasonably stable and mature. (OK, so they're built against 1.2 at the moment.) Who decides on the offical plugin list? For the interested, check out wideangle, degrain, and DBP (and maybe Cineon/DPX, although that's fairly specialised) at: http://members.ozemail.com.au/~hodsond/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] How do I get a plugin into the offical release?
David Hodson wrote: > I've got a bunch of plugins on my website, a couple of which > are reasonably stable and mature. (OK, so they're built against > 1.2 at the moment.) Who decides on the offical plugin list? The official plug-ins are the ones in the main GIMP CVS repository. In general, a plug-in will get accepted if it's (1) reasonably bug free, (2) doing things like data access in a gimpish way, and (3) has an official active maintainer. Oh, and (4) is useful :) Unfortunately, several plug-ins which have in the past been included in the main GIMP distribution, and have then "lost" their maintainer, giving a rather big maintenance headache. Also, plug-ins weren't always bug-free when accepted. There was a time when we were pretty promiscuous about what we accepted (before my time...) Because of the aforementioned maintenance, the standards have been somewhat raised. However, several plug-ins have been accepted into 1.3. > For the interested, check out wideangle, degrain, and DBP (and > maybe Cineon/DPX, although that's fairly specialised) at: Would you be interested in helping keep the plug-in registry up-to-date? It's a job that needs doing, and I honestly don't know who was responsible for that before... I know that Carol was also interested in maintaining a list of 3rd party plug-ins, perhaps you could get talking to each other? Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] How do I get a plugin into the offical release?
I've got a bunch of plugins on my website, a couple of which are reasonably stable and mature. (OK, so they're built against 1.2 at the moment.) Who decides on the offical plugin list? For the interested, check out wideangle, degrain, and DBP (and maybe Cineon/DPX, although that's fairly specialised) at: http://members.ozemail.com.au/~hodsond/ -- David Hodson -- this night wounds time ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer