*Meeting Purpose: * Improve the communication with upstream(community) *Attendees: *ngomp, dgregor, sly, jdisnard, tkopecek, yzhu, Jana, Egor, Brendan,mikem, yulwang
*Meeting Summary:*3 koji stakeholders besides Brew team joined our 2nd koji community meeting. we mainly talked last meeting actions and Koji recent update and get the feedback from community. detail please check our meeting docs: https://public.etherpad-mozilla.org/p/KojiMarch2018
*Meeting Notes:* 1.Review last action items
- "office hours" proposal - Every Tue/Thurs 10:00 - 11:00AM US/ET (welcome your feedback in the meeting notes)
- koji-devel could be there
- which channel? #koji ? #fedora-releng (larger)
- Let's use #koji
- won't be active all the time, but when we have koji conversations let's have them in #koji
- AI: Send an announcement to koji-devel@
- Research on how do external users use the Message bus plugins:
- https://pagure.io/koji/issue/736
- Question from mikem: who might use it?
- AI: mark as deprecated in 1.16 and send out an announcement to speak up if it's still needed(release note+ separate notification)
2.Koji update:
- Koji 1.15 released on Dec 2017 https://docs.pagure.org/koji/release_notes_1.15/
- Fedora in process of upgrading to 1.15
- Koji 1.16 planning: Mar 28, 2018 https://pagure.io/koji/roadmap?status=all&milestone=1.16
- Koji 1.17 planning
3. Community feedback / input
- Mageia
- bootstrap chroot is very important to Mageia. One challenge for koji is that the repo used to bootstrap is likely different than the repo for building
- Maybe use the same repos for both? We already do this for SRPM -> RPM build chroots. Mock's current bootstrap feature works that way.
- issues around auto-generating the SRPM changelog. Questions around how to integrate this prebuild script
- https://gitlab.com/mdklinux/mgapkg-koji
- Variety of issues related to installing koji. messagebus plugin isn't compiling. Some other things... (Neal, can you fill in?)
- Opportunity to use Mageia as a way of making installation easier, or at least documenting it better
- Let's move this to office hours.
- Fedora Releng - Sly
- Schedule: https://fedoraproject.org/wiki/Releases/28/Schedule
- Beta Freeze was March 6
- In the middle of Fedora 28
- Currently no issues with koji
- Have not started Fedora 29 planning yet
Thanks, Yuli
Thank you Yuli for sending this!
Would you please let me know when you expect to have the next Koji community meeting? I want to attend, although I seem to keep missing the meetings :)
- Ken
On Wed, Mar 7, 2018 at 10:13 PM, Yuli Wang yulwang@redhat.com wrote:
Meeting Purpose: Improve the communication with upstream(community) Attendees: ngomp, dgregor, sly, jdisnard, tkopecek, yzhu, Jana, Egor, Brendan,mikem, yulwang Meeting Summary: 3 koji stakeholders besides Brew team joined our 2nd koji community meeting. we mainly talked last meeting actions and Koji recent update and get the feedback from community. detail please check our meeting docs: https://public.etherpad-mozilla.org/p/KojiMarch2018
Meeting Notes: 1.Review last action items
"office hours" proposal - Every Tue/Thurs 10:00 - 11:00AM US/ET (welcome your feedback in the meeting notes)
koji-devel could be there
which channel? #koji ? #fedora-releng (larger)
Let's use #koji
won't be active all the time, but when we have koji conversations let's have them in #koji
AI: Send an announcement to koji-devel@
Research on how do external users use the Message bus plugins:
https://pagure.io/koji/issue/736
Question from mikem: who might use it?
AI: mark as deprecated in 1.16 and send out an announcement to speak up if it's still needed(release note+ separate notification)
2.Koji update:
Koji 1.15 released on Dec 2017 https://docs.pagure.org/koji/release_notes_1.15/
Fedora in process of upgrading to 1.15
Koji 1.16 planning: Mar 28, 2018 https://pagure.io/koji/roadmap?status=all&milestone=1.16
Koji 1.17 planning
- Community feedback / input
Mageia
bootstrap chroot is very important to Mageia. One challenge for koji is that the repo used to bootstrap is likely different than the repo for building
Maybe use the same repos for both? We already do this for SRPM -> RPM build chroots. Mock's current bootstrap feature works that way.
issues around auto-generating the SRPM changelog. Questions around how to integrate this prebuild script
https://gitlab.com/mdklinux/mgapkg-koji
Variety of issues related to installing koji. messagebus plugin isn't compiling. Some other things... (Neal, can you fill in?)
Opportunity to use Mageia as a way of making installation easier, or at least documenting it better
Let's move this to office hours.
Fedora Releng - Sly
Schedule: https://fedoraproject.org/wiki/Releases/28/Schedule
Beta Freeze was March 6
In the middle of Fedora 28
Currently no issues with koji
Have not started Fedora 29 planning yet
Thanks, Yuli
koji-devel mailing list -- koji-devel@lists.fedorahosted.org To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.org
Hi, Ken
Our next Koji meeting is planned on June 6. I will send the invitation and meeting reminder ahead of one week.
Wecome and thanks for your attention.
Thanks, Yuli
On Tue, Mar 27, 2018 at 2:28 AM, Ken Dreyer ktdreyer@ktdreyer.com wrote:
Thank you Yuli for sending this!
Would you please let me know when you expect to have the next Koji community meeting? I want to attend, although I seem to keep missing the meetings :)
- Ken
On Wed, Mar 7, 2018 at 10:13 PM, Yuli Wang yulwang@redhat.com wrote:
Meeting Purpose: Improve the communication with upstream(community) Attendees: ngomp, dgregor, sly, jdisnard, tkopecek, yzhu, Jana, Egor, Brendan,mikem, yulwang Meeting Summary: 3 koji stakeholders besides Brew team joined our 2nd koji community
meeting.
we mainly talked last meeting actions and Koji recent update and get the feedback from community. detail please check our meeting docs: https://public.etherpad-mozilla.org/p/KojiMarch2018
Meeting Notes: 1.Review last action items
"office hours" proposal - Every Tue/Thurs 10:00 - 11:00AM US/ET (welcome your feedback in the meeting notes)
koji-devel could be there
which channel? #koji ? #fedora-releng (larger)
Let's use #koji
won't be active all the time, but when we have koji conversations let's
have
them in #koji
AI: Send an announcement to koji-devel@
Research on how do external users use the Message bus plugins:
https://pagure.io/koji/issue/736
Question from mikem: who might use it?
AI: mark as deprecated in 1.16 and send out an announcement to speak up
if
it's still needed(release note+ separate notification)
2.Koji update:
Koji 1.15 released on Dec 2017 https://docs.pagure.org/koji/release_notes_1.15/
Fedora in process of upgrading to 1.15
Koji 1.16 planning: Mar 28, 2018 https://pagure.io/koji/roadmap?status=all&milestone=1.16
Koji 1.17 planning
- Community feedback / input
Mageia
bootstrap chroot is very important to Mageia. One challenge for koji is that the repo used to bootstrap is likely different than the repo for building
Maybe use the same repos for both? We already do this for SRPM -> RPM
build
chroots. Mock's current bootstrap feature works that way.
issues around auto-generating the SRPM changelog. Questions around how
to
integrate this prebuild script
https://gitlab.com/mdklinux/mgapkg-koji
Variety of issues related to installing koji. messagebus plugin isn't compiling. Some other things... (Neal, can you fill in?)
Opportunity to use Mageia as a way of making installation easier, or at least documenting it better
Let's move this to office hours.
Fedora Releng - Sly
Schedule: https://fedoraproject.org/wiki/Releases/28/Schedule
Beta Freeze was March 6
In the middle of Fedora 28
Currently no issues with koji
Have not started Fedora 29 planning yet
Thanks, Yuli
koji-devel mailing list -- koji-devel@lists.fedorahosted.org To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.org
koji-devel@lists.fedorahosted.org