This repository was archived by the owner on May 14, 2024. It is now read-only.
This repository was archived by the owner on May 14, 2024. It is now read-only.
Closed
Description
Summary
The idea was originally said by @mattclay
We should replace "Changes Impacting collection contributors and maintainers" Issue 45 with a dedicated repository (for example, we could create ansible-collections/changes_impacting_maintainers).
Issue: Now it's a problem to find anything in the issue (even recent announcements) as it's hard to unfold 460 hidden items to find important information. Things get lost there quickly...
Solution:
- Using a repository instead.
- Announcements will be done as separate issues.
Benefits:
- Possibility to ask questions in issues, discuss things, add clarifications.
- Easy tracking maintainers who are subscribed / not subscribed (to remind them if we see that they don't consider the changes in their collections
- Easy linking related PRs / issues in collection repos (now this causes a need to unfold 460 hidden items in the single issue).
Questions that can be asked:
- What about changes that aren't (only) about collections?
- Currently Issue 45 is in
ansible-collections/overview. - At least recently I can see things that relate to collections only. I believe we should keep the focus.
- If there's a need for Issue of broader scope than Changes Impacting, it would already exist.
- We have Bullhorn. We recommend maintainers to subscribe to it. As far as I noticed, important changes of different areas (and global ones) are announced via the newsletter.
- Bullhorn + the repo is a good combination for collection contributors and maintainers. For others, Bullhorn + corresponding repos.
Conclusion:
I suggest creating the repo ansible-collections/changes_impacting_maintainers that will keep focusing on collection contributors and maintainers and close Issue 45.