Hi Kevin,
The sandbox was created to give existing Apache committers a place to
create plugins that may potentially be brought up to full released
plugins. The benefits to putting them here are that the infrastructure
with all the other plugins will be shared (Jira, Svn,Site etc) and it's
the first place people look for plugins. If you aren't already an Apache
committer, then an option would be to try the mojo project on codehaus
(http://mojo.codehaus.org). This is where we host plugins that don't
meet Apache licenses, or are developed by non-apache committers (or they
choose to put it there for other reasons). The barriers to entry are
lower in mojo, but you still need to be active for a while and submit
plugins and patches via jira until you get voted in with full commit
rights.

Hosting a plugin yourself can certainly be easier in the short term, but
you will get more exposure and potential users and developers on either
of the 2 communities I mentioned. It's also easier to get your builds
onto the central repository so people can easily use them.

Hope that helps.

--Brian

-----Original Message-----
From: Kevin Menard [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 05, 2007 8:05 AM
To: [email protected]
Subject: Sandbox question

Hi all,

I have an immature jython plugin I've been working on that has largely
been used internally.  It looks like something that the sandbox could be
useful for, but I'm debating the merits of just hosting it myself.  I
guess what would help me is understand what the sandbox provides.  Is it
just an SVN area?  Where would plugin docs, site, etc. be hosted?  Is
there some sort of graduation path up to a fully supported plugin?

Thanks,
Kevin

Kevin Menard
Servprise International, Inc.
800.832.3823 x308 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to