📢 Moving to a dedicated org - github.com/github-aws-runners 📢

[npalm]

🚀 Big News! terraform-aws-github-runner is Moving! (January 10th, 2025) 🚀

TL;DR

• 📢 We're moving terraform-aws-github-runner to a new organization https://github.com/github-aws-runners in January to foster growth and community ownership!
• 🎉 Join us on our new Discord server for discussions and updates.
• 📅 Moving on January 10th, 2025

👋 Hey everyone,

We've got some exciting news to share about the terraform-aws-github-runner project! To help it grow and better serve the community, we're giving it a new home. 🏠 In January, we'll be moving the repository from the Philips-labs organization to its own dedicated organization on GitHub.

Why are we doing this? 🤔

• More visibility and focus:  A dedicated organization will give the project more room to breathe and make it easier for new users and contributors to find and get involved. 🔎
• Growing the team: We want to expand our maintainer team with talented folks like you! This move will help us bring in more people with diverse skills and perspectives. 🧑‍💻👩‍💻
• Better collaboration and faster development: A bigger community means more hands on deck! We expect more contributions, quicker reviews of pull requests, and a faster release cycle. 🤝🚀
• Community ownership: We believe this move will give the community a greater sense of ownership and encourage even more collaboration. 🤝

What's changing for you? 🔄

• From January onwards, you'll find the updated repository at https://github.com/github-aws-runners/terraform-aws-github-runner. Currently we have forked the repository as place holder. 🗓️
• No worries about existing setups! We'll keep a copy of the repository at the original location (philips-labs/terraform-aws-github-runner) with a copy of the latest release before the move, so your current projects won't be affected. 🍴

Governance and Maintainers 🧑‍⚖️

The current maintainer team will continue to guide the project in the new organization. We're committed to open governance and are excited to expand the maintainer team with clear processes for new members to join.

Join us on Discord! 🎉

We're also moving our community discussions from Slack to Discord! Join our dedicated Discord server to connect with other users, contributors, and maintainers, get help, share ideas, and stay up-to-date. 🎧

We're really looking forward to this new chapter for terraform-aws-github-runner and all the possibilities it opens up. Join us on this journey! More updates coming soon. 🚀

Want to get involved? 🙌

• Interested in becoming a maintainer? Get in touch! 🙋‍♀️🙋‍♂️
• Help spread the word! Share this announcement with your network and help us build an even stronger community. 📢

Thanks for your support! 🙏

Niek Palm

[imphil]

No worries about existing setups! We'll keep a copy of the repository at the original location (philips-labs/terraform-aws-github-runner) with a copy of the latest release before the move, so your current projects won't be affected. 🍴

I don't know if you considered it, but: if you move the repository (using the GitHub transfer repository feature), GitHub will have redirects in place from the old to the new location for all services, including git clones, release downloads, etc.

[npalm]

No worries about existing setups! We'll keep a copy of the repository at the original location (philips-labs/terraform-aws-github-runner) with a copy of the latest release before the move, so your current projects won't be affected. 🍴

I don't know if you considered it, but: if you move the repository (using the GitHub transfer repository feature), GitHub will have redirects in place from the old to the new location for all services, including git clones, release downloads, etc.

Thanks for pointing out. We will use thte transfer repo utility. But due to supply chain security we think it is better to avoid any automatic redirect. For that reason we will move (transfer) ther repo will all history. Next create a copy on the old place, including all releases. This should avoid breakiing any depenency on this repo. But also ensure from a supply chain security we keep it safe and avoid any redirects (now and in the future).