+1 Please do this.
On Apr 9, 2012, at 3:11 PM, Jeff McCune wrote:
> On Mon, Apr 9, 2012 at 5:09 PM, Michael Stahnke
> wrote:
>
> 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-commi
FWIW, I was following puppet-dev before the move to github, but
unsubscribed because of the level of noise it generated.
I'm not a skilled ruby dev, but I like to follow discussions around some
modifications, especially if I see something around an issue I'm
watching on redmine.
not a suggestion
On Mon, Apr 9, 2012 at 2:11 PM, Jeff McCune wrote:
> On Mon, Apr 9, 2012 at 5:09 PM, Michael Stahnke
> wrote:
>>
>>
>> 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 reali
On Mon, Apr 9, 2012 at 5:09 PM, Michael Stahnke wrote:
>
> 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 discu
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 finel
