Action Items from various sessions

[bmbouter] to send proposal for multi-tenancy use of RLS to pulp-dev
- https://pganalyze.com/blog/postgres-row-level-security-django-python
[mdellweg] we need to have some open deep-dives on technology issues - need someone to hit up the mailing-list to get interested parties and suggestions, and open this discussion up to more input (from lockless pulp)
[dkliban] continue discussion/investigation into cherry-picking migrations
[] explore matrix
[ipanova] flip open floor with triage? Add to the next open floor agenda

Interesting Notes From Discussions

UI with cockpit?
RBAC and REST API is very useful as-is
other fedora projects thaty could use pulp:
- copr
- cobbler - SUSE looking into Pulp
- archived copies for bodhi - fedora workflow improvements - would be WAY easier to take advantage of pulp, if pulp3 were already available in Fedora
- package ansible-installer-role as its Own Thing
pulp_deb docs has a "Feature Overview" section - not created w/plugin_template - maybe we can consider adding?
"Not a big fan of the phrase 'Pulp4'" - psychological impact of "Oh No, Not Again"
Release process/versioning - don't have to follow the 'standard' of pulpcore/pulp_rpm, but it makes life easier to follow the crowd
Would love to have a "live-demo" pulp server available. Populated with "real-ish" content (ie, at least some rpm channels synced, ansible collections synced from ah/galaxy.ansible.com, etc for all supported plugins)
- Possibly a read only public one, and a lightly RBAC'ed 'rw' internal one

finding pulp-mailing-lists is REALLY HARD
- can't find redhat.com lists
- fedora lists are discoverable
- assuming we move - fedoramagazine/community blog post(s)
don't have regular community meetings?
- we do, but nobody knows about them
- flip open floor with triage?
social media
- iteraction with people ( in tweets). In addition to release announcements use open quesions - engage people
- explore matrix
guidelines/suggestions for "how to do things" for the plugin-contributor