InnerSourceCommons / InnerSourceCommons/innersource-working-group
Rename and update all the things by 2026-08-10 (InnerSource Working Group)
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 26
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
- @meller13 Change repo name in GitHub from ispo wg to innersource wg: https://github.com/InnerSourceCommons/ispo-working-group
- @jeffabailey Conduct an audit of all refs and links across GitHub repos, teams, and projects .md files and published content in the ISC ecosystem - Managing InnerSource Projects Book
- @jeffabailey Identify refs to be changed to innersource wg (e.g. can historic videos refs stay 'as is' or are they updated)
- @jeffabailey Update refs to innersource wg, change/redirect links across content and run test for broken or dead-links
- @jeffabailey Rename project board: https://github.com/orgs/InnerSourceCommons/projects/4/views/1
- Review that the things on the board are relevant
- @jeffabailey Update the channel name
- @jeffabailey Rename the calendar events
- @jeffabailey Update https://innersourcecommons.org/community/ page @jeffabailey
- @jeffabailey Update the quick start guide pointing to our group
- @rrrutledge Prepare announcement for WG scope change
- Send to work group channel
- Send to members channel
- Send to newsletter
- @rrrutledge Publish announcement
- @meller13 Provide newsletter content
- @meller13 Provide social content
- @meller13 Invite ourselves to the next community call
- @rrrutledge Invite ourselves to the next all members call
- @meller13 Rework the presentation deck
- @meller13 present at the next community call
- @rrrutledge Update video
- Let the FinOS group know they can join forces with us where applicable
- See if we can lift community engagement restrictions within the InnerSource Working Group for the Financial Industry
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 with the unchecked checklist items covering GitHub repositories, teams, projects, .md files, published content, the Managing InnerSource Projects Book, and the docs/slides directory. Audit the references and links, decide which historic references change, update the content, and run a broken- or dead-link check. Done means the remaining rename, announcement, presentation, video, and invitation tasks are completed and verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100