Why not encourage both? Separate the lists but suggest that replying to a commit message on the dev list is encouraged. Or if you can, set reply-to on the commit messages to go back to dev ;-)
On Apr 23, 2012, at 12:19 PM, Michael Stahnke wrote: > So, after a week of contemplation, I don't feel like we landed anywhere. > > We have people that want the github noise off of the list. > > We have people that want to be able to comment on patches on the list, > but not using the current workflow. > > What should we do here? I'm still inclined to promote discussion by > removing the github output from the dev list and switching that to the > commit list. What it sounds like we really want is some magic github > + mailing list integration that doesn't exists to the best of my > knowledge. > > We also got a pretty small sample size in response, so I'm sure that > making any executive decision will sit well. > > Round 2 of discussion? Does anybody have any actions proposed that we > can easily take now? > > > Mike > > -- > 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. > -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- 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.
