Agenda
- Follow up: DAO ownership of website and dashboard
- shared dev process
- OR status/ETA
Discussion
Previous product sync notes: ‣
Document outlining the shared dev processes: Increase diversity for dashboard and website deployment reviewers
Follow up: DAO ownership of website and dashboard - will be discussed at the IG call today
Shared dev process:
- For the dashboard -
- First steps to unblock the development: add 2 Nu members as PR approvers for the Threshold GitHub repo (Dnunez and Maclane)
- Definite solution: Migrate to an infrastructure not controlled by Keep
- Criteria for good use of shared resources: async discussion with Michal
- Unify PR review shared process -
- We need joined practices for PR review
- For Keep Lukasz and Michal will give the review / approve
- For NuCypher David will give the review / approve
- Specifics:
- For TACo part of the dash - Nu don’t need to wait for approval from Keep and likewise for Keep
- For other delicate parts - it is necessary to wait on review and approval from each other
- GitHub Issues 666 & 678 need the attention and review from Lukasz and Michal.
- Bundling issue - NU want to announce this week that they can spin up nodes
- James needs help: when wanting to bundle up app with the dashboard - it is not possible to have them separate - URGENT 1 / 2 days - Michal is the key person to help. Issue 678.
- For the codeowners -
- All repos have proper code owners and are updated.
- Specific example of codeowners: Solidity contracts - Nu: Vicky and David, - Keep: Piotr. Token dashboard: currently owned by Thesis.
- We need to: make sure that the current codeowners are updated, and make sure there is people from both NuCypher and Keep as codewoners for each repo.
- The structure of several repos is different, so adding codeowners can be trickier.
- Specific actions to be taken:
- David will add Lukasz to codeowners for the solidity contracts, Piotr remains as redundancy.
- Token dashboard: to add NuCypher as codeowners, better verify async how to manage the codeowners structures.
- For the testnet assests -
- This is currently working well, NuCypher is offering to share the workload.
- We need to document it better for better visibility and availability. GitHub Issues 34 and 35 at the pm repo. Does this make sense to have at threshold docs?
- NuCypher can initiate the efforts here.
- This will be discussed in a private Keanu thread and keep the conversation open there.
- For emergency response -
- Thesis: on call process to cover for this
- First step: extend to NuCypher. NuCypher doesn’t have similar procedures in place.
- Future: extend to the DAO.
- Keep / Engin will share with NuCypher guidelines of this process - async. Will become a joined process.
- Hosted spaces to IPFS -
- Pushing all the assets to shared repos
- Becoming decentralized is top priority. This is a conversation initiated here but will be discussed async:
- What would be the roadmap
- Shared document to start thinking about this process - Luna5
Optimistic Redemptions Status / ETA:
- Technical work has started