Drupal.org policies

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
This group should probably have more organizers. See documentation on this recommendation.

This group is for members of the Drupal.org site moderator's team and other interested individuals to discuss and help draft policies related to the Drupal.org Web site.

This group has no official standing, and any proposed policies drafted by this group must be submitted to and approved by the Drupal community before they are implemented. Membership in this group is by administrative approval to ensure that only interested and motivated individuals participate and that discussion remains focused and on-topic.

christefano's picture

Downtown Los Angeles Drupal governance policy conference call #2 on August 21, 2012

Start: 
2012-08-21 18:00 - 18:30 America/Los_Angeles
Organizers: 
Event type: 
User group meeting

Several of the Downtown Los Angeles Drupal organizers have scheduled an open conference call on on Tuesday, August 21, 2012 between 5:30-6pm Pacific (8:30-9pm Eastern). This precedes the Downtown Los Angeles Drupal meetup at Droplabs the same night.

The agenda will consist of discussion around the next steps that were discussed during the previous conference call including the new additions to the proposed Downtown Los Angeles Drupal governance policy at http://groups.drupal.org/downtown-los-angeles/governance

For calling in by phone and Skype, we use FreeConferenceCallHD. To receive the conference call information, click the Signup button below. Anyone who's interested in being part of this discussion or is just interested in observing governance in action is welcome to join us.

Read more
christefano's picture

Downtown Los Angeles Drupal governance policy conference call #1 on August 9, 2012

Start: 
2012-08-09 14:00 - 15:00 America/Los_Angeles
Organizers: 
Event type: 
User group meeting

Several of the Downtown Los Angeles Drupal organizers have scheduled an open conference call on on August 9, 2012 between 2-3pm Pacific (5-6pm Eastern).

In light of recent events that led to banning a member of the community, the agenda will consist of discussion around the proposed Downtown Los Angeles Drupal governance policy at http://groups.drupal.org/downtown-los-angeles/governance

For calling in by phone and Skype, we use FreeConferenceCallHD. To receive the conference call information, click the Signup button below. Anyone who's interested in being part of this discussion or is just interested in observing governance in action is welcome to join us.

Read more
gdemet's picture

Create DrupalCon Code of Conduct (Old Draft)

The code of conduct draft has been re-written based on community feedback and is available for community review here: http://groups.drupal.org/node/235308 - we ask that you please offer your comments, questions, and suggestions on that page. Comments have been closed on this page.


The following is the proposed DrupalCon Code of Conduct that has been drafted by a group that includes past DrupalCon organizers, Drupal Association staff and board members, and other community volunteers.

Read more
Senpai's picture

Policy for promotion of content to the homepage of drupal.org

I cannot find a recently updated policy for the promotion of posts to the homepage of drupal.org, so I thought I should start this discussion in order to bring together all the past policies and threads under one roof in an effort to distill something that's relevant, accepted, and less than three years old.

Go! :)

[EDIT] Found this link to Front Page Schedule - aka - How to get your story on the front page but it doesn't have a 'last updated on' published so people can see how recent it is.

Read more
jcnventura's picture

Books page policy

The Drupal books page currently lists all known published books about Drupal 6.x and 7.x.

Read more
Alex UA's picture

Conflicts of Interest and potentially Private Benefit / Inurement on the Drupal Association board

I would like to formally request an investigation into two members of the Drupal Association board who I believe have acted in a Conflicts-of-Interest with regards to DrupalCon Chicago. In addition I formally request the investigation of one member of the Drupal Association general assembly for the same.

I believe that these members of the Board and General Assembly have behaved in ways that not only run counter to basic morals of our community, but I believe that they have also potentially broken nonprofit tax law and have put the tax exempt status of the DA's 501(c)3 at risk.

Read more
Alex UA's picture

Policies to ensure accountability from Webmasters/Site Maintainers

One of the things I've noticed as I've been in the webmaster's queue is that there seem to be few publicly available policies regarding the "ins and outs" of this powerful and important drupal.org designation. Some of the policies I'd like to see clarified publicly:

  • How do people become webmasters? I've only located a few issues where someone requested to become a webmaster, and there appear to be 139 current site maintainers.
  • Are there any objective measures in place to determine when someone should be given these special permissions?
  • How many webmasters does it take to +1 a new member? How many webmasters would it take to "veto" a new member?
  • What checks and balances exists, if any, to ensure that webmasters don't abuse their power?
  • Are people able to file complaints about abuse of these privileges? Where? How does this work?
  • Are any records of complaints kept? If so, where? Can non-webmaster community members access this info?
Read more
Alex UA's picture

Define rules for posting "official" policies

One of the concerns I have with policy making is how current policies are created and posted on Drupal.org as "official" d.o. policy. Some of the items I think need clarity:

  • Where does debate happen?
  • What level of support does something need before becoming a policy? For this I mean both the raw # of votes, as well as the % of votes supporting the proposition (simple majority--i.e. 50+1-- super majority-- i.e. 2/3s?)
  • Who gets to vote? Is anyone qualified? Do they need a certain permission on d.o. (documentation, webmasters, cvs access, etc)? Are any votes worth more than others?
  • Are there certain policy that do not require said procedure? For example, while security policies are obviously best left to the security team, I'm less certain whether they would require their own rules for making policy, but I'm guessing they would.
  • What are the appeal processes for challenging accepted rules?
