-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Bylaw structure #33
Bylaw structure #33
Conversation
c094008
to
6d4c1fe
Compare
6d4c1fe
to
60ecdc4
Compare
- Introduce README in bylaws directory - Clearly include all documents as sections within a whole - Clarify language around how/where records are kept.
60ecdc4
to
899560d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of minor comments. Looks good!
In the unfortunate event that the Commonhaus Foundation must dissolve, the following steps will be taken to ensure a responsible and lawful closure: | ||
|
||
- **Settling Liabilities:** First, we will pay off any outstanding debts or obligations the Foundation has incurred. | ||
- **Asset Distribution:** After clearing all liabilities, any remaining assets will be distributed to one or more organizations that share a similar mission or goals as the CF. This could include other nonprofit groups, like those classified under Section 501(c)(3) (charitable organizations) or other 501(c)(6) organizations (business leagues or chambers of commerce). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does an Asset need to be defined? Does it include the projects that are housed by the CF?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea. I have questions about this one. Let me revisit with some additional text in the mix and see where we land.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. In general, yes: if CF owns the projects, they would need to go to another 501(c)(6) or 501(c)(3) organization, and we would do what we can to help projects get there (according to the wishes of project leaders).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, thanks
|
||
## Project Roles | ||
- Be novel or a substantial fork of an existing project. | ||
- Show recent activity and/or significant usage as measured by downloads from a central package repository (Maven Central, GitHub Packages, etc.). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not necessarily wrong, but these phrases are quite vague - "substantial", "recent", "significant".
Restructured governance documents into bylaws (as a folder).