From kennelson11 at gmail.com Tue Aug 2 21:25:23 2022 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 2 Aug 2022 16:25:23 -0500 Subject: [Openinfralabs] Fwd: Reminder! PTG October 2022 Team Signup Deadline In-Reply-To: References: Message-ID: Hello Everyone, Don't forget to sign your team up for the next Project Teams Gathering (PTG), which will be held in Columbus, OH from Monday, October 17 to Thursday, October 20th, 2022! If you haven't already done so and your team is interested in participating, please complete the survey[1] by August 12th, 2022 at 7:00 UTC. Then make sure to register[2] for the PTG before prices go up on August 15th! Also, please book in the official hotel block for a discounted rate[3]. Booking in the PTG hotel block helps us keep costs low for all attendees, so please encourage your teams to book here. Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] PTG Registration: https://openinfra-ptg.eventbrite.com [3] Hotel Block: https://www.hyatt.com/en-US/group-booking/CMHRC/G-L0RT -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Fri Aug 5 17:52:48 2022 From: kennelson11 at gmail.com (Kendall Nelson) Date: Fri, 5 Aug 2022 12:52:48 -0500 Subject: [Openinfralabs] Fwd: October PTG Update In-Reply-To: References: Message-ID: Hello Everyone, I wanted to provide an update on the October Project Teams Gathering (PTG). After discussing with community members and prospective sponsors, we have made the decision to pivot the event to 100% virtual to be as inclusive as possible. I know that this is not the ideal outcome and there are a lot of factors contributing to this decision, but we think it?s the best decision for the global community at this time. We are continuing to receive feedback on the value and importance of in-person PTGs; we just need to wait for other factors to be less of an obstacle If you have already registered, you should have been contacted for a full refund. We are going to use the same week for a virtual PTG and it will be free to attend, just like the previous ones. The registration is already live [1]. If you have any questions or feedback on this decision, please let us know. We will continue to monitor feedback as we make plans for a 2023 PTG. Thank you, Kendall (diablo_rojo) [1] https://openinfra-ptg.eventbrite.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From kwade at redhat.com Thu Aug 11 23:19:59 2022 From: kwade at redhat.com (Karsten Wade) Date: Thu, 11 Aug 2022 16:19:59 -0700 Subject: [Openinfralabs] Rebuilding the core discussion In-Reply-To: References: Message-ID: Thank you Julia for starting this discussion about getting involved in a reset and what to do next. And I appreciate your patience as people (like me!) get my head together and into this discussion (eventually) around important change management, here in the middle of atypically busy months. Hi all, I haven't posted much (at all?) to this mailing list, I'm one of the "few of us" Julia refers to below. I'm the community architect for the Operate First project ? meaning my role is to lead the design and implementation of a plan to create and scale Open Source communities ? as well as the co-Chair of the Operate First Community Special Interest Group (SIG). I have a vested interest in having a defined mission and governance for Open Infra Labs as a project within the Labs. >From later in this thread, I agree about beginning work in our GitHub repository as the commons where we can draw the most brains and hands (today). tl;dr of below: 1. I propose a three step process to write the vision and mission, including lots of time for feedback 2. To kick it off, I made this PR: https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13 - Under the "FIles Changed" section ( https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13/files ) you can make line-by-line comments by clicking the + sign next to the line number, and you can use the [+-] button to suggest specific changes. 3. That's it! Some comments/questions inline below: On Fri, Jul 8, 2022 at 1:26 PM Julia Kreger wrote: > > Greetings everyone, > > During our recent Open Infrastructure Summit in Berlin, one of the > repeated discussion topics I found myself engaged in suggested a > breakdown in shared context and communication within OpenInfra Labs. A > bit of a root cause analysis occurred, and each discussion quickly > determined there is definitely no fault, but more a result of the > state of engagement which collided against the pandemic. Further > compounded by the time schedule differences which run our various > lives and efforts. It did not help us that we did not use the same > words to begin with. In our discussions in Berlin and beyond, I think I've characterized it as something to the effect of, "We never finished getting alignment before everyone's attention turned to the pandemic. When we drew our attention back out to work on these problems, we saw other people seemed to be out of alignment and on their own paths. Then each of us (person or group) forked just a bit more in chasing our version of the mission while seeing each other as out of alignment with our own vision." > A few of us have continued going back and forth over the last few > weeks and we've reached the conclusion we need to rebuild the core > consensus and discussion. Ultimately a revision of our mission and > long term vision, in order to better support the sharing of knowledge > and context which is fundamentally needed to support the efforts > occurring within OpenInfra Labs. > > Before we really continue onward in these discussions, I think it is > important for us to widen the audience of engagement and enable a > greater chorus of voices to engage as we sort of press the reset > button in order to set expectations, intents, and bring us all back to > a happier, engaged place. In recognition that no single tool or means > will work for everyone, *and* to help provide insight for those that > don't necessarily subscribe to mailing lists or whom are unable to > join our discussions now, the idea has been floated to write about it. > Such as a blog or a journal. To share our story. To share the stories. > To spread the knowledge! > > I think we should start with high bandwidth calls to reach the same > page, and then move forward from there. > > If you're interested in engaging in this discussion, please reply with > to this email with the days of the week and times that would work, or > that would not work, and I'll try to find a mutually agreeable 30 > minute window every two weeks for us to start with. OK, so I agree with this and Julia's later sentiment about getting things started in a git repo. Let's work on these in parallel, how about this as a process: 1. If you want to be part of the discussion right now, let's work on this document together: https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13 That is a straw-draft, meaning it's something we can build a "discussion draft" from. 2. Next opportunity is helping build the discussion draft. You can continue from straw-draft work or join in for that round of writing-and-editing. We'll have time in between each step for broad, general feedback. 3. The discussion draft is what we take to the wider OpenInfrastructure community for feedback. That is three wide rounds of feedback, at least. We can slow down and add more, if needed. Some of that work can occur in live, high-bandwidth meetings. We also need to commit to coming back and keeping this list well informed. Your participation in this is very, very welcome, whenever you arrive into the process. Even when we are "finished" and moving on, we need to really understand our vision and mission as living documents. Maybe we want to have regular review and refresh stages every few years, for example? Just to keep things from getting stale and forgotten. Kind regards, - Karsten > Thanks, > > -Julia > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > https://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > -- Karsten Wade [he/him/his] | Principal Community Architect | @quaid Red Hat Open Source Program Office (OSPO) : @redhatopen The Open Source Way : https://theopensourceway.org Operate First : https://operate-first.cloud -------------- next part -------------- An HTML attachment was scrubbed... URL: From hbrock at redhat.com Mon Aug 15 19:54:49 2022 From: hbrock at redhat.com (Hugh Brock) Date: Mon, 15 Aug 2022 15:54:49 -0400 Subject: [Openinfralabs] Rebuilding the core discussion In-Reply-To: References: Message-ID: Thanks for doing this Karsten. Do we need to reconvene at some point, maybe around a deadline for the first draft of your doc? I'm keen to get this moving in the right direction. Take care, --Hugh On Thu, Aug 11, 2022 at 7:20 PM Karsten Wade wrote: > Thank you Julia for starting this discussion about getting involved in a > reset and what to do next. And I appreciate your patience as people (like > me!) get my head together and into this discussion (eventually) around > important change management, here in the middle of atypically busy months. > > Hi all, > > I haven't posted much (at all?) to this mailing list, I'm one of the "few > of us" Julia refers to below. I'm the community architect for the Operate > First project ? meaning my role is to lead the design and implementation of > a plan to create and scale Open Source communities ? as well as the > co-Chair of the Operate First Community Special Interest Group (SIG). I > have a vested interest in having a defined mission and governance for Open > Infra Labs as a project within the Labs. > > From later in this thread, I agree about beginning work in our GitHub > repository as the commons where we can draw the most brains and hands > (today). > > tl;dr of below: > 1. I propose a three step process to write the vision and mission, > including lots of time for feedback > 2. To kick it off, I made this PR: > https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13 > - Under the "FIles Changed" section ( > https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13/files > ) you can make line-by-line comments by clicking the + sign next to the > line number, and you can use the [+-] button to suggest specific changes. > 3. That's it! > > Some comments/questions inline below: > > On Fri, Jul 8, 2022 at 1:26 PM Julia Kreger > wrote: > > > > Greetings everyone, > > > > During our recent Open Infrastructure Summit in Berlin, one of the > > repeated discussion topics I found myself engaged in suggested a > > breakdown in shared context and communication within OpenInfra Labs. A > > bit of a root cause analysis occurred, and each discussion quickly > > determined there is definitely no fault, but more a result of the > > state of engagement which collided against the pandemic. Further > > compounded by the time schedule differences which run our various > > lives and efforts. It did not help us that we did not use the same > > words to begin with. > > In our discussions in Berlin and beyond, I think I've characterized it as > something to the effect of, > > "We never finished getting alignment before everyone's attention turned to > the pandemic. When we drew our attention back out to work on these > problems, we saw other people seemed to be out of alignment and on their > own paths. Then each of us (person or group) forked just a bit more in > chasing our version of the mission while seeing each other as out of > alignment with our own vision." > > > A few of us have continued going back and forth over the last few > > weeks and we've reached the conclusion we need to rebuild the core > > consensus and discussion. Ultimately a revision of our mission and > > long term vision, in order to better support the sharing of knowledge > > and context which is fundamentally needed to support the efforts > > occurring within OpenInfra Labs. > > > > Before we really continue onward in these discussions, I think it is > > important for us to widen the audience of engagement and enable a > > greater chorus of voices to engage as we sort of press the reset > > button in order to set expectations, intents, and bring us all back to > > a happier, engaged place. In recognition that no single tool or means > > will work for everyone, *and* to help provide insight for those that > > don't necessarily subscribe to mailing lists or whom are unable to > > join our discussions now, the idea has been floated to write about it. > > Such as a blog or a journal. To share our story. To share the stories. > > To spread the knowledge! > > > > I think we should start with high bandwidth calls to reach the same > > page, and then move forward from there. > > > > If you're interested in engaging in this discussion, please reply with > > to this email with the days of the week and times that would work, or > > that would not work, and I'll try to find a mutually agreeable 30 > > minute window every two weeks for us to start with. > > OK, so I agree with this and Julia's later sentiment about getting things > started in a git repo. > > Let's work on these in parallel, how about this as a process: > > 1. If you want to be part of the discussion right now, let's work on this > document together: > > https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13 > > That is a straw-draft, meaning it's something we can build a "discussion > draft" from. > > 2. Next opportunity is helping build the discussion draft. You can > continue from straw-draft work or join in for that round of > writing-and-editing. > > We'll have time in between each step for broad, general feedback. > > 3. The discussion draft is what we take to the wider OpenInfrastructure > community for feedback. > > That is three wide rounds of feedback, at least. We can slow down and add > more, if needed. > > Some of that work can occur in live, high-bandwidth meetings. We also need > to commit to coming back and keeping this list well informed. > > Your participation in this is very, very welcome, whenever you arrive into > the process. Even when we are "finished" and moving on, we need to really > understand our vision and mission as living documents. Maybe we want to > have regular review and refresh stages every few years, for example? Just > to keep things from getting stale and forgotten. > > Kind regards, > - Karsten > > > Thanks, > > > > -Julia > > > > _______________________________________________ > > Openinfralabs mailing list > > Openinfralabs at lists.opendev.org > > https://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > > > > > -- > Karsten Wade [he/him/his] | Principal Community Architect | @quaid > Red Hat Open Source Program Office (OSPO) : @redhatopen > The Open Source Way : https://theopensourceway.org > Operate First : https://operate-first.cloud > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > https://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > -- *Hugh Brock* hbrock at redhat.com, he/him Director, Red Hat Research Subscribe to Red Hat Research Quarterly today! --- "I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant." --Robert McCloskey -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Fri Aug 19 16:48:53 2022 From: kennelson11 at gmail.com (Kendall Nelson) Date: Fri, 19 Aug 2022 11:48:53 -0500 Subject: [Openinfralabs] Fwd: Virtual PTG October 2022 Team Signup Reminder - Last Call In-Reply-To: References: Message-ID: Hello Everyone, This is your last call to sign up your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, October 17 to Friday, October 21st, 2022! NOTE: Since we are now hosting the PTG virtually, we will be holding the event all week (Monday - Friday) and will be using the ?normal? virtual schedule of 4 hour blocks of time covering hours for Americas/APAC, APAC/Europe+Africa, and Europe+Africa/Americas. If you haven't already done so and your team is interested in participating, please complete the survey[1] by August 26th, 2022 at 7:00 UTC. Then make sure to register[2] - it?s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] PTG Registration: https://openinfra-ptg.eventbrite.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From juliaashleykreger at gmail.com Tue Aug 23 15:50:24 2022 From: juliaashleykreger at gmail.com (Julia Kreger) Date: Tue, 23 Aug 2022 08:50:24 -0700 Subject: [Openinfralabs] Rebuilding the core discussion In-Reply-To: References: Message-ID: In accordance with the Open Source contributor, "my apologies for the delay" rule :) Sorry, I've been super occupied the past two weeks. Comments in-line. On Thu, Aug 11, 2022 at 4:20 PM Karsten Wade wrote: > > Thank you Julia for starting this discussion about getting involved in a reset and what to do next. And I appreciate your patience as people (like me!) get my head together and into this discussion (eventually) around important change management, here in the middle of atypically busy months. > > Hi all, > > I haven't posted much (at all?) to this mailing list, I'm one of the "few of us" Julia refers to below. I'm the community architect for the Operate First project ? meaning my role is to lead the design and implementation of a plan to create and scale Open Source communities ? as well as the co-Chair of the Operate First Community Special Interest Group (SIG). I have a vested interest in having a defined mission and governance for Open Infra Labs as a project within the Labs. > > From later in this thread, I agree about beginning work in our GitHub repository as the commons where we can draw the most brains and hands (today). I would love to *eventually* move it over to gerrit. But any git, I think is better. I've got a list of things to discuss with the OpenDev folks, hopefully during the PTG, to work on easing access/use/engagement. I *really* think we've got some discoverability issues mixed in here which makes it difficult for existing folks to grok what is going on and vise versa, but those are entirely independent. > > tl;dr of below: > 1. I propose a three step process to write the vision and mission, including lots of time for feedback > 2. To kick it off, I made this PR: https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13 > - Under the "FIles Changed" section ( https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13/files ) you can make line-by-line comments by clicking the + sign next to the line number, and you can use the [+-] button to suggest specific changes. > 3. That's it! > Sounds good to me! I've left a few comments there, but overall most of them are along the lines of a feeling like we need to swap mission/vision and maybe provide some historical context, which it does do. I've shared a blog post from Zingtrain on 'The Power of Visioning"[0], which we've used previously in the OpenInfra community which primarily talks about the visioning aspects. [0]: https://www.zingtrain.com/article/the-power-of-visioning/ > Some comments/questions inline below: > > On Fri, Jul 8, 2022 at 1:26 PM Julia Kreger wrote: > > > > Greetings everyone, > > > > During our recent Open Infrastructure Summit in Berlin, one of the > > repeated discussion topics I found myself engaged in suggested a > > breakdown in shared context and communication within OpenInfra Labs. A > > bit of a root cause analysis occurred, and each discussion quickly > > determined there is definitely no fault, but more a result of the > > state of engagement which collided against the pandemic. Further > > compounded by the time schedule differences which run our various > > lives and efforts. It did not help us that we did not use the same > > words to begin with. > > In our discussions in Berlin and beyond, I think I've characterized it as something to the effect of, > > "We never finished getting alignment before everyone's attention turned to the pandemic. When we drew our attention back out to work on these problems, we saw other people seemed to be out of alignment and on their own paths. Then each of us (person or group) forked just a bit more in chasing our version of the mission while seeing each other as out of alignment with our own vision." > ++ > > A few of us have continued going back and forth over the last few > > weeks and we've reached the conclusion we need to rebuild the core > > consensus and discussion. Ultimately a revision of our mission and > > long term vision, in order to better support the sharing of knowledge > > and context which is fundamentally needed to support the efforts > > occurring within OpenInfra Labs. > > > > Before we really continue onward in these discussions, I think it is > > important for us to widen the audience of engagement and enable a > > greater chorus of voices to engage as we sort of press the reset > > button in order to set expectations, intents, and bring us all back to > > a happier, engaged place. In recognition that no single tool or means > > will work for everyone, *and* to help provide insight for those that > > don't necessarily subscribe to mailing lists or whom are unable to > > join our discussions now, the idea has been floated to write about it. > > Such as a blog or a journal. To share our story. To share the stories. > > To spread the knowledge! > > > > I think we should start with high bandwidth calls to reach the same > > page, and then move forward from there. > > > > If you're interested in engaging in this discussion, please reply with > > to this email with the days of the week and times that would work, or > > that would not work, and I'll try to find a mutually agreeable 30 > > minute window every two weeks for us to start with. > > OK, so I agree with this and Julia's later sentiment about getting things started in a git repo. > > Let's work on these in parallel, how about this as a process: > > 1. If you want to be part of the discussion right now, let's work on this document together: > > https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13 > > That is a straw-draft, meaning it's something we can build a "discussion draft" from. > > 2. Next opportunity is helping build the discussion draft. You can continue from straw-draft work or join in for that round of writing-and-editing. > > We'll have time in between each step for broad, general feedback. ++, we should setup a meeting in a couple of weeks to force engagement/interaction. I need someone to drive the scheduling aspect if at all possible. Any volunteers? > > 3. The discussion draft is what we take to the wider OpenInfrastructure community for feedback. > > That is three wide rounds of feedback, at least. We can slow down and add more, if needed. > > Some of that work can occur in live, high-bandwidth meetings. We also need to commit to coming back and keeping this list well informed. > ++, we are likely a little early, but perhaps we can find some time during the week of the project team's gathering. > Your participation in this is very, very welcome, whenever you arrive into the process. Even when we are "finished" and moving on, we need to really understand our vision and mission as living documents. Maybe we want to have regular review and refresh stages every few years, for example? Just to keep things from getting stale and forgotten. I've found it *surprisingly* difficult to get people to come back to revising mission/vision statements as time has gone on. Visions being far easier, since it is more the guiding light. I think mostly that is due to people just being busy. But I do agree, this is something that should be done. > > Kind regards, > - Karsten > > > Thanks, > > > > -Julia > > > > _______________________________________________ > > Openinfralabs mailing list > > Openinfralabs at lists.opendev.org > > https://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > > > > > -- > Karsten Wade [he/him/his] | Principal Community Architect | @quaid > Red Hat Open Source Program Office (OSPO) : @redhatopen > The Open Source Way : https://theopensourceway.org > Operate First : https://operate-first.cloud From juliaashleykreger at gmail.com Tue Aug 23 15:57:04 2022 From: juliaashleykreger at gmail.com (Julia Kreger) Date: Tue, 23 Aug 2022 08:57:04 -0700 Subject: [Openinfralabs] Rebuilding the core discussion In-Reply-To: References: Message-ID: On Mon, Aug 15, 2022 at 12:55 PM Hugh Brock wrote: > Thanks for doing this Karsten. > > Do we need to reconvene at some point, maybe around a deadline for the > first draft of your doc? I'm keen to get this moving in the right direction. > I absolutely agree that we need to do so, but we've got ~1-2 week lag in being able to cycle between emails and distinctly different topics. At least, that is in my case. :) I originally wanted to try and make progress "before august" in order to hopefully make a splash in advance of the PTG. Perhaps we might still be able to, but I think we need to get some traction to increase velocity of interaction in the next week or so. -J > Take care, > --Hugh > > On Thu, Aug 11, 2022 at 7:20 PM Karsten Wade wrote: > >> Thank you Julia for starting this discussion about getting involved in a >> reset and what to do next. And I appreciate your patience as people (like >> me!) get my head together and into this discussion (eventually) around >> important change management, here in the middle of atypically busy months. >> >> Hi all, >> >> I haven't posted much (at all?) to this mailing list, I'm one of the "few >> of us" Julia refers to below. I'm the community architect for the Operate >> First project ? meaning my role is to lead the design and implementation of >> a plan to create and scale Open Source communities ? as well as the >> co-Chair of the Operate First Community Special Interest Group (SIG). I >> have a vested interest in having a defined mission and governance for Open >> Infra Labs as a project within the Labs. >> >> From later in this thread, I agree about beginning work in our GitHub >> repository as the commons where we can draw the most brains and hands >> (today). >> >> tl;dr of below: >> 1. I propose a three step process to write the vision and mission, >> including lots of time for feedback >> 2. To kick it off, I made this PR: >> https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13 >> - Under the "FIles Changed" section ( >> https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13/files >> ) you can make line-by-line comments by clicking the + sign next to the >> line number, and you can use the [+-] button to suggest specific changes. >> 3. That's it! >> >> Some comments/questions inline below: >> >> On Fri, Jul 8, 2022 at 1:26 PM Julia Kreger >> wrote: >> > >> > Greetings everyone, >> > >> > During our recent Open Infrastructure Summit in Berlin, one of the >> > repeated discussion topics I found myself engaged in suggested a >> > breakdown in shared context and communication within OpenInfra Labs. A >> > bit of a root cause analysis occurred, and each discussion quickly >> > determined there is definitely no fault, but more a result of the >> > state of engagement which collided against the pandemic. Further >> > compounded by the time schedule differences which run our various >> > lives and efforts. It did not help us that we did not use the same >> > words to begin with. >> >> In our discussions in Berlin and beyond, I think I've characterized it as >> something to the effect of, >> >> "We never finished getting alignment before everyone's attention turned >> to the pandemic. When we drew our attention back out to work on these >> problems, we saw other people seemed to be out of alignment and on their >> own paths. Then each of us (person or group) forked just a bit more in >> chasing our version of the mission while seeing each other as out of >> alignment with our own vision." >> >> > A few of us have continued going back and forth over the last few >> > weeks and we've reached the conclusion we need to rebuild the core >> > consensus and discussion. Ultimately a revision of our mission and >> > long term vision, in order to better support the sharing of knowledge >> > and context which is fundamentally needed to support the efforts >> > occurring within OpenInfra Labs. >> > >> > Before we really continue onward in these discussions, I think it is >> > important for us to widen the audience of engagement and enable a >> > greater chorus of voices to engage as we sort of press the reset >> > button in order to set expectations, intents, and bring us all back to >> > a happier, engaged place. In recognition that no single tool or means >> > will work for everyone, *and* to help provide insight for those that >> > don't necessarily subscribe to mailing lists or whom are unable to >> > join our discussions now, the idea has been floated to write about it. >> > Such as a blog or a journal. To share our story. To share the stories. >> > To spread the knowledge! >> > >> > I think we should start with high bandwidth calls to reach the same >> > page, and then move forward from there. >> > >> > If you're interested in engaging in this discussion, please reply with >> > to this email with the days of the week and times that would work, or >> > that would not work, and I'll try to find a mutually agreeable 30 >> > minute window every two weeks for us to start with. >> >> OK, so I agree with this and Julia's later sentiment about getting things >> started in a git repo. >> >> Let's work on these in parallel, how about this as a process: >> >> 1. If you want to be part of the discussion right now, let's work on this >> document together: >> >> https://github.com/open-infrastructure-labs/openinfralabs-website/pull/13 >> >> That is a straw-draft, meaning it's something we can build a "discussion >> draft" from. >> >> 2. Next opportunity is helping build the discussion draft. You can >> continue from straw-draft work or join in for that round of >> writing-and-editing. >> >> We'll have time in between each step for broad, general feedback. >> >> 3. The discussion draft is what we take to the wider OpenInfrastructure >> community for feedback. >> >> That is three wide rounds of feedback, at least. We can slow down and add >> more, if needed. >> >> Some of that work can occur in live, high-bandwidth meetings. We also >> need to commit to coming back and keeping this list well informed. >> >> Your participation in this is very, very welcome, whenever you arrive >> into the process. Even when we are "finished" and moving on, we need to >> really understand our vision and mission as living documents. Maybe we want >> to have regular review and refresh stages every few years, for example? >> Just to keep things from getting stale and forgotten. >> >> Kind regards, >> - Karsten >> >> > Thanks, >> > >> > -Julia >> > >> > _______________________________________________ >> > Openinfralabs mailing list >> > Openinfralabs at lists.opendev.org >> > https://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >> > >> >> >> -- >> Karsten Wade [he/him/his] | Principal Community Architect | @quaid >> Red Hat Open Source Program Office (OSPO) : @redhatopen >> The Open Source Way : https://theopensourceway.org >> Operate First : https://operate-first.cloud >> _______________________________________________ >> Openinfralabs mailing list >> Openinfralabs at lists.opendev.org >> https://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >> > > > -- > *Hugh Brock* > hbrock at redhat.com, he/him > Director, Red Hat Research > Subscribe to Red Hat Research Quarterly today! > > > --- > "I know that you believe you understand what you think I said, but I'm not > sure you realize that what you heard is not what I meant." --Robert > McCloskey > -------------- next part -------------- An HTML attachment was scrubbed... URL: