13:02:23 <pingou> #startmeeting pagure stakeholder meeting
13:02:23 <zodbot> Meeting started Fri Mar  8 13:02:23 2019 UTC.
13:02:23 <zodbot> This meeting is logged and archived in a public location.
13:02:23 <zodbot> The chair is pingou. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:23 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
13:02:23 <zodbot> The meeting name has been set to 'pagure_stakeholder_meeting'
13:02:26 <pingou> #meetingname pagure-stakeholder
13:02:26 <zodbot> The meeting name has been set to 'pagure-stakeholder'
13:02:28 <pingou> #meetingtopic Pagure development state and plans
13:02:30 <pingou> #info this meeting is recorded using zodbot's meetbot plugins and transcripts will be available at: https://meetbot.fedoraproject.org/
13:02:32 <pingou> #topic rollcall & introduction
13:02:34 <pingou> let's get started then :)
13:02:44 <karsten> .hello karsten
13:02:45 <zodbot> karsten: karsten 'Karsten Hopp' <karsten@redhat.com>
13:02:51 <pingou> .hello2
13:02:52 <zodbot> pingou: pingou 'Pierre-YvesChibon' <pingou@pingoured.fr>
13:02:57 <bkabrda> .hello2
13:02:58 <zodbot> bkabrda: bkabrda 'Bohuslav Kabrda' <slavek.kabrda@gmail.com>
13:04:17 <pingou> cverna: Pharaoh_Atem: do you want to join ?
13:04:21 <pingou> ttomecek: ?
13:07:17 <pingou> ok,
13:07:30 <pingou> let's move on :)
13:07:33 <pingou> #topic back on 5.4
13:07:37 <pingou> so... :)
13:07:40 <pingou> #info pagure 5.4 was due for release yesterday, beta planned for later today
13:07:51 <pingou> there is only one ticket left for 5.4
13:07:54 <pingou> https://pagure.io/pagure/roadmap/5.4/
13:08:03 <pingou> which is a partly a documentation issue
13:08:22 <bkabrda> nice progress!
13:08:22 <pingou> I'll try to fix part of it during the release process of 5.4 and the rest will likely be moved to 5.5
13:08:50 <pingou> one issue is that 5.4 won't have one fix we would need for src.fp.o :(
13:08:58 <pingou> so we'll have to keep a hotfix there for a little longer
13:09:09 <bkabrda> pingou: which one is that?
13:09:19 <pingou> which considering the fact that Fedora infra is in freeze for the beta release may have happened anyway
13:09:58 <pingou> bkabrda: I don't think it affects you: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=6ae1ad7
13:10:08 <pingou> but the commit message should explain the issue :)
13:10:47 <bkabrda> pingou: yeah, that doesn't seem to be an issue for my setup
13:10:49 <bkabrda> thanks
13:11:18 <pingou> there is also https://pagure.io/pagure/pull-request/4295
13:11:29 <pingou> which would have been nice to get in, but lacks tests :(
13:11:43 <pingou> if someone has the time to work on tests for this, I'd be ok with cutting a .z release for this
13:12:57 <pingou> anything else on 5.4?
13:13:28 <bkabrda> not from me
13:13:41 <pingou> let's move onto 5.5 then :)
13:13:44 <pingou> #topic State of 5.5
13:13:46 <pingou> #link https://pagure.io/pagure/roadmap/5.5/
13:13:50 <pingou> so it's going to be a very quick release :-p
13:13:54 <pingou> 2 tickets :)
13:14:08 <bkabrda> well, I'd like to finish https://pagure.io/pagure/pull-request/4264#
13:14:20 <fm-pagure> pagure.issue.tag.added -- pingou tagged ticket pagure#4327: UI and bug https://pagure.io/pagure/issue/4327
13:14:21 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4327 https://pagure.io/pagure/issue/4327
13:14:22 <bkabrda> + also I have a patch that should significantly increase forking speed
13:14:30 <pingou> nice :)
13:14:40 <bkabrda> I think I should be able to clean it up and submit it for 5.5
13:14:46 <pingou> I'm considering getting ride of pygit2.clone_repo()
13:14:56 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4249 https://pagure.io/pagure/issue/4249
13:15:09 <pingou> there has been a few tickets open recently which may be nice to fix
13:15:18 <fm-pagure> pagure.issue.tag.added -- pingou tagged ticket pagure#4325: bug https://pagure.io/pagure/issue/4325
13:15:19 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4325 https://pagure.io/pagure/issue/4325
13:15:49 <fm-pagure> pagure.issue.tag.added -- pingou tagged ticket pagure#4321: bug https://pagure.io/pagure/issue/4321
13:15:50 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4321 https://pagure.io/pagure/issue/4321
13:15:51 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#4321: "Release links broken when annotated tags used for releases" https://pagure.io/pagure/issue/4321#comment-559027
13:16:34 <fm-pagure> pagure.issue.tag.added -- pingou tagged ticket pagure#4317: RFE https://pagure.io/pagure/issue/4317
13:16:41 <fm-pagure> pagure.issue.tag.added -- pingou tagged ticket pagure#4316: bug https://pagure.io/pagure/issue/4316
13:16:42 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4316 https://pagure.io/pagure/issue/4316
13:16:51 <fm-pagure> pagure.issue.tag.added -- pingou tagged ticket pagure#4315: JS, UI, and bug https://pagure.io/pagure/issue/4315
13:16:52 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4315 https://pagure.io/pagure/issue/4315
13:17:14 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4312 https://pagure.io/pagure/issue/4312
13:17:29 * King_InuYasha waves
13:17:33 <King_InuYasha> .hello ngompa
13:17:35 <zodbot> King_InuYasha: ngompa 'Neal Gompa' <ngompa13@gmail.com>
13:17:46 <fm-pagure> pagure.issue.tag.added -- pingou tagged ticket pagure#4309: RFE https://pagure.io/pagure/issue/4309
13:17:47 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4309 https://pagure.io/pagure/issue/4309
13:18:03 <pingou> and just like that there are now 10 tickets for 5.5 :)
13:18:08 <King_InuYasha> pingou: sorry I'm late
13:18:27 <pingou> King_InuYasha: no worries :)
13:18:28 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4300 https://pagure.io/pagure/issue/4300
13:19:02 <King_InuYasha> pingou: the main thing I'm concerned about for 5.5 is our webhooks
13:19:10 <King_InuYasha> and potentially also the pagure-ci/jenkins stuff
13:19:29 <King_InuYasha> https://pagure.io/pagure/issue/4275
13:19:42 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4255 https://pagure.io/pagure/issue/4255
13:19:42 <King_InuYasha> https://pagure.io/pagure/issue/4317
13:19:43 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#4255: "Allow "blocking" users" https://pagure.io/pagure/issue/4255#comment-559035
13:20:12 <fm-pagure> pagure.issue.new -- psss opened a new ticket pagure#4329: "Filtering user issues by close date does not work" https://pagure.io/pagure/issue/4329
13:20:36 <pingou> 4317 seems interesting but I'm not sure I can commit the time to fix it
13:20:57 <pingou> well, that was 4275 in fact
13:21:08 <pingou> 4317 would be good to fix in 5.5
13:21:14 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4317 https://pagure.io/pagure/issue/4317
13:21:14 * cverna is around :)
13:21:27 <King_InuYasha> 4317 is important to make CI work for https://pagure.io/releng/fedora-module-defaults
13:21:38 <pingou> agreed
13:21:48 <King_InuYasha> and 4275 is important for me to develop OpenShift and Buildbot integration for Pagure
13:21:55 <pingou> and shouldn't be too hard, it's another variable to pass
13:22:22 <King_InuYasha> pingou: actually, if there was a way to just pass the whole json payload to Jenkins, we could let Jenkins parse it out into variables
13:22:25 <pingou> 4275 is more work, especially since we may want to reconsider the message payload
13:22:26 <fm-pagure> pagure.issue.comment.added -- psss commented on ticket pagure#4064: "Provide API for searching issues created/closed in given time frame" https://pagure.io/pagure/issue/4064#comment-559038
13:22:53 <pingou> which, if we want to make things right, may results in non-backward compatible changes
13:23:11 <King_InuYasha> pingou: I think at the minimum, we should yank in the message documentation and examples into pagure docs
13:23:44 <King_InuYasha> especially with fedmsg going away and that message format being used in every transport we support
13:24:00 <King_InuYasha> that part would be ideal for 5.4, but strictly speaking, not required
13:24:13 <pingou> 5.4 is today, not gonna happen :)
13:24:17 <King_InuYasha> welp
13:24:21 <King_InuYasha> then 5.5 :)
13:24:22 <pingou> (5.4 was yesterday :))
13:24:37 <King_InuYasha> 5.4 isn't tagged?
13:24:44 <King_InuYasha> I didn't get a notice from anything about it
13:24:45 <pingou> King_InuYasha: if you want to take it I'm happy to put it on the roadmap
13:24:52 <pingou> not yet, it was due yesterday
13:25:03 <pingou> I hope to get a beta today so we can release next week
13:25:17 <fm-pagure> pagure.issue.tag.added -- pingou tagged ticket pagure#4329: bug https://pagure.io/pagure/issue/4329
13:25:19 <King_InuYasha> pingou: I may at least work on pulling the message format documentation into pagure itself
13:25:30 <King_InuYasha> it's silly that it's in fedmsg when pagure controls the format anyway
13:25:55 <pingou> we'll need to work on the message validation with a message schema at one point
13:26:00 <King_InuYasha> yes
13:26:14 <pingou> we have 13 tickets for 5.5
13:26:28 <pingou> I think that's a good number to start with
13:26:38 <pingou> there will likely be a few more coming up
13:26:39 <King_InuYasha> but yeah, I can look at 4275 for 5.5, though I'm not sure if I'll be able to do it alone
13:27:02 <pingou> I'm happy to assist you
13:27:11 <King_InuYasha> thanks :)
13:27:26 <King_InuYasha> I have several questions about how this is done, but that's for after the meeting
13:27:49 <pingou> anything else on 5.5?
13:28:07 <King_InuYasha> what's the state for repoSpanner?
13:28:14 <pingou> as in?
13:28:19 <King_InuYasha> do we need to do anything else for 5.5 for it?
13:28:24 <King_InuYasha> or is it in good shape in 5.4?
13:28:50 <pingou> I think we should be fine
13:29:01 <pingou> not seeing any ticket which should have affected it
13:29:12 <King_InuYasha> cool
13:29:20 <King_InuYasha> also, do we have Rust syntax highlighting? https://pagure.io/pagure/issue/4195
13:29:33 <pingou> does highlight.js have it?
13:29:36 <King_InuYasha> iirc, this should be a config tweak or maybe also a regen of the highlighter js?
13:30:02 <King_InuYasha> pingou: yes
13:30:06 <pingou> we should look at this ticket and the one about yaml
13:30:06 <King_InuYasha> https://highlightjs.org/static/demo/
13:30:18 <pingou> King_InuYasha: let's discuss this after the meeting and test in stg.pagure.io
13:30:26 <King_InuYasha> okay
13:30:34 <pingou> do we want to discuss about 5.6?
13:30:47 <pingou> it seems a little far away considering we have not even started on 5.5 :s
13:31:26 <King_InuYasha> well, hopefully we'll stop slipping, so 5.6 should be appropriate to discuss
13:31:36 <King_InuYasha> especially since that's the release we'll have for oSC19 :O
13:31:41 <pingou> ^^
13:31:53 <pingou> let's start discussing it then :)
13:31:55 <pingou> #topic Planning 5.6
13:31:57 <pingou> #link https://pagure.io/pagure/roadmap/5.6/
13:32:04 <pingou> so what do we want in this one?
13:32:36 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4307 https://pagure.io/pagure/issue/4307
13:32:51 <King_InuYasha> we _definitely_ want https://pagure.io/pagure/issue/4275 fixed for that release
13:33:14 <King_InuYasha> iirc, there were also some issues that fbo had for zuul integration?
13:33:17 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4275 https://pagure.io/pagure/issue/4275
13:33:23 <pingou> let's schedule it
13:33:34 <King_InuYasha> https://pagure.io/pagure/issues?status=Open&author=fbo&close_status=
13:33:38 <pingou> but I'm honestly not sure how much I'll be able to spend on this one
13:33:56 <King_InuYasha> we'll see as we go
13:34:00 <King_InuYasha> we have a whole month ;)
13:34:08 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#3985 https://pagure.io/pagure/issue/3985
13:34:18 <King_InuYasha> but it'd be good to try to get these wrapped up sooner rather than later
13:35:03 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#3948: "Ability to use (Webhook sign material/notitifcation url(s)/API key) for a group of projects" https://pagure.io/pagure/issue/3948#comment-559044
13:36:13 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#4002: "Pull request detail API endpoint should return a non-cached merge_status" https://pagure.io/pagure/issue/4002#comment-559045
13:36:30 <King_InuYasha> pingou: this was a "coming 3 months" thing for a while, do we want to schedule it? https://pagure.io/pagure/issue/2938
13:37:32 <King_InuYasha> and I'm not sure what the state of things is for being able to add subgroup support: https://pagure.io/pagure/issue/3364
13:37:42 <pingou> oh, I met someone in early January that was interested to help on ldap suport
13:37:46 <King_InuYasha> awesome
13:37:48 <pingou> I need to contact that person again
13:38:02 <King_InuYasha> the ldap stuff would be a big help
13:38:18 <King_InuYasha> there's other nice things we can do there, like syncing ssh keys and such
13:38:54 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#3364: "RFE: Support subgroups" https://pagure.io/pagure/issue/3364#comment-559046
13:40:37 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#4226: "Recently merged pull request page returns 500 error" https://pagure.io/pagure/issue/4226#comment-559047
13:40:51 <fm-pagure> pagure.issue.comment.added -- ngompa commented on ticket pagure#3364: "RFE: Support subgroups" https://pagure.io/pagure/issue/3364#comment-559048
13:42:18 <fm-pagure> pagure.issue.comment.edited -- ngompa edited a comment on ticket pagure#3364: "RFE: Support subgroups" https://pagure.io/pagure/issue/3364#comment-559048
13:42:38 <King_InuYasha> pingou: that should clarify what I mean by subgroups
13:44:04 <pingou> let's see later if there are more tickets we can commit to for 5.6
13:44:04 <pingou> #topic Open floor
13:44:04 <pingou> anything you would like to bring up about pagure?
13:44:44 <King_InuYasha> We probably need to start working on our presentation for oSC 19 soon :)
13:44:53 <King_InuYasha> since your talk has been accepted and is now scheduled
13:44:55 <fm-pagure> pagure.issue.edit -- pingou edited the close_status and status fields of ticket pagure#4153 https://pagure.io/pagure/issue/4153
13:44:56 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#4153: "dev-data.py setup is failing" https://pagure.io/pagure/issue/4153#comment-559052
13:45:29 <pingou> I've received a few emails about a schedule being available but I could never access it
13:45:41 <pingou> King_InuYasha: do you mean I have to prepare my talk in advance?
13:45:48 <pingou> what world is that? :D
13:45:55 <King_InuYasha> lol
13:46:16 <King_InuYasha> https://events.opensuse.org/conferences/oSC19/program/proposals/2432
13:46:39 <King_InuYasha> pingou: we should probably have _some_ content so that we have something fun to show off :)
13:47:02 <pingou> King_InuYasha: I'm sure we can figure out content live :D
13:47:09 <King_InuYasha> oh boy
13:47:17 <pingou> “it sounded like a good idea at that time”
13:47:28 <King_InuYasha> XD
13:47:35 <pingou> are you also going then?
13:47:59 <King_InuYasha> yes
13:48:04 <pingou> cool
13:48:08 <King_InuYasha> I also have a talk scheduled separately, too :)
13:48:13 <King_InuYasha> so I'm _definitely_ going
13:48:24 <pingou> joke aside, for the slides I do prepare them in advance, but not that far in advance :)
13:48:31 <pingou> cool
13:48:49 <King_InuYasha> https://events.opensuse.org/conferences/oSC19/program/proposals/2480
13:49:04 <fm-pagure> pagure.issue.comment.added -- psss commented on ticket pagure#4329: "Filtering user issues by close date does not work" https://pagure.io/pagure/issue/4329#comment-559054
13:49:16 <King_InuYasha> pingou: yeah, I figure
13:49:41 <King_InuYasha> pingou: the other thing is that we should seriously figure out what we're going to do for pagure.io CI
13:49:54 <King_InuYasha> it's too hard for people to leverage it, and debugging it is even worse
13:50:02 <pingou> we should talk to bstinson about this
13:50:18 <King_InuYasha> yes
13:50:46 <King_InuYasha> ddevault has an interesting subproject from sourcehut that might be useful to us too
13:51:16 <King_InuYasha> like pagure, it's a flask-based system, and we could leverage some components from there for interop and offering useful CI
13:51:32 <fm-pagure> pagure.issue.comment.added -- psss commented on ticket pagure#4065: "Provide API for searching pull requests created/closed in given time frame" https://pagure.io/pagure/issue/4065#comment-559055
13:51:58 <King_InuYasha> might even be useful for figuring out how to solve https://pagure.io/pagure/issue/15
13:52:46 <King_InuYasha> since his system is oriented around handling email-based workflow
13:54:18 <King_InuYasha> https://sourcehut.org/
13:55:00 <pingou> it would be neat to fix this one for sure
13:55:49 <pingou> there are some bugs I'd not mind fixing either :)
13:55:49 <pingou> (fix the existing ones before introducing new ones :-p)
13:56:02 <pingou> alright, I think we're coming to the end of the meeting
13:56:04 <King_InuYasha> yep
13:56:16 <pingou> if there is nothing else, I'll close in a minute or so :)
13:56:25 <King_InuYasha> I'm good here :)
13:57:41 <pingou> #endmeeting