Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
On Sun, May 02, 2004 at 01:31:20AM -0500, Wilson Jimmy - jiwils wrote:
> I might could help out if you would give me some idea of the time/effort
There's no time obligations -- just package a few plugins here and
there. When enough are packaged, we release a batch.
We would give you access to the plugin submission tracker. You then pick
the ones you want to package, and assign them to your SF username.
In terms of effort, these are the steps to packaging a plugin:
- Get the source -- from CVS, or a download link, etc.
- Make sure the build layout conforms to the plugin build guidelines; if
not, make necessary changes and bitch at the developer :)
- Compile the plugin -- we always compile plugins, instead of using
binaries provided by developers.
- Quick review of plugin core class to catch obvious mistakes like
adding listeners in start() and not removing them in stop() (which
would cause memory leaks on unloading the plugin in 4.2).
- Make sure there is documentation.
- Quick test of the plugin to catch obvious breakage.
- Make sure version number in properties matches advertised version
number; make sure 'activate' property is not 'defer' only if
- Create ZIP/TAR.GZ packages, upload them to the SourceForge server.
You (or anybody else who's interested) can drop by #jedit on IRC. Me and
Ollie can get you started off and give you pointers. Really, there's
not much to it, its just basic QA.