No benefit for me, doesn't matter to me which organization hosts it.
But it makes it easier for the other distributing organizations if it is
in Gimp: one less package.

I suppose I could also maintain other plugins once I learned the ropes.
I would prefer Python.  I've done much exploring of the PyGimp code.

Hate to say it but one benefit for the users is that if the
Resynthesizer comes with the Gimp, then it comes with the MS Windows
build of Gimp, which seems to be a frequent source of problems for
Resynthesizer users.

The main benefit argument is that the plugin is very useful and ought to
be one of the core plugins.



On Wed, 2010-05-19 at 23:49 +0200, Sven Neumann wrote:
> On Wed, 2010-05-19 at 10:03 -0400, lloyd konneker wrote:
> > This is a request to put the Resynthesizer plugin in the Gimp project.
> > 
> > The author, Paul Harrison, has given me permission to maintain
> > Resynthesizer.
> 
> Well, if you maintain the plug-in, that is very good. We really don't
> have enough resources to maintain more plug-ins in the GIMP tree. We
> would love to see even more plug-ins maintained outside the GIMP source
> tree.
> 
> What would be the benefit for you and the core GIMP developers (and the
> users of course), if the plug-in was maintained in the GIMP source tree?
> 
> 
> Sven
> 
> 


_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Reply via email to