In the summer, we organized the very first Drupal Governance Sprint. We sat down and discussed how to evolve Drupal's governance structure to support the Drupal community's continued growth. The result of that meeting was a proposal on how to evolve our governance. After discussing at length and formally chartering the first of these groups, the "Community Working Group" (CWG), we'd like to move on to Drupal.org governance.

One of these groups is the Drupal.org Content Working Group (DCWG). This group will manage guidelines and processes for major content areas on Drupal.org, as well as the overall "look and feel" of the website. They will also handle content moderation, including anti-spam policies, in order to keep Drupal.org's content fresh and relevant for all of its target audiences.

The charter has been committed to Git at http://drupalcode.org/project/governance.git/blob_plain/refs/heads/maste.... For your convenience, I'm including the current version below:

Drupal.org Content Working Group Charter

Mission

The mission of the Drupal.org Content Working Group (DCWG) is to make sure that the content on Drupal.org websites is compelling, well-curated, and relevant for all of its various target audiences and supports a content marketing strategy that serves site visitors and generates revenue to make Drupal.org sustainable.

The DCWG acts as a group to maintain the processes around product messaging, content moderation, and user experience elements of the Drupal.org websites. The DCWG is appointed by the Drupal Association. Together the Drupal Association and DCWG collaborate on strategy, priorities, and implementation.

Scope / duties / responsibilities

Scope

The DCWG manages and is responsible for overall content strategy of Drupal.org websites, maintaining policies around the major content areas on Drupal.org, including the front page, case studies, marketplace, persona-centric landing pages, and Drupal Planet. They also manage the overall look and feel and voice of the website, including its information architecture and design elements.

The DCWG uses an iterative process, based on data-driven analysis, with the goal to constantly improve the content on Drupal.org and to optimize key pages for traffic, usability, and revenue.

Specific duties

  1. Content strategy: Ensure content meets audience needs, facilitate a content marketing strategy that is up-to-date and relevant, and create policies around how to handle legacy content.
  2. Information architecture: Ensure content is well organized, and manage Drupal.org website elements such as navigation, taxonomy, header/footer.
  3. Design and User experience: Develop and maintain a consistent “look and feel" throughout all Drupal.org websites, in alignment with the Drupal brand guidelines. Extend the Drupal Style guide as needed to address new design goals and needs for the website. Establish standards on how people in various target audiences approach the site and find the information that they need.
  4. Moderation: Maintain policies around general user-generated content (e.g. spam, unsolicited advertising, fields on registration form, account deletion policy), as well as major content areas of the site (such as Drupal Planet, Marketplace, Case Studies, etc.)
  5. Analytics and Research: Track analytics and demographic data to determine how well or poorly the content on the site is performing so that it can be continually improved. Perform usability studies to help prioritize improvements and research on who uses Drupal.org and how they use it.

Exclusions

  • The DCWG does not moderate technical documentation such as the Drupal.org documentation guides. This is the responsibility of the Documentation Team.
  • The DCWG also does not deal with policies surrounding advertising on Drupal.org; this is managed by Drupal Association.
  • The DCWG doesn't uniquely define Drupal's marketing positioning and messaging. This is defined by the Branding and Marketing committee in concert with the Drupal Association, and this team ensures that it is applied consistently to the Drupal.org website.
  • The DCWG cannot change or extend its own charter.

Process

Collaboration

The DCWG must establish a process that uses timely decision-making and iterative improvements. The DCWG should work closely with all other working groups, as well as Drupal Association staff, and Branding and Marketing committee, in order to determine overall needs and priorities for Drupal.org content.

Budget

The DCWG works within the budget provided by the Drupal Association, and presents a yearly plan with cost breakdown for Board approval.

Transparency and Appeals

The DCWG aims to be as transparent as possible by documenting its decisions publicly.

Individuals who do not agree with a given DCWG decision may escalate to the Drupal Association staff and/or their designate(s), who will review the decision and can choose to either uphold or alter it. In the meantime, the decision of the DCWG stands.

Membership

The current members are (in no particular order):

  • TODO

Members are appointed by the Drupal Association Board and/or their designate(s).

Charter revisions

The charter will be revised as needed. Any proposed charter revisions must be ratified by the Drupal Association Board and/or their designate(s) prior to acceptance into this charter.

Files: 
CommentFileSizeAuthor
#18 1929530-18-governance.patch1.78 KBtvn

Comments

LeeHunter’s picture

I have added this issue which is relevant to all the proposed working group charters #1934018: Formalize stakeholder roles in working group charters.

LeeHunter’s picture

Issue summary: View changes

Added initial draft

Bojhan’s picture

I'd love to know how it intends to communicate to the larger community, as a group that is focused around content - that should be part of its strategy. I have always liked status updates, but they are often lacking after a few attempts. There is a reference here to a marketing committee, I have not yet seen this emerge?

Shouldn't this also contain a activity/hours per week part? Even though its inclusive, it should be clear what is expected in terms of dedication - something that is also very helpful for employees to schedule in time, once someone chooses to become part.

The duties part is a bit mixed, right now I see 3 distinguishable duties:
1) Content moderation
2) Marketing
3) User experience

This look like quite a vast role for a small group, I assume tvn is going to be a big part in this. I would be a little worried if the content group also has the role of defining and carrying the brand, whatever marketing committee starts they should take part in carrying out the brand. Although the content role can support in this, it being part of their primary tasks makes this sound like this is a Content & Marketing group.

yoroy’s picture

To me the marketing role is the odd one. All the others (ux, moderation, analytics) I interpret as different aspects of 'make managable'. Those are all primarily focussed on facilitating a good content flow.

The marketing one suggest that the working group is responsible for actually generating that content. I can see how the working group should work on *facilitating* marketing messages across d.o., but I'd expect that content to be created by others.

jthorson’s picture

First, I would echo comments which have appeared elsewhere, in that the actual membership list for the group should be separate from the charter itself; since the individual members will be dynamic (while the charter contents themselves should remain relatively static).

Secondly, the Marketing duty seemed out of place for me as well. If the intent is a focus on drupal.org content specifically, this could perhaps be reworked as:

Ensuring brand consistency:
Developing and maintaining a consistent “voice" and “look and feel" throughout all pages on the website, in alignment with the Drupal brand strategy.
Facilitating Drupal marketing:
Focus on communicating the benefits of Drupal, including positioning relative to competitors, use cases, success stories, etc; in alignment with the Drupal marketing strategy.

This presumes that the actual brand strategy and marketing strategy would be developed outside of the content working group. This is consistent with the concept of separating 'strategy' from 'operations' ... areas that may (arguably) leverage different skill sets.

dddave’s picture

I echo #4 and like the proposed formulation re:marketing.

dman’s picture

It all looks reasonable to me. I'm not personally clear on how this differs from what we already do, but I guess it's about just putting it down in writing somewhere rather than relying on the tacit understanding we've been operating under until now.

laura s’s picture

I agree with @yoroy in #3 about marketing, with the additional consideration that marketing transcends what happens directly on *.drupal.org. Maybe marketing could be sharpened to be about facilitating marketing strategy. As for where that marketing strategy comes from, perhaps that's something that could or should be handled by a separate Marketing Working Group that is a joint collaboration of community members with the DA's marketing committee.

tvn’s picture

Agree with most comments about too big focus on marketing role. The list of duties in general looks a bit vague to me. It feels that the main question is missing: what content do we need in the first place? Is our content relevant and up-to-date? Is it well organized?

Another point - my understanding is that this WG is responsible for visual layout of all pages etc. However it is not clear, with only one mention of "design elements". I think we need to emphasize this in the list of duties as well.

With that in mind I propose the following edits to the charter:

Scope
The DCWG manages and is responsible for overall content strategy of Drupal.org websites, maintaining policies around the major content areas on Drupal.org, including the front page, case studies, marketplace, and Drupal Planet. They also manage the overall look and feel and voice of the website, including its information architecture and design elements.

Specific duties:
1. Content strategy: ensure content meets audience needs and facilitates Drupal marketing strategy, is up-to-date and relevant, old content is properly archived/deleted.
2. Information architecture: ensure content is well organized, manage such elements of Drupal.org websites as navigation, taxonomy, header/footer
3. Design and User experience: Establish standards on how people in various target audiences approach the site and find the information that they need, ensure layout follows D.o style guide and brand guidelines, and is consistent throughout all Drupal.org websites
4. Moderation: Policies around general user-generated content (e.g. spam, unsolicited advertising, fields on registration form, account deletion policy), as well as major content areas of the site (such as Drupal Planet, Marketplace, Case Studies etc.)
5. Analytics: Tracking analytics and demographic data to determine how well or poorly the content on the site is performing so that it can be continually improved.

