[forge-issues] [JBoss JIRA] (FORGE-991) Create a plugin/addon repository application for Forge

[George Gastaldi (JIRA)]

George Gastaldi created FORGE-991:
-------------------------------------

             Summary: Create a plugin/addon repository application for Forge
                 Key: FORGE-991
                 URL: https://issues.jboss.org/browse/FORGE-991
             Project: Forge
          Issue Type: Feature Request
          Components: Plugin Repository
            Reporter: George Gastaldi
             Fix For: 2.x Future


>From [~dan.j.allen]:
{quote}
I know that Forge has a plugin repository, but there's always room for new ideas.

The jQuery foundation recently rebooted their plugin registry to drive all contributions to it out of git. I thought you might be interested in reviewing how they set it up and see if any ideas might apply to Forge plugin registry, both in terms of how a plugin is registered and plugin discovery.

Announcement:
http://blog.jquery.com/2013/01/16/announcing-the-jquery-plugin-registry/

Plugin Registry:
http://plugins.jquery.com/

GitHub repo:
https://github.com/jquery/plugins.jquery.com

As they put it:

"The goal is to make sharing and browsing quality jQuery plugins a pleasant experience for everyone!"

Replace jQuery w/ Forge and we have the same goal.
{quote}

{quote}
Oh, and one more thing. I think this is the killer feature:

"To register and publish your plugin, you’ll need to push your code to a public repository on GitHub, and add our post-recieve webhook URL (http://plugins.jquery.com/postreceive-hook) to your repository. The next time you push a semver tag, we’ll take care of registering the plugin name and updating its page on the site. When you’re ready to release the next version of your plugin, just tag and push again!"
{quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira