-
Notifications
You must be signed in to change notification settings - Fork 38
adopt a cooperative operating agreement #72
Comments
I definitely agree this is needed. Are there examples we can base ours off of? |
I believe |
(Have asked on Twitter for a GitHub nick.) |
Is owners the right word here, I would have thought
In Bevry land, we have;
For gittip:
seem appropriate |
Confabulators isn't part of the bylaws. I wanted to avoid |
I actually want multiple people to own the LLC. In the past I've organized a cooperative as an LLC with cooperative bylaws. |
In my opinion |
Not sure if this will be useful to you, but here are the bylaws of our random consumer/shared-services co-op: http://member.datacommons.coop/bylaws. You end up with member-owners who use the co-op's services and elect a board that directs the co-op, and (optionally) patrons who use the services of the co-op without being members. There are professional co-op developers out there who are very helpful at organizing co-op conversions (disclaimer: I'm married to one of them). I wonder also if people like AORTA http://www.aorta.coop/ might also be able to help with the overall situation. |
Ping! (Hi, Chad!) The nutshell at the tip of the iceberg is that as a PA LLC, the Operating Agreement is the definition of the entity. Changing it (by whatever means are currently defined in the agreement) would change the rules of how Gittip is defined. In our case, we'd want to create definitions of owners that fit our own understanding of "We the Gittip". How that relates to contributors, participants, and others is going to be complex. (Building a generous community that is safe from griefers is a delicate matter.) (I have a few links for resources, but not sure how to compile and summarize those usefully yet, so I'll save them and keep researching.) |
(FTR, I've switched from |
http://www.scottbader.com/about-us/11/our-history
http://www.scottbader.com/about-us/45/our-governance-structure (h/t) |
Alright, let's start pushing on this a little bit.
Thanks, @paulfitz! :-)
Yes, that's the general direction we want to go.
We may in fact be interested in talking to the person you're married to. :-) Could you provide contact info here, or privately to [email protected]? I also have a card in front of me for a Pittsburgh lawyer with expertise in worker-owned co-ops, planning to call next week.
Heh, I recognize Esteban Kelley from the Platform Cooperativism conference last week (#384). :-) |
@phoemke Right, okay, so ... bylaws for a corporation, and an operating agreement for an LLC, ya? Gratipay, LLC was formed in 2002, and if we ever had an operating agreement, it's now lost to the sands of time. Let's keep this as a question for the lawyer (once we hire one), what dance we'll need to do to adopt a new operating agreement, given our current situation. |
I believe next steps here are to start with Data Commons' bylaws, which seem as good as any, and start drafting our own operating agreement. I think we should produce a draft ourselves, and then take it to a lawyer for additional revision. That should save us some money. |
We want, eventually, millions of members. Right? Is the upcoming Gratipay retreat (#393) going to be our constitutional convention? Our first annual meeting, where we ratify the new operating agreement? O.O |
I have to say, I really love the Amish way of choosing leadership: they vote their way to a shortlist of four or so, and then draw straws. I don't know if it's actually drawing straws, but it's random, is the point. I would love to incorporate that into Gratipay's operating agreement. :) |
I wonder what it means if becoming a co-op: |
Besides, I sincerely hope our limited resources can be focused on the project, especially if we put it in roadmap publicly, unless a structural change is absolutely necessary before that project is launched. |
I don't think that forkability can be likened to ownership, it's more a lack of monopoly on the code. While forkability allowed me to create Liberapay "quickly" (it still took me 8 months), democratic ownership would have allowed every Gratipay member to vote with equal power on the choices that had to be made, which may or may not have resulted in different decisions than the ones that were taken. Liberapay isn't a co-op, but it has co-directors (currently 4 of them) who each have one vote on every decision taken by its nonprofit organization (that includes any use of donations received by the org, changes to the terms of service, etc). |
That depends on the details of the democracy. Which decisions are constitutional and which are operational? Let's say everything went down exactly as it did, with the exception that yinz had voted me in as CEO or president or director or whatever. That would've counted for a democratic workplace under cooperative principles, even though we didn't hold a formal vote on the particular decision to start banning people (a decision I discussed at length with a number of people, particularly at the retreat that year as well as with you and others on https://github.com/gratipay/violations/issues/1). What's more, you mentioned in person that you probably would've forked even if we had voted and the vote led us in the same direction we in fact took. The bottom line is that the situation we found ourselves in was a conflict-ridden mess, and it's not clear that a fine-grained democratic constitution such as Liberapay's would've performed any better (and for what definition of " It was interesting to discover the following in Ours to Hack and to Own a couple days ago, in Mayo Fuster Morell's description of platform provision as one of "six interrelated factors as determinants and drivers of commons governance" (214):
Though she immediately goes on to say:
(Miriam Cherry's chapter, the next one, is even more highly relevant to our situation.) |
It's not absolutely necessary, of course. But I think a more formal identification with the cooperative movement could solidify our identity for ourselves, and also help to distinguish us from our VC-backed, for-profit competitors (BountySource at one time; now OpenCollective). I think the proposal I'm arriving at here is that we:
In other words, we may be closer than we think to being able to close this ticket! 😱 |
Of course we'll never know for sure whether formal rules similar to Liberapay's would have produced a better outcome or not, but I think they might have helped us reach a compromise.
I'm not denying that, I merely said that forkability isn't "the ultimate democratic ownership". |
Indeed! Such tantalizing what-ifs! :-)
Sure, not in the sense of "ultimate" as best or most thorough or highly developed or something like that. I was thinking of "forkability as an accountability measure." Forkability provides a worst-case scenario that is more democratic (preserving of individual autonomy; non-monopolistic) than the worst-case scenario in a situation lacking forkability. The proper constitution for the best of times is another matter. |
Forkability raises the lower bound on democracy, in other words. |
Here is her conclusion (pp. 226-227):
|
I've kicked off a project to encompass this ticket and related work. |
Sticking with this ticket for the time being for the legal/structural discussion ... what if we formalize three categories of legal relation to Gratipay, LLC:
"Collaborator" covers all three classes, as all are members of the Gratipay project on Gratipay (pending gratipay/gratipay.com#4299), and all compensation runs through twyw and looks the same from that point of view. Perhaps the requirements to become an owner are something like:
|
Re: non-cooperative operating agreements: https://en.wikipedia.org/wiki/Operating_agreement |
Draft bylaws (!m @clone1018). How do bylaws relate to operating agreement? |
bylaws:corporation::operating agreement:LLC https://www.google.com/search?q=bylaws+operating+agreement So we need an operating agreement (and not bylaws). |
Many tabs open, down the rabbit hole. CHAPTER 88: LIMITED LIABILITY COMPANIES (seems to have replaced Chapter 89?) |
LLCs in GeneralLegalZoom overview of operating agreements (non-cooperative) A random member-managed operating agreement (non-cooperative) Worker-owned Co-ops in GeneralMore general guidance on coop structure from SELC. Worker-owned Co-ops as LLCsgeneral guidance on worker-owned coops as LLC @JanelleOrsi's cartoon bylaws for a particular worker-owned coop Details, details, details ...Tax implications for members:
active vs. passive members (etc., etc., etc., etc.) splitting profits and equity incentives and retaining earnings loaning money to one's own LLC manager-managed vs. member-managed taxed as partnership vs. corporation guaranteed payments vs. distributions (old but seemingly still applicable) |
To: CPA
|
|
The tax examples in http://cdi.coop/coop-llc-individual-member-taxes/ come out to 30-35% for a domestic member—close enough to that of a foreign member that I don't think we should worry about any discrepancy there. The ease with which we can bring on foreign members to an LLC vs. C-corp more than makes up for a percentage point or three. |
The "minimalist six-member board" idea above at #72 (comment) is bad because we want people who hang around here a long time to become owners rather than employees. |
Starting over with the #72 (comment) stew in my head ... |
Moving to a PR in #1074. Draft is taking shape here: https://gratipay-operating-agreement.herokuapp.com/big-picture/operating-agreement |
Gratipay now has a cooperative operating agreement! 📜 💃 🌻 A hearty thank you to everyone who participated in this thread! 👏 👍 💯 |
It's time. Gittip right now is an LLC that is wholly owned by me. Gittip is de facto owned by the subset of our users that think of themselves as owning Gittip. We need to make this real de jure. I think we should be able to do this by writing
bylawsan operating agreement for the current LLC.The text was updated successfully, but these errors were encountered: