> On 28 Sep 2018, at 03:52, George Plymale II
> wrote:
>
> Linux is arguably "capsizing" right now, to some extent. The drama
> that's going on, between threats of lawsuits, possible forks, and
> kicking out longtime leaders in the project... well, I'd say that
> "capsizing" is perhaps an
Hi,
Just wanted to respond to a few points made in the last few messages, so
I'm combining my responses into a single message to avoid clutter.
David Gilman writes:
> What are some of these projects that capsized after adopting a code of
> conduct?
Linux is arguably "capsizing" right now, to
What are some of these projects that capsized after adopting a code of conduct?
On Thu, Sep 27, 2018 at 3:06 PM Vincent Habchi wrote:
>
> > In my experience, we in MacPorts-land don't have the obvious Linux issue. I
> > hope others don't experience the MacPorts project (developers, users,
> >
> In my experience, we in MacPorts-land don't have the obvious Linux issue. I
> hope others don't experience the MacPorts project (developers, users,
> commenters) as abusive in any medium (email lists, tickets / issues, PR's, in
> person, whatever). - MLD
In my experience :), when a project
Related, sort of: <
https://www.newyorker.com/science/elements/after-years-of-abusive-e-mails-the-creator-of-linux-steps-aside
>
In my experience, we in MacPorts-land don't have the obvious Linux issue. I
hope others don't experience the MacPorts project (developers, users,
commenters) as
On Tue, 18 Sep 2018 20:25:17 +0530 Jackson Isaac
wrote:
> Lately, I have seen open source projects have started adopting Code
> of Conduct. [1], [2]
>
> I think it is a great step to keep the open source community healthy
> and welcoming to everyone.
I'm against these. They feel like loyalty
I definitely agree that when a document enumerates examples -- even with the
"including but not limited to" -- it sets the stage for your scenario. Thus,
moving away from examples is probably wise. I, too, like the Ruby CoC: it's
short and concise, stating the basic principles rather than
I'm fairly new in the MacPorts community, but I'd like to offer an
opinion on this topic. Personally, I feel that CoC's like the
Contributor Covenant, Postgres CoC, FreeBSD CoC, etc. are very... umm,
let's just say strict. I think they read more like license terns than a
set of guidelines on how
I'll second that having a CoC isn't a bad idea. I like the shorter version <
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html >, which
leaves room for our project to implement various parts as we see fit (the
PostgreSQL CoC is, in my opinion, a little too specific in some
On Sep 18, 2018, at 09:55, Jackson Isaac wrote:
> Lately, I have seen open source projects have started adopting Code of
> Conduct. [1], [2]
>
> I think it is a great step to keep the open source community healthy
> and welcoming to everyone.
>
> I would like to know what other developers
10 matches
Mail list logo
