As a non active (hopefully active in the future) contributer/developer, I would find emailed patches very useful for visibility into the code base and where things are going, and as a nice carrot hanging out in front of me to hopefully motivate me to contribute. Of course the usability of actual contributers is more important. Perhaps a merge mailing list that automatically gets emailed patches when merges happen on major branches if this doesn't go through? (github probably has something I could subscribe to though, I'll have to look into it)
Thanks Brian On Thu, May 22, 2008 at 6:20 PM, Luke Kanies <[EMAIL PROTECTED]> wrote: > > On May 22, 2008, at 5:32 PM, Peter Meier wrote: >> As I'm also quite happy to have at least the bug-mails back :) > > Me too (although that's a lot of emails this week). > > -- > He played the king as if afraid someone else would play the ace. > --John Mason Brown > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
