On Mon, 2012-04-09 at 14:09 -0700, Michael Stahnke wrote: > Since our move to github for pull requests and patches, the usefulness > of puppet-dev has declined significantly. puppet-dev used to be a > great list for development discussion of puppet and the ecosystem > around it. With the information and pull request emails from github, > unless everybody has finely-tuned their email clients, the puppet-dev > list has turned into mostly noise.
IMHO, that's not the root cause of the problem. Back to the time we were sending patches to the list, discussion could spark easily on a topic, based on a comment on a patch. Nowadays, I don't even read patches because they're either one click away or difficult to read in the e-mail. Worst: most of the time I open the "close" pull request e-mail by mistake (thinking it is the open one) and struggle to find the real "open" one to read the patch. (I believe we don't need this "close" e-mail, it just adds unnecessary noise). One reason the patches are difficult to read is that all sub-patches are merged in one big chunk, so you're losing the author intent. More generally the move to github certainly increased the development team velocity (which is good), it might also have increased the community contributions, but I think it also decreased the community involvement on the dev list. Maybe nobody feels like me or that's because there are much more patches than there was before, but the dev list was a good way to stay tuned on what happens in the Puppet code. I just feel it isn't now anymore. Maybe I'm a dinosaur and I need to follow more carefully what happens on github :) Also, a lot of the discussion moved to the pull request in github, so it disappeared from the dev-list. Now to be part of the discussion, you need to follow the pull request discussion manually. If you weren't part of the discussion at start, it now requires more involvement compared to receiving all discussion in my mail client. > We have a goal to foster development discussion from the community. > Because of that, I am proposing we move the github notifications to a > new list, puppet-commits. I realize this may have a consequence of > reducing patch/commit discussion. This should be compensated by: Since the move to github commit discussion happened on github, so that's a non-issue. > 1. Still having a list where pull requests can be commented on > 2. Ability to comment on pull requests directly on github > 3. More forethought and discussion on the dev list prior to making a > pull request/patch. That'd be really great. And I noticed some attempts lately in this direction, which is really good. > 4. You can also watch the RSS feed for the puppet projects you have > the most interest in. You mean the commit/pull request feed on github, or the redmine feed? > This decision isn't final, but I would like to get opinions on the > idea. I welcome feedback until Friday, April 13. What would be utterly awesome would be better pull request e-mails flow on this commit (or on the dev) list: * no close e-mail * more readable inlined patches (syntax coloring?, broken in different e-mails per commit?) * send back to the thread on this list the internal discussion happening on github Thanks, -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
