Skip to content
This repository has been archived by the owner on Jun 17, 2020. It is now read-only.

O> Outline Scopes of the Governance Working Group into a document #133

Closed
patrick727 opened this issue Nov 2, 2017 · 28 comments
Closed
Assignees
Labels
wontfix zz-Governance NEEDS SPONSOR guides @jimscarver, @barneycinnamon, @rayzor zz-Operations NEEDS SPONSOR guides: @TrenchFloat, @jimscarver @Tonyprisca13

Comments

@patrick727
Copy link
Contributor

  1. Take Kenny summary "Identification and selection of directors, officers, and other important roles in the Cooperative, subject to Board approval. Oversee selection of Executive Committee general membership." clarify each point.

  2. Propose/discuss ideas that members consider related to "Governance"

  3. Outline and Draft "Governance Committee" overview

@patrick727 patrick727 changed the title Outline Scope of the Governance Committee into a document O> Outline Scope of the Governance Committee into a document Dec 10, 2017
@Keaycee
Copy link
Contributor

Keaycee commented Dec 26, 2017

Hi @patrick727
I could not find any summary on the above topic written by Kenny Rowe. Please if you do have a link to the above topic, it will be very needed.

@patrick727 patrick727 added zz-Governance NEEDS SPONSOR guides @jimscarver, @barneycinnamon, @rayzor zz-Operations NEEDS SPONSOR guides: @TrenchFloat, @jimscarver @Tonyprisca13 labels Jan 2, 2018
@Keaycee
Copy link
Contributor

Keaycee commented Jan 4, 2018

Hello,

Base on the issue of Governance committee, i have done a comprehensive work on it. I want the members of the cooperative to make a review on it. Below is the document link.

https://docs.google.com/document/d/1U3elyL4y-H8Z6uBU61tiO0sRTWu7DeRmPjfdYgpUOKY/edit?usp=sharing

@patrick727
Copy link
Contributor Author

woah great work @Keaycee

can you join the governance meetings thursdays?

I just lightly reviewed it and will go more in depth as we move forward.

Cheers

@Jake-Gillberg
Copy link
Contributor

@Keaycee Added a few comments to the doc.

@Keaycee
Copy link
Contributor

Keaycee commented Jan 6, 2018

Thank you, for reviewing the issue. I will make a correction base on the your suggestions.

@Keaycee
Copy link
Contributor

Keaycee commented Jan 9, 2018

Yes i can @patrick727

@9rb 9rb self-assigned this Jan 20, 2018
@Keaycee
Copy link
Contributor

Keaycee commented Jan 25, 2018

Corrections and suggestions has been done. However, there may still be need for further review.

https://docs.google.com/document/d/1U3elyL4y-H8Z6uBU61tiO0sRTWu7DeRmPjfdYgpUOKY/edit?usp=sharing

@lapin7
Copy link
Contributor

lapin7 commented Jan 31, 2018

I've set the budget of #133 arbitrarily to $0.00 because of the discussion volunteer and rewards
Please discuss amongst others with @dckc

@dckc
Copy link
Contributor

dckc commented Jan 31, 2018

@patrick727 point 2 in the description muddies the waters considerably. The RChain Nomination and Governance Committee has no mandate beyond "Identification and selection of directors, officers, and other important roles in the Cooperative, subject to Board approval. Oversee selection of Executive Committee general membership."

The use of "Governance Committee" in the issue title made me wonder if you were referring to the same committee introduced in the bylaws, created by the board, and discussed at the annual meeting, but your point 1 clarifies that you are.

As I said in my Jan 27 comment, broader governance work is interesting, but it's separate from the work of the RChain Nomination and Governance Committee.

Anyone who remains unclear on this, please discuss with officers such as @kennyrowe and/or board members such as @drbloom .

@jimscarver
Copy link
Contributor

Indeed there has been some confusion. My takeaway from the annual meeting was the governance committee responsibility went far beyond the specific responsibilities listed in the bylaws including block chain and coop governance with Vlad as a guide.

I took on the task of initiating activities to forward our mandate as I understood it which may have led to confusion. My apologies for my misunderstanding.

In the RGov log I suggested changing the name to "governance working group" when the official "RChain Nomination and Governance Committee" would be a subset of working group members.

I suggest @Keaycee s doc be proposed as the scope of this "RChain Governance Working Group". This is important work that needs to be done.

@dckc
Copy link
Contributor

dckc commented Feb 1, 2018

Thanks, @jimscarver . I'm inclined to revise the title and description of this issue to refer to a "governance working group". I'll stand for a bit by to see if @patrick727 or you or anybody else would rather do it yourself.

@Keaycee Keaycee changed the title O> Outline Scope of the Governance Committee into a document O> Outline Scopes of the RChain Governance Working Group into a document Feb 2, 2018
@Keaycee Keaycee changed the title O> Outline Scopes of the RChain Governance Working Group into a document O> Outline Scopes of the Governance Working Group into a document Feb 2, 2018
@Keaycee Keaycee unassigned 9rb Feb 2, 2018
@dckc dckc assigned 9rb and Keaycee Feb 2, 2018
@dckc
Copy link
Contributor

dckc commented Feb 13, 2018

Which part of the scope document is original work?

Prompted by @drbloom 's comment I took an arbitrary sentence from another section and looked it up in google and found that the entire section on "The Meaning of Decentralization" is copied without attribution from https://medium.com/@VitalikButerin/the-meaning-of-decentralization-a0c92b76a274

