Nov 25 2014
Nov 25
AlexandreCH's picture

Thanks for all the information

pdjohnson's picture

Hi,

Is it too late for me to promote this or would more people still be welcome? I can fire it out on Drupal Twitter if you think there is merit.

Paul

Slurpee's picture

Paul, thanks for reaching out. We would love support in social media. We have been asking around about this for a while and no one could point us in the proper direction...

Do you control all of the social media accounts? Twitter? FB? LinkedIn? Any others?

Susann Linwood's picture

sounds like a fantastic experience

paranozore's picture

is it going to work for a short or long time? anyway i like this project.

lenywella2014's picture

There are a lot of people who are so good in the field. - Marla Ahlgrimm

kalies's picture

yaa, thanks for your good information.

Jul 07 2014
Jul 07
webchick's picture

An alternative is the drupal-cwg [at] drupal.org email address, as documented on https://www.drupal.org/governance/community-working-group.

We chose to use Google Forms because a wide variety of people about whom conflicts may occur have very high-level access to Drupal.org. A neutral third-party service doesn't have this problem, although I totally get why some have ToS concerns with it.

DamienMcKenna's picture

Could we please have that email address added to the top of the Incident Report form, just to make it obvious for people? Thanks!

kattekrab's picture

I've edited the form and updated the issue.

https://www.drupal.org/node/2299737#comment-8950891

Would be good to get some sanity check eyeballs on it though!

Thanks all!
@gaele - for raising the question
@DamienMcKenna - for the suggestions.
@webchick - for adding to the queue.

jhodgdon's picture

You asked for "sanity check eyballs" on https://www.drupal.org/governance/community-working-group/incident-report

I have a few comments:

a) There is a very large wall of text at the top. Maybe it could be organized into bullets or sections or something? [see below]

b) You might also want to take a look at the descriptions for the Who/What etc. questions. They are a bit repetitive.

c) The "Who" question also has a mix of questions (ending in ?) and ... sort-of questions (ending in .) which turned me off.

d) "Please include links or quoted text if relevant." is under "where". Um... I think that would be under "what"? At least the "quoted text" sounds like a "what" not a "where"? It's kind of confusing what the distinction is.

So... Here's my suggestion for the top. Items in [] are my notes on the edits.

The community working group (CWG) upholds the Drupal Code of Conduct (DCOC). See:
- https://drupal.org/governance/community-working-group
- https://drupal.org/dcoc

[made this a bullet list]

Reporting incidents to the CWG

[header added]

This form can be used to report incidents that may breach the code of conduct, or to report non-code, non-technical issues that can't be resolved between members of the community.

Alternatively, you may email the CWG directly: [email protected]
Please make sure to include as much information as you can by answering the questions in the form in your email. [note: small edit in this sentence]

Incidents to report elsewhere

[added header, and this information came from elsewhere on the page]
IMPORTANT: If you are in any kind of immediate physical danger, please contact your local authorities.

Technical disputes should be raised with the Technical Working Group. Personal disputes that have arisen out of technical issues can be brought to the CWG.

https://drupal.org/governance/technical-working-group

Notes about incident reports

[added header, and the information here elsewhere on the page]
We hope you've tried to resolve issues between yourselves. If that failed, we hope that you reached out to fellow friends and colleagues in the community to help mediate your dispute. This form should only be used when those steps did not lead to resolution.

These incident reports are shared with the immediate members of the Drupal Community Working Group and are kept confidential. In some cases we may decide it necessary to make a public statement. In that case, the identities of all involved will remain confidential unless there are strong reasons, or mutual agreement they should be revealed.

Builder of Drupal sites and modules, and Drupal tutor - http://poplarware.com
Drupal Core maintainer for documentation

kattekrab's picture

Thanks Jennifer - really useful review and patch.

Going to paste this into the issue https://www.drupal.org/node/2299737

Let's see if we can tighten up the wording around those questions too.

Patrícia Jyotsna's picture

Hi, I heard about Drupal is now a growing community and knowing that the mentored sprints was attended by many to listen to tools presentation is such a very successful one. In relevance to this, I am with you to say that we must be aware in keeping our shared principles and values in mind when interacting with others to be able to attain an inspiring event like the Drupal sprints at Amsterdam.

Jul 07 2014
Jul 07
webchick's picture

