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

Write and adopt first by-laws #101

Closed
17 tasks done
patcon opened this issue Sep 2, 2019 · 10 comments
Closed
17 tasks done

Write and adopt first by-laws #101

patcon opened this issue Sep 2, 2019 · 10 comments
Assignees
Labels
2020-agm Tasks related to AGM

Comments

@patcon
Copy link
Contributor

patcon commented Sep 2, 2019

Shared Description

πŸ—£οΈ Loomio: https://loomio.hypha.coop/d/5akByK9O/agm-preparations-by-laws-etc-
πŸ“… Due date: by first AGM
🎯 Success criteria: drafted and reviewed bylaws to take into AGM.

To Do

  • seek sample/model by-laws. tweet.
  • draft by-laws
    • initial draft
    • review by gov working group:
      • session 1: membership
      • session 2: meetings, elections, directors
      • session 3: financials, operating
    • dc: review and modify draft based on research below and for AGM requirements
      • articles, voting, indemnification
  • @hyphacoop/finance-wg review Section 6+7 Surplus and Finance sections
  • present for members comment with agenda package - June 5
  • June 10 all hands discussion on bylaws -- request to review
  • June 6-12 commenting / feedback on bylaws (set up in loomio pre-meeting)
  • Updates and prep for June 13 AGM
  • Adopt bylaws at AGM
@patcon
Copy link
Contributor Author

patcon commented Sep 3, 2019

Proposal

Here's my proposal for how to break this down: (this should perhaps be in Loomio. was thinking could migrate if contentious -- messages seem easy to miss in there, and overly private.)

  • migrate NS worker co-op model by-laws to GDocs. done.
  • Migrate annotations verbatim into inline comments
  • snapshot a static copy in inline comments (for easier readable format, but verbatim orginal). done.
  • we create a snapshot to make comments for general updates, based on: (updated ON 2019 doc)
    • updates over time (e.g., 2009 Ontario amendments), and
    • across regions (NS => ON)
  • we start making customized comments/suggestions based on our own desires and inspirations from other co-op by-laws (Canada & US) and rulesets (UK). (our own draft doc)
  • finalize draft -- undetermined future date before AGM
  • approve at AGM

Sounds like a good start? Anyone have feedback or other ideas for approach? cc @hyphacoop/member-workers


Considerations

  • ❀️ I feel that there's a reasonable argument that by-laws aren't our most urgent priority. (I say that proactively, not because I've heard it said.)
  • πŸ” Accountant candidates (incl Hema) have already made recommendations of things that should be in our by-laws.
  • πŸ’‘ Let's at least get a baseline draft up, so we can start marking it up with things we learn/hear.

@patcon
Copy link
Contributor Author

patcon commented Sep 3, 2019

As someone reading through others' by-laws, thinking that a changelog would be nice.

Yes, we'll have a git history (eventually), but it would be a neat precedent to have it in the official by-laws themselves for when it's printed/shared as a doc.

sample format 1
sample format 2

@patcon
Copy link
Contributor Author

patcon commented Sep 4, 2019

@patcon
Copy link
Contributor Author

patcon commented Sep 4, 2019

Feedback from Matt at Fourth Pig:

@patcon sent email:

Member Benefits

The Board may create a reserve fund before any distribution of surplus arising from the
business of the co-operative in each fiscal year is made. Unless the surplus exceeds $12,000 in
one fiscal year, no patronage returns will be allocated, credited or paid to members or
non-members.

Not sure how to square this bit with not-for-profit status and your articles. Can you clarify? :)

Matt reply:

In terms of your question - it is referencing the surplus fund - we are allowed to have a contingency (reserve) fund in order to properly operate the business. We recently put this in to mark that we want to make sure that funds continue to go into the contingency fund. So with the money we get in we a) pay our account receivables b) put money in the reserve fund c) pay off any debts d) provide patronage returns.

Surprised that patronage returns are possible for a not-for-profit worker co-op, so still something I need to understand better

@patcon
Copy link
Contributor Author

patcon commented Oct 4, 2019

From #70 (comment)

We go this advice from our accountant:

document in constitution that money is going into separate bank account and have it all specified in by-laws. it will be part of the reserve.

@dcwalk
Copy link
Contributor

dcwalk commented Dec 12, 2019

Adding myself to this to keep it on my radar, not meant as a claim of exclusivity

@dcwalk
Copy link
Contributor

dcwalk commented Mar 11, 2020

Confirming we are πŸŽ‰ ready to draft πŸŽ‰

@patcon
Copy link
Contributor Author

patcon commented Mar 11, 2020

@dcwalk mentioned in 2020-01-29 gov wg notes:

pc: what's in scope of bylaws? [...]
dc: good chapters in "ours to hack and own" platform coop book

https://worldpece.org/sites/default/files/artifacts/media/pdf/ourstohackandown.pdf

"Chapter 15: Three Essential Building Blocks for Your Platform Cooperative", written by Janelle Orsi, known as the "sharing lawyer", including sharing bylaws.

The list of things I would build into cooperative bylaws is actually
much longer than the above...

She apparently spent quite a bit of time drafting the Loconomic Co-op bylaws (which we'd found already, but maybe an extra reason to lean on them πŸ™‚)

@benhylau benhylau added the 2020-agm Tasks related to AGM label Mar 17, 2020
@benhylau benhylau assigned benhylau and unassigned dcwalk Mar 25, 2020
@dcwalk
Copy link
Contributor

dcwalk commented Mar 25, 2020

@benhylau summary of the Janelle Orsi section:
Three elements to encode securely into the legal structures of platform cooperatives:

  1. Prevent the platform from being sold
    It is critical to adopt strong safeguards against the potential for the platform and any of its major assets to be sold into for-profit structures. A decision to sell major assets of the platform should require a high threshold of approval, such as by 80 percent of members, after what would hopefully be a long public conversation about alternatives.
  2. Put a cap on pay-outs and compensation
    The platform cooperative Loconomics uses data from the Bureau of Labor Statistics to cap employee pay at 3.5 times the median wage for all occupations in the region where the employee works. In the Bay Area, the cap would be $165,000. Among tech CEOs, that might sound like poverty.
  3. Adopt a staff trusteeship model of governance
    Staff trusteeship is a governance model that views all staff members of the cooperative as trustees who manage the platform for its beneficiaries, the body of members as a whole...Staff self-manage using an internal governance and operational model such as Holacracy or sociocracy, which distribute power among staff... In a staff trusteeship cooperative, the board of directors is still elected, but it takes on a role that is more akin to that of a guardian, overseeing the activities of the organization and ensuring that the staff are tuning in to members in every possible way.

@benhylau benhylau assigned dcwalk and unassigned benhylau Apr 8, 2020
@dcwalk dcwalk changed the title Write by-laws Write and adopt first by-laws Jun 13, 2020
@dcwalk
Copy link
Contributor

dcwalk commented Jun 15, 2020

This happened! Followed up from AGM in #307

@dcwalk dcwalk closed this as completed Jun 15, 2020
@dcwalk dcwalk mentioned this issue Jun 15, 2020
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2020-agm Tasks related to AGM
Projects
None yet
Development

No branches or pull requests

4 participants
@patcon @benhylau @dcwalk and others