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
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
I think Jo is on the money: that seems like the smallest step, and work trying.
If that isn't perfect, we can take another small step to something better.
On Mon, Apr 23, 2012 at 12:22, Jo Rhett jrh...@netconsonance.com wrote:
Why not encourage both? Separate the lists but suggest that replying
+1
On Mon, Apr 23, 2012 at 12:24 PM, Daniel Pittman dan...@puppetlabs.com wrote:
I think Jo is on the money: that seems like the smallest step, and work
trying.
If that isn't perfect, we can take another small step to something better.
On Mon, Apr 23, 2012 at 12:22, Jo Rhett
+1
On Mon, Apr 9, 2012 at 2:09 PM, Michael Stahnke stah...@puppetlabs.comwrote:
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
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
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.
I've been moving more discussions onto puppet-dev in the last few
weeks, as I've been delving more
On 12 April 2012 08:48, Brice Figureau brice-pup...@daysofwonder.com wrote:
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
* 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
I agree with Brice. The only way to bring the conversation back here is
not to segment/split the
I just recently started working at Puppet Labs and have been pretty much been
ignoring most of what I see from this list because of the amount of github mail
on it. I think that removing the github email from this list will help it to do
what I'm hoping to see on it, which is to have
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:
1. Still having a
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
12 matches
Mail list logo