Collaboration
The DCWG must establish a process that balances timely decision-making with involvement of a broad spectrum of the Drupal community. The DCWG should also work closely with all other working groups, as well as Drupal Association staff and Branding and Marketing committee in order to determine overall needs and priorities for Drupal.org content.

lisarex’s picture

Great draft charter!

Agree with #4 about separating the marketing out more and #8 about getting into a few more specifics.

A couple things that I think are missing:

  1. In addition to analytics, we should be doing ongoing usability studies to help prioritize improvements and research on who uses Drupal.org and how they use it; no doubt the marketing group will be interested as well
  2. Content generation- the group needs to be prepared to generate content or reach out to others in the community to source good content
  3. Work with the Drupal.org Software Working Group: There's a lot of content we *cannot* touch without patching or involving developers. Most of our landing pages are in code, our nodes are in Book content type, and new sections, such as case studies, require changes to the 'Drupal.org customizations' module
  4. Encouraging / mentoring new content contributors (though this probably goes without saying)
lisarex’s picture

Issue summary: View changes

Updated issue summary.

tvn’s picture

Issue summary: View changes

first round of changes, incorporating feedback

tvn’s picture

Issue summary: View changes

bold

tvn’s picture

I started to modify the charter in issue summary so we could move forward with this.

Re: marketing role. I think this is not a specific duty for this WG, but rather something to keep in mind or follow while performing duties. So I did not separate it into own bullet point as e.g. in #4. Instead it's mentioned in descriptions of other duties:

Content strategy: Ensure content meets audience needs and facilitates Drupal marketing strategy..

Design and User experience: Develop and maintain a consistent “look and feel" throughout all Drupal.org websites, in alignment with the Drupal brand guidelines..

Thoughts?

Re: #9 - I've change 'Analytics' to 'Analytics and Research' and added the line about usability studies. Though I am not sure if WG members should actually run the studies. Maybe this can be worded differently.

- Content generation - I don't really expect this small group of people, with all the other tasks they have, to also generate content. Provide tools for others, maintain policies for content - yes. But not actually write e.g. X case studies per month.

- Work with SWG - we do say "works closely with other WGs".

tvn’s picture

I'd love to know how it intends to communicate to the larger community, as a group that is focused around content - that should be part of its strategy.

All D.o WGs intend to communicate their plans/decisions to the community. I think this is more of a process question, how/where exactly the WGs will work and publish their stuff. It's better to discuss this separately from the charter. Maybe it's something for the first meeting of the future WG?

I have always liked status updates, but they are often lacking after a few attempts.

D.o week notes will be published again soon! promise :)

There is a reference here to a marketing committee, I have not yet seen this emerge?

There is Branding and Marketing committee, though not really active. Here is their group http://groups.drupal.org/marketing-drupal and charter https://association.drupal.org/about/staff/marketing-branding-committee

lisarex’s picture

Re: #9 - I've change 'Analytics' to 'Analytics and Research' and added the line about usability studies. Though I am not sure if WG members should actually run the studies. Maybe this can be worded differently.

The changes look good. Why aren't you sure that WG members should run the studies? If the WG is responsible for d.o. usage research then I think it's part of it. If you want, a more ambiguous way to state it is "Conduct research to help prioritize improvements, learn who uses Drupal.org and how they use it."

- Content generation - I don't really expect this small group of people, with all the other tasks they have, to also generate content. Provide tools for others, maintain policies for content - yes. But not actually write e.g. X case studies per month.

Perhaps 'content sourcing and editing' is a better way to phrase it. We're already doing it. Many of us are reaching out to site owners, editing case studies directly etc. Or is that outside the scope? I'm confused if #4 is about content moderation or about maintaining content policies, or both.

It's also not clear how many people will be part of this WG, initially and in the future.

webchick’s picture

I think there's a little confusion here, so I'll try and clarify.

Each of these working groups is only 3-5 people, focusing on generating policies and making key decisions. They are not there to necessarily do the day-to-day carrying out of those policies (though I imagine they would also be present on the various teams underneath the working groups, which might have 20+ people in them).

