# Podman Core Maintainers Meeting Minutes

**Date:** June 26, 2026
**Time:** 14:28 UTC

---

## 1. Meeting Overview & Attendance

### Present Attendees
* **Matthew Heon** (Red Hat LLC) — Meeting Chair
* **Paul Holzinger** (Red Hat)
* **Brent** (Red Hat LLC)
* **Mohan Boddu** (Red Hat LLC)
* **Giuseppe Scrivano** (Red Hat LLC)
* **Miloslav Trmac** (Red Hat LLC)
* **Nalin Dahyabhai** (Red Hat LLC)
* **Tom Sweeney** (Red Hat LLC)
* **Laura Santamaria** (Red Hat LLC)
* **Ashley Cui** (Red Hat LLC)

---

## 2. Agenda & Discussion Items

### 2.1. Auditing Permissions Outside of GitHub
* **Context:** Paul Holzinger raised the issue of tracking and auditing administrative permissions for third-party integrations, services, and channels that operate outside of GitHub's access controls.
* **Identified Assets:** * The `podman.io` mailing list (currently hosted on Mailman by the Red Hat Open Source Program Office [OSPO], not CNCF-owned).
  * The official project blog.
  * CNCF Oracle Cloud infrastructure accounts.
  * Read the Docs documentation site (`docs.podman.io`).
  * Community communication channels (Matrix and Discord).
* **Key Concerns:** While adding new contributors is straightforward, removing access for inactive or departed members is often forgotten. For example, a former maintainer (Urvashi Mohnani) still retained access to Read the Docs three years after becoming inactive. Additionally, community channels suffer from spam, and not all active maintainers currently have the necessary moderator privileges to handle it promptly.
* **Proposals & Solutions:** * Mohan Boddu suggested looking into an automated daily script tied to a single source of truth for all access controls.
  * Miloslav Trmac noted that while OAuth and Single Sign-On (SSO) are ideal, they are often gated behind enterprise tiers which may not be available for open-source project accounts.
  * A consensus was reached that all repository maintainers should, at a minimum, be granted moderator permissions on community channels (Matrix/Discord) to clean up spam when primary admins are unavailable.
* **Decisions & Action Items:**
  * **Action Item:** Paul Holzinger volunteered to lead the first step, which involves conducting a comprehensive audit of all non-GitHub assets owned by the project, analyzing their authentication systems, and compiling a definitive access list.
  * **Decision:** The team agreed to establish a **private GitHub repository** restricted to core maintainers to securely store asset details, documentation, and sensitive audit records.

### 2.2. CNCF Incubation Application Status
* **Context:** The core maintainers discovered that a CNCF Incubation Application had been filed last week on behalf of Podman. This violated an explicit agreement from the previous meeting stating that no advancement toward incubation would occur without a formal vote and approval from the core maintainers.
* **Issues Identified:**
  * The application was filed without a core maintainer vote or prior notification.
  * The submission used an outdated/incorrect template, which would trigger an automatic rejection by the CNCF.
  * The application contained inaccurate details, falsely listing external projects like `crun` and `Podman Desktop` as official sub-projects.
  * The project is not yet structurally prepared for incubation: it lacks a sufficient number of documented adopters and requires a more diversified, non-Red Hat maintainer base (having only recently onboarded its first non-Red Hat maintainer). An official rejection at this stage could negatively impact the project's reputation.
* **Decisions & Action Items:**
  * **Decision:** The core maintainers voted unanimously to stop and withdraw the current incubation application until the project is genuinely ready.
  * **Action Item:** Matthew Heon will formally contact the CNCF post-meeting to request the immediate closure and withdrawal of the application.
  * **Action Item:** To present a unified front, all core maintainers agreed to add public comments to the open GitHub issue indicating that this was a collective maintainer decision.
  * **Action Item:** Matthew Heon will post the meeting transcript to the Podman repository to maintain an open public record, and will share the issue link in the `Podman Dev` channel for maintainer responses.

### 2.3. Proposal for a Shared Documentation Repository (`community`)
* **Context:** Brent followed up on an ongoing discussion regarding the creation of a dedicated repository under the organization to host non-code, project-wide administrative documents (e.g., project governance, code of conduct, security policies, contribution guidelines, and commit formats).
* **Discussion:** Currently, these files live in the main Podman repository, which has inadvertently turned it into a top-level organization repository. Moving these files to a standalone, low-traffic repository allows community members to track governance updates without wading through high-volume code issues. Laura Santamaria noted that this follows a standard industry pattern and strongly recommended naming the repository `community`.
* **Decisions & Action Items:**
  * **Decision:** Approved the creation of the repository, officially named **`community`**.
  * **Action Item:** Brent will utilize his organization privileges to create the new repository.
  * **Action Item:** Mohan Boddu will take ownership of populating the initial content, with Ashley Cui providing additional support as needed.