Read more
Alex UA's picture

Define Limits of Community Involvement in Webmasters Issue Queue

As you may know, I have been extremely frustrated lately with the ways in which the webmasters issue queue is currently being handled, specifically, I feel that some members of that queue are not open to the opinions of the community at large. At the moment, it doesn't matter what your involvement in Drupal is, nor does it matter whether you are an expert in the domain where you are trying to help, the only thing that many of the more vocal members of the webmaster team care about is whether you are a webmaster.

Read more
greggles's picture

appropriate use of admin accounts on *.d.o: moderation with content where you are personally involved

The "promote to front page" queue on drupal.org follows a few social norms that I think we should generalize for all administrative accounts on all *.drupal.org sites:

  • If you are a friend or directly involved with something that is about to promoted to the front page, you should not do the moderation action yourself but should find a fellow moderator to take the action
  • If you are not directly involved in the ongoing maintenance in an area, taking a one-off case that interests you just because you have the role is likely to lead to a mistake and should therefore be avoided
Read more
greggles's picture

Addition to coding standards: Including names in code

I thought I had seen discussion of this, but can't find it now.

In this issue I mention what I consider to be the standard: we don't include author names in the code itself. We can include them in a MAINTAINERS.txt or a README.txt but shouldn't put them in the code.

  1. It's "what core does" and when in doubt modules and themes should "do what core does."
  2. It would bloat the code to include all authors of patches in a file. If we don't include all authors, then this is not an accurate piece of information.
Read more
moshe weitzman's picture

Adopt a Drupal Code of Conduct (#DCOC)

As our community grows, it is imperative that we preserve the what got us here. Namely, we keep Drupal a fun, welcoming, challenging, and fair place to play. IMO, we need to proactively state our shared ideals with respect to conduct. Think of this as coding standards for people :)

Our friends at Ubuntu have blazed a brilliant trail in this area. They use our CMS, and I propose that we use their Code of Conduct.

Read more
greggles's picture

Should we allow company/product names in module/theme project names

There are a few examples of using a company name in a project name and/or shortname.

Read more
Dave Reid's picture

Username changing or expiration policy

This was already pretty much finalized in http://drupal.org/node/496728 but I thought I should cross-post it here.

* The Drupal.org webmasters team does not expire or change usernames for any reason. This data is considered integral to our community's history.
* If there are legal concerns such as trademark infringement, the user should contact the Drupal Association http://association.drupal.org/contact. All requests must include required documentation to prove identity and trademark holdings. The Drupal Association may or may not act on requests, depending on advice from legal counsel.

I suppose we could mention something explicit about "If you want someone else's username, send them a mail through their contact form and see if you can convince them to change it," but people will probably figure that out without our explicit mention. Morbus has concerns about the fact that authenticated users can change their own usernames, but this has been a feature of Drupal.org since time immemorial so if we want to change that we should discuss it elsewhere.

Read more
Dave Reid's picture

Contributed modules and themes policy

We've had several issues of bad behavior when it comes to contributing modules and themes recently:

  1. Naming or renaming a project to start with '000' or 'aaa' in an attempt to game the alphabetical project listings so their projects are always listed first.
    http://drupal.org/node/484044

  2. Using theme-generating programs like Artisteer and creating/mass-creating themes on drupal.org that are unlikely to be supported since the creator likely doesn't understand how Drupal theming works since they used a Point-n-Click program and never put any work into the source code.

Read more
gdemet's picture

Services Directory policy discussion

This thread is to allow us to discuss the material on the companion wiki page, what insights we can draw from it, and how it should inform the development of a policy.

Based on the items in the "Suggestions" list, one idea I had was that instead of saying, "you need to do all of these things to be listed in the directory", we instead say, "Here's a list of a number of things you can do to be listed in the directory. If you do X number of them, then you're eligible for consideration."

Read more
gdemet's picture

Privacy Policy for Drupal.org

There's a thread in the webmaster's issue queue that has had some sporadic traffic over the last couple of years about creating a privacy policy for *.drupal.org. Currently, the last post is a draft proposal that IMO needs a lot of work before it could be submitted to an attorney or proposed to the community for use on the site.

Read more

Services Directory policy wiki

Following up on the discussion on this thread in the webmaster's issue queue, I'm creating a wiki page to hopefully allow us to collaboratively draft a more detailed policy for who is included in the Drupal.org services directory.

For now, I'm listing the comments, feedback, and suggestions from the thread. My hope is that as we continue to refine this list, a pattern of community consensus will become more clear, and we can draft a policy accordingly:

Goals of the services directory

Read more
Subscribe with RSS Syndicate content

Drupal.org policies

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: