On Fri, Jan 16, 2009 at 9:11 AM, Luke Kanies <[email protected]> wrote: >> I have no major issues but some concerns: >> >> Availability and stability - we've had some issues with this in the >> past >> on Github. Be annoying if GitHub deadpooled too. > > I agree with that, but I also agree with Paul that it's been pretty > damn stable for a while now. > >> >> Communication - the stable repository has been at RL, my Github, now >> back at RL. If we make this change we need to make sure everyone gets >> the message. Personally, I'd be a little confused. > > > Yeah, but I'm not convinced people have quite realized that the stable > is no longer your repo, so it might be a good time to switch to > minimize confusion, assuming we actually do switch. > > That is, before it's completely settled back on the RL repo, switch so > that people don't have to learn it twice in short succession.
An alternative approach which addresses bot GitHub stability and potential confusion, but still buys us the features available on GitHub, is to have the RL repo set up to "mirror" the GitHub repo (or vice-versa). A regular push/pull scheduled via cron might accomplish the task. I think that the workflow for the maintainers could also be improved using GitHub as a tool, which is part of why I recommended it. You can get the gem version of Puppet built "for free"; pull requests could potentially ease the patching process, etc. --Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