### 2.4. Migration of Remaining Repositories to CNCF Organization
* **Context:** The team reviewed the ongoing effort to migrate repositories into the CNCF-governed structure. The migration is roughly 50% complete, with all repositories requiring Continuous Integration (CI) successfully moved.
* **Remaining Repositories:** The outstanding assets include the `podman.io` and `buildah.io` websites, `go.podman.io` (used for Go vanity imports), and the `image_build` repository (which currently has an open pull request requiring review).
* **Discussion on Consolidation:** Mohan Boddu raised a previous discussion about merging the `netavark` and `aardvark-dns` repositories prior to migration. Matthew Heon supported this to minimize administrative overhead. However, Paul Holzinger noted there is no immediate pressure to move them, and Brent explicitly expressed opposition to moving or merging them at this time. The decision on those specific repos was deferred.
* **Decisions & Action Items:**
  * **Decision:** The migration will proceed for the core remaining repos that meet the established criteria (fundamentally related to Podman, matching licensing/governance rules, and approved by maintainers).
  * **Action Item:** Matthew Heon will continue to lead the migration process for `podman.io`, `buildah.io`, `go.podman.io`, and `image_build`, including coordinating the necessary maintainer votes.

### 2.5. Quarterly Audit of Maintainer Files
* **Context:** The quarterly schedule for auditing maintainer files has arrived. The goal is to review active contributions and transition inactive maintainers to more appropriate or emeritus roles.
* **Decisions & Action Items:**
  * **Decision:** Matthew Heon was designated to review all project repositories and draft a proposal identifying inactive maintainers for removal or role adjustments.

---

## 3. Summary of Action Items

| Owner                | Action Item                                                                                               |
|:---------------------|:----------------------------------------------------------------------------------------------------------|
| **Paul Holzinger**   | Conduct a comprehensive audit of all non-GitHub project assets.                                           |
| **Matthew Heon**     | Contact the CNCF to officially withdraw the unauthorized incubation application.                          |
| **Core Maintainers** | Post public comments on the open incubation GitHub issue to confirm the joint decision.                   |
| **Matthew Heon**     | Upload the meeting transcript to the repository and share the issue link in `Podman Dev`.                 |
| **Brent**            | Create the new `community` GitHub repository under organization settings.                                 |
| **Mohan Boddu**      | Populate the newly created `community` repository with governance and policy files.                       |
| **Ashley Cui**       | Assist Mohan Boddu with population and review of the `community` repository.                              |
| **Matthew Heon**     | Drive the migration and maintainer votes for `podman.io`, `buildah.io`, `go.podman.io`, and `image_build`. |
| **Matthew Heon**     | Review all maintainer files across project repos and propose updates for inactive members.                |

---
*These minutes were generated by AI. A full transcript of the meeting is below.*

## 4. Transcript

Unrelated chatter at beginning of meeting has been trimmed for brevity

25
00:04:00.360 --> 00:04:07.990
Matthew Heon (Red Hat LLC): Okay, sorry about that. I had to re-invite Brent. Hopefully he will join in the next couple minutes.

26
00:04:08.360 --> 00:04:10.460
Matthew Heon (Red Hat LLC): In the meantime, I think we can…

27
00:04:10.660 --> 00:04:16.930
Matthew Heon (Red Hat LLC): Probably get started with some of the, easier to deal with, matters on the agenda.

28
00:04:17.250 --> 00:04:26.900
Matthew Heon (Red Hat LLC): So, first thing I would like to go over is a suggestion from Paul. How do we audit permissions outside of GitHub?

29
00:04:26.900 --> 00:04:39.410
Matthew Heon (Red Hat LLC): Including who has access to and control over the Podman mailing list, access to things like our blog, yeah. So, Paul, you wanna leave this one off?

30
00:04:42.830 --> 00:04:48.260
Paul Holzinger: Yeah, I don't… I don't have a proposal or anything, I think it's just something to be aware of, yes.

31
00:04:48.430 --> 00:04:50.310
Paul Holzinger: I don't know how many other…

32
00:04:50.990 --> 00:04:57.590
Paul Holzinger: third-party integrations or tools where there's different authentication and…

33
00:04:58.200 --> 00:05:05.360
Paul Holzinger: You know, we can, update our maintainer files, I think we can reasonably be well audit GitHub permissions.

34
00:05:05.870 --> 00:05:11.080
Paul Holzinger: But… yeah, like, I don't know, everything else, the…

35
00:05:11.300 --> 00:05:16.289
Paul Holzinger: Podman.io mailing list has different logins, with different people having access.

36
00:05:17.090 --> 00:05:23.920
Paul Holzinger: The block is different, the… we got a CNCF Oracle Cloud account, which…

37
00:05:24.210 --> 00:05:28.109
Paul Holzinger: I guess it's also just personal accounts and some email you have.

38
00:05:28.520 --> 00:05:29.830
Paul Holzinger: for, like…

39
00:05:30.400 --> 00:05:42.180
Paul Holzinger: I mean, adding people that need access is always easy. It's remembering to kick people out when they no longer should have access. That's more the concern, I guess.

40
00:05:49.610 --> 00:05:53.480
Mohan Boddu (Red Hat LLC): Is there a way that we can maintain a single source of truth?

41
00:05:53.820 --> 00:06:01.860
Mohan Boddu (Red Hat LLC): But… Kind of, like, runs every day to update all the access controls.

42
00:06:05.020 --> 00:06:16.279
Miloslav Trmac (Red Hat LLC): I think the traditional solution is to use OAuth and single sign-on everywhere, but then accepting OAuth is an enterprise feature that might not be available to us.

43
00:06:23.660 --> 00:06:30.760
Paul Holzinger: Yeah, I mean, the single sign-on would definitely be lovely, but the next problem would be even convincing the various

44
00:06:31.720 --> 00:06:32.390
Paul Holzinger: Holy crap.

45
00:06:32.390 --> 00:06:34.890
Miloslav Trmac (Red Hat LLC): Who lost that in the first place, right?

46
00:06:36.710 --> 00:06:47.300
Paul Holzinger: Yeah, I mean, so Podman I.O. mailing list, that's another thing, is, as far as I know, this is still hosted by the OSPO, by the Red Hat OSPO, this is not something CNCF.

47
00:06:47.710 --> 00:06:48.760
Paul Holzinger: owned.

48
00:06:49.380 --> 00:06:57.280
Paul Holzinger: And that's just, what is this, mailman tree, or whatever that's running? I don't know.

49
00:06:58.280 --> 00:06:59.400
Paul Holzinger: And…

50
00:06:59.960 --> 00:07:06.510
Paul Holzinger: I don't know, there's probably something that could be done for something like that, but yeah, there's so many random… like, I'm…

51
00:07:07.150 --> 00:07:24.369
Paul Holzinger: We can definitely try to automate some stuff, if they have APIs for, like, the off stuff, but yeah, it's just, like, a general problem of, like, anything. Like, if you think further, there's a read the docs page for docs.potment.io. How do we make sure that people have access to that?

52
00:07:24.610 --> 00:07:34.410
Paul Holzinger: I have, Brent has, and when I had to make a change this week, I saw, like, for example, we have Wagashi there, who had the exercise, which…

53
00:07:34.760 --> 00:07:42.899
Paul Holzinger: She had, because she was a maintainer, but, like, 3 years ago, not anymore, so, like, how do we, you know, remember?

54
00:07:44.410 --> 00:07:50.030
Paul Holzinger: or even start knowing where we have all these tokens, I think that's the first thing, like, I don't know.

55
00:07:50.390 --> 00:07:57.859
Paul Holzinger: There's probably a lot of things that we don't remember, even, that people might… eat stuff from.

56
00:07:59.740 --> 00:08:06.529
Matthew Heon (Red Hat LLC): I mean, Dan is still… basically has access to everything, I think, right? So we could probably…

57
00:08:06.770 --> 00:08:13.499
Matthew Heon (Red Hat LLC): I don't… he's still technically a builder maintainer, but he's not active enough to have access to most of this stuff anymore, so we can also…

58
00:08:13.930 --> 00:08:28.319
Matthew Heon (Red Hat LLC): Yeah, I think an audit… I mean, would the first step here just be an audit of the stuff that we actually have? I don't think we have a conclusive list anywhere of all the stuff that we actually maintain for the project.

59
00:08:30.550 --> 00:08:35.710
Paul Holzinger: Yeah, I think that's the first thing, just figuring out What?

60
00:08:35.900 --> 00:08:39.890
Paul Holzinger: Kind of things we own as a collective project, and…

61
00:08:40.289 --> 00:08:48.929
Paul Holzinger: then checking how the authentication systems work, I guess, and who has access. Like, another thing is, that I haven't mentioned yet.

62
00:08:49.200 --> 00:08:54.680
Paul Holzinger: our community channels, like, we have a Matrix channel, there's a Discord server.

63
00:08:54.850 --> 00:08:59.080
Paul Holzinger: But, you know, like, there's a lot of things, basically.

64
00:09:01.370 --> 00:09:10.609
Paul Holzinger: And, for example, I think everybody should have at least, like, moderator access to these channels. Like, if somebody is doing stupid stuff there, they should be able to then…

65
00:09:10.910 --> 00:09:13.150
Paul Holzinger: people, right? Like, I mean, we get a lot of

66
00:09:14.010 --> 00:09:20.749
Paul Holzinger: Yeah, the usual spam, what you get in these channels, like, it would be nice if everybody has the ability to remove those, if,

67
00:09:20.940 --> 00:09:29.949
Paul Holzinger: people with access are not around, because the current list is definitely smaller than the list of all the possible maintainers in all repos, I think.

68
00:09:36.300 --> 00:09:53.699
Matthew Heon (Red Hat LLC): So, it does sound like our first step is, just do an audit of things that we own, so we can produce a list of that, and then from there, we can extend auditing permissions on everything, and then from there, we can extend even further to… maybe there's a way to have a single source of truth.

69
00:09:53.900 --> 00:10:03.089
Matthew Heon (Red Hat LLC): Does anyone want to own this work, at least the first step of figuring out the stuff that we are… that is associated with the project, and ideally making a list of it?

70
00:10:05.400 --> 00:10:06.899
Paul Holzinger: I, I can take that.

71
00:10:07.790 --> 00:10:09.489
Matthew Heon (Red Hat LLC): Okay. Thank you, Paul.

72
00:10:11.580 --> 00:10:13.510
Matthew Heon (Red Hat LLC): All right.

73
00:10:13.510 --> 00:10:16.379
Miloslav Trmac (Red Hat LLC): Yes, we can keep the address reasonably private.

74
00:10:19.800 --> 00:10:24.229
Miloslav Trmac (Red Hat LLC): Probably not worth worrying right now, but eventually there might be weak links there.

75
00:10:26.790 --> 00:10:28.560
Matthew Heon (Red Hat LLC): I mean, we have…

76
00:10:29.400 --> 00:10:41.139
Matthew Heon (Red Hat LLC): Topic 2 was going to be, creating a GitHub repository for all of our public content, that being stuff like the governance and, maintainer lists.

77
00:10:41.390 --> 00:10:57.490
Matthew Heon (Red Hat LLC): But that would not be a private place, that would be completely public. I don't know. Maybe we can ask the CNCF if we can have an internal repo that we can… or a private repo, rather, on GitHub, that we can access control to just maintainers.

78
00:11:01.000 --> 00:11:09.859
Paul Holzinger: like, creating private repos, that's possible, like, I mean, you are owners, you, like, I don't think there's any restriction,

79
00:11:11.360 --> 00:11:14.400
Paul Holzinger: from the, like, GNCF org thing.

80
00:11:15.310 --> 00:11:18.840
Matthew Heon (Red Hat LLC): Okay Alright, in that case, yeah.

81
00:11:19.060 --> 00:11:23.369
Matthew Heon (Red Hat LLC): I would vote that we just make a private repo, and we store all details there.

82
00:11:26.780 --> 00:11:32.510
Matthew Heon (Red Hat LLC): All right, anything more on this? Otherwise, we have a fairly full agenda, so I'd like to keep it moving.

83
00:11:34.900 --> 00:11:45.959
Matthew Heon (Red Hat LLC): Okay, with Brent actually available right now, let's go on to what was supposed to be our first topic, that being, the incubation application.

84
00:11:46.280 --> 00:12:01.819
Matthew Heon (Red Hat LLC): So, last time we met, we agreed that there would be no move to incubation without having a vote of the core maintainers. However, we became aware last week that an incubation application was filed.

85
00:12:01.960 --> 00:12:17.570
Matthew Heon (Red Hat LLC): I don't think that we are prepared right now for this. We don't have enough adopters for the project listed. We don't have enough maintainers, who are not Red Hat. Like, we've only just acquired our first non-Red Hat maintainer.

86
00:12:17.980 --> 00:12:34.559
Matthew Heon (Red Hat LLC): This application was a surprise to, I think, everyone in this room. There was no core maintainer vote, no notification even to the core maintainers. It was filed using the wrong template, and because of that, the CNCF will reject it if it keeps going.

