>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3089403. --> Reported by: [rachel_norfolk](https://www.drupal.org/user/66273) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>There are many roles in the Drupal contributor community that make it work successfully; be they code contributors, project maintainers, documenters, marketers, project managers, event organisers, event volunteers, speakers, or any of those I can't think of right now!</p> <p>We do not, however, have a canonical place where somebody new to the community and looking to increase their involvement can browse the possible roles and understand</p> <ul> <li>which roles are there <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal_org_community/issues/3091381" title="Status: Closed (fixed)">#3091381: Create a list of all roles, skills, responsibilities in the drupal community</a></span> </li><li>what the role involves</li> <li>what skills are required</li> <li>what skills may be learned as part of being in role</li> <li>what mentoring options there are</li> <li>what expectations of communication and reporting there are</li> <li>what expectations of leadership behaviour there are</li> <li>what options are opened after completing time in this role</li> </ul> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Create a new Contributor Guide area, where community groups, such as the CWG, Event Organisers Group, the Mentoring Leads, Maintainers, Project Leadership etc can help to create a single place listing all of the roles, skills, and tasks that make up the Drupal Project Community.</p> <h4>Content model</h4> <p>We have defined 3 new content types and 1 taxonomy vocabulary, and are also using some existing content types:</p> <dl> <dt>new type: Contributor Role</dt> <dd> A contributor role that is documented as part of the Contributor Guide. A Role is a "position" in the community (short- or long-term).</dd> <dt>new type: Contributor Task</dt> <dd>A contributor task that is documented as part of the Contributor Guide. A Task has a well-defined goal and well-defined steps.</dd> <dt>new type: Contributor Skill</dt> <dd>A contributor skill that is documented as part of the Contributor Guide. A Skill gives you the knowledge to perform a Task or fill a role</dd> <dt>new vocabulary: Contribution Area</dt> <dd>An area for contributors to contribute to, such as Documentation, Drupal Core, or Community. You would put a brief description and link to more information in the Description field.</dd> <dt>Contributor Reference Information</dt> <dd>We need a space for background and reference information that is common to more than one Contributor Task. This will be put into its own Documentation Guide in the contributor guide area, with content being Documentation Page/Guide content items.</dd> <dt>existing types: Page, Section</dt> <dd>The landing pages for this new section are type Page or Sectoion. We do need to make a couple of small changes to the Page content type (which is in an existing drupalorg project feature): (a) path auto settings so that these pages will have good URLs (b) allow for certain views panels to be added to Pages. We'll need a small patch to the drupalorg features for these changes.</dd> </dl> <p>Properties of new content types -- The three new content types have the following attributes/properties:<br> - Comments are disabled; instead, we'll have a block telling how to create an issue or get help.<br> - Revisions are required on all changes. However, since comments are disabled, there is at present no way for people to be notified when someone makes a revision.<br> - All confirmed users can edit them (like doc pages), at least for now.</p> <p>Relationships:<br> - Roles have a field called "Tasks this role performs", which lists Tasks. Task pages show the roles that perform the tasks (in a view).<br> - Roles have a field for "might lead to", that references other roles.<br> - Tasks have a field for "might lead to" that references other tasks and roles.<br> - Roles and Tasks have fields for required skills and skills you can improve by doing the role/task. Task pages show roles/tasks related in these ways.<br> - Tasks have a field for background information references<br> - Roles and Tasks have a taxonomy reference for the Contribution Area(s). Displays the name and description in a view.<br> - The Contribution Area taxonomy terms also have generic Page content type landing pages, which have a view pane showing the related tasks/roles (related to the associated taxonomy term), and skills (related via the tasks/roles).<br> - All relationships are displayed in both directions.</p> <h4>Sample pages</h4> <p>We have created a test site with some content types and views... Here are some links to pages to look at on the site (don't take the content/links too seriously -- we just put random content and cross-links in there for testing purposes). <strong>[The user name/password for htaccess on dev sites is always drupal / drupal , and if you want to test creating content, you can log in with bacon / bacon as on all dev sites]</strong></p> <ul> <li>Contributor page (explains content types for contributors): <a href="https://rnorfolk-drupal.dev.devdrupal.org/node/3089309">https://rnorfolk-drupal.dev.devdrupal.org/node/3089309</a></li> <li>Role browser: <a href="https://rnorfolk-drupal.dev.devdrupal.org/node/3089293">https://rnorfolk-drupal.dev.devdrupal.org/node/3089293</a></li> <li>Skill browser: <a href="https://rnorfolk-drupal.dev.devdrupal.org/node/3089302">https://rnorfolk-drupal.dev.devdrupal.org/node/3089302</a></li> <li>Task browser: <a href="https://rnorfolk-drupal.dev.devdrupal.org/node/3089308">https://rnorfolk-drupal.dev.devdrupal.org/node/3089308</a></li> <li>Individual Role page: <a href="https://rnorfolk-drupal.dev.devdrupal.org/getting-involved/role/documentation-editor">https://rnorfolk-drupal.dev.devdrupal.org/getting-involved/role/documentation-editor</a></li> <li>Individual Skill page: <a href="https://rnorfolk-drupal.dev.devdrupal.org/getting-involved/skill/using-git">https://rnorfolk-drupal.dev.devdrupal.org/getting-involved/skill/using-git</a></li> <li>Individual Task page: <a href="https://rnorfolk-drupal.dev.devdrupal.org/getting-involved/task/leading-a-meeting">https://rnorfolk-drupal.dev.devdrupal.org/getting-involved/task/leading-a-meeting</a></li> <li>Contribution area page: <a href="https://rnorfolk-drupal.dev.devdrupal.org/contributor-guide/area/documentation">https://rnorfolk-drupal.dev.devdrupal.org/contributor-guide/area/documentation</a></li> </ul> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Here is a list of what still needs to be done.</p> <h4>Questions to be answered and other remaining engineering To Dos</h4> <p>We need to resolve everything to do with thinking about ongoing use by each group of people: editors of the section, people in charge of contribution areas (such as Drupal Core governance), and contributors using the section to find appropriate contributor tasks/roles:</p> <ul> <li>Breadcrumbs for <a href="https://www.drupal.org/community/contributor-guide/background-and-reference-information">https://www.drupal.org/community/contributor-guide/background-and-reference-information</a> especially, but to some extent also the other landing pages, might need an update. These have been moved to follow-up issues, since they affect other pages on drupal.org as well:<br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupalorg/issues/3115704" title="Status: Closed (fixed)">#3115704: Documentation pages need the ability to "live" in other sections</a></span><br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupalorg/issues/3115701" title="Status: Closed (fixed)">#3115701: Community section headers/breadcrumbs could be nicer</a></span> </li> <li>If we make further mods to the content types or views, we will need to make a new Features patch. We are up-to-date through comment #137.</li> <li>On drupal.org, we need to write up instructions for how to add a new contribution area, including creating its page, its taxonomy term, and adding in the views and sidebar help block.</li> <li>Final approval from DA/Engineering</li> </ul> <h4>Deployment plan</h4> <p>The first steps of this need to be done by someone on the drupal.org infrastructure team. The content editing steps could be done by Jennifer or Rachel if they are given sufficient permission (those steps are annotated to say this).</p> <ol> <li>When we're ready to deploy, we need to have the DA create a new development site, and test that these deployment steps work. If not, we will need to modify the features/patches from the existing dev site so that they capture all the changes we made.</li> <li>Get the codebase ready:<br> - Bluecheese theme -- merge &amp; deploy <code>3089403-contributor-content</code> branch<br> - drupalorg_crosssite -- committed &amp; deployed: <a href="https://git.drupalcode.org/project/drupalorg_crosssite/commit/c8ed5a9">https://git.drupalcode.org/project/drupalorg_crosssite/commit/c8ed5a9</a><br> - drupalorg -- merge &amp; deploy <code>3089403-contributor-content</code> branch </li> <li>(For dev sites) Run <code>bundle exec compass compile</code> in Bluecheese theme to apply the changes to the stylesheets</li> <li>Go to admin/structure/features. Check the box for the new Contributor Guide feature, and click Save changes to enable it.</li> <li>Clear the cache</li> <li>Set up the permissions for the content types (admin/people/permissions):<br> - Grant permission to Add and Edit All for the 3 new content types (Contributor Role, Contributor Task, Contributor Skill) to all Confirmed users.<br> <code>drush -v role-add-perm 'confirmed' 'create contributor_role content,edit any contributor_role content,create contributor_skill content,edit any contributor_skill content,create contributor_task content,edit any contributor_task content' --cache-clear=0</code><br> - For the new taxonomy vocabulary (Contribution Areas), permission to edit its terms should be added to administrator, webmaster, content administrator, content moderator so that several people could be pinged to add terms (this should be fairly rare to need new terms added). <pre>drush -v role-add-perm 'webmaster' 'edit terms in 71,delete terms in 71' --cache-clear=0<br>drush -v role-add-perm 'administrator' 'edit terms in 71,delete terms in 71' --cache-clear=0<br>drush -v role-add-perm 'content administrator' 'edit terms in 71,delete terms in 71' --cache-clear=0<br>drush -v role-add-perm 'content moderator' 'edit terms in 71,delete terms in 71' --cache-clear=0</pre></li> <li>Create the custom block (admin/structure/block/add) that tells where to report problems and get help:<br> Block description: Contributor guide help<br> Visibility: Sidebar Second on Contributor Role, Skill, and Task content types<br> Block content: <pre>&lt;h3&gt;Help improve this page&lt;/h3&gt;<br>&lt;a href="/node/add/project-issue/drupal_org_community"&gt;Create an issue&lt;/a&gt; describing the problem.<br><br>&lt;h3&gt;Need help deciding how to contribute?&lt;/h3&gt;<br>Visit the &lt;a href="/community"&gt;Community landing page&lt;/a&gt; to learn more about the Drupal community, or start at the top of the &lt;a href="/community/contributor-guide"&gt;Contributor Guide&lt;/a&gt; to find roles and tasks organized by skills and community areas.<br><br>&lt;h3&gt;Need help completing a task?&lt;/h3&gt;<br>Check out the &lt;a href="/community/contributor-guide/background-and-reference-information/getting-help-with-contributing"&gt;Getting help with contributing&lt;/a&gt; section.</pre></li> <li>Back on the admin/structure/block page, enable these blocks for Sidebar second:<br> - [Visibility: on Contributor Task] View: Contributor Guide Blocks and Panes: Roles using task<br> - [on Contributor Role] View: Contributor Guide Blocks and Panes: Sidebar fields for Role<br> - [on Contributor Task] View: Contributor Guide Blocks and Panes: Sidebar fields for Task<br> - [on Contributor Skill] View: Contributor Guide Blocks and Panes: Tasks/Roles improve skill<br> - [on Contributor Skill] View: Contributor Guide Blocks and Panes: Tasks/Roles require skill<br> - [on Contributor Task and Contributor Role] View: Contributor Guide taxonomy views: Areas for Task/Role page<br> - [on Contributor Skill] View: Contributor Guide taxonomy views: Areas for skills page </li> <li>Still on admin/structure/block, drag the blocks in Sidebar Second so they are in this order and Save blocks:<br> View: Contributor Guide Blocks and Panes: Sidebar fields for Role<br> View: Contributor Guide Blocks and Panes: Sidebar fields for Task<br> View: Contributor Guide Blocks and Panes: Roles using task<br> View: Contributor Guide taxonomy views: Areas for Task/Role page<br> View: Contributor Guide Blocks and Panes: Tasks/Roles require skill<br> View: Contributor Guide Blocks and Panes: Tasks/Roles improve skill<br> View: Contributor Guide taxonomy views: Areas for skills page<br> Contributor guide help </li> <li>Edit the Panelizer settings for Page content so that it allows the following content to be used<br> (Go to admin/structure/panelizer and find the Page content type, click "allowed content" -- or go directly to<br> admin/structure/panelizer/node/page/allowed)<br> Enable:<br> Allowed block content &gt; Contributor Guide Help<br> Allowed views panes content &gt; View: Contributor Guide Blocks and panes --- all of the following:<br> - Role Browser<br> - Task Browser<br> - Skill Browser<br> - Tasks/Roles in area<br> - Skills related to area<br> (and click Save) <p>Also edit the Panelizer settings for Section content on admin/structure/panelizer/node/section/allowed so that it allows:<br> Allowed block content &gt; Contributor Guide Help</p> </li> <li>(Could be Jennifer/Rachel) Add views and blocks to the Roles, Skills, and Task browser pages:<br> - Find these three pages starting at community/contributor-guide<br> - Add the content by going to Customize display &gt; Content; the content to be added is in the "Blocks" and "Views panes" sections.<br> - Child page "Find your role":<br> -- Bottom right: Contributor Guide help block<br> -- Left content: View: Contributor Guide Blocks and panes: Role browser pane<br> - Child page "User or improve your skills":<br> -- Bottom right: Contributor Guide help block<br> -- Main content area: View: Contributor Guide Blocks and panes: Skill browser pane<br> - Child page "Find a task":<br> -- Bottom right: Contributor Guide help block<br> -- Main content area: View: Contributor Guide Blocks and panes: Task browser pane </li> <li>(Could be Jennifer/Rachel) Fix up the contribution area pages. For each page that is a child of community/contributor-guide/contribution-areas :<br> a) Go to admin/structure/taxonomy/contribution_area/add and add a new term. The term name should match the menu link (such as Accessibility). The term description should say: <pre>Contribute to improving NAME_OF_AREA. &lt;a href="/community/contributor-guide/contribution-areas/END_OF_URL_HERE"&gt;Read more about contributing to this area&lt;/a&gt;.</pre><p> (Save the term)</p> <p>b) Go back to admin/structure/taxonomy/contribution_area and find the term ID of the term you just added.</p> <p>c) On the contributor area page, go to Customize display / Content. Add the following:<br> - Bottom right: Blocks &gt; Contributor guide help<br> - Left content: View panes &gt; View: Contributor Guide Blocks and Panes: Tasks/Roles in area and Skills related to area [you will need to enter the term ID as Contributor Area when you add the pane] </p></li> <li>If you want to test if it's OK, I suggest going to admin/content and adding a related set of Contributor Skill, Task, and Role (in that order). Then starting at community/contributor-guide, see if all the pages have some links on them. </li></ol> > Related issue: [Issue #2974016](https://www.drupal.org/node/2974016) > Related issue: [Issue #3071313](https://www.drupal.org/node/3071313)