-
Notifications
You must be signed in to change notification settings - Fork 62
O> Outline Scopes of the Governance Working Group into a document #133
Comments
Hi @patrick727 |
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 |
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 |
@Keaycee Added a few comments to the doc. |
Thank you, for reviewing the issue. I will make a correction base on the your suggestions. |
Yes i can @patrick727 |
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 |
@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 . |
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. |
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. |
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 |
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. |
Is there a blurb about intellectual theft on the member sign up document? If not there should be an ‘acceptable use’ policy. |
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. |
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. |
@jimscarver @patrick727 @Jake-Gillberg @lapin7 @pythonical The above has been added to the document. Suggested correction were made. |
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? |
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? |
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. |
I edited this comment to reflect my apology below. |
@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. |
@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. |
@pythonical I was not referring to you or anyone in particular. The comment was just a pointer :) |
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? |
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. |
Anyone who wants to move this forward, please clarify the description and re-open it. |
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.
Propose/discuss ideas that members consider related to "Governance"
Outline and Draft "Governance Committee" overview
The text was updated successfully, but these errors were encountered: