On Fri, 18 May 2001, "Branko Collin" <[EMAIL PROTECTED]> wrote:
> My question is: when is a reworking of a script good enough to be
> included in the distribution? Is there some kind of policy for this?
Well, if you add some features that can generally be considered useful
and you do not remove existing features (breaking APIs), then you should
definitely submit a patch so that the updated script can be included in
a future release of the Gimp.
> As I understand, script-fu is also there so that anybody can write up
> their own scripts for their own purposes. Should I send the changed
> script to the original author with an explanation of what the changes
> are for?
There are basically four ways to submit your patches:
1 - Send them to the original author. But you should first try to
estimate when this author made his/her last contribution to the Gimp
because he might not be active anymore. Especially for Script-Fu,
many scripts have been updated in CVS since the original author
released them. In that case, the other three solutions are more
appropriate because the original author might not have the latest
version of the script.
2 - Post the patch to this list. The patch should be in "diff -u" format.
This only applies to small patches. If your patch exceeds a few dozen
lines, then you should consider the other solutions. People do not
like to receive big files in their mailboxes if they haven't asked for
3 - Submit a new bug report to http://bugzilla.gnome.org/ describing what
your patch does, set its severity to "enhancement" and attach the
patch file to the bug report using the "create attachment" feature.
4 - Store your patch in the incoming directory of ftp.gimp.org and send a
README file to the ftp admins, as described in the message that you
will get when you enter the incoming directory.
Gimp-developer mailing list