12:04:56 #startmeeting pagure stakeholder meeting 12:04:56 Meeting started Mon Apr 8 12:04:56 2019 UTC. 12:04:56 This meeting is logged and archived in a public location. 12:04:56 The chair is pingou. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:04:56 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:04:56 The meeting name has been set to 'pagure_stakeholder_meeting' 12:04:59 #meetingname pagure-stakeholder 12:04:59 The meeting name has been set to 'pagure-stakeholder' 12:05:01 #meetingtopic Pagure development state and plans 12:05:03 #info this meeting is recorded using zodbot's meetbot plugins and transcripts will be available at: https://meetbot.fedoraproject.org/ 12:05:05 #topic rollcall & introduction 12:05:06 .hello2 12:05:10 pingou: pingou 'Pierre-YvesChibon' 12:05:34 .hello2 12:05:35 dperpeet: dperpeet 'None' 12:05:37 .hello2 12:05:40 msrb: msrb 'Michal Srb' 12:05:44 .hello karsten 12:05:48 karsten: karsten 'Karsten Hopp' 12:06:26 Son_Goku: joining? 12:06:34 .hello2 ngompa 12:06:35 Son_Goku: Sorry, but you don't exist 12:06:39 .hello ngompa 12:06:40 Son_Goku: ngompa 'Neal Gompa' 12:06:52 anyone else joining us? 12:06:56 * Son_Goku just woke up a few minutes ago 12:07:04 * pingou hands some coffee to Son_Goku 12:07:20 * Son_Goku stares at the coffee 12:07:27 * Son_Goku sips 12:08:21 alright, let's move 12:08:24 #topic back on 5.5 12:08:26 #link https://pagure.io/pagure/roadmap/5.5/ 12:08:27 #info pagure 5.5 was release a few hours ago, I still have the send the announcements 12:08:30 There is one ticket left on the roadmap for 5.5, it will be figured out (if fixed or still pending) once 5.4 or 5.5 are deployed. 12:08:49 I believe smooge wanted to push 5.4 later today (possibly even 5.5, I'm not sure) 12:09:14 I think 5.5 12:09:16 otherwise, 5.5 is looking nice :) 12:09:19 at this point, we might as well 12:09:35 the only problem is that 5.5 as-is doesn't install on Fedora or openSUSE :( 12:09:43 sqlalchemy 1.3.1 in both distributions 12:09:46 in rawhide you mean? 12:09:50 Fedora 30 12:10:00 :( 12:10:03 this afflicts Fedora 30 and newer, as well as openSUSE Tumbleweed 12:10:22 I'm not sure the issue would appear if deploying pagure w/ postgresql 12:10:32 I'm patching currently to workaround it: https://src.fedoraproject.org/rpms/pagure/blob/master/f/0501-Revert-Add-a-upper-limit-to-sqlalchemy.patch 12:10:33 it seems to be related to sqlite 12:10:48 but we should really get in touch with upstream to figure out what's wrong 12:11:00 you could just use sed in the spec :) 12:11:23 the point is to know why I did it :) 12:11:27 fair :) 12:11:29 .hello2 12:11:30 ttomecek: ttomecek 'Tomas Tomecek' 12:11:36 oh new person :D 12:11:57 * ttomecek just lurks 12:12:02 anything else for 5.5? 12:12:12 I think we're good on 5.5 otherwise 12:12:17 otherwise we can start looking at 5.6 :) 12:12:20 #topic State of 5.6 12:12:23 #link https://pagure.io/pagure/roadmap/5.6/ 12:12:29 2 tickets so far :) 12:12:34 wow, we don't have much 12:12:41 Son_Goku: have you made a ticket for sqlalchemy? 12:12:47 I don't remember 12:12:50 I'll make one anyway 12:12:56 let's deal with this for 5.6 12:13:03 I saw a few tickets from fbo which I suspect relate to zuul 12:13:10 so may be nice to address them 12:13:21 pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4400 https://pagure.io/pagure/issue/4400 12:13:25 pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4399 https://pagure.io/pagure/issue/4399 12:13:36 pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4398 https://pagure.io/pagure/issue/4398 12:13:52 pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4385 https://pagure.io/pagure/issue/4385 12:14:27 one of these days we'll really have to sit and fix the search fields :s 12:14:57 pagure.issue.tag.added -- pingou tagged ticket pagure#4319: JS https://pagure.io/pagure/issue/4319 12:14:58 pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4319 https://pagure.io/pagure/issue/4319 12:15:12 .here 12:15:19 github.star -- quickerlab starred Pagure/pagure https://github.com/Pagure/pagure/stargazers 12:15:20 pagure.issue.new -- ngompa opened a new ticket pagure#4415: "Pagure 5.4+ is not installable on Fedora 30+ and openSUSE Tumbleweed due to shipping sqlalchemy 1.3.0+" https://pagure.io/pagure/issue/4415 12:15:39 pingou ^ 12:15:43 pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4415 https://pagure.io/pagure/issue/4415 12:15:58 pagure.issue.tag.added -- pingou tagged ticket pagure#4413: RFE https://pagure.io/pagure/issue/4413 12:16:14 and we're now at 8 tickets :) 12:17:00 while the roadmap for 5.6 is being discussed, are there any open issues/missing pieces around repospanner? 12:17:10 Docs :) 12:17:13 there are several 12:17:18 that's an obvious one :) 12:18:13 the entire "how to set-up pagure w/o gitolite" and "how to set-up pagure with repoSpanner" docs are to be written 12:19:17 pagure.issue.comment.added -- pingou commented on ticket pagure#4170: "Creating new projects with an initial import from another server doesn't work (Pagure 5.1.93)" https://pagure.io/pagure/issue/4170#comment-564957 12:20:39 anything else people would like to see in 5.6? 12:21:49 otherwise we can also start planning for 5.7 12:21:53 #topic Planning 5.7 12:21:56 #link https://pagure.io/pagure/roadmap/5.7/ 12:22:01 I've just created the milestone 12:22:33 pagure.issue.comment.added -- ngompa commented on ticket pagure#4170: "Creating new projects with an initial import from another server doesn't work (Pagure 5.1.93)" https://pagure.io/pagure/issue/4170#comment-564958 12:23:07 pingou, LDAP for 5.6 maybe? 12:23:17 https://pagure.io/pagure/issue/2938 12:23:42 pagure.issue.tag.added -- pingou tagged ticket pagure#4085: easyfix https://pagure.io/pagure/issue/4085 12:23:43 pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4085 https://pagure.io/pagure/issue/4085 12:23:44 pagure.issue.comment.added -- pingou commented on ticket pagure#4085: "Better UI for searching project issues" https://pagure.io/pagure/issue/4085#comment-564959 12:23:55 Son_Goku: the issue w/ this one is that I cannot commit to it :( 12:23:59 but I'd love to 12:24:56 what about this? https://pagure.io/pagure/issue/3364 12:26:07 pagure.issue.edit -- pingou edited the close_status and status fields of ticket pagure#4080 https://pagure.io/pagure/issue/4080 12:26:08 pagure.issue.comment.added -- pingou commented on ticket pagure#4080: "Issues and PR's sorted by last modified by default" https://pagure.io/pagure/issue/4080#comment-564961 12:27:09 Son_Goku: for groups potentially doable, the hierarchy at the URL/FS level I'm not fan 12:27:56 that feature is basically the only thing that keeps us from overlaying our existing gitolite/cgit setup with pagure 12:28:03 our current approach already give us some troubles: https://pagure.io/pagure/issue/4409 12:28:03 (aside from the auth thing...) 12:28:44 pingou, we don't have a /-/projects/rpms/tree slug for that? 12:28:51 err 12:29:00 err... /-/groups/rpms/tree 12:29:15 could be an option 12:29:25 we should be putting all "magic" paths in /-/// 12:29:32 that was the point of introducing it in pagure 5.0 12:30:07 I'm going to have to cut this meeting short, I'm happy to revist some of these subject later on today or tomorrow 12:30:14 okay :( 12:30:22 I've a conflicting meeting :( 12:30:23 I have one item 12:30:30 shoot :) 12:30:50 that is I would like to update to 5.5 on stg.pagure.io and pagure.io 12:31:04 5.5 is already in stg.pagure.io 12:31:19 :) 12:31:22 src.stg.fpo and src.fpo would need to wait until CentOS team are ready and I will exclude them 12:31:34 pingou, cool. 12:31:37 and thanks 12:32:03 cool :) 12:32:10 smooge: let me know if/when I can help with pagure.io :) 12:32:13 there is a script for upgrades which needs work to make it work with repospanner systems so we aren't manually doing updates 12:32:20 pingou, let me know when meeting time ends for you 12:32:34 and we will do it 12:32:49 thanks :) 12:32:53 pingou, I've also submitted a talk for devconf.us about introducing pagure 12:32:57 that is all 12:32:59 nice! 12:33:07 so we'll see if I get that talk slot :) 12:33:20 cool :) 12:33:23 #topic next-meetings 12:33:51 It'll be May 9th - May 8th being a national day off for me :) 12:34:06 #info we'll again on May 9th 12:34:26 I guess that's it for me and I need to run now :) 12:34:31 #endmeeting