@dckc
Copy link
Contributor

dckc commented Feb 13, 2018

I'm very much conflicted... I think wholesale copying without attribution is behavior deserving immediate and permanent revocation of contributor privileges. And in #319, @lapin7 made me an admin. So now if I don't remove the author's contributor status in this repository, I'm complicit.

I'll stand by for a day or two for suitable explanation.

@9rb 9rb removed their assignment Feb 13, 2018
@burn1ngchr0me
Copy link

Is there a blurb about intellectual theft on the member sign up document? If not there should be an ‘acceptable use’ policy.

@lapin7
Copy link
Contributor

lapin7 commented Feb 13, 2018

@dckc I suggest that @Keaycee doesn't get any reward for his work done in February. Everywhere he appears in the reward sheet, I will downvote him. Others can do the same.

Copying like this and claiming that you wrote it, is an awful behavior.
@Keaycee please explain this action!!!

@Keaycee
Copy link
Contributor

Keaycee commented Feb 14, 2018

My work is base on research and contribution from experienced experts online. However the work is still on progress and still under review. After proper corrections and review, conclusion and reference will be added.
I made research and got this put together, but if my work (Document) is not worth anything to RChain Cooperative then anybody can act as they see fit.

@dckc dckc self-assigned this Feb 14, 2018
@dckc
Copy link
Contributor

dckc commented Feb 14, 2018

Nothing in your comment answers my question: Which part of the scope document is original work? You have not identified any sentence or paragraph that is original work.

@Keaycee
Copy link
Contributor

Keaycee commented Feb 20, 2018

@jimscarver @patrick727 @Jake-Gillberg @lapin7 @pythonical
Summary
Conclusion
Recommendation
Reference

The above has been added to the document. Suggested correction were made.
This work is completed, although there maybe need for further review and suggestions.

@dckc
Copy link
Contributor

dckc commented Feb 20, 2018

The blatant plagiarism remains.

Comments (including specific requests that quoted material be marked as such) are closed without being addressed. Repeatedly: 1:16 PM Jan 6, 11:49 AM Feb 14, 11:50 AM Feb 14, 8:32 AM Today.

@patrick727 @jimscarver do you see any reason why I shouldn't revoke @Keaycee 's privileges?

@burn1ngchr0me
Copy link

i really hate seeing this having to take place but it does make me wonder is there any process for 'reviews' of such cases and is/will there be any recourse for someone to plead their case after the fact?

@Ojimadu
Copy link
Contributor

Ojimadu commented Feb 21, 2018

Revocation of member's rights should not be based on a decision by a single member. There needs to be a review of cases like this and not based off an arbitrary decision.

@Keaycee
Copy link
Contributor

Keaycee commented Feb 21, 2018

I edited this comment to reflect my apology below.

@Keaycee
Copy link
Contributor

Keaycee commented Feb 21, 2018

@patrick727 @Jake-Gillberg @lapin7 @jimscarver @dckc @pythonical I'm very sorry about everything and I accept my mistakes and wrongs. I really do not feel nice about the way this is going. Issue #133 was the first issue that I worked on when I became a member of the coop. I'm new to collaborative work. I tried my best to make corrections and also reference on how my work came about, but it seem the plagiarism is still very obvious.
I suggest that this document be removed since it's not yet a working document and has not yet been adopted.
I also suggest that my reward for this issue be removed and I also should be unassigned from it.

@Keaycee Keaycee removed their assignment Feb 21, 2018
@burn1ngchr0me
Copy link

@Ojimadu others have looked at it and commented along the thread so it isn’t just down to one. I am a bit disturbed by these last comments by keaycee. Something odd.

@Ojimadu
Copy link
Contributor

Ojimadu commented Feb 21, 2018

@pythonical I was not referring to you or anyone in particular. The comment was just a pointer :)

@dckc
Copy link
Contributor

dckc commented Feb 21, 2018

I looked more closely into the history of contributions by @Keaycee and I found a good conversation on telegram in Africa (#225).

I'm light of that contribution, I am inclined to look at this as a misunderstanding. I accept your apology.

I see @lapin7 is making more comments to clarify norms for quoting work by others. That's good, but it could be a slow process, and this really should be addressed quickly.

Would a co-author please step forward and request edit access?

Or should we mark this document obsolete and begin again later?

@dckc
Copy link
Contributor

dckc commented Feb 22, 2018

I got some input from @jimscarver ; he encouraged me to not just request changes but demonstrate what I have in mind. I replaced wholesale copy and paste sections by placeholders: pending appropriate excerpt / summary.

I'm not available to do the excerpts / summaries just now. I hope another collaborator comes along for that.

The remaining text, starting with the GOVERNANCE working group MODEL also seems to be copied and pasted from other sources, but (a) it seems to be a somewhat novel synthesis, and (b) those sources are coop governance materials with a reasonably clear heritage of liberal copying and pasting.

I also added a byline with some status info an a link to this issue for context.

@dckc
Copy link
Contributor

dckc commented Mar 2, 2018

Anyone who wants to move this forward, please clarify the description and re-open it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
wontfix zz-Governance NEEDS SPONSOR guides @jimscarver, @barneycinnamon, @rayzor zz-Operations NEEDS SPONSOR guides: @TrenchFloat, @jimscarver @Tonyprisca13
Projects
None yet
Development

No branches or pull requests

9 participants