Future of the Ansible Community package

I’m not sure what you mean. Only include collections in the community namespace or only include collections that have their repos in ansible-collections? I don’t think including only collections in the community namespace would work, since for example community.aws depends on amazon.aws. I think this would be a problem.

I think there should have to be at least some to tests to make sure the package is not completely broken.

I’m not backing you’re suggestion, but it looks interesting. At least something that’s worth thinking about.

not suggesting 0 tests, docs should build, pkg should build, but not extensive tests on code quality/linting/etc
This does not mean code is not tested, I expect each collection repo to do so, just that you can skip most of it when doing the full package build.

and dependencies would get drawn in, just need to make sure people don’t go crazy there

One of the replies I saw about this notion (can’t recall if it’s here or someplace else) was that there is some assumed quality in the ansible package. So using something included is considered better than just finding something on Galaxy and hoping for the best so to speak. That I think was part of the ‘badge’ idea - to review and give community ‘seal of approval’ for collections that jump through what is today the inclusion checklist for the package.

1 Like

Here’s a blog post (“a love letter”) by David on the Ansible package: Simplicity is a feature | ARA Records Ansible | ara.recordsansible.org

7 Likes

After thinking about it and reading a lot of people’s opinions and POV’s on the matter, I think I would like the ACP itself to continue as it is. (option 3 in the poll).

I also want @Andersson007’s workload to be reduced where inclusions are concerned. (which more or less has been addressed in the other thread).

That said, I think I would like to have another poll weighing in on some of the ideas that came up in this thread and potentially doing them in addition to maintaining the status quo of the ACP.

This obviously would mean more work than less, but not necessarily at the detriment of the inclusion process itself.

Things I would like to vote on:

  1. Including non-ACP collections in docs.ansible.com
  2. A badge/reputation system. This could be something implemented in galaxy.ansible.com, or in docs.ansible.com (especially if 1. was voted in favor of). This system could reflect who (what team) reviewed and approved of the collection’s content. (core-certified, community-certified, etc)
  3. Building smaller pip package derivatives of the ACP in addition to the ACP itself. The overhead of this might be small if these are built adjacent to the ACP in the same CI.
1 Like

the funny thing, this exact discussion was taking place about ‘core time’ when we decided to move to collections to make the maintenance and support a lot easier and clearer. At the time i pointed out that community.general was just reducing and transferring the problem vs actually fully solving it. … well, it did solve it for ‘core’ …

3 Likes

I’ve been a bit underwater this last week, just catching up on my notifications :wink:

I’d be happy to help on this. One of my goals for the year has been to restart the community surveys, but rather than the small quarterly ones we used to do, go for a big one that covers at least a few questions from each part of the ecosystem (skippable of course, for those not using a given project), and then collate the results in a big blog post. I used to do this a shockingly long time ago and it would be nice to do it again.

I see this as a good candidate to add to that, and as a fairly “charged” topic might prompt more people to fill in the rest of the survey :slight_smile:

I will bump this up my todo, and start drawing up a list of questions somewhere that we can work on as a group - those interested can look out for such a topic here in Project Discussions in the near future.

5 Likes

Just to return to this - I was out of action for a good chunk of the last month, which means the survey got pushed back too. I’m still planning it though, and hope to speak to people about possible questions in the next few weeks. I’m gutted I didn’t have it ready for DevConf though.