Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transparency and Credibility in voting, Vote Invalidation and Member Removal #51

Open
qwertyone opened this issue Jan 10, 2018 · 3 comments
Assignees

Comments

@qwertyone
Copy link
Contributor

qwertyone commented Jan 10, 2018

Problem

Social identities across platforms can be an issue as that identities cannot be confirmed. We operate as a group whereby our avatars are the only way for us to identify individuals in the group. With the recent controversy in the world about voter fraud, foreign meddling, and the concern of governance being the authenticity of those inside the collective. The votes on this platform are no different. I am for one guilty of perpetrating the problem in this proposal, though unintentionally. I had my accounts at times prior to the current governance structure within the group. Across Slack, GitHub, Google, Wiki, etc, there are opportunities for outside individuals to become involved in the affairs of the group, for better or worse. Unlike the Wiki and the Slack channels, Github and Google allow for a broader group to monitor and participate the happenings in the group. Github allows for individuals to vote without following or watching the proposal process. As such, the current voting system is potentially compromised because identities cannot be confirmed across platforms.

Proposal

The proposal insists that members of the collective maintain their first name and at minimum a last initial (added after suggestion by @shirishgoyal ) a list of voting members will be collected and profile usernames cross checked into a database across all platform profile pages. Otherwise, votes and participation will be considered invalid. If after the first notification of the situation to a participant has not responded within 3 days or that person is unable to be reached within the same period, they will be removed from the collective and black listed on GitHub, This will be written as a part of the Code of Conduct for the collective headed by Dilrukshi (@iceLearn ).

Implications

Authentication of votes where there is currently none. Dismissal of people who do not accept the Code of Conduct.


Use comments to share your response or use emoji 👍 to show your support. To officially join in, add yourself as an assignee to the proposal. To break consensus, comment using this template. To find out more about this process, read the how-to.

@qwertyone qwertyone changed the title Transparency and Credibility in voting, Vote Invalidation Transparency and Credibility in voting, Vote Invalidation and Member Removal Jan 10, 2018
@shirishgoyal
Copy link

I assume you are going to send this proposal to Github also to start showing actual names than their usernames as across the whole of Github, it is the username which is shown and even on hover there appears no info for the user. Also I wonder how this solves the problem as N users can keep the same first name and last name both on Slack and Github (including applies for the photographs if you are thinking around that). It is better to maintain a record of all usernames across platforms. Also Code of Conduct is a collective effort not headed by anybody. And same is true for the whole of collective.

@qwertyone
Copy link
Contributor Author

@shirishgoyal suggestion implemented

@markwhiting
Copy link
Member

@qwertyone just checking, did you intend to assign yourself here? (if so, you have consensus, if not I'll remove that).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants