Meeting Purpose: Improve Brew/Koji communication with upstream(community)
Attendees: ngompa(Neal Gompa ), dgilmore, .dgregor , breilly, tkopecek, yzhu, eberdnik, puiterwijk ,Don Zickus, Jeff Burke , Pat Riehecky, William Peck, Mike McLean, Jon Disnard, Yuli
Summary:We had the 1st Koji community meeting on Dec, 6 with 15 attendees from upstream, Kernal CI, Engineering team and so on. The lively discussion on koji last for more than 60 mins and left several action items for Koji. Stay tuned our next Koji meeting - Feb 7.
Meeting Notes/Actions:- Changes in the last year
- Brew/Koji team expanded development and more frequent releases
- Dedicated QE resources - Effort on test coverage and automation
- Koji 1.15
- User discussion / input : Fedora rel-eng
- Koji 1.16
- Community Feedback
- kernel CI - potentially hundreds of kernel builds a day. How do we scale to that with koji?
- systems engineering team (jeff burke) looking at bringing CI into the productization
- Neal - fedora rust sig / using koji in mageia - https://wiki.mageia.org/en/Feature:Migrate_to_Koji
- papat - scientific linux - koji namespaces
- Message bus plugin is heavily used at scientific linux - just tracking 'TAG/UNTAG' right now, but it is the core workflow
- Message bus plugins
- koji has two used internally at red hat, one is likely to be deprecated
- fedora has its own plugin
- how do external users use the plugins? further discussion would be useful - Filed https://pagure.io/koji/issue/736
- any thoughts on moving kojid to amqp to further leverage message bus?
- python 3
- cli / library support added in 1.13
- what would be next? builder is the preference
- Brew/Koji contribution - Jeff Burke https://pagure.io/koji/stats#authors
- At present QE/Automation for Brew, have plan in Koji in future
- Installation / deployment of koji continues to be a pain point
- wiki for koji ? NO,but docs https://docs.pagure.org/koji/server_howto/
- #koji could use more activity
- "office hours" would be particularly useful