[Podman] Re: Podman Community Meeting - Tues June 1, 2021 11:00 a.m. EDT (UTC-4)

We'd probably start it in Google Meet or BlueJeans

Urvashi, let's talk details?

I know Dan replied, and I've meant to tie off with Urvashi about this next bit. We've talked about it briefly, but haven't dottted all the i's or crossed all the t's yet. What I'm suggesting to Urvashi is to covert the standup meeting that she runs for the Red Hat folks on the third Thursday of the month to an open ended standup meeting, open to anyone in the community. If people dial into the conference, we'll take any questions that we can handle in the hour that the standup runs. If no one shows, then we'll just do our usual standup. That meeting happens at 11:00 a.m. on that Thursday and I would send out reminders via this list and twitter for folks to join in. We'd probably start it in Google Meet or BlueJeans, if it got too big, we could talk about Twitch, YouTube or some other platform later. Currently the community meeting is getting about 30 to 50 attendees. Would that work? Urvashi, let's talk details? t ps. Sorry for the tardy reply, my inbox is overflowing as of late. On 6/9/21 1:50 PM, Erik Bernoth wrote: Alright, I didn't get more responses, so I think payout for invested time is the key issue. For me, Podman is a key technology that could be running everywhere, including Mars rovers, including smart phones (let's face it, Apps are basically containers), etc. Everywhere where IoT can be used podman makes sense. And the amount of IoT that surrounds us will just grow. So it's a huge project, even if it hasn't reached that scale yet in terms of daily work. Therefore, I would say that the community interaction should also be thought of in these terms. And if I look at other big projects, they often have community office hours, where users can bring in discussion topics. E.g. https://github.com/kubernetes/community/blob/master/events/office-hours.md So the value of thinking big in terms of community management is huge. But the personal time investment of individual people doesn't have to be. A few ideas: (1) The work could be split up, like cleaning the kitchen in a shared apartment (2) Users could be involved in the facilitation of individual sessions (3) One could look for other companies that would be interested enough in this project's growth to add some headcount (e.g., big customers) (4) One could find other companies that want to create something similar and keep an eye on what this project is doing (thinking Apple might be wanting to build their own container engine on their own kernel but make sure the CLI is almost identical) (5) There might be other FOSS projects that have, or could have in the future, a high dependency on Podman's success, and therefore might be interested in sharing community management resources (6) If we can think up an experiment that can show community traction (or even better: customer traction), and that experiment succeeds, then usually management is happy to add a headcount or two So, it doesn't mean that people who are busy crunching bugs would have attend an online meeting every week. What do you think about that? Do you have other ideas that I could add to the list? Best, Erik PS: I have to admit that after only getting a response from Dan, I was a little frustrated. My main intention when I started this was trying to figure out if I can use my newly acquired Agile skills in the project. But I don't think I can transfer these skills from colorful sticky notes to IRC messages. If someone has an idea who else might have tried something like that, I'm also curious to learn about it. What I am doing now with that desire is I'm looking for communities that work more with audio-visual communication anyways. And maybe there's still some opportunity to combine both through (5) in the future. On Mon, 31 May 2021 at 09:28, Erik Bernoth <erik.bernoth(a)gmail.com&gt; wrote: > Thanks for sharing, Dan! > > I also want to share a worry that I have: As I was the one suggesting, I > worry that the success of the idea fully depends on me doing all the work > forever to keep it going, > and that my success as a member of the community would be measured only > in the value of that mini-project. > Logically I already know that this is not the case, but I'm not always > logical. > > Worries about weekly video call: > - time commitment > - personal responsibility and impact > > What other possible problems might we encounter? > > On Sun, 30 May 2021 at 13:09, Daniel Walsh <dwalsh(a)redhat.com&gt; wrote: > >> On 5/30/21 02:41, Erik Bernoth wrote: >> >> Thanks a lot for all the inputs. >> >> From what I see, I would say that extending the Open Forum part of the >> meeting would require other people cutting their allotted speaking time. >> If they don't have much to share anyways, then that is okay. But usually >> that doesn't sound like a good exchange for me, allowing one person to >> speak more >> by decreasing what is accepted for another person. >> >> Mainly peoples commitment of time. We could try an IRC Meeting like >> this, where people could partially pay attention, but have a video meeting >> on a weekly basis, might be a time sync, with limited benefit. >> >> So, I was thinking. What would stop us from doing a weekly meeting that >> is mostly Open Forum? Then the monthly meeting would be free for the >> preplanned >> agenda items, right? >> >> Best, >> Erik >> >> On Thu, 27 May 2021 at 22:56, Tom Sweeney <tom.sweeney(a)redhat.com&gt; >> wrote: >> >>> Brent, >>> >>> Thanks let's plan on dropping the demo unless there's a new twist or >>> two from the last time. If folks still want to see the demo, perhaps you >>> could run them through it after the Open Forum time. >>> >>> t >>> >>> On 5/27/21 1:52 PM, Brent Baude wrote: >>> >>> @Tom Sweeney <tsweeney(a)redhat.com&gt; >>> >>> I think I could shorten my presentation and instead of giving a demo >>> (which has been done already), I can give a state of affairs on where we >>> are, what is left to be done, etc. That should free up some extra time. >>> >>> >>> On Thu, May 27, 2021 at 9:39 AM Daniel Walsh <dwalsh(a)redhat.com&gt; wrote: >>> >>>> On 5/27/21 09:46, Erik Bernoth wrote: >>>> >>>> Hi Tom and others, >>>> >>>> With 5 minutes the Open Forum seems a little short to really discuss a >>>> topic that is not on the agenda. Are there other communities or regular >>>> events (e.g. with Fedora or OCI) >>>> where people can discuss ideas and questions with video+audio and >>>> podman developers present? >>>> Some topics take just so much longer when discussed via email. How are >>>> these usually treated in this community? >>>> >>>> Best, >>>> Erik >>>> >>>> If you want more time, please suggest a topic and specify the amount >>>> of time you would like. >>>> >>>> On Thu, 20 May 2021 at 20:08, Tom Sweeney <tom.sweeney(a)redhat.com&gt; >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> Just a quick note that the next Podman Community Meeting is >>>>> coming >>>>> up a week from this coming Tuesday. It will be Tuesday June 1, 2021 >>>>> at >>>>> 11:00 a.m. EDT (UTC-4). We're overloaded with topics this time and >>>>> will be talking about Podman and TYE, Podman v3.2.0 updates, Podman >>>>> in >>>>> Kubernetes and Podman Machine updates. The full agenda with the link >>>>> to >>>>> the video conference is here >>>>> (https://podman.io/community/meeting/agenda/). Check out the link >>>>> to >>>>> WorldTImeBuddy at the top of the web page for the agenda for an easy >>>>> time converter for your local time. As usual, no charge to attend! >>>>> >>>>> Also, I just posted the meeting notes from the May 2021 >>>>> meeting. >>>>> They include links to the slides on Sysbox runtime, a link to the >>>>> video >>>>> recording and my bad attempt at taking notes during the meeting. >>>>> https://podman.io/community/meeting/notes/2021-05-04/ >>>>> >>>>> As a quick note, given the number of people that we've heard >>>>> from >>>>> who will be on vacation in early July, we have decided to not hold >>>>> the >>>>> meeting that month. Our following meeting will be Tuesday August >>>>> 3rd, >>>>> also at 11:00 a.m. EDT (UTC-4). >>>>> >>>>> t >>>>> _______________________________________________ >>>>> Podman mailing list -- podman(a)lists.podman.io >>>>> To unsubscribe send an email to podman-leave(a)lists.podman.io >>>>> >>>> >>>> _______________________________________________ >>>> Podman mailing list -- podman(a)lists.podman.io >>>> To unsubscribe send an email to podman-leave(a)lists.podman.io >>>> >>>> >>>> _______________________________________________ >>>> Podman mailing list -- podman(a)lists.podman.io >>>> To unsubscribe send an email to podman-leave(a)lists.podman.io >>>> >>> >>> _______________________________________________ >>> Podman mailing list -- podman(a)lists.podman.io >>> To unsubscribe send an email to podman-leave(a)lists.podman.io >>> >> >>