Hi Jürgen (et all), apologies on not creating the JIRA component yet, had a real busy week..
I've just asked on general@i.a.o about his and they've kindly pointed me to http://code.google.com/a/apache-extras.org/hosting/ which seems to fit a lot better than an undetermined number of JIRAs (we get svn, issue tracker, downloads section, etc.). So, I see two possibilities: 1.- we can create one jspwiki-[contrib|extras|whatever] project there, and grant commit access to whoever asks. We add a link on the website. This way contributions will be easier to track, look at, and promote 2.- whoever wants to develop his/her extension(s) opens a project in there, labelling it at least with "jspwiki". We add a link to the tag on the website. This option is easier to set up, as anyone anytime can open a new project, not depending on anyone to start his/her project, but linking to a tag will decrease its visibility (i.e.: it's difficult to see at a glance what are the different projects at http://code.google.com/a/apache-extras.org/hosting/search?q=label%3aMaven) I'm more inclined to option #1 but, @all, WDYT? br, juan pablo On Thu, Mar 7, 2013 at 9:29 AM, Juan Pablo Santos Rodríguez < juanpablo.san...@gmail.com> wrote: > Hi, > > I'd prefer a Jira per plugin. I'll create a "Contributions" component on > Jira this afternoon, so we can reach all contributed > plugins/filters/templates/whatever from one URL > > Also, another possibility could be set up a jspwiki-extras account on > github/google code/etc., granting commit access per request (something > similar to what is done on Jenkins). @all: WDYT? > > > br, > juan pablo > > > On Wed, Mar 6, 2013 at 2:33 PM, Jürgen Weber <webe...@gmail.com> wrote: > >> Hi, >> >> jspwiki.org is r/o now, so, how does one contribute plugins nowadays? >> Create a jira for each plugin and add the source? Or have a meta Jira >> that contains all contributed plugins? >> >> Thx, Juergen >> > >