# Pulpcore 2020 Archive

# December 15, 2020

## Previous action items
* [dkliban] to schedule backlog grooming meeting
* done
* [dkliban] to email plugins about and close out https://pulp.plan.io/issues/7895
* email sent, the issue will be closed today
* [bmbouter] release pulp_file 1.5.0
* dkliban will do it today

## Topics
* Move off Travis https://pulp.plan.io/issues/7859
* Wrap up remaining issues?
* ttereshc to pick up the cherrypick processor removal
* need a volunteer for the reamining task to publish docs on every push
* pulp_file 1.5.0 https://pulp.plan.io/issues/7953
* Looks like brian was able to fix the deprecation https://github.com/pulp/pulp_file/pull/451
* Still needs release and a volunteer
* Object labels https://pulp.plan.io/issues/7127
* Updated issue with the design
* Hoping someone can move this forward to deliver in pulpcore 3.10
* Backports https://pulp.plan.io/issues/7950 and https://pulp.plan.io/issues/7951
* on hold till the fixes are merged
* galaxy requirement: pulpcore>=3.7,<3.9 (backport will be needed in 3.7 and 3.8) https://github.com/ansible/galaxy_ng/blob/4.2.0/setup.py#L60
* Is it ok that user can't see any checksum for on_demand content? https://paste.ofcode.org/nXQBX7zVQWaxRbCFx2zrFw
* I wonder if it matters for the FIPS reporting case
* probably ok to have it as is, not much added value but a hassle to make the remote checksum available
* RBAC - objects that do not have access policy are accesible by default
* should we change for the opposite behaviour?
* discuss on pulp-dev [x9c4]
* bump of the plugin version during the pulpcore compatiblity release
* what is the reason to bump Y version if no major changes have been in the plugin?
* the change of the floor version of pulpcore dependency
* should we document this somewhere? It might be helpful to have a guide that will tell when to bump plugin version and pulpcore version in the plugin release process
* update the release guide and plugin templates in plan.io
* Can we make the users, groups and permissions resources manageble by the rest-api?
* enables us to add cli commands for them
* Can we add a test that searches for log messages with deprecation warnings?
* it would be nice, but where?
* plugin-from-pypi? probably too late
* [x9c4] write a task
* Should backports be backported to every (minor) version between the fix and the requested version
* We need an LTS, 3.7 is defacto an LTS version.

## Action Items
* [dkliban] to release 1.5.0
* [ttereshc] work on https://pulp.plan.io/issues/7869
* [x9c4] write a task to have a test that searches for log messages with deprecation warnings [done]
* https://pulp.plan.io/issues/7997
* [x9c4] start a pulp-dev thread about RBAC - objects that do not have access policy are accesible by default [done]
* [dklban] to look at https://github.com/pulp/pulpcore/pull/799
* [ttereshc] update the release guide and plugin templates in plan.io clarify when to bump plugin's Y release.

# December 8, 2020

## Previous action items
* [ttereshc] to file a task to implement plugin removal
* Done https://pulp.plan.io/issues/7822
* [fao89] to figure out the use case for this fix https://github.com/ansible/galaxy_ng/pull/572/files#diff-6b9632eb49cb924f729282743cdac58a36f7625974fef12da2ea7b946ac19866R32
* DRF raises 400/500 instead of 409
* https://issues.redhat.com/browse/AAH-152
* https://issues.redhat.com/browse/AAH-132
* https://httpstatusdogs.com/409-conflict
* https://http.cat/409
* Wait for user to report this. We need a reproducer

## Topics
* Backlog grooming
* pulp_file 1.5.0 release
* bmbouter to fix plugin config version and release
* Object label proposal
* https://hackmd.io/N4WFhHGWQtib7D1JIKzCDQ
* pulp_file docs
* Looks like the 1.4.0post1 release build succeeded? Docs still say 1.3
* [dkliban] fix in progress
* Task to take down read the docs for pulp_file: https://pulp.plan.io/issues/7932
* Move off Travis check in
* https://pulp.plan.io/issues/7859
* Meet on Dec 15 & 22?
* Cancel Dec 22

## Action items
* [dkliban] to schedule backlog grooming meeting
* [dkliban] to email plugins about and close out https://pulp.plan.io/issues/7895
* [bmbouter] release pulp_file 1.5.0

# December 1, 2020

### Previous action items
* [fao89] look at driving forward release automation.
* Automate post-release steps (branching, bumping to dev versions, updating template config, etc)
* https://pulp.plan.io/issues/7817 (needs grooming, please provide feedback)
* https://pulp.plan.io/issues/7818 (~~needs grooming~~)
* Done for now, focus is on moving off Travis for the short term.
* Defer until after 3.9 GA
* [ttereshc] to file a task to implement plugin removal
* Done https://pulp.plan.io/issues/7822
* [fao89] to figure out the use case for this fix https://github.com/ansible/galaxy_ng/pull/572/files#diff-6b9632eb49cb924f729282743cdac58a36f7625974fef12da2ea7b946ac19866R32
* DRF raises 400/500 instead of 409
* https://issues.redhat.com/browse/AAH-152
* https://issues.redhat.com/browse/AAH-132
* [david] updates on tagging planning https://pulp.plan.io/issues/7127
* Design is in progress. Will email out this week.

### Topics
* pulp_file 1.4.0
* ttereshc can be voluntold to do that
* dkliban to work on this this week
* alternate content sources design review
* https://pulp.plan.io/issues/7832

### Action items
* [ttereshc] to file a task to implement plugin removal
* [fao89] to figure out the use case for this fix https://github.com/ansible/galaxy_ng/pull/572/files#diff-6b9632eb49cb924f729282743cdac58a36f7625974fef12da2ea7b946ac19866R32

# November 24, 2020

### Previous action items
* [david] To send out last call for feedback before merging https://github.com/pulp/pulp-ci/pull/737
* Hold off until after Github Actions move
* [fao89] look at driving forward release automation.
* Automate post-release steps (branching, bumping to dev versions, updating template config, etc)
* https://pulp.plan.io/issues/7817 (needs grooming, please provide feedback)
* https://pulp.plan.io/issues/7818 (~~needs grooming~~)
* [david] ~~a Pulp query that shows issues for pulpcore (filters out installer, operator, etc)~~
* Done: https://pulp.plan.io/projects/pulp/issues?query_id=166
* [david] ~~move django fips repo to pulp~~
* Done: https://github.com/pulp/django/
* [david] ~~notify pulp-list mailing list of 3.9 release schedule~~
* [ttereshc] ~~file a task to have task management code manage working dir~~
* [david] ~~to start on tagging planning~~
* https://pulp.plan.io/issues/7127
* Started. Met with David Newswanger yesterday.
* Hope to have draft design by next week.

### Topics
* two feature plans pending for pulp-dev discussion
* parallelizing orphan cleanup while avoiding runtime errors(ipanova)
* started wrting down a proposal
* alternate content sources(bmbouter)
* needs feedback
* meeting with Katello next week
* https://pulp.plan.io/issues/7832
* RBAC pulpcore issue
* https://pulp.plan.io/issues/7710
* 3.9 blocker
* how to remove a plugin, including the relevant data in the db
* pulpcore-manager command?
* checks if the plugin is installed
* if not, drops all <plugin_app_label>_* tables?
* use cases
* migration plugin is the one which everyone would want to remove eventually
* it's needed for katello
* if no general solution is available, we will make some custom one for the migration plugin only
* incompatible plugins, one might want to remove one
* ttereshc to create a task
* Validate existing group on pulpcore?
* https://github.com/ansible/galaxy_ng/pull/572/files#diff-6b9632eb49cb924f729282743cdac58a36f7625974fef12da2ea7b946ac19866R32
* pulpcore uses Django Group model, not a custom one, so no need
* https://github.com/django/django/blob/7af8f4127397279d19ef7c7899e93018274e2f9b/django/contrib/auth/models.py#L109
* 3.10 release
* Tentatively planned for Jan 8? due to holidays. Feedback welcome.
* probably too early, maybe end of January?
* Galaxy NG will likely need a release of pulpcore at the end of Jan'21
* Conference driven release
* Decide after 3.9 release
* Needs volunteer to release
* An assumption in the ArtifactSaver stage that a d_artifact always has a remote.
* https://github.com/pulp/pulpcore/blob/master/pulpcore/plugin/stages/artifact_stages.py#L297
* Is it intentional?
* Not intentional
* move the check on line 300 couple of lines up
* Currently causes issues for the migration
* https://pulp.plan.io/issues/7876

