<aside> ℹ️ https://github.com/threshold-network/pm/issues/35

• We have seen that some environments definitely need some manual approval for critical actions: </aside>

Issue 35 Outstanding Questions

1. who are the people capable of approving the deployment of changes to the website?
2. how is the approval process managed? Are there several people with the ability to manage changes? that's interesting to understand in case we need to rush a change
3. who is the owner of this process? e.g., can grant the permissions to other team members to be able to manage approvals / changes to the website?
4. is there a similar process for changes to the dashboard?
5. How do we unify PR review patterns (eg what needs manual QA?)?

• How do we Approve + merge authority across other repos?
• How do we unify Codeowners?

Next steps from mtg on Dec 4, 2023:

• Immediate: Add 2 devs from NuCypher to approve builds
  • Scope: dashboard + website
  • Who from Nu: MacLane and David
  • Target Date: Dec 6, 2023
  • TODO: Lukasz to add
• Async collab on PR review patterns (include Michal from Thesis)
  • Team: Lukasz, Michal, David
  • Consider: website, dApp, staking front ends…
  • Deliverable: Written doc outlining the PR review process
  • Target date: ???
  • TODO: Initiating the async collab between Lukasz, Michal, and David as a DAO
  • Document → Shared PR Review Processes
• Codeowners:
  • All repos have proper code owners and they are updated
  • E.g. Solidity contracts: Update or not?
    • Nu: VT?, David N, Piotr
    • Should we update from Piotr to Lukasz?
      • TODO: @David Núñez Add Lukasz to Codeowners, keep Piotr
  • Should we apply the same ownership structure to other repos?
    • E.g. Token Dashboard code owner is Thesis
    • TODO: Lukasz to add David N into the Token Dashboard CI file
• The multisig for Sepolia testnet, facilitates tests, deployment, assets
  • This is already working, we do need to document it for broader accessibility
  • Issues PM repo #34,35
  • Discuss: where is a good place for his documentation?
  • TODO: @David Núñez to document the current state and share with Thesis
• Arj: Help with bundling issue
  • TODO: Michal to help @James by end of week
• On call rotation across DAO
  • Nu does not have the same process
  • TODO: @Engin Erdogan to share Thesis on-call rotation process with NuCypher
• dApp on IPFS
  • What are things we need to do?
  • What is the roadmap?
  • TODO: @Luna5 to create a shared document for brainstorming on this → 2023-12-04 Product Sync
    • Document → dApps on IPFS