Migrating: Doobie

[valencik]

Migration Checklist

Project Submission Issue: #125

For Organization Projects:

• Create a team for the repo with maintainer as team member
• After repo transfer, add repo with write permissions to the created team

For All Projects:

• Add project to the site by adding an entry to the projects.yml file

Announcements

These steps are optional but encouraged.

• Write a blog post announcing the change
• Post to our social channels (Mastodon)

[samspills]

Hey @jatcwang! I'd like to get the ball rolling on the package switch from tpolecat -> typelevel. Step 1 is the repo transfer. If you give me admin access to the doobie repo I can trigger that transfer and then finish setting up the doobie team.

How do you feel about that plan? Would this timing work for you??

[jatcwang]

Thanks @samspills. Currently I believe there's a blocker for repo transfer which is the docs site on https://tpolecat.github.io/doobie/ with many years of links to it so ideally we should setup a redirect to https://typelevel.org/doobie/.

I need to figure that part out and we can proceed with the repo transfer. (I'm not an admin for tpolecat/doobie so will need to ask Rob to set that up)

[armanbilge]

so ideally we should setup a redirect to https://typelevel.org/doobie/

After we move this repo, I think we'll have to setup a doobie repo under tpolecat again that publishes a redirect index.html file to its GH pages branch e.g.

https://github.com/http4s/http4s-jdk-http-client/blob/3bbf3b984d26710b4bfa9c9f6d519d83717e0c5c/index.html

---

I'm not an admin for tpolecat/doobie so will need to ask Rob to set that up

For personal repos I'm not sure if it's possible for anyone besides the owner to admin.

[jatcwang]

Good to know we've done that already thanks @armanbilge. I'm guessing we will need an .index file per existing page since with just index.html at top level will only redirect the homepage I think? Will play around with it

[armanbilge]

I'm guessing we will need an .index file per existing page since with just index.html at top level will only redirect the homepage I think?

Hmm. That would be the best way but annoying to set up.

Alternatively, I think GitHub lets you customize the 404 page. So we could redirect all 404s to the new site, although not to the specific page requested. Edit: well maybe with some JavaScript it could be possible, but not sure.

[jatcwang]

Ok I've tested the docs redirect (Created a redirect html file for every doobie doc page) so we should be sorted on that front.

However, I am thinking of doing another RC release with the current credentials (should hopefully be out in a few weeks). Will reach out once we're ready :) Thanks!

[jatcwang]

Repo transfer is complete and docs redirect are working 👍 Thanks for your help!

Regarding publishing, I'm guessing I can remove github secrets like PGP_PASSPHRASE and publishing should just work by inheriting org secrets?

[samspills]

Regarding publishing, I'm guessing I can remove github secrets like PGP_PASSPHRASE and publishing should just work by inheriting org secrets?

@jatcwang Yup! Just remove all the repo secrets
Edit: actually, I'm not sure if you have permissions to access repo secrets now that it's a Typelevel repo. I can go ahead and remove them