[chef] Re: Re: Re: Re: Re: Reprepro cookbook

[Sean OMeara < >]

Documentation PRs are super easy to merge, too.  They don't require
tests, just human parsing.
Totally my fave.
-s


On Fri, Jun 19, 2015 at 3:30 PM, Peter Burkholder 
<
 >
 wrote:
> Here's a thought: when we are most frustrated, that's also when we have the
> chance to make real contributions back to open-source. Even if your skills
> aren't yet up to the level of submitting new features or fixing bugs, almost
> every project needs better READMEs, HOW-TOs and examples.
>
> Frustration is a sign you've hit the envelope of what's currently
> well-documented, and your experience, if submitted as a PR back to a
> project, is a gift that keeps on giving. And that contribution is
> tremendously empowering as you've gone from hapless consumer to kick-ass
> contributor (and, yes, documentation _does_ count).
>
> --Peter
>
> On Fri, Jun 19, 2015 at 4:55 PM Charles Johnson 
> <
 >
>  wrote:
>>
>> Doug,
>>
>> It's okay to point out what's wrong. It's not okay to tear people down
>> when you feel that the work they have given you for free isn't good enough
>> for you to re-use.
>>
>> If you are unable to understand the difference between saying "I'm really
>> frustrated and stuck, this is broken and I can't get it to work, and I 
>> don't
>> know how to fix it," and saying "disappointing quality from Opscode," then 
>> I
>> don't know what to tell you. Regardless of who disappointed you, this isn't
>> a constructive thing to share with a software community.
>>
>> Criticism is welcomed form of expression when it isn't just bashing on
>> people with snide remarks. "Disappointing quality from Opscode" doesn't 
>> make
>> anyone who reads it want to help you be better at your job, or help you
>> improve the free cookbooks you're re-using. If you don't know how to 
>> express
>> your feelings in a way that invites others to help, then again I really
>> don't know what to say.
>>
>> I understand that you feel stuck in a problem you don't know how to solve.
>> I understand that you're angry about being censured again. But instead of
>> responding with an attempt to rules-lawyer the community guidelines by
>> pointing out that your particular brand of negativity isn't *specifically*
>> disallowed, perhaps you should focus on how your future contributions can
>> motivate us all make the code and the community better for both yourself 
>> and
>> everyone else.
>>
>> None of us want to see you unhappy. All of us want to see you succeed
>> beyond your wildest dreams. But we can't enable that goal at the expense of
>> others in this community.
>>
>> Thanks,
>>     --Charles
>>
>>
>>
>> On June 19, 2015 at 12:35:31 PM, Douglas Garstang
>> (
 )
>>  wrote:
>>
>> Lamont,
>>
>> I'm biting my tongue as I write this doing my best to restrain my anger.
>> It is quite apparent that no matter what I say, it will be deemed
>> inappropriate. The README.md at the bottom states Opscode. It's not my 
>> place
>> to know if that is accurate or not. I also took pains to specifically
>> mention in my original post that it might actually be my fault. For reasons
>> I don't understand, you've latched onto my personal opinion of a piece of
>> software generated by a  commercial enterprise being below the quality I'd
>> expect. Again, like before, there's nothing in the community guidelines
>> about this being not being allowed.
>>
>> Douglas.
>>
>> On Fri, Jun 19, 2015 at 12:19 PM, Lamont Granquist 
>> <
 >
>>  wrote:
>>>
>>>
>>>
>>> On 06/19/2015 07:31 AM, Douglas Garstang wrote:
>>>>
>>>>
>>>> Disappointing quality from something with Opscode's name on it.
>>>
>>>
>>> Doug you've been warned repeatedly that you need to stop making
>>> statements like this.
>>>
>>> That cookbook has also been transferred to community support by Jesse
>>> Adams, which should be obvious from the URL to the repo that you pasted, 
>>> so
>>> you're actually insulting a community member.  The banner at the top is
>>> incorrect and has not been updated.  AFAIK nobody at Chef Software has
>>> commit rights to that repo (I certainly do not).
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Douglas Garstang
>> http://www.linkedin.com/in/garstang
>> Email: 
>> 
 
>> Cell: +1-805-340-5627