Problem/Motivation

Based upon the personas defined in #3071311: Proposed personas for the Getting Involved Guide, we need an outline of the Getting Involved Guide, at the highest level, from which to work.

This outline does not need to define every single piece of content, only the major sections required and for whom they are developed.

See also these sites that are about finding volunteer opportunities (across non-profit agencies):
https://www.idealist.org/ (world-wide)
https://www.volunteerspokane.org/need/ (local to Spokane, WA)

Note that they both have various filters (geographic, time commitment, what the agency does [impact area], skills to be used, etc.).

Proposed resolution

Here is the proposed outline, including a summary of what each page/section would contain.

Getting Involved (landing page)
welcome; explain that the Drupal project is a world-wide community that comes together voluntarily to build and maintain the Drupal software, Drupal documentation, and the Drupal community; these areas are overlapping; this section exists to help people figure out fulfilling and productive ways to get involved in these efforts (find tasks to work on; learn about the logistics, policies, and politics of contributing); link to the Community landing page and explain what that is for, explain the organization of this section. Suggest an immediate way to get involved by completing a simple task, and then how to deepen involvement.
Help build and maintain the Drupal community (landing page with sub-pages)
Talk about the importance of having a healthy community in order to come together to build great software and documentation. Talk about the world-wide nature and diversity of the Drupal community, and inclusion. Talk about on-line vs. in-person interactions, local to regional to international scope. Point to the community landing page for an overview of the ways the community comes together. Overview of different ways that people can help build community (participating, organizing, mentoring, etc.). Link to contributor taks search.
Help build and maintain Drupal software (landing page with sub-pages)
Explain the organization of Projects (Drupal core, modules, themes, distributions). Explain that many different skills are needed (visual design, programming, usability, accessibility, translation, ...). High-level overview of the processes for contributing (Git repositories, issues, patch-based workflow, chatting on Slack, etc.), with links to specific information in the Reference information section. Initiatives in Drupal Core. Link to the Contributor task search.
Help build and maintain Drupal documentation (landing page with sub-pages)
Talk about the different types of Drupal documentation, and at a high level, how each is generated and maintained. High-level overview of the processes for contributing to each type of documentation, with links to specific information in the Reference information section. Initiatives in Documentation. Link to the Contributor task search.
Contributor task search
"Task library" with search/filter by skills needed, expertise level, time to complete the task, etc. Tasks would link to reference information pages rather than repeating the information. See comment #2 on this issue. Tasks would include things like attending a local Drupal meetup (with info on how to find one near you) -- make sure the tasks cover getting involved in Community, Software, and Documentation. [Maybe task is not the best word... is there something better?]. Each task needs to state its goal, time commitment, and skills needed (see more about that in the Skills section below). Also each task should be classified as to whether it relates to building community, software, or documentation.
Reference information for contributors
Sections/pages on how to use Git, make a patch, use the issue queue, etc. so that each Task in the Task library doesn't have to repeat the same information. I don't think this needs to have a filter/search function particularly.
Contributor roles search
"Roles library" that would describe different roles people can hold in the Drupal Community. Should include a "just getting started in contributing" role, and a "occasionally have time" role [not sure about those names, but we need to be inclusive and realistic about the time availability of some people, and still value their contributions.]. Roles should cross-link to tasks, but be more about the "why", level of commitment, and how filling this role has a positive impact on the project. Should include information about the time commitment, and we also need a page about how to gracefully step down from a role. Also each role should be classified as to whether it relates to building community, software, or documentation.
Skills browser
"Skills library" that would have a page describing each skill that someone could either use or improve in their contribution work. Would also describe how to learn the skill, and how to improve it via contributor tasks/roles. Contributor tasks and contributor roles would have entity references to these skills, along with an expertise level for each one, so that if you were on a page for a particular skill, you should be able to see the tasks/roles that need this skill, what level of expertise you need, and maybe a flag for "this is a good task for improving this skill".

Remaining tasks

Decide on the outline.

Comments

rachel_norfolk created an issue. See original summary.

jhodgdon’s picture