### Action items
* [david] To send out last call for feedback before merging https://github.com/pulp/pulp-ci/pull/737
* Hold off until after Github Actions move
* [fao89] look at driving forward release automation.
* Automate post-release steps (branching, bumping to dev versions, updating template config, etc)
* https://pulp.plan.io/issues/7817 (needs grooming, please provide feedback)
* https://pulp.plan.io/issues/7818 (~~needs grooming~~)
* [ttereshc] to file a task to implement plugin removal
* [fao89] to figure out the use case for this fix https://github.com/ansible/galaxy_ng/pull/572/files#diff-6b9632eb49cb924f729282743cdac58a36f7625974fef12da2ea7b946ac19866R32
* [david] updates on tagging planning https://pulp.plan.io/issues/7127

## November 10, 2020

### Previous action items
* [david] To send out last call for feedback before merging https://github.com/pulp/pulp-ci/pull/737
* ~~[dkliban] file a task for running tests for multiple plugins in one fips environment in the installer nightly~~
* [fao89] look at driving forward release automation.
* Automate post-release steps (branching, bumping to dev versions, updating template config, etc)
* [david] a Pulp query that shows issues for pulpcore (filters out installer, operator, etc)
* [david] move django fips repo to pulp
* [david] schedule go/no-go for nov 24
* Done
* ~~[x9c4] to follow up on mailing list with proposal for setting pulpcore requirements for plugins [done]~~

### Topics
* Review 3 month planning
* Correlation ID PR https://github.com/pulp/pulpcore/pull/1017
* Ready for review
* No log messages from CI container
* Skip log check
* WorkingDirectory
* https://github.com/pulp/pulp_rpm/pull/1879#issuecomment-724653199
* Have task management code manage working directory in 3.9
* Remove WorkingDirectory in 3.10

### Action Items
* [david] To send out last call for feedback before merging https://github.com/pulp/pulp-ci/pull/737
* [fao89] look at driving forward release automation.
* Automate post-release steps (branching, bumping to dev versions, updating template config, etc)
* [david] a Pulp query that shows issues for pulpcore (filters out installer, operator, etc)
* [david] move django fips repo to pulp
* [david] notify pulp-list mailing list of 3.9 release schedule
* [ttereshc] file a task to have task management code manage working dir
* [david] to start on tagging planning

## November 3, 2020

### Previous action items
* [david] To send out last call for feedback before merging https://github.com/pulp/pulp-ci/pull/737
* [david] schedule pulpcore FIPS meeting with bmbouter for later in November
* Done.
* [dkliban] file a task for running tests for multiple plugins in one fips environment in the installer nightly
* [fao89] look at driving forward release automation
* [x9c4] to backport https://pulp.plan.io/issues/7737 and release 3.6.z
* In progress
* [dkliban] cherry-pick 'request' commit to 3.8 branch
* Abandoned since change is a feature
* [ipanova] open a doc bug re:don't use settings in the models fields
* done https://pulp.plan.io/issues/7776
* [daniel] revert data corruption issue
* done. also have PR for repair all repos api endpoint.

### Topics
* FIPS epic for pulpcore - https://pulp.plan.io/issues/3778
* Closed out, new issues to be filed as needed
* Release automation next steps
* Post-release steps (branching, bumping to dev versions, updating template config, etc)
* Need a Pulp query that shows issues for pulpcore (filters out installer, operator, etc)
* Have automation open all PRs at once? Makes it easy to have a reviewer review everything together
* Installation of our fips patch to Django is not working reliably in pypi and source installation
* ask mikedep333 to take a look
* docs day
* nov 23
* go/no-go meetings?
* when do plugins bump requirement when they need a pulpcore feature
* Bump the floor version when you merge the change that requires pulpcore feature
* If you require a change in pulpcore master, bump the floor to dev version
* Remove dev from pulpcore version when releasing a plugin

