...
Plan to Create the Cacti Repository and Migrate (Import) Weaver Into Cacti
Port hyperledgerPort hyperledger/cactus to cactus to hyperledger/cacti, either by:
Renaming the project repository:
Forking
cacti/main
fromcactus
/main
and archivingcactus
/main
done
cactus to cactii
Transfer (move)
hyperledger-labs/weaver-dlt-interoperability
tohyperledger
/weaver-dlt-interoperability
Create a branch
hyperledger
/weaver-dlt-interoperability/cacti-port
fromhyperledger
/weaver-dlt-interoperability
/main
In the branch
weaver-dlt-interoperability/cacti-port
:Create a subfolder in the root folder named
weaver
Move all other files and folders in the root folder to
weaver
Merge
hyperledger
/weaver-dlt-interoperability/cacti-port
intohyperledger/cacti
/main
as follows: In the same location in the file system, clone the following:Clone the following
hyperledger
/weaver-dlt-interoperability
hyperledger/cacti
and run:git remote add weaver-dlt-interoperability ../hyperledger/weaver-dlt-interoperability
git fetch weaver-dlt-interoperability
git merge weaver-dlt-interoperability/cacti-port --allow-unrelated-histories
In the same location in the file system, clone the following:
Navigate to the clone of
hyperledger/cacti
and run:
Transfer all relevant issues from
hyperledger
/weaver-dlt-interoperability
tohyperledger/cacti
:Navigate to the
hyperledger
/weaver-dlt-interoperability
Github repo in a web browserTransfer each issue to
hyperledger/cacti
according to the instructions in https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository
Transfer (move)
hyperledger
/weaver-dlt-interoperability
back tohyperledger-labs/weaver-dlt-interoperability
(Future) Archive
hyperledger-labs/weaver-dlt-interoperability
cactus
to cacti
, orhyperledger/cacti
...
- Project page update on Hyperledger site (Hyperledger staff)
- https://www.hyperledger.org/use/cactus Hyperledger top page (including Cactus GitHub URL)
- Rename GitHub repository
- GitHub allows redirection from the old URL to the new one. Note however: This will only work as long as there isn't another project later created with the same (old) project name.
- Also note that contributors will receive a warning message from git prompting them to update their git remote URLs from the old the the new one. This is something that all contributors have to address locally on their own machines.
- Mailing list (Hyperledger staff)
- Note: mailing lists cannot be renamed. Instead a brand new list will have to be created by Hyperledger staff and then previous subscribers will have to subscribe to that one again.
- Permissions will have to be set up from scratch (e.g. maintainers to be mods of the list, etc.)
- Chat rooms (Discord)
- Wiki pages (Hyperledger staff/project maintainers)