Update on bylaws/board/entity status?

Clearing the Path
1

Where would I go to see the latest status of the snowdrift entity/organization/board/bylaws etc?
Who is leading this effort? Who is the secondary lead? How can I help with this process?

Here is a possible lawyer resource that may be wise to engage:

1 Appreciation
2

The current Board (which still is not the first version of a Board to be elected under Bylaws by co-op members) has been drafting updated Bylaws to get to usable-enough state. There are some old versions we have been drawing from, but we are close to usable now.

We have a co-op focused lawyer who has not been a pro bono volunteer but who has helped us establish legal Articles and such.

The current belief is that Bylaws do need to be legally sound but that we can effectively use them internally in terms of following our own best-practices. Once we have a draft co-op member agreement good enough to invite patrons to accept and become official members, we should run that and the Bylaws draft by the lawyer to check for any concerns or some legal wordsmithing.

We have all legal and governance documents in

And I just opened a pull-request to include the current draft files

You @charles and anyone else is welcome to help by reviewing, commenting, or anything else to motivate the volunteer work to finish the process.

3

Thank you for this. Very helpful.

One super quick bit of feedback… perhaps create a “release” (a git tag) (or some directories) showing what’s current vs legacy vs administrative vs architecture/ design

Or maybe what’s adopted / “enforced” vs proposed ?

I could maybe infer that by last update.

I am working on this issue at TSYS and using git tags / releases in contracts , so that the agreement is unambiguous (it will reference a sha256 hash ).

So that , for example , in the operating agreement I can reference / delegate to a board charter or inter series contract and the entire “stack” is tied together.

1 Appreciation
4

Any interest in me organizing the repo content into an mdbook and submitting a PR with it ?

Right now it’s “just” a “pile of docs” with no clear structure.

I use mdbook heavily…

Rendered version:
https://jointventure.turnsys.com/

Repo:

Essentially it’s 99% pure markdown files with a book.Toml and SUMMARY.md.

An mdbook build creates the html and can be hosted on any static file hosting.

Nothing changes for the markdown edit / review / approve cycle .

5

That sounds nice, clearer structure. Structural cleaning is worthwhile. We’re happy to give that a try, especially since you’d be starting that work, thanks!

Only caveat is that things are being drafted, and we’d want to not have to worry about SUMMARY getting out of alignment or other things in the interim (it’s okay if marked as such).

6

Notes:

  1. The governance repo started out just including the roles & circles - which are still at the root of the repo. When we migrated from GitLab, I consolidated a bunch of other repos into it (assets, legal, mechanism, and publications). The intent was to make it easier to (A) find stuff and (B) reorganize the structure while preserving file history. At this point the “governance” title is narrower than its actual scope (anything related to running snowdrift-the-organization).

  2. I’m skeptical of the value of the meeting notes being there (except board meeting notes). If we start taking meeting notes again, I would probably just post them as comments in Weekly team meeting and "coffee-shop".