archive.innersourcecommons.org
archive.innersourcecommons.org copied to clipboard
InnerSourceCommons
InnerSource commons history
I am creating this issue as a follow up of the this InnerSource slack thread: https://innersourcecommons.slack.com/archives/C04PXKRN4/p1581342026046400
@dellagustin: That question is actually in line with something I consider an unsung best practice: Keep a record of a project's history I just added this weekend a history section to a personal project of mine (a podcast aggregator distributed as a chrome - and soon other browsers - extension): https://github.com/podStation/podStation#history I was also looking for the opportunity to show my baby :grinning: I think it helps people that reach the project to understand why it exist and how it got there. I would propose that we add this to the list of InnerSource best practices and upstream it to the Open Source community (I am assuming this is not yet a generally agreed best practice): I would also propose we add a history session to the innersourcecommons.org website. I will create an issue for that.
I accepted driving this topic, so please assign me to this issue if possible.
References
- Where does the logo come from - https://innersourcecommons.slack.com/archives/C04PXKRN4/p1581357073049900?thread_ts=1581342026.046400&cid=C04PXKRN4
Acceptance Criteria
- A community-agreed plan
- An issue(s) that, when finished, will implement the plan.
Hi @rrrutledge I do not know yet, I will fork it and come with a few different proposal for use to compare. It could be a step by step approach, start with a short section on README, and migrate to a dedicated History page on the website.
What do you think about this approach?
That will work fine! I am thinking of updating this issue to have the acceptance criteria of producing:
- A community-agreed plan
- An issue(s) that, when finished, will implement the plan.
So this issue tracks the investigation/planning of this work rather than tracking its actual completion.
Does that make sense?
Sounds great, Guilherme! I have updated the description with this acceptance criteria and assigned to you. Please take a crack at it and let us know when you think you have something.
Just as info - I am prioritizing #91 , as I want to have an easy to setup development environment before working on the other issues I am assigned to.