Where to upload?
smitchel writes:
My son and I wrote some code for Xemacs and while it is useful to
us and adds to our user experience--and we want to share, I don't
think it is enough to make a package out of it. Do all things need
to be made into packages to b e distributed?
If you want it distributed by xemacs.org, yes, practically it needs to
be in a package. (In theory it could be added to core XEmacs, but
XEmacs 21.4 core is basically permanently feature-frozen, so it would
only be available to XEmacs 21.5 users. But if the code is in a
package 21.4 users can use it too.)
Alternative informal distributions are possible in several ways: via
public hosting facilities like Savannah, SourceForge, Google Code, or
github, by posting to the emacswiki (emacswiki.org), or by posting to
the newsgroup gnu.emacs.sources.
Is that what I should do?
That depends. If some parts of the code are closely related to
existing functionality of some package, they could be added to that
library. If a related segment of the code is moderate-sized (50 lines
of code and user documentation, without license boilerplate and hacker
documentation), it can be put into a separate file and added to an
existing package. If it's all thematically related and there's no
existing package that's a good match, then making a new package makes
sense.
You can also just post it here on XEmacs Beta if it's not too large
(up to say 50kB). Once it's decided to add the code and where to put
the package, it's rarely much work for us to make a package out of
your code.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta