See also: https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 Overview Purpose: Facilitate release-planning between Pulp3, Katello, and pulp_deb releases Attendees: pulpcore, katello, pulp_deb reps; others as needed Template ## YYYY-MM-DD 1000-1030 GMT-5 ### Attendees: ### Regrets:

Overview Core SME List Release rotation (2 months)RELEASING: https://github.com/pulp/pulpcore/blob/main/releasing.md CURRENT: ggainey - March, April decko gerrod dkliban dalley jitka mdellweg Meeting lead (2 months) CURRENT: gerrod - March, April mdellweg decko dalley dkliban jitka ggainey

https://github.com/pulp/pulp-cli/pulls Untriaged: https://github.com/pulp/pulp-cli/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed CI Check: https://github.com/pulp/pulp-cli/actions/workflows/nightly.yml "Interesting" branches 0.14 (katello packaged) 0.30 (current release) Pending action items Agenda

Pending action items: AI: [ggainey] stand up an rpm/deb/ansible install and experiment, to get hard details on the actual behavior (CopySerializer issue) discuss adopting zero-downtime-migration strategyhttps://pulpproject.org/pulpcore/docs/dev/learn/plugin-concepts/?h=zero#zero-downtime-upgrades last copr issue https://github.com/pulp/pulp_rpm/issues/2271 Agenda template ### Month DD, 2023 Action Items: Discussion Topics:

Meeting time: 1030 GMT-5 Members: mhradil, znemecko, ggainey, pbrochado, mdellweg pulp-ui reponon-draft open PRs pulp-ui oci-env profile Template ## YYYY-MM-DD ### Attendees: *

Tests for DomainBasedPermission The code to test is here. Any authenticated user can list domains An anonymous user can't list a domain Only owners can delete a domain Admin can create + delete a repo inside the default domain Test domain creation + create repo inside domain using a user Authenticating with Basic Auth (create the user ahead of time via API) A user presnts an identity header just with their username and no org_id. Then try to create a domain, create a repo inside the domain, and then delete that domain.

2024 November 21, 2024 https://github.com/pulp/pulp_rpm/issues/3469 November 14, 2024 CI-update PRstest-failures now addressed Elsewhere dalley to re-run CI job October 31, 2024 When pulp 4 happens, there are a handful of API changes we should probably makeremoval of location_href, etc.

December 17, 2024 Pulp snapshot featurehttps://discourse.pulpproject.org/t/pulp-snapshot-feature-proposal/1839 moustafa working on POC - will demo to this group when ready Scheduled package releases - https://github.com/pulp/pulpcore/issues/6153 Would like to be able to add packages to a repo and publish it at a specific time in the future Perhaps related to https://github.com/pulp/pulpcore/issues/6104 Is this a breaking change?

2024-12-03 1000-1030 GMT-5 Attendees: ggainey, quba42, mbucher, dalley, pbrochado, sjha, hstct, qjames, mdellweg Regrets: Agenda: Rolling Content Viewsfirst draft PR: https://github.com/Katello/katello/pull/11240 SCA impacted how some pulp_deb users were relying on subscriptions to limit content-access open topics:handling of IndexContent ("fairly finished") sync or async integration of repo-publish (e.g. in repo-sync) lots of ATIX/katello discussion ensues

Pulp open floor, every Tuesday at 10:30 ET (either EST or EDT) (That is 16:30 CET) in pulp-meeting on Matrix. See https://pulpproject.org/help/community/get-involved/ for more info about this meeting. Open Floor Agenda pulpcore Triage query: https://github.com/pulp/pulpcore/issues?q=is%3Aopen+is%3Aissue+label%3ATriage-Needed Agenda Next November 19, 2024 quba42: Is there a good way to turn a Pulp ID into an href and vice versa? I am trying to avoid doing something like the following in plugin code:​​package_href = f"{settings.V3_API_ROOT}content/deb/packages/{package.pulp_id}/"

This is a list of "high-level" Areas of Expertise of the pulpcore project. Within each is a list of "people to talk to" for anyone who has questions. content appggainey pbrochad redis caching gerrod dalley

Fringe day: Pulp 4 discussion (wed?) Talk ideas: Dennis:Introduction to Pulp Reflection Retrospective 2 yrs of services.Pulp 4 forecast Matthias:

GOOGLE MEET LINK TO JOIN PULPCON Welcome to PulpCon 2024! We prepared 3 days of various sessions, including user, admin, dev oriented topics. Missed anything? Watch a recording at the PulpProject youtube channel! For speakers In the schedule for your talk, please add* a link to your slides, notes, presentation, agenda or whatever you have and willing to share, so attendees could get an idea what your talk is about and also have some urls/commands handy if you share those.

Back to PulpCon2024 Schedule Interested in: sharing a quick update on your Pulp plugin/component? sharing a cool feature you used while developing your plugin? having more contributions to your Pulp component? anything else? Add your topic below, you will have 5-10 mins for your lightning talk

CfP from 2023 https://discourse.pulpproject.org/t/virtual-pulpcon-2023-call-for-proposals/963/6 planning spreadsheet (2023) https://docs.google.com/spreadsheets/d/12la6Zhy_FLlkUftV7KM0yuZs0_S9Z7wpeSVSUF7jsM4/edit?hl=en&gid=0#gid=0 (internal only) DATES: 4-8 NOV 2024 Team ggainey, ttereshc To-Do finalize dates

Back to PulpCon2023 Schedule Interested in: sharing a quick update on your Pulp plugin/component? sharing a cool feature you used while developing your plugin? having more contributions to your Pulp component? anything else? Add your topic below, you will have 5 mins for your lightning talk

GOOGLE MEET LINK TO JOIN PULPCON Welcome to PulpCon 2023! We prepared 4 days of various sessions, including user, admin, dev oriented topics. Missed anything? Watch a recording at the PulpProject youtube channel! For speakers In the schedule for your talk, please add* a link to your slides, notes, presentation, agenda or whatever you have and willing to share, so attendees could get an idea what your talk is about and also have some urls/commands handy if you share those.

Triage Query: https://github.com/pulp/pulp-oci-images/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-Needed https://github.com/pulp/pulp-operator/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-Needed Oct 22 Mike to focus on documenting / polishing things over the next week or 2 Showed off Konflux CI 1 2 3 Oct 1 More CI improvements planned :smiley:

Removal of pulp_href support The "prn" will be the only way to reference an object in Pulp. Switch all installations to domain-enabled Goal: To convert all non domain-enabled installations to domain-enabled installations. Why with Pulp4? To switch from a non domain-enabled installation to a domain-enabled installation your URLs will have to change. With Pulp4 URLs will have to change anyway (replacing /v3/ with /v4/)

When will we know the time is right? What will push us over the edge? We are building up technical debt (concerns or issues or solutions are put off because it would be a breaking change requiring a Pulp 4)Self fulfilling prophecy (making migration/upgrade more painful) What are the list of features that would require a new X Release? (just pick 1) Thought experiment if we did a release a new X release, what are the things that would need to change to make this happen? Note: we aren't suggesting time based features, just force us to think about what things need to change in order to start putting out a roadmap where 1 thing can be picked as the Pulp 4 release Will we ship a v3 and v4 API at the same time?