Remove dependencies on me

[cb372]

The fact that #345 took 6 months to get merged makes it pretty clear that I'm a blocker for progress on this project. Let's try to get me out of the critical path:

• sbt-ci-release, so @lewisjkl can perform releases
• publish the microsite as part of the release process, so I don't have to do it from my laptop (here's how I did it for cats-retry: Publish site on release cats-retry#163)
• find a couple more maintainers to help review/approve PRs
• move to a GitHub org

[cb372]

I've made a GH org but I got too scared to press the big red transfer button 😅

I think the only thing it will break will be that the microsite will move from https://cb372.github.io/scalacache to https://scalacache.github.io/scalacache ? After I transfer the repo I can set up a simple gh-pages site at https://cb372.github.io/scalacache to redirect to the new location.

[lewisjkl]

Hey @cb372, are there any of these tasks that I can help out with at all? I am thinking that I will help a PR for making the microsite deployment part of the CI process. Beyond that I can also help looking for more maintainers. I think that getting these items squared away prior to another release of the library probably makes sense. What do you think?

[cb372]

Hello it's me, the ghost of scalacache past! 👻

It's great to see you guys are actively working on the project. Shall I go ahead and transfer the repo to the scalacache org? I've made @lewisjkl an org admin and sent @kubukoz an invite.

[kubukoz]

It'll probably take some work in the microsite settings, so we should probably at least have a branch with these changes before the transfer.

[lewisjkl]

It'll probably take some work in the microsite settings

I've never dealt with a migration of a microsite between orgs like this before. Any ideas on how we can validate that we make the changes appropriately prior to transferring? Or is it just a best-guess kind of thing?

Is there anything we can do to create a redirect or something from the current microsite url to the new one?

Oh and good to hear from you Chris! Hope all is well for you 🙂

[kubukoz]

Or is it just a best-guess kind of thing?

Now you're getting it...

Is there anything we can do to create a redirect or something from the current microsite url to the new one?

I don't know... I just moved a repository between orgs and the old URL started giving 404s soon afterwards. It's possible in plain HTML with no JavaScript: https://gist.github.com/domenic/1f286d415559b56d725bee51a62c24a7, might be worth a try. An alternative could be some JS + a fallback link for those users with JS off.