Hi, It is a friendly reminder that we are still in the process of collecting input for the Community Blueprint idea. I would like to encourage all of you to __add your stories to our etherpad__, we already have a few started at the bottom for inspiration! It is enough to add only an abstract at this stage. Please add your name to your story as well so I can reach out to you with follow up steps and questions: https://etherpad.opendev.org/p/community-blueprint For additional background: The stories are intended to focus on experiences that you or the community you work(ed) with, had, which either created an issue for the community or helped ensuring their success or long term sustainability. Our goal is to help OpenInfra and adjacent communities along with companies and individuals who launch and participate in projects to avoid making the “usual” mistakes. The OpenInfra communities and Foundation follow the Four Opens as guiding principles. While we documented what these principles are, for someone who’s new to open source or haven’t yet had a good experience it is challenging to translate them into practice. The stories that we are looking for intend to help put the challenges as well as the Four Opens into perspective to encourage and enable open collaboration throughout the ecosystem. The next step, as we have more stories collected, is to start structuring the content. I will reach out again in January to organize our next meeting and sync up with all of you who are interested in participating. Please let me know if you have any questions or comments in the meantime. Happy Holidays to all of you who are celebrating! Thanks and Best Regards, Ildikó ——— Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation
On Sep 22, 2022, at 16:27, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Hi,
I’m reaching out to you with updates, as a few of us had a follow up call this week to continue the conversation about the Community Blueprint idea and next steps.
Here are some of the highlights of the meeting:
* We started with a summary of recent progress and quickly moved into a conversation about existing resources and how this effort is intended to be different: + The Four Opens document only describes the guiding principles and gives some examples about what they are, without a specific group as target audience: https://opendev.org/openinfra/four-opens + There are similar documents and whitepapers available in the ecosystem that target to explain similar principles and methods + We discussed the first group of target audience and agreed to __address “middle-layer” management__ in the first iteration + We also agreed that __we will NOT call the document that we are about to create, “The Way”__, since every community is different and there is no one golden route that will work for everyone
* We also talked about strategy to build and present content: + We will use stories to share our experiences related to OpenInfra as well as adjacent communities to put any practice, principle or process into perspective + When someone shares a story from their own perspective that is easier to relate to than more generic examples from a community’s daily life. We would like to help people to relate and find similarities between their own experience and efforts and stories in the new document to help create good habits and leave behind harmful ones.
* Next steps: + We agreed to collect stories first and then look into how to group and organize them + The stories are planned to set the tone and create the context for chapters and sections in the document(s) that we will create - We will then add available and recommended practices and processes, where applicable, to help individuals avoid or get out of bad/undesired habits + I will set up a call once we have a good amount of stories that people contributed
For more detailed notes please see the idea etherpad: https://etherpad.opendev.org/p/community-blueprint
CALL TO ACTION: I would like to encourage all of you to __add your stories to the etherpad__, we already have a few started at the bottom for inspiration! It is enough to add only an abstract at this stage. Please add your name to your story as well so I can reach out to you with follow up steps and questions.
Thanks and Best Regards, Ildikó
———
Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation
On Sep 1, 2022, at 10:42, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Hi,
I’m reaching out to you with an update.
Based on the poll results we settled on September 21 (Wednesday) at 1300 UTC to have the follow-up call.
You can find the dial-in information and further details on this etherpad: https://etherpad.opendev.org/p/community-blueprint
Please let me know if you have any questions or would like to get a calendar invite.
Thanks and Best Regards, Ildikó
———
Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation
On Aug 23, 2022, at 12:56, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Hi,
It is a friendly reminder to our open poll to schedule a call to discuss the Community Blueprint/OpenInfra Way idea further.
You can access the poll here: https://framadate.org/5jNiF8t8C7oH71pj
Based on the current results, the favored options are: * September 20 (Tuesday) at 1300 UTC * September 21 (Wednesday) at 1300 UTC
__If you are interested in participating in the discussion and haven’t filled out the poll yet, please do so by the end of this week (August 28).__
Please let me know if you have any questions.
Thanks and Best Regards, Ildikó
———
Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation
On Aug 8, 2022, at 17:44, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Hi,
I’m reaching out to you with some quick updates.
I gave a short overview about the progress with this effort at the recent OpenInfra Board of Directors meeting on the 2nd of August. The feedback was overall positive and new ideas came up during the short conversation we had during the call. The main discussion explored the concept of describing culture and providing input for decision making through sharing stories and experiences, that we’ve had throughout our journey in open source.
The option to organize a follow-up call also came up, so we can dive deeper into the above idea and overall content of the new document(s) we are planning to create. To capture interest, I created a poll with a few options for September: https://framadate.org/5jNiF8t8C7oH71pj
__If you are interested in participating and sharing your comments, experiences or stories please fill out the form by August 24.__
As a reminder, here are a few resources you can look into for further details: - Repository: https://opendev.org/openinfra/way - Open review to add seed content: https://review.opendev.org/c/openinfra/way/+/851768/ - Further details about the Community Blueprint idea: https://etherpad.opendev.org/p/community-blueprint
Please let me know if you have any questions or comments.
Thanks and Best Regards, Ildikó
———
Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation
On Jul 18, 2022, at 13:43, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Hi,
I'm reaching out to you as a follow up to one of the ideas that was brought up during the OpenInfra Board of Directors (BoD) meeting in Berlin on June 6, called Community Blueprint.
The prupose of this email is to raise awareness of the activities around the idea and invite you to participate in next steps, if you are interested.
A few of us from the OpenInfra Foundation staff and BoD met recently to discuss the idea in a bit more details and identify goals and next steps. Highlights from our conversation include:
* Goals - Create a playbook that new projects can use to make well-informed choices in areas such as licensing, governance, community structure and more - Beyond documenting processes and tools, the playbook will also discuss expectations, i.e.: what commitments the project founders will have, what the ecosystem and community expects from them - The playbook is intended to be used by prospective new OpenInfra projects, and in addition showing thought leadership in the open source ecosystem
* Playbook documents - Target audience + 1st stage: Managers and executives to understand what it means and entails to do something in open source + 2nd stage: Contributors and developers - Seed content: https://etherpad.opendev.org/p/hflJmbl2SGsD0Pkkr-Sa - Repository: https://opendev.org/openinfra/way
* Further background - We went through an overview of the original idea that was targeting the balance and sustainability of the open source ecosystem, and the OpenInfra Foundation's opportunity to provide guidance to our current and prospective projects as well as the ecosystem at large - We looked into the history of long-existing open source projects as well as the current trend of mass-creation of new projects + Experienced contributors can help build and maintain community culture + New projects without experienced members can easily become dysfunctional without the community noticing —> These models are also replicating in the current ecosystem by projects following bad examples
* Next steps - Use the new Git repository and seed content linked above to start outlining the document structure and content
For more detailed notes of our conversation please see the following etherpad: https://etherpad.opendev.org/p/community-blueprint
If you have any question or would like to participate in the effort please reply to this thread or reach out to me directly.
Thanks and Best Regards, Ildikó
———
Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation
_______________________________________________ Foundation-board mailing list Foundation-board@lists.openinfra.dev https://lists.openinfra.dev/cgi-bin/mailman/listinfo/foundation-board
_______________________________________________ Foundation-board mailing list Foundation-board@lists.openinfra.dev https://lists.openinfra.dev/cgi-bin/mailman/listinfo/foundation-board