Maxwell G

Ah, I forgot I opened this. Thanks everyone. I'll close the issue.

> I'm not sure what short string would be the best descriptor. Maybe "Removal in"? Maybe "Scheduled removal"?

Yeah, sphinx is a memory hog, especially when parallelization is enabled and the size/complexity of our docs that @samccann mentioned. You can try exporting `CPUS=1` — or another number that's...

> For the record: I'm not a _new contributor_. I've already contributed: Thank you for your contributions! For now, [the bot](github.com/ansible/ansible-documentation/tree/devel/hacking/pr_labeler) currently only considers issues and PRs made in the...

Thanks!

Please take a look at the outstanding sanity test errors. https://github.com/ansible-community/package-test-results/blob/main/rendered/10.3.0/google.cloud.md contains the results for the latest version of ansible. Note that, if these issues aren't acknowledged within a reasonable...

Any update here? I have started processing Removal from Ansible tickets for the other collections that failed testing.

> Note that, if these issues aren't acknowledged within a reasonable time period, the collection may be subject to [removal from Ansible](https://github.com/ansible-collections/overview/blob/main/removal_from_ansible.rst). https://forum.ansible.com/t/collection-removal-google-cloud/8609 starts the collection removal process

Thanks for the detailed response, @lachmanfrantisek! > Do we know about real projects/people interested in this? Would be nice to see the possible demand before spending the time on this....

A maintainer needs to create the branch, but after that, anyone can theoretically submit a PR against it to make the necessary changes.