Re: [forge-dev] a reference example of a plugin repository

I find these various combinations of custom registries fascinating - all so damn flexible but makes it more or less impossible to have a notion of a registry/stream with custom patches. i.e. maven have mirrors and qualifiers for this; rpm's has arch and distro type (and repo lists); how does something like this works in things like jquery and forge world ? This is not a bitching question btw. i'm honestly interested in finding out how it can be done without too much manual fiddling. /max On Mon, Apr 01, 2013 at 05:05:59PM -0300, ggastald(a)redhat.com wrote: >This is absolutely awesome !! Thanks for the suggestion Dan, we'll >really look forward to implementing something like it > >On 04/01/2013 04:35 PM, Dan Allen wrote: >> 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!" >> >> -Dan >> >> >> On Mon, Apr 1, 2013 at 1:34 PM, Dan Allen <dan.j.allen(a)gmail.com >> <mailto:dan.j.allen@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. >> >> -Dan >> >> >> On Mon, Apr 1, 2013 at 1:33 PM, Dan Allen <dan.j.allen(a)gmail.com >> <mailto:dan.j.allen@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 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 >> >> -Dan >> >> -- >> Dan Allen >> Principal Software Engineer, Red Hat | Author of Seam in Action >> Registered Linux User #231597 >> >> http://google.com/profiles/dan.j.allen >> http://mojavelinux.com >> http://mojavelinux.com/seaminaction >> >> >> >> >> -- >> Dan Allen >> Principal Software Engineer, Red Hat | Author of Seam in Action >> Registered Linux User #231597 >> >> http://google.com/profiles/dan.j.allen >> http://mojavelinux.com >> http://mojavelinux.com/seaminaction >> >> >> >> >> -- >> Dan Allen >> Principal Software Engineer, Red Hat | Author of Seam in Action >> Registered Linux User #231597 >> >> http://google.com/profiles/dan.j.allen >> http://mojavelinux.com >> http://mojavelinux.com/seaminaction >> >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev > >-- >*George Gastaldi* | /Senior Software Engineer/ >JBoss Forge Team >Red Hat >_______________________________________________ >forge-dev mailing list &gt;forge-dev(a)lists.jboss.org >https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev