# Move to OWF Checklist :::warning A lot of the tasks listed below are about renaming and removing the Aries brand. *Agent Framework JavaScript* was originally intended as a working title. In order to move forward quickly and avoid confusion, we need to decide on a name ASAP. ::: ## Technical ### AFJ main - [x] Migrate repo to OWF org - [ ] Update README(s) -- replace/remove all mentions of `aries` - [ ] Update repo tags -- replace/remove all mentions of `aries` - [ ] Verify CI pipeline is working as expected - [ ] Update CD pipeline to release packages under the new NPM namespace - [ ] Deprecate latest package versions under the old NPM namespace -- include message referring to the new namespace ### AFJ extensions - [x] Migrate repo to OWF org - [ ] Update README(s) -- replace/remove all mentions of `aries` - [ ] Update repo tags -- replace/remove all mentions of `aries` - [ ] Verify CI pipeline is working as expected - [ ] Update CD pipeline to release packages under the new NPM namespace - [ ] Deprecate latest package versions under the old NPM namespace -- include message referring to the new namespace ### AFJ docs - [x] Migrate repo to OWF org - opened https://github.com/openwallet-foundation/tac/issues/88 - [ ] Update README(s) -- replace/remove all mentions of `aries` - [ ] Update docs -- replace/remove all mentions of `aries` - [ ] Update repo tags -- replace/remove all mentions of `aries` - [ ] Verify CI is working as expected - [ ] Decide on new hosting location (we can't use https://aries.js.org anymore) - [ ] Set up new hosting location - [ ] Update CD pipeline to deploy to new location ## GitHub projects - [ ] Migrate GitHub projects board - Likely not possible. If not, we should manually replicate all active project boards. ## Community communication :::warning To avoid confusion, the tasks below should only be picked up once we have total clarity for ourselves. ::: ### General announcements - [ ] Announce finalization of the move in Identosphere - [x] Announce finalization of the move in HL mailing list - [ ] Announce finalization of the move on social platforms - Including this because I want to do this from our Animo accounts, but I think more === better. Feel free to join the party with your personal and/or company accounts as well. **We should coördinate on timing**. ### Bifold maintainers - [x] Inform them about the finalization of the move to OWF - [ ] Inquire about their plans (are they planning to move as well?) ### HL Discord - [ ] Announce finalization of the move in HL `#aries-framework` Discord channel - [ ] Deprecate the channel - [ ] Refer to new (OWF) channel - [ ] Announce finalization of the move in HL `#aries` Discord channel - [ ] Announce finalization of the move in HL `#aca-py` Discord channel - [ ] Announce finalization of the move in HL `#bifold` Discord channel ### Working group stuff - [ ] Working group calls - [x] Inform about OWF's procedures around WG calls - [ ] Ensure reoccurring Zoom calls are set up - [ ] Ensure maintainers have hosting permissions - We're kind of winging the WG calls lately. This is a good opportunity to create more structure. - [ ] Decide and set up Confluence alternative - Check what OWF has to offer - What to do with old meeting notes? - If not migrated, we should probably create a backup - [ ] Decide on what to do with old meeting recordings - Recent recordings are posted under the HL YouTube account. This may confuse future viewers. Is it worth appending a note about the move to the video descriptions?