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

Announcement: Website restored #2

Open
waldyrious opened this issue Oct 7, 2023 · 3 comments
Open

Announcement: Website restored #2

waldyrious opened this issue Oct 7, 2023 · 3 comments

Comments

@waldyrious
Copy link
Owner

I noticed in a couple conversations in the original repository that the original site has been taken over (snwh#74), and various previous forks (snwh#41) are no longer accessible.

Since the project is a Jekyll site, I thought it might be straightforward to simply fork the repo and set up deployment via GitHub Pages. In reality I ended up having to do a few adjustments to make the links and image URLs continue to work under a different domain (0b07dcf, 374e084), as well as modify how categories and tags are listed (5ddbafe) but overall the site is now back online and functioning pretty much as it did before. Check it out at https://waldyrious.github.io/computefreely/.

With this setup now working and sourced directly from this GitHub repository, instead of simply having a static archive of the original site, I decided to experiment with accepting contributions and updates (55b1349). Hence I'm inviting the contributors to the original project, as well as participants in the issue tracker, to consider contributing to this renewal, which at least should remain live as long as GitHub Pages is available and free.

cc: @rugk, @luke2m, @danarel, @CaKrome, @Justinzobel, @pr0way, @mestaritonttu, @cassidyjames, @jrr.

By the way: @snwh, I noticed that you archived the original repository just a few days ago (3 Oct 2023). If you would prefer, I'd be happy to contribute my updates as a PR and help maintain the original repo if you unarchive it. Otherwise, let me know if you have any requests or recommendations about how the fork is currently set up and/or should be carried moving forward.

@snwh
Copy link

snwh commented Oct 30, 2023

I archived it to stop issue reports as well as to signal that I have no time or intention of picking it back up especially since I didn't notice the domain expiring. So, you have my blessing to do whatever you wish with the fork.

@waldyrious
Copy link
Owner Author

Cool, thanks for confirming! I will transfer this repo to an organization and add the people mentioned above (and you) as members. Cheers :)

@waldyrious
Copy link
Owner Author

Quick update: I will make some additional quick cleanup/background changes before setting up the organization. One such change was the renaming of the primary branch from master to main, which I did just now. Anyone who's got a local clone of this repository should update their clones by running the following commands:

git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

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

2 participants