An alternative is the drupal-cwg [at] drupal.org email address, as documented on https://www.drupal.org/governance/community-working-group.

We chose to use Google Forms because a wide variety of people about whom conflicts may occur have very high-level access to Drupal.org. A neutral third-party service doesn't have this problem, although I totally get why some have ToS concerns with it.

DamienMcKenna's picture

Could we please have that email address added to the top of the Incident Report form, just to make it obvious for people? Thanks!

kattekrab's picture

I've edited the form and updated the issue.

https://www.drupal.org/node/2299737#comment-8950891

Would be good to get some sanity check eyeballs on it though!

Thanks all!
@gaele - for raising the question
@DamienMcKenna - for the suggestions.
@webchick - for adding to the queue.

jhodgdon's picture

You asked for "sanity check eyballs" on https://www.drupal.org/governance/community-working-group/incident-report

I have a few comments:

a) There is a very large wall of text at the top. Maybe it could be organized into bullets or sections or something? [see below]

b) You might also want to take a look at the descriptions for the Who/What etc. questions. They are a bit repetitive.

c) The "Who" question also has a mix of questions (ending in ?) and ... sort-of questions (ending in .) which turned me off.

d) "Please include links or quoted text if relevant." is under "where". Um... I think that would be under "what"? At least the "quoted text" sounds like a "what" not a "where"? It's kind of confusing what the distinction is.

So... Here's my suggestion for the top. Items in [] are my notes on the edits.

The community working group (CWG) upholds the Drupal Code of Conduct (DCOC). See:
- https://drupal.org/governance/community-working-group
- https://drupal.org/dcoc

[made this a bullet list]

Reporting incidents to the CWG

[header added]

This form can be used to report incidents that may breach the code of conduct, or to report non-code, non-technical issues that can't be resolved between members of the community.

Alternatively, you may email the CWG directly: [email protected]
Please make sure to include as much information as you can by answering the questions in the form in your email. [note: small edit in this sentence]

Incidents to report elsewhere

[added header, and this information came from elsewhere on the page]
IMPORTANT: If you are in any kind of immediate physical danger, please contact your local authorities.

Technical disputes should be raised with the Technical Working Group. Personal disputes that have arisen out of technical issues can be brought to the CWG.

https://drupal.org/governance/technical-working-group

Notes about incident reports

[added header, and the information here elsewhere on the page]
We hope you've tried to resolve issues between yourselves. If that failed, we hope that you reached out to fellow friends and colleagues in the community to help mediate your dispute. This form should only be used when those steps did not lead to resolution.

These incident reports are shared with the immediate members of the Drupal Community Working Group and are kept confidential. In some cases we may decide it necessary to make a public statement. In that case, the identities of all involved will remain confidential unless there are strong reasons, or mutual agreement they should be revealed.

Builder of Drupal sites and modules, and Drupal tutor - http://poplarware.com
Drupal Core maintainer for documentation

kattekrab's picture

Thanks Jennifer - really useful review and patch.

Going to paste this into the issue https://www.drupal.org/node/2299737

Let's see if we can tighten up the wording around those questions too.

Patrícia Jyotsna's picture

Hi, I heard about Drupal is now a growing community and knowing that the mentored sprints was attended by many to listen to tools presentation is such a very successful one. In relevance to this, I am with you to say that we must be aware in keeping our shared principles and values in mind when interacting with others to be able to attain an inspiring event like the Drupal sprints at Amsterdam.

Mar 13 2013
Mar 13

A week or so ago, Dries posted this

Which links to a number of draft charters for working groups focussed on different facets of the community, the software project, our tools and infrastructure.

Dries wrote

This is a work in progress. Please help shape the future of Drupal.org governance by reviewing and commenting on the following proposals:

Please take a moment to review Dries post, and each of the draft charters. Please comment, and please help spread the word about this proposal. It's important. :-)

Sep 24 2012
Sep 24

Voting is now open in the community elections for new Directors "At Large".

How to vote?

  1. Login to association.drupal.org
  2. Check box and confirm you're eligible to vote.
  3. Rank the candidates in your order of preference.
    You do not need to rank all candidates.
    Why rank them? Watch this video.
  4. Save the form.

Voting is open for two weeks, closing at 23:59 UTC 7 Oct 2012.

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web