### Action Items
* [david] To send out last call for feedback before merging https://github.com/pulp/pulp-ci/pull/737
* [dkliban] file a task for running tests for multiple plugins in one fips environment in the installer nightly
* [fao89] look at driving forward release automation.
* Automate post-release steps (branching, bumping to dev versions, updating template config, etc)
* [david] a Pulp query that shows issues for pulpcore (filters out installer, operator, etc)
* [david] move django fips repo to pulp
* [david] schedule go/no-go for nov 24
* [x9c4] to follow up on mailing list with proposal for setting pulpcore requirements for plugins

## October 27, 2020

### Previous action items
* [ttereshc] follow up on relative_path problem on mailing list
* Done
* [david] To send out last call for feedback before merging https://github.com/pulp/pulp-ci/pull/737
* [dkliban] to follow up with bmbouters about fips checks
* [ipanova] send an email to archive PUPS repository and file docs task
* Done https://www.redhat.com/archives/pulp-dev/2020-October/msg00050.html
* [dkliban] file a task for running tests for multiple plugins in one fips environment in the installer nightly

### Topics
* Tasking system improvements
* orhpan cleanup running in parallel
* bmbouter and ipanova collab on the design
* moved back a week
* resource manager bottleneck
* next step is to do an evaluation of tasking system performance
* Enforce funtional tests in pulp_file
* Add a check in Travis
* filed issue https://pulp.plan.io/issues/7748 potentially consider adding option "enforce_tests" to the template instead?
* Commit bit for mdellweg
* 2 required reviews affects release process
* Should we pre-agree that 2 specific people are available for reviews?
* Would excluding release branches from 2 ack be a solution?
* Go back to 1 required review, but opt into asking for 2 reviews for any significant change?
* pulpbot to approve release PRs?
* For now, decrease # of required ACKs for release branches, designate reviewers, and improve automation
* pulpcore version in plugin api
* https://pulp.plan.io/issues/7624
* https://pulp.plan.io/issues/6671
* need a volunteer to backport a fix to 3.6 and release it
* https://pulp.plan.io/issues/7737
* pulpcore 3.8.1 - can in include a backwards compatible change to the plugin API?
* https://github.com/pulp/pulpcore/commit/4063c346b4b75ffe74d2b0a95d650732dfb5ed8e
* settings should not be used in the models fields
* https://github.com/pulp/pulp_container/pull/170/files#diff-1707426fbe1933a12da3490e42f0dbceea79e47f7c883708c0b0cb49755b1d94L383
* https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/upload.py#L23
* proposal - add to the plugin writers docs to not use settings in the models but rather 'hardcode' those values
* Silent data corruption bug
* https://pulp.plan.io/issues/7676#note-8
* revert the commit
* cp to 3.7 and 3.8
* open a new issue to repair the damage done
* 3.9.0 planned date?
* daviddavis to release (tentatively November 30)
* When pulpcore is released and master branch version is bumped, the nightly job for plugins will start failing.
* Release pulp_file?

### Action items
* [david] To send out last call for feedback before merging https://github.com/pulp/pulp-ci/pull/737
* [david] schedule pulpcore FIPS meeting with bmbouter for later in November
* [dkliban] file a task for running tests for multiple plugins in one fips environment in the installer nightly
* [fao89] look at driving forward release automation
* [x9c4] to backport https://pulp.plan.io/issues/7737 and release 3.6.z
* [dkliban] cherry-pick 'request' commit to 3.8 branch
* [ipanova] open a doc bug re:don't use settings in the models fields
* [daniel] revert data corruption issue

## October 20, 2020

### Previous action items
* [david] to update https://github.com/pulp/pulp-ci/pull/737
* ~~When PR is ready, email about the PR and ask for feedback~~
* ~~Done. Date set to Oct 23, 2020~~
* Will send an announcement and plugin information once merged
* ~~[ina] to file redmine issue about demo video requirement~~
* ~~done https://pulp.plan.io/issues/7703 and https://pulp.plan.io/issues/7704~~
* ~~[david] to make meeting one hour~~
* ~~Done!~~
* [ttereshc] follow up on relative_path problem on mailing list, in progress

