Revive Cornucopia

[LouisGariepy]

Top level tracking issue for merging Clorinde back into Cornucopia. See clorinde#252 for context.

Permissions

• Invite @beanpuppy as org owner on cornucopia-rs
• Invite @djc as org member on cornucopia-rs
• Grant @djc admin access on the cornucopia repo
• Add @beanpuppy as crates.io owner
• Add @djc as crates.io owner

Code

• Decide on how to merge Clorinde
• Rename any Clorinde-specific package names/references back to Cornucopia
• Merge Clorinde changes into Cornucopia

CICD and Infra

• Update GitHub Actions workflows as needed
• Verify crates.io publishing works

Repo

• Migrate Clorinde issues
• Close outdated Cornucopia issues

Documentation and communication

• Update README
• Update CHANGELOG with merged changes
• Update website (and investigate moving out of netlify to a platform that has free multi-ownership)
• Add migration guide for Cornucopia 1.0
• Decide the new versioning
• Publish new release to crates.io
• Notify users (add notice to the Clorinde repo, reddit post, etc.)

Licenses and contributing

• Attribute Clorinde (and Cornucopia) contributors
• Address the MIT copyright holder change

Post-transition tasks

• Resolve RustSec unmaintained advisory
• Decide what to do with the Clorinde repo

[LouisGariepy]

This is just a provisional list, @beanpuppy @djc feel free to update as needed.

[beanpuppy]

This looks good to me @LouisGariepy, can't think of anything else that needs to be done right now.

Decide on merge strategy

I think it easiest to merge Clorinde into a branch here and do all the work there ?

Update website (and investigate moving out of netlify to a platform that has free multi-ownership)

The obvious answer to me here is GitHub Pages, it should be a simple swap over.

[LouisGariepy]

@beanpuppy #271 🥳 I'd appreciate it if you could do a quick review, thanks!

[dlight]

Maybe there some tooling that could be used to move/copy Github issues from Clorinde back into this repo? Maybe some obscure Github feature, a bot, or something?

Another thing to think is whether the issues in this repo are still applicable to the Clorinde codebase

[LouisGariepy]

Hey @dlight good to see you

Maybe there some tooling that could be used to move/copy Github issues from Clorinde back into this repo? Maybe some obscure Github feature, a bot, or something?

I believe GitHub has a built-in feature to transfer issues between repos as long as you have write permissions on both. Only transferring open issues should be sufficient since closed issues will still be findable through the changelog and commit history (which have both been preserved). Maybe @beanpuppy could look into this since I don't have permissions on the Clorinde repo.

Another thing to think is whether the issues in this repo are still applicable to the Clorinde codebase

Yeah, once we're satisfied with the state of the merge back, I'll cross reference with the changelog and clorinde issues and close the ones that need to be closed.

[dlight]

Oh nice. Using the web UI it appears to allow transferring one by one, but since one can also transfer with the CLI, a script could do a bulk transfer (and easily transfer even the closed issues if desired)

[beanpuppy]

Hey @LouisGariepy I just remembered the Discord server exists, do you have any plans for it ?

[LouisGariepy]

I'd like to keep the Discord server open since it's a good place to ask informal/repetitive questions and for internal dev discussions, but I don't have enough time to properly moderate the server at the moment. If you would like, I can give you admin rights to manage the server just let me know 😄

Once we release 1.0 (just need to finish sorting out all the issues and PRs, should be done today), we can make an announcement in the server too.

[LouisGariepy]

@dlight After reading the docs

You can only transfer issues between repositories owned by the same user or organization account. A private repository issue cannot be transferred to a public repository.

So unfortunately it doesn't seem like there would be a clean way to transfer the issues.

@beanpuppy do you have an opinion on this? Otherwise I'll just go ahead and manually copy Clorinde's open issues (with links back to Clorinde).

[beanpuppy]

I'd like to keep the Discord server open since it's a good place to ask informal/repetitive questions and for internal dev discussions, but I don't have enough time to properly moderate the server at the moment. If you would like, I can give you admin rights to manage the server just let me know 😄

Yeah if you think you'll need it, I'm happy to help out.

@beanpuppy do you have an opinion on this? Otherwise I'll just go ahead and manually copy Clorinde's open issues (with links back to Clorinde).

I could consider moving the Clorinde repo here, doing all the transfers, then moving it back but I have no idea if that would break anything 😅. Since there are only 13 issues I think doing it manually would be safer and shouldn't take that long.