# 2020 Open Floor/Triage Minutes
## 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`