### Topics
* SigningService changes (on sprint, fyi really)
* https://pulp.plan.io/issues/7700
* https://pulp.plan.io/issues/7701
* Improvements to FIPS checks
* https://pulp.plan.io/issues/7696
* need one on checking for "future checksum use" e.g. during publish time
* We no longer use PUPS, do we? we should update docs
* https://docs.pulpproject.org/pulpcore/contributing/index.html#suggesting-changes-to-the-pulp-development-process
* maybe also mark repo a deprecated?
* how and where should we propose process improvement suggestions?
* [bmbouter] I can't attend so leaving comment here, +1 to archiving this repo and announcing the process as no longer used. We should try to move the relavent parts to the docs somehow (maybe file tickets). I don't expect to replace this process with a formal process.
* Enforce funtional tests in pulp_file
* Add a check in Travis
* docs style guide question: newlines after each sentence or no?
* https://pulp.plan.io/issues/7570
* [bmbouter] my concern with having newlines instead of paragraphs was that the docs unrendered become difficult to read (even though the blame log does get easier).
* Backport to 3.7
* https://pulp.plan.io/issues/7702
* Should we regularly review redmine issues filed in between pulpcore meetings? All except the "issue" type, since it's covered at triage.
* https://bit.ly/3m1e3nr
* running functional tests for all FIPS compliant plugins
* re-prioritize https://pulp.plan.io/issues/4832
* +1

### Action items
* [david] To send out last call for feedback before merging https://github.com/pulp/pulp-ci/pull/737
* [ttereshc] follow up on relative_path problem on mailing list
* [dkliban] to follow up with bmbouters about fips checks
* [ipanova] send an email to archive PUPS repository and file docs task
* [dkliban] file a task for running tests for multiple plugins in one fips environment in the installer nightly

## October 13, 2020

### Previous Action Items
* [bmbouter] to write up SigningService public key and immuatbility requirement
* [dkliban] email pulp-dev about namespacing base_path of Distributions. ask for usecases outside of pulp_container.
* [bmbouter] to write up tasking system improvements

### Topics
* auto merge PRs?
* Enable for pulpcore
* david to revisit https://github.com/pulp/pulp-ci/pull/737
* require 2 acks?
* demo video requirement for pulpcore/pulp_file features?
* We need to document this requirement
* Update the demo docs
* 3 month planning
* relative_path problem?
* AI: ttereshc to follow up
* Signing improvements
* Tasking system improvements
* auto-distribute (pulp_file)
* RBAC for pulpcore
* labels?
* Pulp AdminModels
* Docs day!
* https://pulp.plan.io/issues/7692
* https://pulp.plan.io/issues/7476
* https://pulp.plan.io/issues/7475
* https://pulp.plan.io/issues/7474
* https://pulp.plan.io/issues/6990
* https://pulp.plan.io/issues/6658
* do we have docs day query?
* https://pulp.plan.io/issues?query_id=150
* look through https://pulp.plan.io/issues?query_id=128 to find more to add to sprint
* Pulpcore tests rely on pulpcore.app.settings
* https://pulp.plan.io/issues/7690
* This meeting is not long enough

## Action Items
* [david] to update https://github.com/pulp/pulp-ci/pull/737
* When PR is ready, email about the PR and ask for feedback
* Will send an announcement and plugin information once merged
* [ina] to file redmine issue about demo video requirement
* [david] to make meeting one hour
* [ttereshc] follow up on relative_path problem on mailing list

## October 6, 2020

### Previous action items
* [bmbouter] to write up SigningService public key and immuatbility requirement

### Topics
* 2 approvals for merging pulpcore PRs?
* [david] will configure requirement in github
* Namespaces as a pulpcore feature
* Each namespace could be associated with any resource that needs to be accessed by an individual or a group of individuals.
* In pulp_container distributions are associated with a namespace. In other plugins I could see repositories being associated with a namespace also.
* Correlation id comments https://pulp.plan.io/issues/4689#note-30
* Task system improvements planning
* orphan cleanup run in parallel
* removal of resource_manager from the architecture
* auto-merge after two acks?
* Not a quorum today. Revisit next week.
* Start using code owners more?
* For now, just ping code owners on PRs

### Action Items
* [bmbouter] to write up SigningService public key and immuatbility requirement
* [dkliban] email pulp-dev about namespacing base_path of Distributions. ask for usecases outside of pulp_container.
* [bmbouter] to write up tasking system improvements

## September 29, 2020

