Where are the grails plugins sources?

[a.shneyderman]

Hi, guys!

There used to be a prominent link somewhere on the grails site that I
can not locate anymore.

Is there a document that has some guidance on what it takes

1. To have a JIRA for the plugin?
2. To take over a plugin that does not seem to be maintained?

Cheers,
Alex.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Graeme Rocher-2]

What plugin in particular are you interested in contributing to? Those still hosted on SVN can be found at http://plugins.grails.org/

-- 

Graeme Rocher

On Wednesday, February 22, 2012 at 3:26 PM, Alex Shneyderman wrote:

Hi, guys!

There used to be a prominent link somewhere on the grails site that I

can not locate anymore.

Is there a document that has some guidance on what it takes

1. To have a JIRA for the plugin?

2. To take over a plugin that does not seem to be maintained?

Cheers,

Alex.

---------------------------------------------------------------------

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[pledbrook]

> There used to be a prominent link somewhere on the grails site that I
> can not locate anymore.
>
> Is there a document that has some guidance on what it takes
>
> 1. To have a JIRA for the plugin?
> 2. To take over a plugin that does not seem to be maintained?

I don't think we have this information on the site.

1. Ask here for one. We don't have a better approach than this right
now. It would be nice to have something integrated into the plugin
portal.
2. Attempt to contact the original author and get them to send a
message to dev mailing list that the transfer is OK. If you don't get
a response, send an email to dev list saying you want to take over a
particular plugin. We'll go from there.

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Matthias Hryniszak]

I'm kind of interested in the second question. How do you take over a plugin that's not maintained anymore but still adds value to projects - just needs to be updated with bug fixes and/or external dependency updates.

In the past I've done it with the routing plugin (which was probably the worst idea ever) making a fork of the camel plugin and building on top of it the necessary adjustments. But that adds to the overall confusion...

 Matthias

2012/2/22 Peter Ledbrook <[hidden email]>

> There used to be a prominent link somewhere on the grails site that I
> can not locate anymore.
>
> Is there a document that has some guidance on what it takes
>
> 1. To have a JIRA for the plugin?
> 2. To take over a plugin that does not seem to be maintained?

I don't think we have this information on the site.

1. Ask here for one. We don't have a better approach than this right
now. It would be nice to have something integrated into the plugin
portal.
2. Attempt to contact the original author and get them to send a
message to dev mailing list that the transfer is OK. If you don't get
a response, send an email to dev list saying you want to take over a
particular plugin. We'll go from there.

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[a.shneyderman]

> 1. Ask here for one. We don't have a better approach than this right
> now. It would be nice to have something integrated into the plugin
> portal.

ok, I guess for this plugin I do not really need to have JIRA project
as it is not a plugin that has/will have much of activity. I just did
not know if every plugin gets a project JIRA, hence the question.

> 2. Attempt to contact the original author and get them to send a
> message to dev mailing list that the transfer is OK. If you don't get
> a response, send an email to dev list saying you want to take over a
> particular plugin. We'll go from there.

Ok, I did ask on the user list (about hibernate filters plugin). No
answer. So, I would like to fix a bug (it turns out that there is
actually a JIRA for it already) and release a new version. Is there
anything special that I need to do to be able to "take over" the
plugin's maintenance? I do have an account on codehaus already and I
am grailsplugins project member. Is there anything else that I have to
need?

Cheers,
Alex.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email