So for example (I'm kinda handwaving this, but...), the DCWG might draw up some guidelines on how to perform usability studies on Drupal.org, which the Drupal.org content team then goes out and does as part of the data-gathering process of a new improvement. The DCWG would then meet once a month in order to take the results of those studies, as well as GA logs or what have you, and lay out the next step of Drupal.org's content strategy, and/or go in and chime in (as a group) on any of the blocked issues waiting on decisions.

It's definitely not the intention that this governance group spends all day deleting spam. ;) But they *would* establish policies for what qualifies as spam, and what to do about it. Make sense?

lisarex’s picture

Yes, that makes sense. Thanks Angie. I would have probably gleaned that if I slowed down and read all of the posts around this, but I was pinged and went into action mode. :D

In that case, scratch my 'editing' suggestion. I am not sure about 'content sourcing' as good content generally doesn't arrive on the doorstep, so the WG may need to encourage that somehow. Thoughts?

One last thing, in #4 about Moderation there's no mention of the About pages, which are an area of confusion (community thinks the DA maintains those pages) so if we could clarify that one way or another, that would be swell. :)

beejeebus’s picture

perhaps we need to emphasise 'governance' in the name of this group then?

beejeebus’s picture

Issue summary: View changes

some more edits

Dries’s picture

Status: Active » Needs review

Megan and Kieran from the Drupal Association had additional edits they wanted to make to further reflect the importance of the DA's role in the Drupal.org Content Working Group, especially as it relates to the overall marketing strategy and ability to make Drupal.org sustainable. I've incorporated most of those comments, as well as the improvements by tvn, lisarex, and others and committed them to Git at http://drupalcode.org/project/governance.git/blob_plain/refs/heads/maste... , and also updated the issue summary (view the "diff").

I'll leave this at "needs review" for another while to give people a chance to provide feedback on these changes. However, with our infrastructure bills now totalling approx. $80,000/year, it's more critical than ever for the Drupal Association to be able to move quickly to create focused landing pages and other areas of the site that can help support the site, so the "meat" of the charter is unlikely to change much.

Thanks everyone for your feedback so far. It has been most helpful! :)

Amazon’s picture

Here are notes that Megan, from the DA, and I made.

More tools and roles to improve content analysis of Drupal.org

Background we use Google analytics for links in the related projects block on project pages to improve recommended projects. Similarly, the governance should allow for other content analysis tools be used such as GA real time, A/B and multivariate tools that are pretty standard for content evaluation and effectiveness.
This may include the creation of roles specifically for help with the development of marketing landing pages including common SEO and SEM tasks such as adding paths, or tagging content with analytics tools.

Talk about taking direction from the DA when we want to do something like

  1. Provide guidance for content marketing for the association to generate new revenue and make Drupal.org sustainable.
  2. The ability to implement a content strategy and aggregate and focus content around specific new sections of the site. For example, a new page on Drupal talent, drupal.org/talent, would need to aggregate existing content on drupal.org and become the key page for this on Drupal.org. This may involve updating or linking from content in documentation, forums, and existing landing pages on Drupal.org. The association will be doing rapid iterations with these new marketing pages and will need latitude to conduct these changes without having to go through a rigorous and slow review process. The changes will stay in line with trying to ensure any advertising is contextual, relevant, and useful.
  3. Make that page awesome looking which means expand the style guide in some ways to experiment with new layouts. It’s a guide, and there needs to be some creative freedom to create market landing pages and search engine marketing landing pages on Drupal.org.
tvn’s picture

FileSize
1.78 KB

I posted human-readable copy of the charter here https://drupal.org/node/2001502 with clear notice that it's a copy and original is in git.
I do not think that the Charter should include the actual names of current or ex members. There is a page for each working group, which contains this information. E.g. for Content WG: https://drupal.org/governance/drupalorg-working-groups/content
Attached patch removes placeholders for member names from the D.o charters.
I think once that's done this issue can be set to fixed.

webchick’s picture

Assigned: Unassigned » Dries
Status: Needs review » Reviewed & tested by the community

Looks good!

Dries’s picture

Assigned: Dries » Unassigned

Committed the patch in #18.

webchick’s picture

Status: Reviewed & tested by the community » Fixed

Woohoo!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

Updated issue summary.