87
00:12:34.800 --> 00:12:38.669
Matthew Heon (Red Hat LLC): And I think that that would have potential negative implications for the project.

88
00:12:39.230 --> 00:12:46.329
Matthew Heon (Red Hat LLC): So, based on all of these things, I move that, we have a core maintainer vote to

89
00:12:46.450 --> 00:12:52.859
Matthew Heon (Red Hat LLC): Stop this application and basically formally say we are withdrawing until we feel like we are actually ready.

90
00:12:58.320 --> 00:13:01.010
Matthew Heon (Red Hat LLC): Anyone object to this?

91
00:13:03.580 --> 00:13:08.580
Paul Holzinger: Yeah, I… I posted the link for those who haven't seen it yet. The…

92
00:13:08.840 --> 00:13:14.179
Paul Holzinger: My biggest problem is, yeah, like you said, there was no vote on it, no communication, and…

93
00:13:14.460 --> 00:13:21.650
Paul Holzinger: if I look at this, like, the even bigger problem is, like, the information provided is just false, like,

94
00:13:22.080 --> 00:13:24.529
Paul Holzinger: That's the… that's the biggest problem.

95
00:13:26.580 --> 00:13:29.480
Paul Holzinger: So… Yeah.

96
00:13:31.020 --> 00:13:37.690
Paul Holzinger: I don't know, yeah, like, sub-projects listed, like Seamrun, for example, or Podman Desktop, like, this is not…

97
00:13:38.740 --> 00:13:42.510
Paul Holzinger: They are definitely not sub-projects from us, like, this is just…

98
00:13:43.940 --> 00:13:47.659
Paul Holzinger: Yeah, needs to be withdrawn, basically, based on that alone.

99
00:13:48.830 --> 00:13:58.350
brent: Am I correct that we actually documented that the submission, when done, would need to be run by this group?

100
00:13:58.480 --> 00:13:59.060
brent: And the.

101
00:13:59.060 --> 00:13:59.520
Matthew Heon (Red Hat LLC): Yes.

102
00:13:59.520 --> 00:14:03.560
brent: All need to be in… a majority would need to be in favor in order to proceed.

103
00:14:04.770 --> 00:14:15.220
Matthew Heon (Red Hat LLC): Last time, we agreed as a group that a vote would be required to advance this. No vote was taken, and that decision was documented and posted to the repo.

104
00:14:15.380 --> 00:14:19.250
Matthew Heon (Red Hat LLC): And relevant parties should have been in the meeting regardless, so they should have heard it.

105
00:14:24.060 --> 00:14:26.010
Matthew Heon (Red Hat LLC): Alright,

106
00:14:27.180 --> 00:14:42.859
Matthew Heon (Red Hat LLC): I don't think we need to do a voice vote here, but any objections, speak now or forever hold your peace, and if there are no objections, I will go ahead and request after the meeting that the CNCF, close this application, as we don't feel it's ready yet.

107
00:14:49.270 --> 00:14:54.869
Paul Holzinger: Do you need… should we comment on the public issue? Or…

108
00:14:55.600 --> 00:15:05.559
Matthew Heon (Red Hat LLC): If everyone is comfortable, that would be ideal. Like, I can… I can say that the core maintainers have come to a decision, and if everyone would be willing to comment after that, that'd be great.

109
00:15:07.690 --> 00:15:11.860
Paul Holzinger: Yeah, because otherwise you have the same problem, it's just one person saying something. Yeah.

110
00:15:12.120 --> 00:15:30.380
Matthew Heon (Red Hat LLC): I mean, we are recording this meeting, and we will have a transcript. I set the auto-transcription to on, so we can just post the transcript to the Podman repo after this happens, like we've been trying to do for the other core maintainers meeting, so we will have a record, but yeah, it would be best if we put it all in writing as well.

111
00:15:36.570 --> 00:15:45.929
Matthew Heon (Red Hat LLC): Okay, I think that addresses that. Any final bits on this? Otherwise, we have… Plenty more to discuss.

112
00:15:48.850 --> 00:15:52.320
Ashley Cui (Red Hat LLC): When you do that, can you link where to comment, or…

113
00:15:54.590 --> 00:16:00.159
Matthew Heon (Red Hat LLC): I'll throw a link in Podman Dev when I do, how about that?

114
00:16:00.160 --> 00:16:01.050
Ashley Cui (Red Hat LLC): Okay, sure.

115
00:16:04.170 --> 00:16:06.959
Matthew Heon (Red Hat LLC): Okay, let's see…

