Bylaw structure #33
Merged
Bylaw structure #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ebullient
force-pushed
the
bylaw-structure
branch
from
c094008
to
6d4c1fe
Compare
ebullient
force-pushed
the
bylaw-structure
branch
from
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.
ebullient
force-pushed
the
bylaw-structure
branch
from
60ecdc4
to
899560d
Compare
kenfinnigan
approved these changes
Nov 14, 2023
| 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.
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.
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.
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.
Makes sense, thanks
Merged
sebersole
reviewed
Nov 15, 2023
|
|
||
| ## 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.
Not necessarily wrong, but these phrases are quite vague - "substantial", "recent", "significant".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Restructured governance documents into bylaws (as a folder).