todogroup.org
todogroup.org copied to clipboard
todogroup
TODO Guide Employee Open Source Engagement Guide - Principle 6: Ends Gracefully
Quotes/Thoughts/BrainDump/etc
- "The most common motivation among open source contributors is to add a feature that they themselves want to see, [Jeremy Stretch] said. “Once this has been achieved, the contributor rarely sticks around.”" [1]
[1] https://thenewstack.io/how-an-ospo-can-help-your-engineers-give-back-to-open-source/
Adding to reading list for class, thanks! :-)
On Mar 23, 2022, at 4:37 PM, alyssa wright @.***> wrote:
Quotes/Thoughts/BrainDump/etc
"The most common motivation among open source contributors is to add a feature that they themselves want to see, [Jeremy Stretch https://www.linkedin.com/in/jeremy-stretch/] said. “Once this has been achieved, the contributor rarely sticks around.”" [1] [1] https://thenewstack.io/how-an-ospo-can-help-your-engineers-give-back-to-open-source/ https://thenewstack.io/how-an-ospo-can-help-your-engineers-give-back-to-open-source/ — Reply to this email directly, view it on GitHub https://github.com/todogroup/todogroup.org/issues/294#issuecomment-1076795715, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAII2PLR6ICJ3D5GJWU74LTVBN6IFANCNFSM5QKLY3BA. You are receiving this because you are subscribed to this thread.
Any chance you can pass over the syllabus of readings? Curious to see if any of your “canon” can also inform a thoughtful guide for corporate engagement.
On Thu, Mar 24, 2022 at 7:29 AM, Stephen Jacobs @.***> wrote:
Adding to reading list for class, thanks! :-)
On Mar 23, 2022, at 4:37 PM, alyssa wright @.***> wrote:
Quotes/Thoughts/BrainDump/etc
"The most common motivation among open source contributors is to add a feature that they themselves want to see, [Jeremy Stretch < https://www.linkedin.com/in/jeremy-stretch/>] said. “Once this has been achieved, the contributor rarely sticks around.”" [1] [1] https://thenewstack.io/how-an-ospo-can-help-your-engineers-give-back-to-open-source/ < https://thenewstack.io/how-an-ospo-can-help-your-engineers-give-back-to-open-source/
— Reply to this email directly, view it on GitHub < https://github.com/todogroup/todogroup.org/issues/294#issuecomment-1076795715>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAII2PLR6ICJ3D5GJWU74LTVBN6IFANCNFSM5QKLY3BA . You are receiving this because you are subscribed to this thread.
— Reply to this email directly, view it on GitHub https://github.com/todogroup/todogroup.org/issues/294#issuecomment-1077526436, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAATESRLHYGTIWPPPGSN73DVBRG3HANCNFSM5QKLY3BA . You are receiving this because you commented.Message ID: @.***>
Some thoughts:
- Be open: Share the expected commitment and involvement in the project. No collaboration is too short, as long as it's well defined upfront
- Be mindful: Priorities change, or unexpected things happen, it's fine. Sharing at the earliest possible point in time with the community is crucial. This is true for premature ending and for unexpected extensions
Anything else on my mind on this topic is just circling back to the same things.
This needs to be revised, but a beginning:
"People remember how we leave a room. Our open source endings are a stepping stone to how we enter our next space, whether we return to the same room or enter a new one. Too often well-meaning open source contributors will just disappear, leaving silence and questions in their wake.
Your endings are just as important as any other juncture in the open source journey. How you choose to close it all out should bring to bear all the principles we’ve been discussing to life.
See principles 4 and 5 especially. Be transparent and be respectful. At the onset of engagement, we suggest you share the expected commitment and involvement in the project. At the closure, summarize and share the wrap up. Share where things have gone because no collaboration is too short, as long as it's well defined upfront. And continually defined ongoing.
Be respectful and mindful that things change. Priorities change, or unexpected things happen, it's fine. Sharing at the earliest possible point in time with the community is crucial. This is true for premature ending and for unexpected extensions."
