As someone with dozens of plugins and very little time, it's very unlikely I'll be able to spend the administrative time to create and manage my own Google Code project. For those with only one or two plugins the overhead would be even higher.
Without sounding too pessimistic, this approach (I believe) will tend to minimise input, rather than maximise it. There aren't that many people willing to manage entire projects composed of just one or two plugins. I'm not sure what the ideal solution is, but this (frankly) doesn't sound like it. Perhaps more dialogue about how to balance the input of contributors vs. the need for stable releases is in order... Ichiro On Thu, Mar 14, 2013 at 2:37 AM, Jürgen Weber <[email protected]> wrote: > I also support Glen's suggestion with code.google.com, even I see it a > bit of overkill when you have a project for a 200 liner plugin. > > Hope the new JSPwiki powered Apache wiki site will be up soon. > > Cheers, > Juergen
