On Thu, Mar 14, 2013 at 1:32 PM, Glen Mazza <glen.ma...@gmail.com> wrote:
> Well, some risks if you did--half-done plugins starting to accumulate > under apache-extras, people uploading insert-porn-picture or similar nasty > plugins, copyrighted work being uploaded, unhealthy code dependencies being > created between plugins, vandalism/bad coding wrecking many plugins > compared to just a few if they were hosted in multiple locations. [snip] This was the situation with www.jspwiki.org; luckily nothing nasty occured (that I was aware of). Just wondering which is/are the most comfortable way/s for contributors. Don't mind opening a project wherever and grant commit access per request if that eases contributions. If someone prefers to hold his contributions on github that's ok too. The serve-yourself approach at www.jspwiki.org worked reasonably well so I my intention was to mimic that approach as much as possible. Giving it a second thought, maybe the important thing isn't where are the contributions holded, but to keep track them from the yet-to-be-created contributions page.. cheers, juan pablo [/snip] Glen > > > > On 03/14/2013 06:10 AM, Juan Pablo Santos Rodríguez wrote: > >> Hi, >> >> I also thought about the overhead of creating a project for a plugin (with >> maybe just one or two classes) >> >> what about having a project at apache-extras for these kind of situation? >> Just we don't enforce anyone to >> commit his/her contributions there, we're going to have a "contributions" >> page on the website anyway >> so we can link there whatever we want >> >> >> br, >> juan pablo >> >> On Thu, Mar 14, 2013 at 10:49 AM, Ichiro Furusato < >> ichiro.furus...@gmail.com >> >>> wrote: >>> 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 <webe...@gmail.com> 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 >>>> >>> >