116
00:16:07.820 --> 00:16:16.209
Matthew Heon (Red Hat LLC): Next up would be, shared documentation repo. So, Brent raised this a while back, but he recently…

117
00:16:16.320 --> 00:16:20.969
Matthew Heon (Red Hat LLC): actually went ahead and made a GitHub discussion about it, which…

118
00:16:21.130 --> 00:16:23.639
Matthew Heon (Red Hat LLC): Or what's the discussion or issue? It doesn't really matter.

119
00:16:23.750 --> 00:16:32.390
Matthew Heon (Red Hat LLC): So, basically the idea here is we should have a separate GitHub repo under Podman Container Tools, which will host

120
00:16:32.390 --> 00:16:50.609
Matthew Heon (Red Hat LLC): a lot of the stuff that lives in Podman right now, that being the governance, the code of conduct, the security policy, how common used to be in the containers repo? Because we've sort of promoted Podman to being the top-level repo of the entire org, which it really shouldn't be.

121
00:16:50.930 --> 00:17:05.600
Matthew Heon (Red Hat LLC): This is basically gonna be an entry point for people just finding things about us, and it could also make things a lot simpler, because it'll be a low-traffic repo, and people who just want to subscribe to governance issues can just subscribe to governance issues.

122
00:17:06.190 --> 00:17:09.170
Matthew Heon (Red Hat LLC): Any thoughts or objections about this?

123
00:17:14.430 --> 00:17:17.190
Paul Holzinger: Yeah, I would say it's maybe used it a bit…

124
00:17:17.599 --> 00:17:22.370
Paul Holzinger: More for some non-governance stuff, like… yeah, start a…

125
00:17:22.619 --> 00:17:27.979
Paul Holzinger: Kind of shared documentation with the… General contribution thing, like…

126
00:17:29.230 --> 00:17:32.270
Paul Holzinger: Commit formats, and stuff like that.

127
00:17:32.420 --> 00:17:34.409
Paul Holzinger: Which are noted in the issue, I think.

128
00:17:34.570 --> 00:17:38.000
Paul Holzinger: Those could live in the same repo, it's probably easier.

129
00:17:39.690 --> 00:17:44.300
Paul Holzinger: To have, like, one sample thing there instead of yet another thing.

130
00:18:02.760 --> 00:18:11.570
Matthew Heon (Red Hat LLC): Okay, it sounds like we all agree this is a good idea. Anyone want to take this one on? Brent, I know you were talking about potentially doing it, would you be willing?

131
00:18:16.620 --> 00:18:17.670
brent: Can you hear me now?

132
00:18:18.090 --> 00:18:19.240
Matthew Heon (Red Hat LLC): Yeah, we can hear you.

133
00:18:19.240 --> 00:18:24.820
brent: Okay, I… this thing doesn't tell me whether I'm on mute or not, it just clicks.

134
00:18:25.670 --> 00:18:32.479
brent: I wanted to sort of see if anyone else wanted to do it. If not, I can be the default assignee.

135
00:18:33.220 --> 00:18:40.900
brent: I think we need to determine what it's called as a group before, you know, I can actually start creating it, but…

136
00:18:41.180 --> 00:18:46.970
brent: Given that I have, org privileges and whatnot, it probably makes sense.

137
00:18:49.850 --> 00:18:53.800
Matthew Heon (Red Hat LLC): At the very least, you can make the repo, and then someone else can populate it.

138
00:18:54.380 --> 00:18:56.640
Mohan Boddu (Red Hat LLC): I was about to say, if you can,

139
00:18:57.390 --> 00:19:03.579
Mohan Boddu (Red Hat LLC): create the repo, or if one of the core maintainers can create the repo, I can populate the contents.

140
00:19:05.590 --> 00:19:15.829
Mohan Boddu (Red Hat LLC): I mean… Perfect. Somewhere it said, like, it's core maintainers in the issue, so as long as it's okay coming from a community manager, I'm more than happy to take it.

141
00:19:16.460 --> 00:19:21.070
brent: Yeah, I'll work with you then, Mohan. It's… if you're agreeable, then…

142
00:19:21.170 --> 00:19:30.849
brent: Matt, we've got our assignees. If anyone has a brilliant suggestion for a repo name, I'd love to hear it. Otherwise, I'll probably start a

143
00:19:31.670 --> 00:19:35.980
brent: discussion on Podman like we did with, OrgName.

144
00:19:36.670 --> 00:19:37.540
Laura Santamaria (Red Hat): So…

