Shared Stacksgov and Stacks Resources

[whoabuddy]

Sharing is Caring

As part of #14 and #15, I would like to consider the bigger picture for shared accounts and resources. What type of accounts should we configure, and how could we utilize the Blockstack ecosystem where possible?

Shared Accounts

After the foundation is setup, it will likely take control stewardship of a few "company" or "shared" accounts that cover the work we do in this group now, including:

• the Github Stacksgov organization, membership, and repos
• the Zoom Pro account and financial responsibility
• the Youtube account and related channels

Anyone involved with these accounts will likely share a username and password, but how do we achieve the same level of interaction with a Blockstack ID?

Shared Blockstack Accounts

How can we effectively share stacksgov.id.blockstack?

I could see a use case for:

• xordrive: to store a copy of all downloaded videos
• noteriot: to store a copy of all meeting notes before GH publish
• runkod: to host a website for the organization
• sigle: to publish our regular blog updates
• blocksurvey: to gather data when needed
• also: projects, passwords, 2 factor auth, etc.

My concerns:

• The only way I can see to do this now would be to share the 12-word phrase with anyone who needed access, allowing them to login to the same account. The problem is there would be no way to "revoke access" per user, each user would have access to the key and that cannot be changed like a password.
• I am curious if Keystone solves this problem, but I would have to look into it further.
• The alternative is to have multiple community members create an account and host info, but that also feels like it would get messy over time. I wonder if we can designate someone to hold the "main" and someone to hold the "backups" similar to designating a host for the meetings.

Thoughts?

[lrettig]

Thanks for consolidating and sharing your thoughts here. First things first, it seems to me that we are trying to accomplish two related but distinct tasks here. The first is sharing accounts and resources (video calls, file storage, etc.). The second is transitioning our workflow to Blockstack-based dapps as much as possible. I wonder if it might not make sense to split this into two distinct sets of tasks.

I'm not terribly familiar with the existing tools, capabilities, and limitations of Blockstack dapps - that's still a work in progress - but speaking from general knowledge (and of how things work in Ethereum), we probably want some combination of:

1. Better processes and workflow - e.g., the sort of redundancy you're talking about - no one person should ever be a bottleneck, or be the only person who holds the keys to an account
2. Multisig wallet for control of funds, resources, and keys more generally--I imagine the Foundation will need something like this anyway
3. A "DAO" that would let us hand out (and revoke) keys, vote, disburse funds, and generally interact with apps and services as a collective "entity" - Aragon is one project that offers this functionality. It's not Blockstack-based, but could theoretically be ported to Stacks 2.0 in the future.

[dantrevino]

I suggest using github pages. This allows interested parties to see historical versions of documents and also allows documents to be presented in a simple user-consumable way.

[whoabuddy]

Throwing out an idea: this could make a good grant wish list proposal?