Puppet Module Repository Beta
Finally! Luke and I took out a minute and hashed up a scheme to get the ball rolling on a central one-stop-shop for puppet modules.
Let me quote the pertinent part from
Luke‘s mail:
DavidS wrote:
- Create a new github account to collect all modules with a repo per module.
- Add devs as available to the modules/repos as collaborators to allow them to push changes.
- Use the issue tracker attached to each module for bug tracking.
- Use a meta-repo to combine “matching” module versions into “releases”.
- Encourage wide-spread collaboration.
I’m willing to do all the necessary legwork to set this up. Just say the word.
That’s basically the plan. If you make a ‘puppet-modules’ account and want to set it up… That would be awesome.
So there we go, I’ve created a
puppet-modules account on
github where useful and maintained repos can be published. To seed the effort I’ve already committed a few of my core modules and expect to add some more at a later time when the workflow is settled in.
The primary entry point for local perusal is the
puppet-manifests repository which contains all others as
submodules. This is very convenient to clone all modules at once:
$ git clone git://github.com/puppet-modules/puppet-manifests.git
$ cd puppet-manifests/
$ git submodule init
$ git submodule update
Within
modules/ you can now find git repositories for all published modules, ready to go.
For working on the repos, I’ve created forks of all modules in
my private github account to avoid cluttering the “published” versions.
If you have any patches or modules to contribute or want to collaborate, please use github’s issue tracker of the concerned module or send a shout to puppet-users or me privately.
