Mario Lenz

> 1. Always add the `SPDX-License-Identifier:` directly after the existing license identifier, as in: > ``` > # Copyright: (c) 2022, ... > # GNU General Public License v3.0+ (see...

@felixfontein Just because the Core team doesn't want to follow this proposal doesn't mean we can't make this a recommendation for collections, does it? I think it's a good proposal...

I think we should close this issue since it's only an announcement. @Andersson007 @felixfontein Feel free to re-open it again if you think I've been wrong doing this.

> We want it to show up at the top of the issue queue I think. It's already pinned, but it's good to have it show both in the issue...

@cidrblock Please close this issue if done, or open a new forum topic and then close the issue with a pointer to the new discussion: [Community-topics: Archiving the repo](https://forum.ansible.com/t/4990/8)

@gotmax23 Please close this issue if done, or open a new forum topic and then close the issue with a pointer to the new discussion: [Community-topics: Archiving the repo](https://forum.ansible.com/t/4990/8)

@felixfontein Please close this issue if done, or open a new forum topic and then close the issue with a pointer to the new discussion: [Community-topics: Archiving the repo](https://forum.ansible.com/t/4990/8)

I think this is a good idea. I also think that using `_` as a prefix for private modules makes sense. Most collections are implemented in Python, and there a...

@felixfontein Please close this issue if done, or open a new forum topic and then close the issue with a pointer to the new discussion: [Community-topics: Archiving the repo](https://forum.ansible.com/t/4990/8)

Sounds reasonable. But I have a question about this: > 2. Give all collections that fail this some time to fix it. If they don't, say, in two months, let's...