Potential initiatives

[Andersson007]

Potential initiatives

Relates to PM https://hackmd.io/BpraeZMFRDWM3DW1Q6MUcA?view

Note: you can see some tasks in more than one potential initiative.

0. Community central place, aka forum

• ...
• ...

1. Docsite: new homepage based on personas (would be a great chance to work as a team):

• Main topic Mapping user journeys for the Ansible docsite community-topics#175
• docs.ansible.com: projects besides collections we can put behind the "Project owner/maintainer" persona card community-topics#193
• Docsite user/contributor improvement, personas #120
• Personas https://hackmd.io/pZb5w5JFRQW3RJ73n23tlw?view
• POC https://hackmd.io/MguEzoFwT2GAg6IJ7J6xKw
• mindmaps

2. Collection documentation gaps and other improvements:

• Consisten doc on how to make a collection up and running Docs: is there a consistent doc how to make a new collection up and running? #17
• Make inclusion visible on docs.ansible.com Collection Inclusion: make it visible on docs.ansible.com #77
• Patchback, collection bot and GHA info to docs.ansible.com Patchback, collection bot and GHA info to docs.ansible.com #108
• How Can I Help: Add community topics and SC info docsite, how can I help: add community topics and steering committee info #146
• Merging How Can I Help and Contributor path: Docsite: think of merging How Can I Help and the Contributor path #147

3. Package testing:

• Main topic [Epic] Testing collections in the package #57
• Implementation Testing Collections: implementations #59
• Identify issues Testing Collections: identify issues #58

4. Community architecture practices:

• Strong mission statement:
  • Community Strong Mission statement to define #131
  • https://discourse.ansible.im/t/ansible-community-strong-mission-statement/82

5. Ansible package inclusion experience improvement:

• Role-focused collection inclusion Role or playbook-focused collections: include in the Ansible or not? If yes, which criteria/requirements to use? community-topics#197
• Clarify documentation for community collection testing #109
• Collection community approval instead of inclusion community topic "Community-approved collections" instead of file inclusion in the Ansible package. community-topics#198
• Collection inclusion improvement Collection inclusion: improvement #76
• Make inclusion visible on docs.ansible.com Collection Inclusion: make it visible on docs.ansible.com #77
• Update inclusion guidelines Update inclusion guidelines #100
• Update collection requirements Collection Requirements: update based on discussion in community-topics #106
• Update collection removal procedures Update collection removal procedure #72
• Move inclusion related pages to docs.ansible.com docs.ansible.com: move inclusion related pages to Ansible doc site #66

6. How to make life of our contributors easier (relates to some other initiatives listed here)

• Think about ways on how to make life of our contributors easier #94
• board for community-topics, decision implementation control

7. Tidy up/update things in our community repos:

• ansible/community ansible/community: update/close what should be #87
• community-topics Tidy up project in community-topics, re-arrange it to track decision implementation progress #24
• ansible-collections/overview ansible-collections/overview: tidy up #26
• ansible-inclusion ansible-inclusion repository: tidy up discussions #11

8. Do something with community.network:

• community.network: find maintainers #85
• community.network: collection bot does not work #111

8. Outreach program

• Group outreach
• Individual contributor outreach leveraging Savannah, Greg's radial plot, etc (i.e. talking to people, identifying their motives, helping, etc).
  • Analyze activities of all (non-redhat) contributors from Greg's radial plots #8

[samccann]

This was helpful, thanks.

I put some on the team initiatives board. The rest, I put comments on some, but others are more tactical. We decided that the intitiatives board is for our top main areas of focus for the year. I added an 'Improve Ansible Package' and in that intitiative I put some of the collection stuff here, but not all. A lot of them are documentation issues that should be moved to ansible/ansible, but I do realize that may make it 'out of site out of mind' so to speak. But if we don't move it, then maybe we keep the community-team project board and add it to that one. We could us that board for people to 'self-triage' so to speak, and try to handle keeping those issues moving forward asynchronously?

[Andersson007]

I think most of those tasks with comments about moving to ansible/ansible belong to the "Improve User/Contributor experience" initiative.
Those things currently are not visible/do not exist which is a big obstacle IMO. When we eliminate obstacles/covere gaps, won't it improve the overall contributor experience?

[samccann]

good point - added them to the project board