Contributor Experience: Plan

The Contributor Experience had a wide remit, though is currently focusing on the following themes.

Discussion welcome in #ansible-community

# Theme 1: Build up working groups Objective: This is about scale and empowering others * Form, motivate (via their own success) and grow groups

## Measure existing working groups Goal: Find out if we are building up and maintaining active groups.

Possible Metrics * Unique people active in IRC meetings * Number of people active on agenda issues ## Blockers & pain points: Identify & document Goal: Make life easier

• Asking a wider range of people for pain points allows us to spot common issues and address them
• Review previous Contributor Summit docs
• Ask newest members

## Share any best practices

• "AWS: Monthly status"
• "Network: track actions on agenda"

## Ensure each group has some way of showing what it's achieved Goal: Showing progress keeps motivation

• Motivates existing and new people
• Such as AWS's boto3 porting and testing monthly stats

## Ensure each group has a task list Goal: Ensure that new people that want to get involved have something to help with

• MUST include non-Python tasks
• MUST include some well defined simple items

## Identify and invite others to join

• Possibly put on hold till other
• ~~[Ansibullbot to promote IRC Working groups #820](https://github.com/ansible/ansibullbot/issues/820)~~ DONE

(Lots of things can be done here)

## Blog posts series on the cool things the groups are doing

# Theme 2: How to develop modules Objective: * Docs: dev_guide reorg to make it easier to create and write content (acozine is working on this) * Docs: Real examples on how to document your module * Docs: fix module checklist * Docs: How to write a good integration tests * Continue to spot common issues with new PRs and doc/automatically test them

# Theme 3: PR(/issue) backlog (Will partly be addressed by theme 1) I'm not interested in discussions regarding moving content out of ansible/ansible, that's out of scope * break PR workflow into a flowchart, stats on where on the workflow PRs are * Attack these areas as individual items