Milestone cycles:

Cycle 1: 7 July
Cycle 2: 28 July
Cycle 3: 18 August

--- Main focus ---

1. Token permissions to enable control of community smart contracts

• Before a community founder can use any of the community token admin functionality, they first have to deploy Owner and Token Master contracts.
• This work involves: new empty state screen for Mint and Airdrop tokens (before current empty state screen is revealed), new flow for deploying the community's Owner and Token Master contracts in a single step, a fixed uneditable permission giving anybody who holds the Token Master token admin rights for the community should be automatically created.
• Only the holder of the single Owner token can access the Token Master airdrop, remote destruct, and view holders functions. Anybody who holds the Token Master token can access all token admin options, excluding those related to the Token Master token itself, as well as being and Admin of the community.
• This will all be explained in more detail in the designs.

Backend Epic: #11249

2. Update Community Admin home screen inc control node transfer and associated dialogues

• Remove ability for a Owner to leave a community on the computer that's running as that community's control node
• Community Admin home screen cleanup (inc. adding at least one of the three graphs, whichever is easiest to implement).
  • Graph issue: #11152
  • Community overview: #11278

3. Ability for user to select & manage accounts shared with each community control node

• This item is quite a bit of work
• Touches Community settings, as well as all of the community join flows
• Backend issues:
  • Join API: #11154
  • Edit API: #11153

4. Encryption for token gated channels that are inside Open (not token gated) communities
#10998

5. Final screens and bits and bobs needed prior to public beta

• Modal that's shown every time after login, reminding user's that Status Desktop is in Beta #11044
• The bug with 'requests to join' a community not constantly arriving, or sometimes arriving after a delay, must be fixed. #8264
• Anything that didn't get completed in 0.13 related to new share URL format
• All the outstanding bugs and small items that got pushed into the 0.14 milestone.

--- Things that we SHOULD NOT work on during the 0.14 cycle ---

• Messaging and UI teams shouldn't work on perf. in 0.14 (but Wallet team should!)
• Anything big mutual contacts related, other than fixing small bugs we find like #10497 #10498 #11120 #11121 (hopefully this functionality working good enough now!)

--- Wallet Team ---

1. Finish any outstanding work related to Activity screens (top priority - aim to have complete by July 14th)

2. Updated Wallet Settings screens UI inc. account syncing functionality Synced information should immediately be reflected in the UI after it is received (sometimes synced info is currently only displayed after the next app restart, this needs to be fixed)

3. Wallet performance and memory consumption optimisations

4. Fix bugs, clean up loose ends (to get things in a good state before the work on the Mobile wallet starts)