### Previous action items
* https://pulp.plan.io/issues/7487 is breaking pclean
* [daviddavis] revert and revisit for 3.8
* [bmbouter] to coordinate planning on https://pulp.plan.io/issues/6926
* no core changes are needed to complete this task

### Topics
* Dependency PRs
* https://github.com/pulp/pulpcore/pulls?q=is%3Aopen+is%3Apr+label%3Adependencies
* daviddavis to review and merge
* Upload chunks stored in default storage: https://github.com/pulp/pulpcore/pull/914
* How to handle upgrades?
* Add note to release notes that users have to clean up uploads before upgrading
* Publish pre-releases of pulpcore - https://pulp.plan.io/issues/7608
* 3.7.1 needs to be published today
* Retro from release
* proposal: stop releasing pulp_file "with" pulpcore
* the installer needs a plugin for test
* with new deprecation policy, last version of pulp_file should work

### Action Items
* [bmbouter] to write up SigningService public key and immuatbility requirement

## September 22, 2020

### Previous action items
* [bmbouter] to respond and close https://github.com/pulp/pulpcore/pull/659
* Done!

### Topics

* Keeping the plugin API's call interface official (aka no private or semi-private interfaces)
* Agreed, document as part of a greater push for better plugin writer docs
* Pulpcore grooming on Friday
* David will be at DevConf.us
* dkliban to drive
* Signing reboot, next steps
* https://pulp.plan.io/issues/6926
* 3.7.0 release is happening today
* https://pulp.plan.io/issues/7463

### Action Items

* https://pulp.plan.io/issues/7487 is breaking pclean
* [daviddavis] revert and revisit for 3.8
* [bmbouter] to coordinate planning on https://pulp.plan.io/issues/6926

## September 8, 2020

### Previous action items
* [dkliban] file a story to allow auto-publish and distribute
* Done. https://pulp.plan.io/issues/7469
* [bmbouter] to respond and close https://github.com/pulp/pulpcore/pull/659
* not done, moved forward to next week

### Topics

* 3.7.0 is scheduled for Sept 22
* https://pulp.plan.io/issues/7463
* Go/No-Go: Tuesday Sept 15th, 12pm - 12:30pm EDT. https://everytimezone.com/s/68f4535a
* Pulp UI project accepted by UMAss Lowell. Professors have started recruiting students to take on the project.

### Action Items
* [bmbouter] to respond and close https://github.com/pulp/pulpcore/pull/659

## September 1, 2020

### Previous action items
* [dkliban] file a story to allow auto-publish and distribute
* [daviddavis] announce possible black PR merge date
* Done. Will merge tomorrow.
* [dkliban] call for release 3.6.1 tomorrow at open floor
* Going out today
* https://pulp.plan.io/issues/7429

### Topics
* PRs without any activity in the past month. Can we move them forward or close them?
* https://github.com/pulp/pulpcore/pull/659
* https://github.com/pulp/pulpcore/pull/610
* https://github.com/pulp/pulpcore/pull/657
* closed
* Need a host for the next meeting September 8
* David has training, ttereshc and ipanova are on pto
* Roll out deprecations to plugins?
* https://github.com/pulp/plugin_template/pull/257
* Plugins can customize this.
* New plugins will have deprecations by default.
* Existing plugins can decide and roll it out themselves.

### Action Items
* [dkliban] file a story to allow auto-publish and distribute
* [bmbouter] to respond and close https://github.com/pulp/pulpcore/pull/659

## August 27, 2020

### Previous action items
* [daviddavis] to add a 2-hour backlog grooming meeting to focus on pulpcore backlog
* Scheduled for Monday August 31
* [dkliban] file a story to allow auto-distribution of publications
* a user on the irc had similar request and filed an issue https://pulp.plan.io/issues/7390
* his main complaint was he needs to re-publish and assign a new publication to the distribution everytime when content gets added/removed