145
00:19:37.730 --> 00:19:48.070
Laura Santamaria (Red Hat): I'll just chime in here and say that it's a very common pattern to use the community name. I commented on the issue as well.

146
00:19:48.320 --> 00:20:00.680
Laura Santamaria (Red Hat): we'll see this in a bunch of different places. If you would like to see some of the commands I used to start doing it for the Bootsy group, we're doing the same thing for them. So, happy to share, what we're doing there as,

147
00:20:00.930 --> 00:20:04.139
Laura Santamaria (Red Hat): We collect information in one place for them as well.

148
00:20:04.670 --> 00:20:07.249
Laura Santamaria (Red Hat): So, but I would recommend just calling it community.

149
00:20:08.790 --> 00:20:13.519
brent: Perfect. I'm agreeable to that. Does anyone object? Otherwise, we can run with that.

150
00:20:14.840 --> 00:20:15.980
Matthew Heon (Red Hat LLC): Sounds good to me.

151
00:20:17.340 --> 00:20:18.839
brent: That was Laura, thank you.

152
00:20:19.930 --> 00:20:20.800
Laura Santamaria (Red Hat): It was.

153
00:20:22.110 --> 00:20:22.820
brent: Thank you.

154
00:20:23.420 --> 00:20:26.650
Ashley Cui (Red Hat LLC): Yep, and I'm also happy to help if you need, anything.

155
00:20:27.290 --> 00:20:29.350
brent: Okay, I'll huddle us together.

156
00:20:32.100 --> 00:20:36.600
Matthew Heon (Red Hat LLC): Alright, sounds good. We have assignees for that. Thank you, everyone.

157
00:20:38.540 --> 00:20:49.269
Matthew Heon (Red Hat LLC): All right, anything else on this? Otherwise, we can move on to moving the remaining repos into the, what do you call it, CNCF work. So, we had…

158
00:20:49.270 --> 00:20:57.359
Matthew Heon (Red Hat LLC): Last time we agreed we were going to move a bunch of stuff in. We are, I would say, about halfway done. Everything that needed CI got moved in.

159
00:20:57.360 --> 00:21:09.580
Matthew Heon (Red Hat LLC): But we did not yet get to some of the important ones. Podman.io, Build.io, so both the websites, Automation Images, or not Automation, sorry, Image Build.

160
00:21:09.680 --> 00:21:15.760
Matthew Heon (Red Hat LLC): ImageBuild has a PR opens, but it needs comments. Let me find a link for that one.

161
00:21:16.080 --> 00:21:23.839
Matthew Heon (Red Hat LLC): And I am probably forgetting a few. Anyone remember the other ones that were supposed to move in, besides the websites?

162
00:21:27.040 --> 00:21:33.890
Paul Holzinger: There's a small one, go.podman.io, for the… Like, Go imports.

163
00:21:37.240 --> 00:21:42.829
Paul Holzinger: And… Yeah, I think only the website and the image grid right now.

164
00:21:43.890 --> 00:21:46.109
Paul Holzinger: Don't think we need others at the moment.

165
00:21:47.860 --> 00:21:48.640
Matthew Heon (Red Hat LLC): Okay.

166
00:21:49.740 --> 00:21:55.379
Matthew Heon (Red Hat LLC): I can probably continue to take the lead on these, if people don't mind.

167
00:21:55.630 --> 00:22:02.579
Matthew Heon (Red Hat LLC): I think I've got the process down now, and it doesn't take much besides poking people. Tom, sorry.

168
00:22:03.150 --> 00:22:07.659
Tom Sweeney (Red Hat LLC): Do we have any requirements with CNCF before we start stashing stuff in there?

169
00:22:09.250 --> 00:22:13.790
Matthew Heon (Red Hat LLC): I think we're fine as long as it matches the license, and…

170
00:22:14.060 --> 00:22:24.570
Matthew Heon (Red Hat LLC): as long as it… the process we set up says it has to be fundamentally related to Podman, it has to match license, it has to match governance, and it has to be,

171
00:22:24.740 --> 00:22:32.130
Matthew Heon (Red Hat LLC): well-maintained and well-written project. I think that's the broad guidance we left ourselves.

172
00:22:33.570 --> 00:22:36.569
Paul Holzinger: And it needs to be voted in by the core maintainers.

173
00:22:37.070 --> 00:22:38.119
Paul Holzinger: Yeah, that's fine.

174
00:22:39.820 --> 00:22:42.120
Tom Sweeney (Red Hat LLC): Have we officially voted for these guys?

175
00:22:42.770 --> 00:22:44.750
Matthew Heon (Red Hat LLC): Not yet, that would be part of the move.

176
00:22:44.750 --> 00:22:45.340
Tom Sweeney (Red Hat LLC): Okay.

177
00:22:47.860 --> 00:22:49.400
Matthew Heon (Red Hat LLC): Mohan.

178
00:22:49.400 --> 00:22:57.490
Mohan Boddu (Red Hat LLC): Yeah, Matt, you and I kind of discussed about this after I came back from the PTO, like, thinking of network and artwork, so,

179
00:22:58.310 --> 00:23:03.970
Mohan Boddu (Red Hat LLC): I know we thought, like, it's better to merge them before moving here.

180
00:23:04.220 --> 00:23:08.720
Mohan Boddu (Red Hat LLC): Just wanted to bring it up if it is still the plan, or… I know we haven't…

181
00:23:09.610 --> 00:23:13.850
Mohan Boddu (Red Hat LLC): Formally brought it up to the team or anything, it's just a random discussion we had.

182
00:23:14.140 --> 00:23:16.230
Mohan Boddu (Red Hat LLC): I just want to bring it up here as well.

183
00:23:17.340 --> 00:23:29.260
Matthew Heon (Red Hat LLC): I think it's a good idea. I do… I would wait until we merge the repos. It seems like it'd be extra effort to put two of them in, and then take it down to one at some later point when we merge them, so…

184
00:23:33.050 --> 00:23:39.749
Paul Holzinger: I don't mind that much, but I don't really see a reason why they need to be moved at the moment.

185
00:23:40.960 --> 00:23:46.299
brent: And I am not in favor of doing that. I've been… I've been on the record about that.

186
00:23:50.130 --> 00:23:50.780
Matthew Heon (Red Hat LLC): Alright.

187
00:23:50.920 --> 00:23:53.460
Matthew Heon (Red Hat LLC): Let's hold off on those until we have…

188
00:23:53.580 --> 00:23:56.670
Matthew Heon (Red Hat LLC): What do you call it? A better idea of what's going on, then.

189
00:24:00.620 --> 00:24:09.120
Matthew Heon (Red Hat LLC): Okay, anything else on repo moves? Otherwise, I believe we have… One more topic.

190
00:24:11.240 --> 00:24:22.229
Matthew Heon (Red Hat LLC): Audit of maintainer files. So it is about time for our quarterly audit of who's actually an active maintainer, and maybe we should move some of these people, out.

191
00:24:22.510 --> 00:24:36.290
Matthew Heon (Red Hat LLC): Anyone want to volunteer to go through the maintainer files and propose anyone who's inactive for either removal or reduction to a more suitable role?

192
00:24:48.270 --> 00:24:52.010
Matthew Heon (Red Hat LLC): I am willing to take this if no one else wants it, but .

193
00:24:57.620 --> 00:24:58.250
brent: I don't think you're…

194
00:24:58.250 --> 00:24:58.589
Matthew Heon (Red Hat LLC): figure it out.

195
00:24:58.590 --> 00:24:59.300
brent: argument.

196
00:25:01.490 --> 00:25:11.929
Matthew Heon (Red Hat LLC): All right, through the astounding confidence of the core maintainers, I have been voted in to examine all of our repos and propose some folks for removal.

197
00:25:12.170 --> 00:25:16.329
Matthew Heon (Red Hat LLC): If they are not at… no longer active maintainers, I should say.

198
00:25:17.750 --> 00:25:24.940
Matthew Heon (Red Hat LLC): Alright, that was the last topic I had on the agenda. Anyone else have anything they'd like to discuss?

199
00:25:34.130 --> 00:25:36.779
Matthew Heon (Red Hat LLC): I'm hearing a whole lot of nothing. Alright.

200
00:25:36.890 --> 00:25:40.560
Matthew Heon (Red Hat LLC): Thank you everyone for attending.

201
00:25:40.960 --> 00:25:54.860
Matthew Heon (Red Hat LLC): Once this is done, I will try and figure out how to get the transcript and post the, what do you call it? Post the minutes to the Podman repo, which eventually this should all move into the community repo, but oh well, we can do that later.

202
00:25:54.970 --> 00:26:00.109
Matthew Heon (Red Hat LLC): Anyways, thank you everyone for attending, and I will see y'all later.

203
00:26:00.790 --> 00:26:01.739
Matthew Heon (Red Hat LLC): Bye, folks.

204
00:26:04.400 --> 00:26:05.160
Mohan Boddu (Red Hat LLC): Bye, Al.
