Trevor Clarke

@starpause this is definitely something that needs consideration. Here's the current new spec: https://github.com/near-daos/sputnik-dao-contract/wiki/%5BDRAFT%5D-DAO-Data-Model-Architectures#dao-proposal-data I had originally added permissions & voting requirements at the proposal level - but here's the...

I believe this issue to be lack of documentation - Goal would be to document methods & setup for Sputnik Staking contracts.

## Deliverable: CI/CD Based on the repo setup, i believe the build & releases can be automated based on a solid git flow & actions. This would allow a standardized...

@zavodil will need to review more in depth, but I believe this is actually duplicate logic. Maybe @constantindogaru has more insights, but the DAO policy configures a `proposal_period` that proposals...

@ctindogaru docs look good - going to move them into a scripts folder that can be used as tools during the upgrade process. Also see: https://github.com/near-daos/sputnik-dao-contract/wiki/Sputnik-Factory-V2-Upgrade-Action-Plan

@OllieMurray interesting find, can you give more details on how you generated this example?

Chiming in on this: I've heard & needed the following types of DAO deletions: 1. DAO is dissolving - allow the DAO to fully remove its account from factory &...

@crypto-credit I suspect the real issue here revolves around the threshold closure preference, meaning if we had a way to allow poll accepting votes until the expiration of the proposal,...

I like the idea here @netpoe, here's a couple thoughts on the matter: 1. Imagine a single proposal including a batch of adding members - If any 1 of those...

Lastly - wanted to note here - initializing the contract is different, and is deployed with a policy from the beginning which can be configured to have many members or...