{"action":"created","issue":{"url":"https://api.github.com/repos/AegirCoop/aegir-coop-docs/issues/1","repository_url":"https://api.github.com/repos/AegirCoop/aegir-coop-docs","labels_url":"https://api.github.com/repos/AegirCoop/aegir-coop-docs/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/AegirCoop/aegir-coop-docs/issues/1/comments","events_url":"https://api.github.com/repos/AegirCoop/aegir-coop-docs/issues/1/events","html_url":"https://github.com/AegirCoop/aegir-coop-docs/issues/1","id":141692763,"number":1,"title":"Determine how we will handle voting","user":{"login":"cweagans","id":101590,"avatar_url":"https://avatars.githubusercontent.com/u/101590?v=3","gravatar_id":"","url":"https://api.github.com/users/cweagans","html_url":"https://github.com/cweagans","followers_url":"https://api.github.com/users/cweagans/followers","following_url":"https://api.github.com/users/cweagans/following{/other_user}","gists_url":"https://api.github.com/users/cweagans/gists{/gist_id}","starred_url":"https://api.github.com/users/cweagans/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cweagans/subscriptions","organizations_url":"https://api.github.com/users/cweagans/orgs","repos_url":"https://api.github.com/users/cweagans/repos","events_url":"https://api.github.com/users/cweagans/events{/privacy}","received_events_url":"https://api.github.com/users/cweagans/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-03-17T20:05:17Z","updated_at":"2016-03-28T16:10:58Z","closed_at":null,"body":"I didn't just make the change in the bylaws because it affects our day-to-day workflow, and I figured people would want to have some say in how this works. If/when we land on a solution here, I'm happy to write up the actual changes to the bylaws - just want to gain consensus here first.\r\n\r\nRelevant sections:\r\n\r\n* §1.V.2 (Remote participation)\r\n* §1.V.8 (Vote)\r\n* §1.IV.1 (Admission requirements - may not be changed)\r\n\r\nWe may need to add some extra definitions depending on the result of this discussion.\r\n\r\nTo start with, I propose that we use PGP signed email messages. When we have a vote, the member that's running the meeting should send a message to a members list with a summary of the question and the voting options. Each member should then respond with a signed message with their vote. This way, the email messages and signed responses can be archived with meeting minutes so that we have a paper trail.\r\n\r\nThis requires that members have a known PGP key, hence my suggested modification to §1.IV.1 -- there would be an added requirement to supply a PGP public key as a requirement of membership. This is easy enough to do with Keybase - they'll even generate a key for you, and you can create a signed message in the keybase web UI, which lowers the barrier to entry.\r\n\r\nIf PGP is not an acceptable solution here (and I totally understand if it's not - PGP is not a very simple thing in some cases), perhaps something like BitCongress would be a valid alternative?\r\n\r\nI think that something that's based on strong crypto would be a good idea, as it eliminates scenarios in the future where there's any doubt about how or if somebody voted on a given proposal."},"comment":{"url":"https://api.github.com/repos/AegirCoop/aegir-coop-docs/issues/comments/202464781","html_url":"https://github.com/AegirCoop/aegir-coop-docs/issues/1#issuecomment-202464781","issue_url":"https://api.github.com/repos/AegirCoop/aegir-coop-docs/issues/1","id":202464781,"user":{"login":"cweagans","id":101590,"avatar_url":"https://avatars.githubusercontent.com/u/101590?v=3","gravatar_id":"","url":"https://api.github.com/users/cweagans","html_url":"https://github.com/cweagans","followers_url":"https://api.github.com/users/cweagans/followers","following_url":"https://api.github.com/users/cweagans/following{/other_user}","gists_url":"https://api.github.com/users/cweagans/gists{/gist_id}","starred_url":"https://api.github.com/users/cweagans/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cweagans/subscriptions","organizations_url":"https://api.github.com/users/cweagans/orgs","repos_url":"https://api.github.com/users/cweagans/repos","events_url":"https://api.github.com/users/cweagans/events{/privacy}","received_events_url":"https://api.github.com/users/cweagans/received_events","type":"User","site_admin":false},"created_at":"2016-03-28T16:10:58Z","updated_at":"2016-03-28T16:10:58Z","body":"Oh, that's an interesting idea. So the person calling the vote would sign a commit that adds a file with the details of the vote, and then each person adds their vote to that file and does a signed commit? That way, we're forced to have a timestamped record of our votes, and there's no question about who voted and when. I'd be okay with that.\r\n\r\nHow much detail needs to go into the initial file (i.e. should we include details of what we're voting on and the different choices)? Where will we keep those files? In this repo?"}}