[Scons-dev] Code of conduct?

Gary Oberbrunner garyo at oberbrunner.com
Tue Dec 8 16:36:09 EST 2015


Indeed. I think the discussion so far points to let's have one, keep it
short & sweet. I don't see any real reasons not to, and some possible
benefits to having one.

On Tue, Dec 8, 2015 at 2:57 PM, Bill Deegan <bill at baddogconsulting.com>
wrote:

> Anatoly,
>
> In the entire history of SCons we've only had a small handful of instances
> where any of the proposed CoC's might have been violated.
> So infrequent I can't remember the last one.
>
> That said, if you can prove harm or point to any project where it harmed
> their community to have a CoC, then I (and I expect the rest of the SCons
> developer list) would be interested in such.
>
> Nothing you've said thus far has been convincing to me (nor it seems any
> other community member).
> Otherwise it is speculation.
>
> I can say for certain that some organizations expect such when providing
> grant money to open source communities.
> For me that's sufficient reason.
>
> I will also say that if the SCons project finds that having a CoC is
> damaging to it's community, then we'll revise or revoke it as appropriate.
> (where damaging doesn't equal one person is being unreasonable or abusive
> and doesn't like having the fact that their behavior violates the CoC, but
> does equal contributions to the project including features and/or bugfixes
> and/or docs slow to a standstill, and/or usage of SCons diminishes in a
> meaningful way measurable to the adoption of a CoC).
>
> -Bill
>
> On Tue, Dec 8, 2015 at 2:10 PM, anatoly techtonik <techtonik at gmail.com>
> wrote:
>
>> On Tue, Dec 8, 2015 at 8:02 PM, William Blevins <wblevins001 at gmail.com>
>> wrote:
>> > On Tue, Dec 8, 2015 at 2:59 AM, Bill Deegan <bill at baddogconsulting.com>
>> > wrote:
>> >>
>> >> An extra 2cents of opinion from me.. ;)
>> >>
>> >> A few things a CoC would help with:
>> >> 1) It could encourage more participation on the mailing lists. Open
>> source
>> >> projects have been notorious for scathing responses to simple
>> questions.
>> >> Surprisingly I've been at clients who have used SCons for years and
>> never a
>> >> single member of their staff has asked a question on the mailing
>> list.. I
>> >> was shocked.
>> >
>> >
>> > I don't think this attitude is uncommon.  Many of my past coworkers view
>> > interacting on forums and mailing lists as a "hassle", and they would
>> rather
>> > try to brute force since they "know" best. I'm not sure this can be
>> helped.
>> > unfortunately.
>>
>> I agree. Businesses discourage people from spending time on forums. They
>> can only understand it if they pay money for it. Also not many companies
>> want outside World to know that they can't do something themselves.
>>
>> So, if business people want straightforward and nice discussions, let them
>> pay for it. Otherwise there is conflict that those of us who volunteers
>> and
>> are not being paid should behave well in order to provide free service for
>> those who don't care.
>>
>> The paragraph above is an example that CoC doesn't solve anything, because
>> it doesn't remove causes of conflicts.
>>
>> --
>> anatoly t.
>> _______________________________________________
>> Scons-dev mailing list
>> Scons-dev at scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>
>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>


-- 
Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20151208/d86a9005/attachment.html>


More information about the Scons-dev mailing list