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

nornir.tech will expire on May 16th #988

Open
dbarrosop opened this issue Feb 20, 2025 · 5 comments
Open

nornir.tech will expire on May 16th #988

dbarrosop opened this issue Feb 20, 2025 · 5 comments

Comments

@dbarrosop
Copy link
Contributor

dbarrosop commented Feb 20, 2025

Hello,
this is not really an issue but I wanted to create one for awareness in the community (or at least those watching the repo).

On May 16th the domain nornir.tech will expire and currently I have no intentions of renewing them. The only implication is that https://nornir.tech will stop working. We have a few solutions here:

  1. Abandon the website. The only thing interesting there is https://nornir.tech/nornir/plugins/ and that can easily be added to nornir's README.md
  2. Change the domain to the github one (we host this on github pages to something like https://nornir.github.io)
  3. Someone covers renewal costs and we postpone this decision until next expiration date. Current renewal costs are 62,98$/year I think.

Anyway, if I don't hear anything or people don't have strong opinions I will probably go with 1 as it's the simplest long term. The only downside to abandoning the domain will be that it will most certainly taken over by some shady website with AI-stolen-and-regurgitated content like it happened with napalm-automation's website.

Regards

@dgarros
Copy link
Contributor

dgarros commented Feb 20, 2025

@dbarrosop I'm happy to cover the cost for the dns, I was looking for ways to better support some projects from the community so it's a (small) step in that direction.

@dbarrosop
Copy link
Contributor Author

Thanks! Honestly, I think it's more about the usefulness of it than the money itself so I'd rather focus on what we think is the best course of action first.

I would personally not miss the website regardless of if we use nornir.tech or the github domain. Other than the occasional plugin being added to the list it's been mostly inactive/abandoned and that plugin list can easily be added to nornir's repo. The only concern will be the AI-generated-crap that will surely take over the site but that happened with nornir-automation and it wasn't a huge deal AFAIK so my vote would be to just scrap the website and move the plugins to the nornir's repo.

@dgarros
Copy link
Contributor

dgarros commented Feb 20, 2025

my vote would be to just scrap the website and move the plugins to the nornir's repo. [ ... ]
The only concern will be the AI-generated-crap that will surely take over the site

I agree, I was also thinking about that
To help with the migration, it might be good to renew the domain this time and add a page to indicate that the site has moved to a new address.

@ubaumann
Copy link
Contributor

Long term moving away from the domain makes sense for me too.
Hosting the page on nornir-automation.github.io would be easy but I see the point of just have a README.

For a long time now, I wanted to create a PoC mkdocs project using the multirepo plugin to include all the mkdocs documentation from the plugins. The goal is to have one webpage dynamically include the plugin documentation. But that's providing many challenges and a lot of work.

@dbarrosop
Copy link
Contributor Author

dbarrosop commented Feb 20, 2025

it might be good to renew the domain this time and add a page to indicate that the site has moved to a new address.

we still have (almost) 3 months so if we want to do this we could add a warning that we are phasing out the website and that they will be redirected to the README.md of the project in 10s. I don't think the content or the importance of the website is big enough to warrant a year long deprecation process :P

The goal is to have one webpage dynamically include the plugin documentation

That's really cool. However, that's probably orthogonal to this issue as that's a completely new thing that could be hosted on the github pages domain. By the way, you may want to "standardize" the docs format for them to be included in the central repo but I suspect you are going to have a lot of fun (not) both in the short term implementing and in the long term dealing with issues XD

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

3 participants