InnerSourceCommons / InnerSourceCommons/innersourcecommons.org
Define how the foundation works as a whole and make it public
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 31
- Forks
- 33
- Avg merge
- 15h 24m
- Merged PRs (30d)
- 22
Description
In a meeting on 2026-01-13
ISC WG meeting (Membership Discussion)
Problems raised:
- People don’t understand the benefits of membership.
- Some members aren’t engaged.
- Some people are engaged, but haven’t been nominated.
Action Items
- 1. Update what it means to be a member here: https://innersourcecommons.org/about/members/
- 2. Make the bylaws public: https://tinyurl.com/ISCByLaws
- 3. Clean up the member list based on actual attendance and/or what it means to be a member.
References
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the membership page at about/members/, the bylaws PDF at static/documents/bylaws.pdf, the membership application, and the linked onboarding proposal. Clarify the public membership definition and bylaws presentation, then reconcile the member list with the agreed criteria and attendance. Done means the membership information is updated, the bylaws are publicly accessible, and the member list reflects the decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100