For issues to be done by the Community Team that don't fall into a particular repository
Go through and tidy up discussions in the ansible-inclusion repository.
Along the way:
Maintainers feedback needed or Maintainers do not respond.Accessibility is not a one time fix-it-all and forget about it task. As a community we need to come up with a way to ensure we provide an accessible documentation and it remains accessible for the long term.
Expected Results
Provide a plan to ensure our documentation remains accessible over time.
Update collection inclusion submission docs to ask submitters to review another request before submitting their requests.
Justification:
Announce docs moved from [community-docs](https://github.com/ansible/[community-docs](https://github.com/ansible/community-docs/) to docs.ansible.com.
Why: we have those important contributor docs on our site but many people don't know about it so can't use.
Analyze UX for contributor/maintainer docs, in particular:
[email protected]?TO FIX:
Currently if any file is changed in a repository with GHA, it runs all available tests (all targets).
It affects GHA CI performance across all the collection under the ansible-collections.
It causes the long queue, so contributors can wait for hours with "Queued task" to get the result.
If we could find a way to make GHA to run only targets related to changed files, it'd be really cool.
Relates to ansible-community/community-topics#122
As the Community Topics project is not used to track discussion progress anyway, we (the Community) decided to use it to track the decision implementation progress.
What does having an accessible documentation means ?
Goal of this issue is to gather a set of resources that help clarify for anyone interested in this topic what this means. What does it mean for us - as we write documentation - to keep in mind ?
Expected Result
The expected result of this conversation, before we can close it, is a list of actionable information we could leverage to make our documentation more accessible
community.sap: can we disable tests as the collection has been superseded by another collection?
EOL docs still get a lot of hits due to showing up in google search results. Investigate options on how to recover from this.
We may need to adhere to the following accessibility standard across all of ansible.com:
https://www.ibm.com/able/
While this is still pending, we should investigate what this means and see if there are some easy fixes we can apply.
Create a rep and a project for Community Team work tasks.
Need to figure out how it works, its features, etc. I.e. read the full guidelines.
Workflow:
Assignees property emptyhelp_wanted labelGoals:
Create on-boarding document
In order to grow our community base, we should be thinking about how do we reach outside current Ansible community. How do we get people interested in contributing into one of the various ansible communities. An Ansible contributor is not meant to be only a python coder, there are various way that someone can engage with the various communities (Documentation, Release, People management - running meetings, getting people in touch - Infra, etc...).
The goal of this EPIC is to write, communicate and implement an Outreach program that will help get external to Ansible community contributors to be active contributors in our ecosystem
Help a new maintainer with releasing community.mysql 1.4.8, 2.3.9 and 3.4.0
Docs: is there a consistent doc under https://docs.ansible.com/ansible/devel/community about how to make a new collection up and running?
If not create it.
Among other thing should cover:
per Matt Clay's request:
ansible/ansible#78424
Fixes a broken reference. The question is - why was this problem not picked up by the ansible/ansible CI infrastructure.
Currently we can't update our docs dependencies to rstcheck 6.0 or above because it spits out too many warnings in CI tests to fix before the 2.14 branch pull.
We need to :
Please put a list of collections you reviewed in a comment + all important info
Conduct a PR day regularly across all the collections under ansible-collections (not necessarily all at once).
Goals:
Hacktoberfest is a yearly event that encourages people from all over the planet to contribute (in a meaningful way) to Open Source.
The goal is to provide easy enough, yet impactful issues to contributors that are not normally part of your traditional contributors circle.
Our commitment is to be engaged with them to ensure their contributions land in a timely fashion and they get the assistance they need.
Expected Results
ansible/ansible (and other repo under ansible org) have added the hacktoberfest topic in their descriptionhacktoberfest label and clear explanation on what's exectedBefore going out and "capture new contributors" we need to understand the current state of our community. How active it is on Github ? How active it is on IRC/Matrix ? How active it is on mailing list ? How active it is on social events like Meetups ?
Having visibility in those data can help see what is it we are doing right and help isolate the gap we have to attract a new set of contributors.
Expected Results
In order to close that issue, we need to have a way to visualize current community "health" over time (engagement, activity, ...). This could take the form of HTML report that could be shared.
Communicate in the email thread with a RH's partner ExxonMobil about their collection
Mid 2021, the Ansible Community team provided Matrix as an alternative to IRC, allowing user to choose which protocol they wanted to use to be able to communicate for instant messaging (IM). The intent behind this move was well described in @GregSutcliffe 's blog post
This sentence summarized the reason of the move pretty well.
The world turns, and we move with it. The way in which we communicate has evolved, as it always has, and periodically we must catch up if we want to attract new people to our community. Today, that means offering a place where new and existing contributors feel welcomed, safe, and valued, with a rich interface and a low barrier to entry. I want to help build that, because I fear that if we don’t, we will fade, and Ansible deserves better than that.
To follow up with what has been done for instant messaging, we should rethink our approach to email-based communication (mailing lists) and ensure we provide new contributors with a low barrier to entry (easy contributor experience) while still allow contributors to use the mailing lists.
Expected Results
Have a conversation and provide a path forward (or not with justification) on how to evolve our currently email-based communication system to a lower barrier to entry one new contributors might find it easier to use.
Productization team is using docs/docsite/requirements.txt but that file is for bleeding edge testing on docs builds. Discuss how they can switch to the code-smell test file, or how we can coordinate so docs, CI, and productization are using the same requirements and in sync when those requirements change.
As there are 5-6 inclusion requests are waiting for inclusion reviews, it'd be nice to conduct a kinda review day:
https://github.com/ansible-collections/ansible-inclusion/discussions/
Analyze activities of all (non-redhat) contributors from Greg's radial plots.
Goals:
Implement regular automated PyPI package testing:
Related issues:
Collection inclusion: Add ibm.spectrum_virtualize to the ansible package:
ansible-collections/ansible-inclusion#35
ansible-community/community-topics#85
ansible-community/ansible-build-data#148
Write a script to get 3d party repo URLs of collections included in Ansible
Community engineer role requirements
The Ansible community aims to be the most inclusive it can potentially be. Inclusion encompass several areas, one of them being offering tools and resources that are usable for people of all abilities.
As such we aim to offer a documentation that is accessible to as many people as we can. Accessibility is not an after thought but something that needs to come first as we design and write our documentation.
This issue is not a one-actionable item, but aim to list the issues we need to get done before being able to label ourselves as providing an accessible documentation
Plan of actions:
Andrei to link his Matrix and IRC accounts
Zuul configuration repo was moved to https://github.com/ansible/zuul-config half a year ago.
The process of adding collection for auto-publishing by Zuul has changed.
Update the PR2 section of README to reflect the following comment by goneri:
Q: one more question https://github.com/ansible/zuul-config/issues/425
A: It's true if your project the following rules:
https://github.com/ansible/zuul-config/blob/master/zuul.d/projects.yaml#L4-L6
https://github.com/ansible/zuul-config/blob/master/zuul.d/projects.yaml#L20-L23
Q: so the second rule says that all collections under ansible-collections which names start with community* are published when tags are added, correct?
A: Yes, IF you project name starts with ansible-collections/community.
Scenario guides that are specific to a collection should no longer be in the ansible/ansible repository. Open issues on the following collection repos to request they move their guides. Point to the following in each issue on how to do this:
Where are we currently at with accessibility ?
Goal of this issue is to audit our current accessibility forces and gaps. What is it we are doing good and we should keep doing as well as what can we improve on and leverage #41 findings to implement
Expected Results
The description of the current state of our documentation accessibility wise. The good and the bad. So we have a clear idea of where we are at and can proceed with improvement.
Tidy up in https://github.com/ansible-collections/overview/ repository (issues/PRs)
Create a new collection community.arduino under the ansible-collections org and guide maintainers about further actions
ansible/community#587
Collection request checklist under the ansible-collections org:
write at leastThe Ansible community aims to be a healthy, inclusive, new-comer friendly, long live community. A community is made of people, people come, join a community, contribute / participate and eventually move on as their lives permit.
The Ansible community is always looking for new contributors to bring their contributions to the Ansible journey.
This issue is not a one-actionable item, but aim to list the issues we need to go through to go and capture new contributors
Plan of action:
Accessibility is important. Once we improve how accessible our documentation is, we should be proud of it and have a dedicated page in our documentation to talk about it. Why we care, what we do to ensure continuous accessibility, etc...
Expected Results
A page in docs.ansible.com that explains our position and practices around accessibility
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.