Redirection to CLOVER 5

[BenWinchester]

Notes

This issue is a duplicate of Redirection to CLOVER 5 #165

Issue

Academic researchers based at other institutions, i.e., outside of the @CLOVER-energy/clover-development-team remain unaware of the migration from CLOVER 4.0 to CLOVER 5.0. As a result, users are asking for help and information on the CLOVER 4.0 repository which is not being maintained.

Proposal

Provide a link in the CLOVER 4.0 repo directing users to CLOVER 5.0

The alternatives may be

• archiving the CLOVER 4.0 repository;
• business as usual.

[BenWinchester]

@phil-sandwell ,

I think there are just two more things we should do to make it clear to users. (NOTE: As part of this review, several steps from the guide here have been taken.)

• [ ] Change the GitHub description. This is often the first thing people see for the repository, and the first line that people will see if looking at the repository in the Organization view. The most important thing to do is to add the word DEPRECATED at the front of the description. This clearly marks it will not be updated. You can also add an emoji to it. ⛔️ DEPRECATED <former description> makes it pop out a bit more.
• [ ] Add GitHub topics: deprecated, obselete, and archived are all good ones.