One thing that came out of the meeting today
#3071307: Meeting - Getting Involved Guide - 30 July 2019
was the idea of having some kind of a "Task Library" as part of Getting Involved. Features:
- Central repository for specific tasks that contributors could do
- Tags/taxonomy for various skills (based on the Personas list from #3068287: Consensus on contribution personas
- People could search/filter for tasks based on the skills taxonomy.
- Task pages should have a specific structure. Either a page template or fields could help enforce that structure.
- We have some tasks written up now at https://www.drupal.org/contributor-tasks -- and there is also a template -- which could be a good starting point
- Based on that section, there also needs to be a section on "Background information" that would apply to multiple tasks. Things like a description of drupal.org issues, git information, etc.

jhodgdon’s picture

Another note: there was a proposed outline for this section on #1414988: [Meta/Plan] Create a new Getting Involved Guide section, in the issue summary. I'm not saying we should use that outline, but it might be a starting point?

jhodgdon’s picture

I'm going to make a first draft of this, as discussed in today's meeting

jhodgdon’s picture

Issue summary: View changes
Status: Active » Needs review

Here are my preliminary ideas on how to organize Getting Involved.

mradcliffe’s picture

> Suggest an immediate way to get involved by completing a simple task, and then how to deepen involvement.

I really like this idea for the initial page. Getting on Drupal chat and creating a drupal.org user account are usually the first things that we cover at in-person events.

Regarding contributor task search and reference, one of the things I struggle with is which one to link first. I usually find the contributor task page first and link from there, but I try to mention that there are links to reference items on those page that also tell how to do them. I think this organization is probably fine, but would like to be able to better call out the reference for a task.

It almost seems like the first two lead into contributor tasks which lead into reference, but then also a continuing contributor would want to quickly find, review and/or link to a specific reference or task page.

As a new contributor, I probably want to be guided through a clear hierarchy more so than decide what I think I would need to click on to get the information. Getting Involved > Help build > task > reference

As a continuing contributor, I probably want the ability to quickly find a specific reference or task page so that I can review and/or link to it. Getting Involved > task(s) or Getting Involved > reference(s).

jhodgdon’s picture

Issue summary: View changes

At Tuesday's meeting for this project, we discussed that besides the "tasks library", we also need a "skills library" and a "roles library". So, adding something about these to the issue summary proposal.

jhodgdon’s picture

Issue summary: View changes

fix HTML syntax

mradcliffe’s picture

@jhodgdon brought up a good question in the online meeting on 2019.10.08, "Besides it being maybe short on details...are there ideas we need to incorporate, overarching goals, etc.?"

@rachel_norfolk mentioned that the Getting Involved guide "needs to be more than just prose" and contain "some active components that allow us to build tools that let people define roles, growth opportunities, skills", etc... And about the "why" and not just the "how".

Given that, I think I see two remaining tasks on this issue:

1. Review and possibly add what @rachel_norfolk touched on.
2. Create or find the follow-up issues(s) that may be implementation or getting to implementation.

I think analyzing the outline and trying to break down what is currently possible out of it and what content editing or content building tools on drupal.org need to be improved or changed could be a follow-up, but could also be done in this issue?

jhodgdon’s picture

I don't know what "active components that let us build tools that let people define ..." means at all.

But that aside... As far as the why vs. the how... I thought that the goal of the Getting Involved Guide was more practical: you've decided you want to contribute your time, and this guide should:
- help you find a fulfilling way to contribute your time
- help you learn about the available roles and tasks
- help you learn the skills and practicalities of how to fulfill the roles and do the tasks

In other words, I think that the Community landing page and the group subsections there are more about the "why" and Getting Involved is more about the "how".

If "how" isn't the goal... then we need another guide that does that. But that is what I thought we were building here?

jhodgdon’s picture

Component: Getting Involved Guide » Community Content
Status: Needs review » Fixed

This has pretty much been implemented in the new Contributor Guide section (which is a work in progress). I think we can mark this as Fixed.
https://www.drupal.org/community/contributor-guide/

See also the guidelines about content types for the new guide:
https://www.drupal.org/community/contributor-guide/background-and-refere...

And this meta issue about fleshing out the content:
#3144893: [Meta] Content for the new Contributor Guide

Status: Fixed » Closed (fixed)

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