[forge-dev] a reference example of a plugin repository
dan.j.allen at gmail.com
Mon Apr 1 15:35:25 EDT 2013
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!"
On Mon, Apr 1, 2013 at 1:34 PM, Dan Allen <dan.j.allen at gmail.com> wrote:
> 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.
> On Mon, Apr 1, 2013 at 1:33 PM, Dan Allen <dan.j.allen at gmail.com> wrote:
>> 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
>> Plugin Registry:
>> GitHub repo:
>> Dan Allen
>> Principal Software Engineer, Red Hat | Author of Seam in Action
>> Registered Linux User #231597
> Dan Allen
> Principal Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the forge-dev