# 2021 Open Floor/Triage Minutes
## 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
###### tags: `Minutes`