Skip to content
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.

Contributor Experience: Plan

John R Barker edited this page Aug 3, 2018 · 15 revisions

Contributor Experience Plan

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

  • Theme 1: Build up working groups
  • Theme 2: Make it clearer how to develop modules
  • Theme 3: Reduce issue/PR backlog

Discussion welcome in #ansible-community

Objective: This is about scale and empowering others to do things themselves

A well functioning group should be able to:

  • Welcome new members into the group
  • Provide a variety of items for people to get involved with
  • Keep on top of their backlog
  • Set direction

Goal: Find out if we are building up and maintaining active groups.

aka If we don't measure, how do we know if we are improving

  • Unique people active in IRC meetings
  • Number of people active on agenda issues

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
  • Important to get input from new contributors

The various groups have found things that work for them, we should review, document and roll out for other groups what works. If something doesn't work then analyse why not

Goal: Showing progress keeps motivation

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

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

On hold till till above items have been done, we don't want to invite more people till the groups are in a better state

On hold till till above items have been done

Series of blog posts, one per working group, showing what they've achieved and how to get involved.

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

(Will partly be addressed by theme 1) 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

Merging

(ARchived) Working groups

Working groups are now in the Ansible forum

Ansible project:
Community, Contributor Experience, Docs, News, Outreach, RelEng, Testing

Cloud:
AWS, Azure, CloudStack, Container, DigitalOcean, Docker, hcloud, Kubernetes, Linode, OpenStack, oVirt, Virt, VMware

Networking:
ACI, AVI, F5, Meraki, Network, NXOS

Ansible Developer Tools:
Ansible-developer-tools

Software:
Crypto, Foreman, GDrive, GitLab, Grafana, IPA, JBoss, MongoDB, MySQL, PostgreSQL, RabbitMQ, Zabbix

System:
AIX, BSD, HP-UX, macOS, Remote Management, Solaris, Windows

Security:
Security-Automation, Lockdown

Tooling:
AWX, Galaxy, Molecule

Communities

Modules:
unarchive, xml

Plugins:
httpapi

Wiki

Roles, Communication, Reviewing, Checklist, TODO

Clone this wiki locally