[Openinfralabs] Rebuilding the core discussion

Tue Aug 23 15:57:04 UTC 2022

On Mon, Aug 15, 2022 at 12:55 PM Hugh Brock <hbrock at redhat.com> 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 <kwade at redhat.com> 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 <juliaashleykreger at gmail.com>
>> 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 <http://research.redhat.com>
> Subscribe to Red Hat Research Quarterly today!
> <https://research.redhat.com/quarterly/>
>
> ---
> "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: <https://lists.opendev.org/pipermail/openinfralabs/attachments/20220823/6bbea7ed/attachment-0001.htm>