You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Shane Curcuru <as...@shanecurcuru.org> on 2018/10/09 21:50:21 UTC

[REVIEW] Escalation guide for issues at the ASF

I've written a guide for effective ways to escalate issues at the ASF
that I hope is helpful for anytime there are issues that anyone may feel
aren't being addressed within a specific project or mailing list:

  https://www.apache.org/board/escalation

Having read many Apache lists for years now, I've come to understand the
difficulties in discussing contentious issues - especially when we're
discussing or raising them *across* communities.

Every Apache project has their own communication style; many private
mailing lists like the board and members lists also have their own
styles. When individuals raise issues across these communities - from a
project to board@ or from anywhere to members@ - all too often there is
extra communication friction in the *way* the concern was brought from
one list to the other - separate from the actual issue at question itself.

I'm looking for some feedback and potential patches to ensure this is a
helpful guide for effective escalations, and then I plan to include
links to this in a broader email in the months to come.  I've already
incorporated a few fixes from some Members, but since this is deserved
to serve all of our communities, I'm hoping for some broader feedback.

We're all volunteers, and we each participate in many different
communities. Ensuring we take the time to be clear, specific, and
neutral in how we raise issues across groups helps everyone participate.

Thanks,
-- 

- Shane
  Vice Chairman
  The Apache Software Foundation

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org


Escalation guide for issues at the ASF

Posted by Dmitriy Pavlov <dp...@gmail.com>.
Hi all,

An escalation guide for Apache issues was recently posted on
dev@community.apache.org.  I wanted to make sure our community was
aware of this as well:

https://www.apache.org/board/escalation

In general, I invite you to discuss problems you see with the Ignite
project/PMCs/PMC Chair.  A discussion should be done openly, on the
dev@ignite.apache.org list, or, in some cases,
private@ignite.apache.org.  Addressing issues early and publicly
will keep most points from becoming too large to handle.

Best Regards,
Dmitriy Pavlov

---------- Forwarded message ---------
From: Shane Curcuru <as...@shanecurcuru.org>
Date: ср, 10 окт. 2018 г. в 0:50
Subject: [REVIEW] Escalation guide for issues at the ASF
To: Apache ComDev <de...@community.apache.org>


I've written a guide for effective ways to escalate issues at the ASF
that I hope is helpful for anytime there are issues that anyone may feel
aren't being addressed within a specific project or mailing list:

  https://www.apache.org/board/escalation

Having read many Apache lists for years now, I've come to understand the
difficulties in discussing contentious issues - especially when we're
discussing or raising them *across* communities.

Every Apache project has their own communication style; many private
mailing lists like the board and members lists also have their own
styles. When individuals raise issues across these communities - from a
project to board@ or from anywhere to members@ - all too often there is
extra communication friction in the *way* the concern was brought from
one list to the other - separate from the actual issue at question itself.

I'm looking for some feedback and potential patches to ensure this is a
helpful guide for effective escalations, and then I plan to include
links to this in a broader email in the months to come.  I've already
incorporated a few fixes from some Members, but since this is deserved
to serve all of our communities, I'm hoping for some broader feedback.

We're all volunteers, and we each participate in many different
communities. Ensuring we take the time to be clear, specific, and
neutral in how we raise issues across groups helps everyone participate.

Thanks,
-- 

- Shane
  Vice Chairman
  The Apache Software Foundation

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org