search

ansible / docsite

Static HTML and assets for docs.ansible.com
18 stars 15 forks source link

Add antsibull-docs and antsibull-changelog to ecosystem #223

Closed felixfontein closed 5 months ago

oraNod commented 8 months ago

Thanks for adding this @felixfontein :rocket: It's great to see these tools getting included in the ecosystem!

This PR is very welcome. My instinct is to just approve and merge this but I feel like doing so might be jumping the gun a little, considering the need for clear governance rules. For that reason I would ask @GregSutcliffe for his guidance on defining "table stakes" before we proceed. Nothing major, let's just have a chat and try to reach consensus on baselines for projects in the ecosystem. For instance, projects should have certain types of licensing, code of conduct, some minimum level of adoption / usage in the community.

The intention is to do things in a consistent, fair, and ordered way. This ecosystem page is going to evolve over time and need maintenance so it is with that in mind that I feel we should hash out some process a bit more before we proceed with merging these changes. I hope you find my intentions reasonable.

I also look forward to hearing any thoughts you or anyone else has on what those table stakes might be. Cheers!

gotmax23 commented 8 months ago

I recall discussing the "what should be on the list" issue sometime last year, but I don't remember where or what the consensus was. I do remember general agreement that anything in one of the ansible/ansible-community can be included. @samccann might know better than me :).

samccann commented 8 months ago

Alas, I don't recall much of the earlier conversations, but I think there are two main points to consider:

On the second one, I know we've held off on adding ara to the ecosystem docs page and I think that repo also exists under the ansible-community github Org. While what it does could be vastly different from what antsibull-docs etc do, it seems they are in a similar category of completely-community-owned projects.

On the third one - antsibull docs etc are value-add tools for other Ansible projects. That's a bit of a new category compared to what exists on the ecosystem page today. We also have a couple of other items, like the onboarding toolkit and meetup toolkit. Where do we put them wrt ecosystem page (or some other community page?).
...maybe it all should be a forum post or something?

oraNod commented 7 months ago

@felixfontein and @gotmax23 Hi, I've been waiting to kick off the conversation on "table stakes" for the ecosystem page. I've been hoping that we could move things to the new website and that it would launch soon. However I think the date has been pushed out and maybe we shouldn't hold off any longer. Thanks for the patience.

You can find the forum post to define table stakes here: https://forum.ansible.com/t/table-stakes-for-including-projects-on-the-ecosystem-page/4341

oraNod commented 5 months ago

@felixfontein Hi, we've been discussing it and have come to the decision that it's probably not necessary to have this docsite ecosystem page now that the new ansible.com has launched with its own ecosystem. As outlined in the forum post, I'm updating this docsite ecosystem page to point to that new ansible.com page and the Awesome Ansible list.

There are a couple of things going on. The broader issue of governance is going to take a while and this is a smaller piece that fits into that. Another thing is that we probably don't really need two ecosystem pages as well as the Awesome Ansible list. I was hoping to be able to fully replace the docsite ecosystem with the one on the main domain (ansible.com/ecosystem). I guess that has still happened but no one from the community team has have any permissions on that repo or any control over it. With that in mind, it seems more straightforward to just point to those two places (ansible.com/ecosystem and the Awesome Ansible list) from here (the docsite ecosystem).

Hopefully what we're doing here makes sense. I do want to say that I acknowledge the fact this isn't the outcome you probably wanted. And my personal opinion is that we should definitely include these projects as part of the ecosystem because they are essential parts of the toolchain.

For now, how about we add these into the Awesome Ansible list? I'd be more than willing to help clean that up and make it a bit fancier. In fact, I'm planning to add some work items to the community team sprint to focus on that.

If you do want to, it's certainly possible to send a PR to the new ansible.com source repo and request that the projects get added to the ecosystem: https://github.com/ansible/ansible-collaborative While I don't have merge rights or any special influence there I'd be willing to chime in and voice my thoughts on why these projects should be included there. Please just let me know what you think.

Thanks again for everything @felixfontein