-
Notifications
You must be signed in to change notification settings - Fork 2
Potential initiatives #148
Comments
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? |
I think most of those tasks with comments about moving to ansible/ansible belong to the "Improve User/Contributor experience" initiative. |
good point - added them to the project board |
Potential initiatives
Relates to PM https://hackmd.io/BpraeZMFRDWM3DW1Q6MUcA?view
0. Community central place, aka forum
1. Docsite: new homepage based on personas (would be a great chance to work as a team):
2. Collection documentation gaps and other improvements:
3. Package testing:
4. Community architecture practices:
5. Ansible package inclusion experience improvement:
6. How to make life of our contributors easier (relates to some other initiatives listed here)
7. Tidy up/update things in our community repos:
8. Do something with community.network:
8. Outreach program
The text was updated successfully, but these errors were encountered: