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/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
* pulp_file Triage query: https://github.com/pulp/pulp_file/issues?q=is%3Aopen+is%3Aissue+label%3ATriage-Needed

# May 17
* Need to be more explicit about pulp_installer no longer supported
* https://github.com/pulp/pulp_installer/issues/1478
* pointers in other places/docs need to be updated as well
* [discourse announcement](https://discourse.pulpproject.org/t/pulp-installer-3-22-will-be-the-last-release-for-the-installer/706)
* clearly not sufficient based on upstream feedback
* AI: [ipanova] to open task to track down remaining references

# May 9
* [quba42] pulp_deb cloud CI test woes:
* Azure CI tests often failing (sometimes succeed) for all branches: e.g.: https://github.com/pulp/pulp_deb/pull/759
* https://github.com/pulp/pulp_deb/pull/744 fails the s3 test only (may be identifying a real issue?) not sure how to debug.
* In general: How to interpret tests failing for just a single cloud provider? Random failures vs. real issue?!
* running tests in oci-env in parallel (or not):
* `pytest -v -r sx --color=yes --suppress-no-test-exit-code --pyargs pulp_deb.tests.functional -m parallel -n 8`
* `pytest -v -r sx --color=yes --pyargs pulp_deb.tests.functional -m 'not parallel'`
* can use the minio profile to siumulate S3
* core/3.25 releasing today!
* assuming github gets better...
* compatibility promise is now "pulpcore<3.40"

# May 2
* core/3.24 releasing Today
* last release before the breaking-changes in core/3.25 happen
* core/3.25 coming SOON
* will be based on Django4.2

# April 18
- [hstct] We have a problem with the web server created by the pytest fixtures which seems to be due to some missing content header configuration.
- This is driven by a community contribution and requires a change in pulp-smash.
- Can we get some input on how move forward with this?
- https://github.com/pulp/pulp_deb/issues/742
- https://github.com/pulp/pulp-smash/issues/1309
- https://github.com/pulp/pulp-smash/pull/1310
- discussion ensued
- outcomes: pulp-smash PR accepted/merged, #742 moved to pulpcore to get same applied to pulpcore fixture-utils

# April 11
* discussion around https://github.com/pulp/pulpcore/issues/3730
* decision: revert some problem code in pulp_container to help AAP, take some time to review implications of the associated PR before accepting

# March 14th

- [quba42] Can I get maintainer status on pypi for [pulp-cli-deb](https://pypi.org/project/pulp-cli-deb/) for user [quba42](https://pypi.org/user/quba42/)? (Right now I have access to pulp-deb and pulp-deb-client).

# February 14, 2023
- [lmjachky] What do you think about renaming repositories from pulp-plugin to pulp_plugin (e.g., pulp-certguard -> pulp_certguard)?
- This is just to prevent discrepancies between installed packages and repositories' names (there is an issue with this when running oci_env with pulp-certguard).
- GitHub provides a facility for redirects:
- github.com/evgeni/debian-talks/
- [quba42] The search on the [documentation](https://docs.pulpproject.org/pulpcore/) is broken (also for various plugins)!
- To me this renders the docs nearly useless, it is a serious issue!
- Is this a pulpcore or a plugin_template issue?! => We should open an issue to track this!
- errors in webconsole:
- Uncaught ReferenceError: jQuery is not defined
- Uncaught ReferenceError: $ is not defined

# January 17, 2023
- contribute to the tech preview labels discussion https://discourse.pulpproject.org/t/features-in-tech-preview/737

# January 10, 2023
* hstct: Pulp doesn't have permission to create symlinks in the container CI. I don't know who to ask for advice here. [reference](https://github.com/pulp/pulp_deb/pull/704#issuecomment-1375483512)

# December 20, 2022
* [core/3.22 released!](https://docs.pulpproject.org/pulpcore/changes.html#id1) Thanks ipanova!
* Cancel next week's meeting?

# December 13, 2022
- December 3.22 release https://discourse.pulpproject.org/t/3-22-release/719
- How to sync-then-publish? https://github.com/pulp/pulpcore/issues/3452

# December 6, 2022
- quba42: Need help assessing https://github.com/pulp/pulp_deb/issues/690 since I don't know enough about orphan cleanup.

# November 29, 2022
- pulpcore 3.22 tentative GA date is scheduled for Dec 5th
- CodeQL checks in github
- do it, or not?
- if "do it" - we need to actually look at and address all findings

# Oct 25, 2022
- Will there ever be a feature [like this](https://discourse.pulpproject.org/t/skip-specific-rpms-during-sync/670)? Does it need/have a ticket?
- ggainey responded for pulp_rpm - no current plan, asked for a Feature ticket to be opened to continue the discussion
- [hstct for pulp_deb maintainer](https://discourse.pulpproject.org/t/i-nominate-hstct-for-pulp-deb-merge-access/668)
- bmbouter to work w/ quba42 to make this happen

# October 4, 2022
- https://discourse.pulpproject.org/t/support-zero-downtime-updates/645/4
- We've started planning this work and will have a GitHub issue soon

# September 27, 2022
- Proposal advertisement: Remove the single commit check from the CI and use Squash merging
- https://discourse.pulpproject.org/t/removing-the-one-commit-check-in-the-ci/639
- Should pulp_deb issues appear on the new [Pulp Kanban board](https://github.com/orgs/pulp/projects/8/views/1)? See also [this GitHub PR comment](https://github.com/pulp/pulp_deb/pull/644#discussion_r979802699).
- CfP for PulpCon is due today. Do we want to extend it till Monday? I see only one Pulp team member as a speaker among the proposed talks. https://discourse.pulpproject.org/t/pulpcon-2022-call-for-proposals/590

# September 20, 2022
- Plugin writers please broaden and declare your dependencies, see these docs
- https://github.com/pulp/pulpcore/blob/main/docs/plugins/plugin-writer/concepts/index.rst#declaring-dependencies
- Container Based Pulp Install Next Steps (FYI):
- Moving the operator images to be built in pulp-oci-images repo (all container builds will live in that repo)
- Operator images will likely become the images we recommend for use, while the single container is more for trying out all of the plugins
- Operator images will replace ansible build with a docker file so users can more easily build the containers locally

# September 6, 2022
- [lmjachky, ewoud] Is it worth publishing bindings on a daily basis?
- The bindings for clients are built daily and published on PyPI (even when no change was recorded).
- Does it makes sense to store the bindings in GIT repositories for the sake of the history and publishing?
- it would become a new nightly process to import bindings into GIT; then, have a GH action to publish a nightly package if there was a new commit created
- that could allow us to determine if a new release is needed
* [quba42] pulp_deb Nightly CI/CD failing on "publish" step:
* https://github.com/pulp/pulp_deb/actions/workflows/nightly.yml
* https://github.com/pulp/pulp_deb/actions/runs/2997626890
* [dalley] UUID generator wrapper https://github.com/pulp/pulpcore/pull/3136

# August 30, 2022
* Release pulpcore 3.21 go/no-go
* Can we think about adding a "context report" feature to Task, that could be used to report specific-task-request info back to the invoker? Examples:
* quba42's [Store sync-options on task](https://github.com/pulp/pulpcore/issues/3137)
* wibbit's [pulp_rpm copy dry-run request](https://github.com/pulp/pulp_rpm/issues/2722)
* FYI: pulp-smash proposal to be put into read-only mode on Sept 5th
* https://discourse.pulpproject.org/t/retirement-of-pulp-smash/579

# August 23, 2022

* https://discourse.pulpproject.org/t/remote-fields-vs-sync-options/568

# August 2, 2022

* pulpcore 3.18 release today?
* yes
* Can we find a naming consensus for https://github.com/pulp/pulpcore/pull/2999#issuecomment-1202674644
* The provisional consensus for the name is `info`.

# July 26, 2022
* Should we relese pulp_file this week?
* yes, we should. x9c4 will do the release

# July 19, 2022
* Can we remove the Required PR machinery from the CI?
* Or at least mark a PR using it as not ready to ship.
* Solution: There should be a test to prevent PR's to merge before all the required ones are merged.
* Should we assume that tests _always_ run on the same box as pulp services
* https://discourse.pulpproject.org/t/functional-tests-will-now-run-inside-the-container-running-pulp/498

# July 12, 2022

* https://discourse.pulpproject.org/t/potential-breaking-api-changes-and-complex-migrations-in-pulp-deb/530

# May 31, 2022
* [lmjachky] Why do not we ship signing scripts with plugins when the only required fields that are set by administrators are basically a keyid, gnupghome, and name of a signing service?
* **If we strictly define the interface, signing utility (gnupg), and environment variables (administrators should in no way touch the environment variables) of a signing script, does it still make sense to allow them to write their custom scripts?**
* In the end, we will have just one pulp-provided script referenced from multiple signing service instances where each instance differs from the other by a keyid, name, and potentially gnupghome.

# May 24, 2022

* pulpcore 3.20 release date
* June 14th!
* introduction Tobias (hstct)
* pulp_deb tests are broken on master with:
* `pulp_smash.pulp3.bindings.PulpTaskError: (PulpTaskError(...), "Pulp task failed (DeclarativeArtifact must not provide both 'url' and 'urls')")`
* See: https://github.com/pulp/pulp_deb/runs/6566690326?check_suite_focus=true
* see https://github.com/pulp/pulp_python/pull/536/files on how to fix
* Cannot run local tests on freshly built `pulp3-source-fedora35` (pulp_installer, pulpcore, pulp_rpm, pulp_deb all from latest main branch):
* `ImportError: cannot import name 'OrphansApi' from 'pulpcore.client.pulpcore' (/usr/local/lib/pulp/lib64/python3.10/site-packages/pulpcore/client/pulpcore/__init__.py)`

# May 17, 2022

* Ingest by url?
*

# April 26th, 2022

* [lmjachky] Assigning GH issues to myself is very cumbersome. All pulp contributors should be allowed to assign themselves to any issue within any pulp repository.
* In order to enable assignments, one has to have write permissions to a repository.
* Should we enable all people inside the Pulp organization to have write permissions: https://github.com/orgs/pulp/people?

* [lmjachky] What is the status for sprint planning dashboards that should replace the boards available at plan.io: https://github.com/orgs/pulp/projects?type=beta?
* Can we at least start using GH Project Boards similarly to pulp_ostree: https://github.com/orgs/pulp/projects/7?

* [quba42] How to deal with https://github.com/pulp/pulp_rpm/issues/2501 (as far back as pulp_rpm 3.9 for Katello 2to3 migrations)?

# April 12, 2022

* Checking the `post_docs_test.sh` I understand that they are meant to ensure that the documented examples work as expected. I'm not sure if this is valid, but what if we added the steps to remove/clean the "objects" (content, repository, distribution, etc) in the documentation workflow (this way, we would cover the entire "_lifecycle_" workflow of a plugin) and `post_docs_test.sh` script as well?

# April 5, 2022

* FYI some discussion on the goal of making tests independant of all other tests
* https://discourse.pulpproject.org/t/making-tests-totally-independant/412

# March 29, 2022

* "Release Day"
* releases are 'easy', but still take up time/spoons
* can we declare releases to all happen on one day of the week?
* how about Tuesday?
* Yes, let's try to do this!!!

# March 22, 2022

* It may come up in triage anyway, but I was wondering what the plan for the following issue is: https://github.com/pulp/pulp_rpm/issues/2422
* I originally found it via: https://bugzilla.redhat.com/show_bug.cgi?id=2024963

# March 15

* https://github.com/pulp/pulp-oci-images/issues/161
* Any way to prioritize this/add to sprint?
*

# March 8

* 3.19.0 release date. How about April 12?

# March 1

* What should a user do to avoid certificate errors when serving content from a distribution within the pulp:latest image via HTTPS (maybe pulp_ostree specific)
* When accessing the content, the following error is shown: "Peer certificate cannot be authenticated with given CA certificate"
* Disabling TLS verification helps, but it is not a real solution if the user wants to distribute the content via the HTTPS schema
* Upcoming plugin_template breaking change
* The unit test runner is switching to pytest
* Will require several unit tests to be rewritten when applied.
* These tests mostly are all the same as they originally came from the plugin_template itself
* The pulpcore and pulp_file PRs should show how to fix

# Feb 22nd

# Feb 15th

* https://discourse.pulpproject.org/t/pulp-cli-usability-discussion/370
* options naming for pulp-cli
* FYI: please let bmbouter know if you see this error in the CI
* The failing test is `test_sync_https_through_http_proxy` that [fails like this](https://github.com/abhinavsingh/proxy.py/issues/1086)
* please read and provide feedback if any on the work that docs SIG has done https://discourse.pulpproject.org/t/pulp-docs-sig-findings-conclusions-software-repository-management/372
*
# Feb 8th
* FYI run tests only in your nightly CI run with the `nightly` pytest mark
* Now on the plugin_template [here](https://github.com/pulp/plugin_template/pull/567).
* [Here's an example](https://github.com/pulp/pulp_ansible/blob/f9b52dc4d5b3d835a32f559a9f544db730f31710/pulp_ansible/tests/functional/api/collection/v2/test_sync.py#L150) of `pulp_ansible` using it.
* New Prometheus metrics exporter built by the team supporting the internal PyPI (Thoth)
* https://github.com/thoth-station/pulp-metrics-exporter
* Very basic right now and current focus on python plugin stats
* They would appreciate us contributing to it as well

# Feb 1st
* FYI a new `ptest` is available in the vagrant env, use it to run the functional tests
* `ptest` or `ptest pulpcore` will test pulpcore
* `ptest <plugin_name>` will run a plugin, e.g. `ptest pulp_file`
* Later the unit tests will also be run with this too
* FYI new proxy tests are available
* pulp-smash has new fixtures so they will run nicely locally
* https://github.com/pulp/pulp-smash/pull/1271
* See pulpcore's tests as an example:
* https://github.com/pulp/pulpcore/pull/2174
* Github - https://discourse.pulpproject.org/t/github-issues-and-labels/333/3

# Jan 25
* CI: Replace docker with github registry
* https://github.com/pulp/pulp-oci-images/pull/144
* https://github.com/pulp/pulp_npm/pull/147
* https://github.com/orgs/pulp/packages
* For awareness, 3.18.0 tentative schedule https://discourse.pulpproject.org/t/pulpcore-3-18-0-release-schedule/330
* Proposal / Question: Can plugin teams have 1 person for 1 day try to port their plugin docs to use pulp_cli by Feb 4th?

# Jan 18

* we've discussed how backport process, BZ re-integration is going to change after the move to GHI, let's talk some about triage process too. And sprint planning
* do we want a `tutorial` section on discourse, this potentially will be redundant depending on how we plan to re-structure docs https://community.theforeman.org/c/tutorials/23
* FYI two testing related things
* upcoming recording on how to adjust writing tests to use the new fixtures
* https://discourse.pulpproject.org/t/event-testing-pulp-using-the-new-pytest-fixtures/311
* please discontinue writing tests that inherit from unittest, instead use pytest
* parallel testing is now available in the CI
* https://discourse.pulpproject.org/t/parallel-test-runs-added-to-ci/320
* need unique fixtures still to make much more usable
* bmbouter's hope: All mini teams update plugin docs sites as if it's the only site your users will ever see

# Jan 11

~~* Proposal: put old projects into read-only mode, e.g. Crane, Docker, Nectar, and Puppet Support
* https://pulp.plan.io/projects
* [done]~~
* we've discussed how backport process, BZ re-integration is going to change after the move to GHI, let's talk some about triage process too
* do we want a `tutorial` section on discourse, this potentially will be redundant depending on how we plan to re-structure docs https://community.theforeman.org/c/tutorials/23

# Jan 4

* https://discourse.pulpproject.org/t/design-question-why-do-publications-not-have-a-unique-name/300
* 3.18 release date?
* Feb 8?

# Dec 14

* Is there a reason why we use TextFiled and not URLField for url on a Remote in pulpcore?
* pulpcore usage https://github.com/pulp/pulpcore/blob/main/pulpcore/app/models/repository.py#L322
* URLField https://docs.djangoproject.com/en/3.2/ref/models/fields/#urlfield
* we had an OpenAPI issue: https://github.com/pulp/pulpcore/pull/919
but we killed the OpenAPI schema view, so we can use it again
* pulpcore 3.17 plugin compatibility check-in

# Dec 07
* should CI/CD team have write permissions to all repos?
* expanding the pulpcore commit bit to include subject matter experts
* https://discourse.pulpproject.org/t/expanding-pulpcore-committers/266

# Nov 30

* GH badges are out of date
* Feedback Requested: aiohttp.Server draft PR is posted: https://github.com/pulp/pulpcore/pull/1728/files
* pulpcore 'master' branch has been renamed to 'main'

# Nov 23
* On November 30, pulpcore is going to rename 'master' branch to 'main'. All plugins will need to update their CI.

# Nov 15
* proposal: only introduce plugin API breaking changes in pulpcore releases pulpcore_version % 5 == 0
* https://discourse.pulpproject.org/t/what-to-do-to-reduce-unecessary-plugin-compatibility-releases/236
* question: what needs to happen to do this
* default branch name transition: https://discourse.pulpproject.org/t/pulp-github-repositories-will-change-master-branch-to-main/214/4?u=gerrod
* GitHub sponsorship for Pulp?
* from ewoud :
~~~
if you're going more and more to GH, have you considered asking for sponsorship from GH? Foreman is: https://community.theforeman.org/t/our-github-organization-is-now-sponsored-on-the-teams-plan/25414"
for Foreman it was just send an email and within a day we had it approved
they did ask to add them as sponsors on https://theforeman.org/sponsors.html but that's a fair thing to ask :)
~~~
* thoughts?
# Nov 2
* branch names consistency: main x master
* How much review do CI update PRs need?
e.g.: https://github.com/pulp/pulp_deb/pull/368
* They have already been reviewed in the plugin_template, is that enough?
* The CI pipeline on the PR is green, is that enough?

# Oct 26

* ~~Could the following be a pulpcore issue with long artifact names?~~
https://community.theforeman.org/t/katello-value-too-long-for-type-character-varying-255/24953
* I found the cause of this issue in pulp_deb
* pulp_rpm 3.16 has not declared compatibility against pulpcore 3.17. Should pulp_deb do the same/is there a breaking change in 3.17 that ignores the deprecation policy?
* [dalley] no, I'm not aware of one, I just left the specifier as it was since I knew we could change it in a Z release - and I wasn't sure what was going into 3.17

# Oct 12

* Mirrored Sync, metadata mirroring, and keeping pulp_deb from diverging from pulp_rpm (for similar features and problems)
* https://pulp.plan.io/issues/9316#note-19
* see also
* https://pulp.plan.io/issues/6353
* https://pulp.plan.io/issues/8687
* https://pulp.plan.io/issues/8856
* pulp_rpm Oracle ULN with HTTP proxy not working.
* ref https://pulp.plan.io/issues/9064
* https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/app/downloaders.py#L105 vs
https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/app/downloaders.py#L175

# Oct 5

* Last call for PulpCon proposals. CFP ends Friday.
* https://discourse.pulpproject.org/t/pulpcon-2021-call-for-proposals/134
* Pulpcore 3.16.0 plugin compatibility check-in
* pulp_ansible [needs a backport]
* ~~pulp-certguard - needs a release [ggainey]~~
* pulp_container - needs a release
* pulp_deb - decleared compatible
* pulp_maven (?) - needs a release but currently not being included in the container
* pulp_python
* pulp_rpm
* Please have a look at the roles PR in pulpcore especially if you agree with the REST api for assigning roles.
* https://github.com/pulp/pulpcore/pull/1627
* https://github.com/pulp/pulp-cli/pull/382

# September 28

# September 21

# September 14

# August 31
* [9247](https://pulp.plan.io/issues/9247) - "Lost" workers and task-state
* shoot a worker in the head, eventually its task gets marked as 'canceled'
* for the user looking for success or failure, 'canceled' feels misleading
* can we 'fail' such tasks instead? What are the implications?
* [Fun with deadlocks](https://discourse.pulpproject.org/t/concurrency-ordering-and-fun-with-deadlocks/71/)
* We have some known potential deadlocks, with a potential (hacky) set of fixes
* What's the right thing to do given the root problem (postgres has no implicit ordering on queries)
* What to do about https://github.com/pulp/community
* discussions are disabled, only wiki left
* 3.16 release date
* proposal: Sep-28
* a time-driven (not stakeholder-driven) date

# August 24
*

# August 3
* https://github.com/pulp/community/discussions/73
* https://pulp.plan.io/issues/9084
* CI and pulp_deb : https://github.com/pulp/pulp_deb/runs/3227024308?check_suite_focus=true

# July 27
* drf_access_policy version bump is not compatible with 2 cycle deprecation policy - plugins can't be compatible with both 0.9.1 and 1.0.1
* [mdellweg] check if condition_expression is usable in all cases and add a deprecated pulpcore compatibility layer
* Loosen the constraints around what can be in a new-repository-version
* https://github.com/pulp/pulpcore/pull/1513/
* needs more eyes and a backport at least to 3.14
* Proposal: dropping the traditional tasking system with 3.16
* FYI: switching settings to enable AccessPolicyFromDB by default this week
* https://pulp.plan.io/issues/8974

# July 20
* pulpcore 3.15 release date
* last week we proposed August 3 - is this still realistic?
* [dkliban] will schedulea go-no-go meeting for Wednesday July 21
* pulpcore 3.14.3 release Wednesday July 21, please open any backport requests today

# July 13
* triage **first** to catch up on backlog
* pulpcore 3.14.2
* [david] I can release today or we can postpone until next week
* [meeting] Let's do it today and 3.14.3 next week
* pulpcore 3.15.0 release date?

# July 6
* pulp 2to3 migration (Backports):
* https://pulp.plan.io/issues/8945
* https://pulp.plan.io/issues/9017
* pulp2:
* https://pulp.plan.io/issues/9011

# June 29

# June 22

# June 15
* pulp-list and pulp-dev lists
* Thoughts on decommissioning them?
* Can we keep the archives up?
* Can we have a process for reverts?
* When we revert a commit, i believe we should reopen the the original ticket (or move it to wontfix)
* https://github.com/pulp/pulpcore/pull/1407
* https://github.com/pulp/pulpcore/pull/1406
* Bringing back pulpbot
* proposal: ressurect pulpbot as a matrix bot https://github.com/pulp/community/discussions/2#discussioncomment-817556

# June 8
* pulpcore 3.14 release date
* June 29th with @bmbouter doing the release. go/no-go on June 15 and June 22.

# June 1
* Does it make sense to start doing regular Z releases (for the latest Y stream) and not wait with bugfixes for the next Y release.
* Have a specific repo to host Github Discussions rather than use pulpcore
* Examples: https://github.com/github/feedback
* Libera/matrix bridge is live: https://fosstodon.org/@liberachat/106320476905973945
* no-meeting-Fridays June-August - should we resched the second triage-mtg? Or just have one per week?
* [idea]: what if recoccuring meeting announcements all went on one thread instead of one per meeting?
* e.g. https://github.com/pulp/pulpcore/pull/1345/files
* Is everything in place for the 3.13 container image release today? (some plugin issues late last week were blocking)
* we need to release pulp-ansible

# May 25
* [topic from May 21] Any incompatible releases for upcoming 3.13 left? (except pulp_python which can be released only after 3.13 is out)
* [topic from May 21] Does it make sense to start doing regular Z releases (for the latest Y stream) and not wait with bugfixes for the next Y release.
* [topic from May 21] libera.chat and Project registering
* whether we move Elsewhere or not, we'll be on IRC for "a while"
* do we want to own the Pulp namespace on libera?
* see https://libera.chat/chanreg
* Github discussions https://github.com/daviddavis/pulpcore/discussions
* Signing up for a mailing list to ask a question is too much friction
* Most everyone already has a github login
* org level: https://github.com/orgs/github/discussions
* docs: https://docs.github.com/en/discussions
* Discourse?
* Works well with mailing list integration
* Easy categorization
* Event listing
* RSS Feed integration
* SSO integration for login
* What to replace freenode with?
* https://git.io/Jsxat
* https://www.devever.net/~hl/freenode_abuse

# May 21 (cancelled, topics moved to May 25)
* Any incompatible releases for upcoming 3.13 left? (except pulp_python which can be released only after 3.13 is out)
* Does it make sense to start doing regular Z releases (for the latest Y stream) and not wait with bugfixes for the next Y release.
* libera.chat and Project registering
* whether we move Elsewhere or not, we'll be on IRC for "a while"
* do we want to own the Pulp namespace on libera?
* see https://libera.chat/chanreg

# May 18
* We have incompatible releases for upcoming 3.13 (used in oci-images) (https://github.com/pulp/pulp-oci-images/blob/latest/pulp/Containerfile#L14)
* pulp_ansible
* pulp-certguard
* pulp_container
* pulp_maven (?)
* pulp_python
* pulp_rpm

# May 14
* Dependabot is suggesting upgrading major versions of dependencies a lot.
* e.g. we state that we want to use Django 2.2.* LTS and it keeps suggesting 3.*
* Would like to remove the Single Container category since issues are now on Github
* Unlike tags, removing the category will remove it from older issues
* Options: (1) that's ok (2) create a SC tag, add it to older issues, then remove it
* Please update and test your dev environment with https enabled
* In theory you can run the tests with https now
* Update the pulp_installer and drop `pulp_webserver_disable_https: true` from your local config

# May 11
*

# May 7
*

# May 4
* 3.13 proposed release date and lead

# Apr 30
* Does Pulp have a color scheme/theme? If so, can we modify the DRF templates to match?
* https://www.django-rest-framework.org/topics/browsable-api/#customizing

# Apr 27
* Best way to go about extending a plugin's api? Through urls.py or extending content app urls?
* https://docs.pulpproject.org/pulpcore/plugins/plugin-writer/concepts/index.html#custom-api-url-routes
* Python publishes the simple api to the content app, good enough for sycing/pip but needs to support POST operations in order to support Twine

# Apr 23
*

# Apr 20
* 3.13 release date (decided to postpone the decision on the date)

# Apr 16
* No items

# Apr 9
* How to properly use `PackageReleaseComponent` and `Modulemd` for creating repositories/distributions that target multiple distros & distro versions

# Mar 26
* Would like to remove https://github.com/pulp/dummy
* Was supposed to be github issues test but now we have actual repos (pulp-cli and pulp_python)
* Any concern w/removing pulp-smash from pypi and using git repo instead?
* Need a volunteer to release pulp_file compatible with 3.12

# Mar 23
* Need a volunteer to release pulp_file compatible with 3.12

# Mar 19

* Next pulpcore release date and release shepherd
* 3.12 release review, to move items to 3.13
* https://pulp.plan.io/versions/182

# Mar 16

* Pulp Python has moved all of its issues over to Github. What should happen to the pulp.plan.io page?
* closed pulp_python project

# Mar 12
* CI running on ubuntu 20
* 
* Plugin removal
* Problems with non-revertable migrations
* Problems when deleting a detail-table
* needed for migration plugin
* https://hackmd.io/cKZ-MwkdSUiFKJo0W5zQ_A

# Mar 5
*

# Feb 23
*

# Feb 19
* Discussion about https://pulp.plan.io/issues/8277

# Feb 16
* No topics

# Feb 12
* 3.10 release party
* 3.11 - removing md5 and sha1 by default
* call for feedback https://hackmd.io/vuW2zLSuRvSGpMleEDXXlw
* impact on RPM?
* PSA: things that go into the installer don't follow Pulp everywhere it goes
* e.g. the MEDIA_ROOT changes in 3.10

# Feb 9
* Remove WIP labels, use drafts instead

# Feb 2

* closing out old milestones?
* e.g. pulpcore's https://pulp.plan.io/projects/pulp/roadmap

# Jan 29
* start with triage today?
* extend open floor time?
* NO TRIAGE AND NO OPEN FLOOR!(kidding)
* if we call out that topics are taking too long, that might be the best solutoin right now
* remove: https://hub.docker.com/r/pulp/pulp-fedora31
* Documenting workflows with CLI - https://docs.pulpproject.org/pulp_ansible/en/master/nightly/workflows/collections.html
* avoid bash scripts?
* https://www.sphinx-doc.org/en/master/usage/extensions/doctest.html
* https://sphinxcontrib-programoutput.readthedocs.io/en/latest/
* problem: how to ship changes to a default access policy?

# Jan 26
* Pulp-NEXT query
* https://pulp.plan.io/issues?query_id=168
* backport definition and workflow
* clarify in the docs: backporting is the act of cherrypicking back, and we don't pick all bugs so if someone wants something on even latest z they need to tell us
* Permissions to manage repository versions
* is there a need to have dedicated object-level permissions for repository versions?
* Which pulp_installer FIPS/Vagrant tests, which take **~90 min**, to run for PRs vs cronjobs vs tagged jobs?
* Mike's proposal:
* PRs:
* pulp3-source-centos7-fips
* pulp3-source-centos8-fips
* cron:
* pulp3-source-centos7-fips
* pulp3-source-centos8-fips
* pulp3-sandbox-centos7-fips
* pulp3-sandbox-centos8-fips
* pulp3-source-fedora32
* pulp3-source-debian10
* tagged:
* pulp3-sandbox-centos7-fips
* pulp3-sandbox-centos8-fips
* branches:
* None
* We'd sometimes merge PRs while the 2 jobs are still running
* Will re-evaluate once SELinux CI is finished
* GHA is warning us that ubuntu-latest will become ubuntu-20.04 sometime soon.

# Jan 22
* Spam script removing actual users
* AI: turn it off
* New tags in Redmine
* Pulp-NEXT and Wishlist
* AI: have a query with them
* Make worker ttl configurable

# Jan 19
* How specific can we be in Access Denied type of errors not to give away too much information but also to make it less painful for users and devs to debug permission problems?
* E.g. https://paste.centos.org/view/df93d584
* Spam script removing actual users
* New tags in Redmine
* Pulp-NEXT and Wishlist
* Should model validation be skipped altogether?
* e.g. https://git.io/JttPW

# Jan 15
* Reminder: 3.10 release https://pulp.plan.io/versions/166
* January 26
* Label selector problem https://pulp.plan.io/issues/8067#note-1
*

# Jan 12
* 3.10 release https://pulp.plan.io/versions/166
* Issues, dates, volunteer(s)?
* Move off Travis - https://pulp.plan.io/issues/7859
* Would like to get this task closed out

# Jan 8

# Jan 5

## Agenda

# Dec 18

## Agenda
*

# Dec 15

## Agenda
* As a user I'd like the pulp content landing page to be less cluttered
* https://pulp.plan.io/issues/7977
* added to Q1-2021
* When to use quarter field?
* querying before 3 months planning

# Dec 11

## Agenda
*

# Dec 8

## Agenda
* CI status check - how to deal with lack of dashboard?
* status check at mini-teams
* maybe consolidate CI badges in one place (pulpproject.org)? https://github.com/arjun024/actions-dashboard
* Github Universe this week - https://githubuniverse.com/schedule/

# Dec 4

## Agenda
* How to deal with backports and Travis? https://pulp.plan.io/issues/7885
* Move old release branches to GHA as needed
* fixtures.pulpproject.org is temporarily not updating automatically
* If you merge a PR, ping duck or misc at redhat.com

# Dec 1

## Agenda
*

# Nov 17

## Agenda
* 3.10 release timeframe?
* mid-December (eg Dec 21) or early January?
* Jan 7th tentative
* Go/No-go Jan 4th
* release owner TBD
* Completely drop support of Travis from plugin_template?
* disinclude --travis from --all +1
* wait till we have plugins running on GHA
* Send out deprecation notice with a removal date to pulp-dev

# Nov 10

## Agenda
* Alternate Content Sources call for review
* https://pulp.plan.io/issues/7832

# Nov 3

## Agenda
* Travis pricing - https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
* Makefile https://github.com/pulp/plugin_template/pull/278
* Are there any builds we can disable in Travis?
* eg https://travis-ci.com/github/pulp/pulplift/builds/197596891
*

# Oct 30
* CI status check - https://travis-ci.com/github/pulp
* pulp_rpm - performance tests are failing - https://travis-ci.com/github/pulp/pulp_rpm/builds/195874182

## Agenda
*

# Oct 27

## Agenda
*

# Oct 23

## Agenda
* Process for backporting cherry picks and issue #s?
* Automation checks that attached issues aren't CLOSED
* Cherry pick issues could be closed if they are already released
* Also, release automation checks issues/assigns them to milestones
*

# Oct 20

## Agenda
*

# Oct 9

## Agenda
* docs day cross-plugin
* Plugin A would pick a workflow
* Person from Plugin B would try that workflow and document what is missing

# Oct 6

## Agenda

* backporting migrations (revisited)
* hacktober: project-participation now requires a label to be added to the project(s)
* downside: may attract spam - https://github.com/theforeman/theforeman.org/pull/1688
* https://www.youtube.com/watch?v=MfvFRAJS9nw&ab_channel=JeffGeerling
* question: what does everyone want out of open floor, e.g. decisions or discussion?

# Oct 2

## Agenda

* pulpcore 3.8 release date?
* 4 weeks would be Oct 20th, 5 weeks Oct 27th
* ttreshc will be the release shepherd
* it will be at Oct 20th
* https://pulp.plan.io/issues/7645
* go/no-go meeting - Oct 13th
* new pulp org for pulp tooling (to balance Travis)
* fao89 to send an email
* is there a way to test packaging? (MANIFEST.in issues)
* https://pypi.org/project/check-manifest/

# Sept 29

## Agenda

* PoC for automatic PR merges https://github.com/pulp/pulp-ci/pull/737
* Rebases commits unless it detects signed commits
* Do we support backporting fixes that include migrations?
* FYI: 3.7.1 is releasing today with 1 packaging fix
* https://github.com/pulp/pulpcore/pull/943

# Sept 25

## Agenda

* Enabling docstring linting with pydocstyle?
* proposal: next step, advertise and ask for concerns on pulp-dev
* https://pulp.plan.io/issues/5022
* https://pulp.plan.io/issues/5024
* Propose: Dropping the (unwritten) rule to format docs sources in block layout with 100 chars width.
* Instead add linebreaks at language features like end-of-sentence.
* Pulp2 and makedirs
* https://pulp.plan.io/issues/7445

# Sept 22

## Agenda

* CI status check
* pulp is failing - https://travis-ci.org/github/pulp/pulp/
* pulplift is failing - https://travis-ci.com/github/pulp/pulplift
* Flip triage will open floor. It is easier to advertise and get attention for open floor then triage
* flip on next Friday
* Proposal: disable merging by commit for pulpcore and pulp_file
* https://imgur.com/a/uiIa0Mr
* What about a "Pulp, what the heck?" invite, maybe with video (or not)?
* The goal is to have users tell us one, frustrating thing about Pulp
* Then if we can, we fix it
* hass.io has been doing this recently and it's been good for them
* https://www.home-assistant.io/blog/2020/08/18/the-month-of-what-the-heck/

# Sept 11

## Agenda
* why redmine queries are so easy to delete? +1
* Add a tag or new tracker to track release tasks (e.g. https://pulp.plan.io/issues/7463)?
* hacktoberfest - https://hacktoberfest.digitalocean.com/
* hacktoberfest label for getting contributors during October
* pulpcon video links
* I ran the test and we can record multiple recordings on one conference bridge, so [bmbouter] will create one videoconf bridge to keep it simple

# Sept 8

## Agenda
* CI status check
* pulp_file is broken - https://travis-ci.com/github/pulp/pulp_file/builds/183346449

# Sept 4

## Agenda

* CI status check
* https://travis-ci.com/github/pulp
* discussion: z-stream migrations allowed or not
* 3.6.3 release check-in
* 3.7.0 go/no-go release meeting times
* will anyone be able to release pulp_rpm with the proxy fix?
* proposal: remove the test_file_decriptors test from everywhere
* https://pulp.plan.io/issues/7452
* https://pulp.plan.io/issues/7453
* https://pulp.plan.io/issues/7454
* others?
* Docs day - schedule some time during pulpcon week?
* if release is on 22 we won't have time to address docs issues after pulpcon and before the release

# Sept 1

## Agenda

* CI status check
* https://travis-ci.com/github/pulp
* pulp_maven - black
* pulp_container - black
* pulp_rpm - sync issue
* pulp_gem - Enable cron and add it to contributors group
* Putting 1-release deprecation cycle epic into effect for 3.7
* move onto sprint
* https://pulp.plan.io/issues/7416
* add 3.7 milestone
* proposal for pulpcore and pulp_file
* require a test for each fix or feature
* https://www.redhat.com/archives/pulp-dev/2020-August/msg00053.html
* [bmbouter next steps]
* write a docs story, groom via #pulp-dev and add to sprint
* email back to thread linking to that on-sprint issue
* 3.6.1 release task https://pulp.plan.io/issues/7429
* dkilban to release later today

# August 28

## Agenda
* remove lgtm badges or enable lgtm code review?
* https://lgtm.com/projects/g/pulp/pulpcore/ci/
* https://lgtm.com/projects/g/pulp/pulpcore/context:python
* https://lgtm.com/projects/g/pulp/pulpcore/alerts?mode=list
* AI: remove
* should we release pulpcore 3.6.1?
* https://github.com/pulp/pulpcore/pull/859
* https://github.com/pulp/pulpcore/pull/860
* https://github.com/pulp/pulpcore/pull/863
* https://github.com/pulp/pulpcore/pull/864
* AI: yes!
* black update - https://github.com/pulp/pulpcore/pull/870
* Any objections to merging?
* Propose merge date of September 2, 2020
* Katello proposal to change layout
* ewoud is awaiting feedback: https://github.com/pulp/pulpcore/pull/799#issuecomment-682014733
* Spam cleaner seems to be removing users but not removing spam (eg https://pulp.plan.io/issues/5965#note-10)
* 2-release pulpcore deprecation policy next steps?
* https://www.redhat.com/archives/pulp-dev/2020-August/msg00065.html
* https://pulp.plan.io/issues/7411
* radical proposal: switch issue tracking to github

# August 25

## Agenda

* https://github.com/pulp/pulp-oci-images/pull/13
* How to manage/update our versions?
* https://pulp.plan.io/issues/7356

# August 18

## Agenda

* Adoption of django-cleanup https://github.com/pulp/pulpcore/pull/844#discussion_r469935506
* 3.7 tentative release date
* pulpcore 2-release backwards compatible policy?
* pulpcore and pulp_file test requirement
* https://www.redhat.com/archives/pulp-dev/2020-August/msg00053.html

# August 11

## Agenda

* How to version plugin_template? https://pulp.plan.io/issues/7273
* In order to use towncrier, we have to version plugin_template
* Maybe use the date (2020.08.11)?
* Spam: do we clean up comments and issues or just leave them for the spam script?
* Release
* release blockers
* https://github.com/pulp/pulpcore/pull/820 [yes]
* https://github.com/pulp/pulpcore/pull/834 [yes]
* https://github.com/pulp/pulpcore/pull/829 [merged]
* https://github.com/pulp/pulpcore/pull/770 [merged]
* https://github.com/pulp/pulpcore/pull/835 [no]
* https://pulp.plan.io/issues/7299 should be a blocker? [yes]
* announcement https://hackmd.io/xd5-j7xFSxSTJFn2cvO6Lg
* What is the installer readiness for release?
* needs review: https://github.com/pulp/pulp_installer/pull/385
* letsencrypt
* From Mike's status:
* Schedule issues:
- Will not finish pulp_installer's support for letsencrypt in time for 3.6.0 release today.
- I have a good backup plan that involves dropping CI testing. Will discuss with dklban / bmbouter.
* what is **The Plan** :
* dkliban releasing pulpcore/pulp_file
* blockers above need to be fixed/merged first
* RBAC docs for plugin-writers needed
* bmbouter sending email to pulp-dev@ with details, 3.7-ish proposal
* letsencrypt support *not* slated for 3.6, using Mike's fallback proposal
* plugin-release-owners?
* pulp_ansible
* pulp_container
* pulp_rpm

# August 7

## Agenda

* Redmine improvement:
* Problem:
* Version field is often out of date, users can't specify an appropriate version
* It's also shared between Pulp, Rpm and Puppet.
* Proposal:
* Stop using Version field
* Create Version - Pulpcore and Version - RPM (other plugins have their fields already).
* Version - Pulpcore should be shared across projects. other Version - * should belong to one project only.
* Add a new value as a part of the release process to keep it up to date.
* Any objections to giving ALL users ability to reopen issues?
* Except CLOSED - COMPLETE, CLOSED - DUPLICATE, and CLOSED - CURRENT RELEASE
* Need more feedback on pulp-dev list about closing issues
* https://www.redhat.com/archives/pulp-dev/2020-August/msg00017.html
* RBAC: call for review
* https://github.com/pulp/pulpcore/pull/815
* fixing some small things today, but hoping for review + merge by EOB today
* User docs are coming in a separate PR to be merged by EOB monday
* 3.6 release announcement
* Please write draft content here: https://hackmd.io/xd5-j7xFSxSTJFn2cvO6Lg

# August 4

## Agenda

* Create changelog for plugin_template?
* yes
* release with pulpcore
* we can do more often releases adhoc ones when needed
* 3.6 - do we need to send out email to announce?
* yes. Need to find release shepherd
* add backport to triage query
* I had made this test https://pulp.plan.io/issues/7269 and I didn't see it in triage
* The triage query is specifically looking for Triaged = No.
* FYI: external contribution to django-lifecycle needed for Pulp's use (which RBAC PR uses)
* https://github.com/rsinger86/django-lifecycle/pull/58
* 3.6 will need to use bmbouter's branch as a temporary workaround until it can be merged + released

# July 31

## Agenda

* Noticed that several projects are failing https://travis-ci.com/github/pulp
* Django update in pulp 2 https://github.com/pulp/pulp-packaging/pull/111
* Several CVE fixes:
* https://docs.djangoproject.com/en/3.0/releases/1.11.19/
* https://docs.djangoproject.com/en/3.0/releases/1.11.18/
* etc
* Changing download_concurrency to 10
* https://pulp.plan.io/issues/7212
* No objections on pulp-dev list to doing a migration
* Give users the ability to reopen closed issues?
* Limit to authors or allow everyone?
* All closed issues or CLOSED - WONTFIX?
* Limit to authors, all closed states other than CURRENTRELEASE, DUPLICATE
* RBAC for pulpcore: attempting to merge next week
* https://github.com/pulp/pulpcore/pull/815
* Endpoints will be protected one-by-one over several releases in pulpcore and in plugins
* Will send email to pulp-dev once docs are done
* Proposal: Start allowing old z-streams
* https://www.redhat.com/archives/pulp-dev/2020-July/msg00100.html
* Need to create a way to request backports, (needed regardless)
* Solution: create a `Backport` tracker type
* Supporting content mapping in export https://pulp.plan.io/issues/7252
* Could use some feedback today/Monday as I'll be blocked

# July 28

## Agenda

* CI status check
* pulp-rpm failing on CDN test - ppicka and dkliban
* pulp-container failing on cherrypick - x9c4
* pulp-openapi-generator failing - fix: https://github.com/pulp/pulp-openapi-generator/pull/35
* pulp-operator failing - fix: https://github.com/pulp/pulp-operator/pull/50
* Should we lower the download concurrency level?
* https://hackmd.io/@ggainey/pulp3_sync_concurrency
* blog post +1+1+1+1+1+1 +1
* migration to 10 +1+1+1+1
* no migration to 10 +1 +1 +1
* other (please add other options if needed)
* migration proposal:
* `<daviddavis> it's like a one line update: pulpcore-manager shell_plus -c "Remote.objects.all().filter(download_concurrency=20).update(download_concurrency=10)"`
* Feedback on OpenAPI v3 - is everything working?
* Python bindings docs - host on read the docs or pulpproject.org?
* preview: https://github.com/pulp/pulpcore/pull/805
* Reminder: add/vote for pulpcon topics: https://hackmd.io/hIOjFsFiSkGJR7VqtAJ8eQ

# July 24

## Agenda

* Should we delete alpha versions of released pulp packages from pypi?
* AI: david to remove alpha versions
* Can we configure modified as a closed state in redmine?
* currently tickets in milestones are only considered closed on release, which is basically when we close the milestone itself
* with modified ~ closed, the roadmap statistics would carry a message
* https://pulp.plan.io/projects/pulp_container/roadmap
* What do you all think about renaming master-branches to develop?
* Adjusting download concurrency -- needs a bit of testing first
* https://pulp.plan.io/issues/7212
* RBAC: permission creation solution FYI
* https://pulp.plan.io/issues/7210
* Redmine proposal: removal of ON_QA and Verified issue states which we don't use

# July 21

## Agenda

* Back up fixtures and take them down https://pulp.plan.io/issues/6649
* Repo name uniqueness constraint per repository type
* Adding 'user' field to tasks
* https://pulp.plan.io/issues/7180
* Reminder: add topics to pulpcon agenda
* https://hackmd.io/hIOjFsFiSkGJR7VqtAJ8eQ

# July 17

## Agenda

* Proposal: pulpcore 3.6 tentative release date Aug 11th
* RBAC needed at that time by galaxy_ng
* Roughly 4-5 weeks since pulpcore 3.5 release
* CI/CD team is no longer meeting regularly
* One of the things we did was spend 5 min to check the CI to see if any projects are failing
* https://travis-ci.com/github/pulp
* https://github.com/pulp/pulp_installer/actions?query=workflow%3A%22Pulp+CI%22
* https://github.com/pulp/pulp-oci-images/actions?query=workflow%3A%22Build+and+publish+OCI+Images%22
* Would like to make this check part of Tuesday or Friday bug triages
* RBAC for pulpcore update
* tasks are docs
* what other API endpoints need protecting for pulpcore's APIs to be fully RBAC protected?
* orphan cleanup
* exporters? exports? importers? imports?
* task groups?
* uploads?
* status & workers?
* can be fully public

# July 14

## Agenda

* zero down time upgrades
* https://pulp.plan.io/issues/7120
* do we use SessionAuthentication? https://github.com/pulp/pulpcore/blob/master/pulpcore/app/settings.py#L132
* call for more input: API designs for RBAC
* https://www.redhat.com/archives/pulp-dev/2020-July/msg00039.html

# July 10

## Agenda

* zero down time upgrades
* Retry fix https://github.com/pulp/nectar/pull/67/
* MODIFIED issues. Can these be closed out?
* https://pulp.plan.io/issues/6750
* https://pulp.plan.io/issues/6768
* https://pulp.plan.io/issues/6713
* https://pulp.plan.io/issues/6834
* https://pulp.plan.io/issues/6899
* bindings - too magical (where is the code? where are the docs?)
* release automation -- what's next?

# July 7

## Agenda

* allow_list and deny_list vs. includes and excludes .. Should we strive for uniform language between plugins or is that not practical?
* should we create a mail list for each mini-team? AKA async meeting
* IRC channel for sharing tech stuff
* Going to merge https://github.com/pulp/pulp-fixtures/pull/177
* The modular package could be helpful in Pulp 3 testing.
* release blocker
* [7087](https://pulp.plan.io/issues/7087)

# June 30

## Agenda
* Do we want to move mdellweg/ansible_module_pulp to the pulp namespace and publish as pulp.squeezer on galaxy? https://github.com/mdellweg/ansible_modules_pulp
* PulpCon call for participation draft review.
* https://hackmd.io/4dL6Eg2fSyq2MQsUydGM2A
* Should we relax the Repository name uniqueness accross all of Pulp to be just for a single plugin?
* Feedback? Can someone work on this before 3.5? https://pulp.plan.io/issues/6899

# June 26

## Agenda

* Should we stop automatically requesting QE to review PRs with changed tests?
* AI: david to file an issue
* When do we want to do the 3.5 release of pulpcore?
* Which major features are we still waiting on?
* RBAC as "tech preview" in core?
* enable django-admin w/ Users and Groups only
* add django-guardian as a dependency
* enable it as an Authentication backend
* would not be a user-facing feature
* July 7th
* AI: dkliban to send out announcement
* Content app treatment of "//" in URLs - https://pulp.plan.io/issues/7003
* AI: dkliban to update issue based on decision

# June 23

## Agenda

* The artifacts method on RepoVersion doesn't return all artifacts https://pulp.plan.io/issues/7021

# June 19

## Agenda

* Redmine Simplification 1: Delete the 'External' Redmine project. It's no longer used and 100% of issues are in CLOSED.
* Redmine Simplification 2: Configure Redmine to not show the Due Date, Start Date, and Estimated Time fields for all projects. They are unused.
* Redmine Simplification 3: Remove the 'Target Release - Deployment' field. It was never used. It originally was for the "puppet installer" from many years ago, which is now not even an active Redmine project.
* Redmine Simplficiation 4: Remove the 'Versions - Deployment' same reasoning as above, never used.
* Users are confused as to where to file "pulpcore" issues
* Could use some feedback about how to handle exporting Content with its own Content (DistributionTrees)
* https://hackmd.io/bI4Pc9fTRfGNAH_d6ASX4Q?view

# June 16

## Agenda

* Redmine Simplification 1: where to file CLI issues? Currently we have a CLI 'Category' and also a CLI project https://pulp.plan.io/projects/pulp-cli
* For Pulp 3 CLI issues, right now we are using the Pulp CLI project
* Redmine Simplification 2: should we delete or start using the 'API' category?
* Redmine Simplification 3: rename 'Sync Performance' tag to 'Performance'
* Plans for 'Release Engineering' tag in redmine?
* https://pulp.plan.io/issues/6974 Publication bug
* Calling Publication.create() creates an empty/invalid publication https://git.io/Jf7Mo
* Should we implement `incomplete` on Publications like we do for repo versions?
* Can https://github.com/pulp/plugin_template/pull/217 be closed out?

# June 9

## Agenda

* Redmine Simplification
* proposal: remove 'Smash Test' custom field
* proposal: remove 'Complexity' custom field
* proposal: remove 'QA Contact' custom field
* proposal: remove 'Blocks Release' custom field
* Local CI checks https://pulp.plan.io/issues/6938
* Is it possible to have friendly hackmd links?
* **YES, IT IS**: https://hackmd.io/c/tutorials/%2Fs%2Fhow-to-publish-note
* current: https://hackmd.io/SVCMjpwXTfOMqF2OeyyLRw
* ideal:
* https://hackmd.io/pulp-triage
* https://<default-pulp-shortener>/pulp-triage
* I published the pad at https://hackmd.io/@pulp/triage/edit
* So we only need to update it at the calendar +1
* Take down fixtures at fedorapeople.org https://pulp.plan.io/issues/6649
* Set a date?
* Who has access that can take them down?
* Triage on Friday - reschedule or cancel?

# June 5

## Agenda

* Redmine Simplification
* proposal: remove 'Known Issue for Release Notes' tag
* proposal: remove 'Verified' custom field
* proposal: remove 'Verification Required' custom field
* proposal: remove 'Backwards Incompatible' custom field
* Is there a way to turn off notifications for a particular issue in redmine (eg https://pulp.plan.io/issues/4248)
* Django Admin will likely be added to pulp, probably needed for RBAC

# June 2

## Agenda
* how to deduplicate pulpcore Documentation tag and Documentation category?
* announcing https://fixtures.pulpproject.org/fixtures/
* what is the purpose of the 'backlog' Tag?
* proposal: removing the 'Demo Requested' tag

# May 29

## Agenda
* redmine spam resolution discussion - https://pulp.plan.io/issues/5878
* [bmbouter] Can we remove the pulp-admin "category" from Redmine?
* schema view html - https://github.com/pulp/pulpcore/pull/724#issuecomment-634275398

# May 26

## Agenda

* Checkin for pulpcore 3.4.0 release tomorrow
* redmine notifications are effectively broken
* added check for uncommitted migrations https://github.com/pulp/plugin_template/pull/222
* merging pulp_file and pulpcore release scripts

# May 22

## Agenda
* review write_field usage audit
* minutes not being recorded https://pulp.plan.io/issues/6791
* discuss moving requirements out of setup.py to a dedicated file
* https://www.redhat.com/archives/pulp-dev/2020-May/msg00124.html
* Deferring https://github.com/pulp/pulpcore/pull/577 because we can't review today
* Closing 2.17.0 milestone that is old and released

# May 19

## Agenda

* pulpcore 3.4.0 release date proposal: May 27th
* pulpcore 3.4.0 call for blockers
* review write_field usage audit
logs: https://pulpadmin.fedorapeople.org/triage/pulp-meeting/2020/pulp-meeting.2020-05-19-14.30.html

###### tags: `Minutes`