### Topics
* black update - https://github.com/pulp/pulpcore/pull/870
* We've pinned for now.
* Wait until 1.0 release? merge now?
* 3.6.1 release
* OpenAPI - https://github.com/pulp/pulpcore/pull/859
* OpenAPI - https://github.com/pulp/pulpcore/pull/860
* PulpTemporaryFile - https://github.com/pulp/pulpcore/pull/863
* Groups API validation - https://github.com/pulp/pulpcore/pull/864
* David has meeting conflict again next week September 1
* Reschedule or find new host?
* ttereshc will host
* docs.pulpproject.org is going to forward to docs.pulpproject.org/pulpcore/
* https://github.com/pulp/plugin_template/pull/253 - Adds job for publishing docs to docs.pulpproject.org.
* https://pulp.plan.io/issues/7229
*

### Action Items
* [dkliban] file a story to allow auto-publish and distribute
* [daviddavis] announce possible black PR merge date
* [dkliban] call for release 3.6.1 tomorrow at open floor

## August 18, 2020

### Previous action items
* None

### Topics
* Grooming the backlog?
* https://pulp.plan.io/projects/pulp/issues?status_id=1
* Remove pulpcore items from sprint?
* https://pulp.plan.io/projects/pulp/issues?query_id=150
* How should the UI update a Distribution associated with a repository? Right now we don't have a relationship between distributions and repositories. So there is no way to schedule a task to update a distribution before a publication finishes being created.
* Semi-related, similar problem with publications and repo-verisions unless using "auto-publish" https://pulp.plan.io/issues/4793
* RBAC for UI endpoints being added in 3.7
* Proposal: functional test required for each feature and bug fix for pulpcore and pulp_file
* pulp_rpm has this convention already

### Action items
* [daviddavis] to add a 2-hour backlog grooming meeting to focus on pulpcore backlog
* [dkliban] file a story to allow auto-distribution of publications

## August 4, 2020

### Previous action items
* ~~[daviddavis] disable cherry pick processor for pulpcore and pulp_file~~

### Topics
* Are we ready for 3.6 release date (August 11)?
* RBAC should be ready although not all endpoints will be protected
* OpenAPIv3 ironed out
* Are rewritten stages going in as previously discussed? If so, they need review.
* [mdellweg] to review
* Backporting process for pulpcore and pulp_file
* Check that triage queries include backport tracker type
* [daviddavis] done

### Action items

## July 28, 2020

### Previous action items
* [bmbouter and daviddavis] to look into merging https://github.com/pulp/pulpcore/pull/763
* merged!
* [bmbouter] aggregate tags/labels feedback on the issue
* [ipanova] mostly waiting on CDT to ack.

### Topics
* The same two declarative content units in one batch which differ only in a remote they refer to
* https://pulp.plan.io/issues/7147
* is it too unexpected use case?
* should it be fixed in the pulpcore (or is it too special case and better be fixed in the plugin)?
* Yes, let's fix it in pulpcore. Talk about implementation later.
* adjusting default download concurrency?
* https://hackmd.io/@ggainey/pulp3_sync_concurrency
* Discuss more at open floor
* Pulpcore cherry pick processor
* retiring the cherry pick processor for pulpcore and pulp_file
* cherry picks will be done on an as-needed basis by hand

### Action items
* [daviddavis] disable cherry pick processor for pulpcore and pulp_file
* Close out open PRs
* Delete "Needs Cherry Pick" label

## July 21, 2020

### Previous action items
* [bmbouter and daviddavis] to look into merging https://github.com/pulp/pulpcore/pull/763
* Pinged contributor. Will give him one more week.
* ~~[daviddavis] update correlation id feature to store cid on task instead of passing it around~~
* ~~[daviddavis] to create pulpcore hackmd pad~~
* [bmbouter] to follow up about use cases for tags/labels
* ~~[dalley] to file an issue for performance improvement PRs and assign it to a 3.6 milestone~~

### Topics
* github team membership check-in
* https://github.com/orgs/pulp/teams/core/members
* Cherry pick to 3.5 is failing
* https://github.com/pulp/pulpcore/pull/796
* dkliban to update template_config.yml on 3.5 branch
* Omit some views in OpenAPI schema - https://pulp.plan.io/issues/7133
* Add to sprint
* Adding 'user' to the Task
* https://pulp.plan.io/issues/7180
* Discuss more at open floor

### Action Items
* [bmbouter and daviddavis] to look into merging https://github.com/pulp/pulpcore/pull/763
* [bmbouter] aggregate tags/labels feedback on the issue

###### tags: `pulpcore`