Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preparing for rusoto.org non-renewal #138

Open
matthewkmayer opened this issue Dec 8, 2020 · 3 comments
Open

Preparing for rusoto.org non-renewal #138

matthewkmayer opened this issue Dec 8, 2020 · 3 comments

Comments

@matthewkmayer
Copy link
Member

Since I'm no longer maintaining Rusoto it's time to figure out what to do with the rusoto.org domain. It expires in November 2021.

Where to keep content

Should we make the current content available somewhere else that doesn't cost money to run? Can we publish this via GitHub Pages? What other options do we have?

What to do with the domain

I'm not planning on renewing the domain. This makes it available for squatters or more nefarious users. How can we address this problem without requiring money from me?

Please post options you can think of. Thanks! ❤️

@xrl
Copy link

xrl commented Dec 8, 2020

Thank you so much for sponsoring the domain, this project would be nowhere without your investment of time and money. The domain helped me understand that this is a big, serious project, so it worked for bringing me in to the mix.

Unless someone is willing to step up and pay the $12/year (or so?) for the domain, then I think it's OK to let it lapse. And it will get squatted and that's just life on the internet.

People will just see this issue and understand. Crates.io and github are good starting points for bringing people in to the mix

Just my two cents. Thanks!

@nilslice
Copy link

Fantastic project, @matthewkmayer, thank you for all your work and support!

I'm happy to take over sponsorship and management of the domain in the near-term. Would rather keep all the links live than comb through all repos and update to another domain.

Ideally AWS would directly support this at some point - but in my experience it takes a long time to get a bigco to handle something like this.

@brainstorm
Copy link

I'd be happy to take over and sponsor this as well if AWS doesn't step up, although there's some internal movement at AWS in the right direction I reckon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants