13:02:56 <pingou> #startmeeting pagure stakeholder meeting
13:02:56 <zodbot> Meeting started Tue Jan  8 13:02:56 2019 UTC.
13:02:56 <zodbot> This meeting is logged and archived in a public location.
13:02:56 <zodbot> The chair is pingou. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:56 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
13:02:56 <zodbot> The meeting name has been set to 'pagure_stakeholder_meeting'
13:02:59 <pingou> #meetingname pagure-stakeholder
13:02:59 <zodbot> The meeting name has been set to 'pagure-stakeholder'
13:03:01 <pingou> #meetingtopic Pagure development state and plans
13:03:03 <pingou> #info this meeting is recorded using zodbot's meetbot plugins and transcripts will be available at: https://meetbot.fedoraproject.org/
13:03:13 <pingou> #topic rollcall & introduction
13:03:16 <pingou> .hello pingou
13:03:17 <zodbot> pingou: pingou 'Pierre-YvesChibon' <pingou@pingoured.fr>
13:03:19 * Son_Goku pokes lcp, Ark74, fbo, stormi, puiterwijk
13:03:24 <bkabrda> hi everyone!
13:03:25 <Son_Goku> .hello ngompa
13:03:26 <zodbot> Son_Goku: ngompa 'Neal Gompa' <ngompa13@gmail.com>
13:03:29 * pingou pokes cverna
13:03:33 <bcotton> .hello2
13:03:34 <zodbot> bcotton: bcotton 'Ben Cotton' <bcotton@redhat.com>
13:03:42 <karsten> .hello
13:03:42 <zodbot> karsten: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
13:03:43 * lcp feels poked
13:03:45 * cverna waves
13:03:53 <karsten> .hello karsten
13:03:53 <zodbot> karsten: karsten 'Karsten Hopp' <karsten@redhat.com>
13:04:06 <cverna> hi everyone
13:04:18 * Son_Goku pokes Arrfab
13:04:20 <karsten> bkabrda ^ ?
13:04:35 <bkabrda> .hello bkabrda
13:04:36 <zodbot> bkabrda: bkabrda 'Bohuslav Kabrda' <bkabrda@redhat.com>
13:05:50 <fm-pagure> pagure.issue.edit -- pingou edited the close_status and status fields of ticket pagure#4163 https://pagure.io/pagure/issue/4163
13:06:04 <pingou> anyone else?
13:06:41 <pingou> let's keep going then :)
13:06:44 <pingou> #topic back on 5.2
13:06:46 <pingou> #info pagure 5.2 was released yesterday
13:06:50 <Son_Goku> yay
13:06:58 <pingou> #info so far no major issues reported with 5.2
13:07:02 <fm-pagure> pagure.pull-request.flag.updated -- jenkins #2049 updated the flags on pagure#4179 with: "Build successful (commit: f08de6cf)" https://pagure.io/pagure/pull-request/4179
13:07:13 <pingou> pagure.io and src.fp.o have both been updated with this release
13:07:27 <fm-pagure> pagure.pull-request.flag.added -- jenkins #2053 flagged pagure#4179 with "Build in progress (commit: f08de6cf)" https://pagure.io/pagure/pull-request/4179
13:07:30 <Son_Goku> this release was rolled out pretty smoothly
13:07:40 <pingou> src.fp.o has required a small fix in the default hook because of the way it's deployed, 5.3 with the new way to run the hooks shouldn't have this issue anymore
13:07:58 <pingou> Son_Goku: agreed, it's quite nice :)
13:08:24 <pingou> and we need to port pagure to redis 3.0+ for 5.3 as this is blocking pushing 5.2 out there
13:08:37 <Son_Goku> yep
13:08:42 <fm-pagure> pagure.issue.tag.added -- pingou tagged ticket pagure#4183: RFE https://pagure.io/pagure/issue/4183
13:08:43 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4183 https://pagure.io/pagure/issue/4183
13:08:48 <bkabrda> what do we need to do to port it to redis 3?
13:09:11 <pingou> bkabrda: last time we tried jenkins was really not happy, so we backed out, we should look into it again
13:09:16 <Son_Goku> hopefully not much
13:09:26 <Son_Goku> it looks like the 3.0 release didn't have world-ending breakages
13:09:33 <bkabrda> I'd assume that most of it should be covered by celery/kombu
13:09:48 <Son_Goku> we use redis directly in some cases
13:09:49 <pingou> devils is in the details, but we'll need to look a little bit more
13:10:27 <Son_Goku> looks like 3.0 hated the version of celery we were pulling in
13:10:29 <pingou> nothing else on 5.2 ?
13:10:42 <pingou> Son_Goku: or vice-versa :D
13:10:51 <Son_Goku> potentially, but this also comes back to another point
13:11:00 <Son_Goku> I need help getting celery into EPEL7
13:11:21 <Son_Goku> the maintainers of billiard and kombu said they'd rather have the latest versions pulled into EPEL7 if we're doing it at all
13:11:36 <pingou> which brings on new deps?
13:11:39 <Son_Goku> potentially
13:11:43 <Son_Goku> I haven't looked deeply at it yet
13:11:57 <Son_Goku> but pingou, I'd like you to request co-maintainership of the celery stack too
13:11:59 <pingou> I'd argue that who does the work gets to choose which version gets pushed
13:12:18 <pingou> Son_Goku: feel free to add me
13:12:33 <Son_Goku> I don't have rights for kombu or billiard, but I'll do it for celery
13:12:40 <pingou> thanks
13:12:41 <Son_Goku> someone needs to get ahold of mrunge
13:12:52 <pingou> didn't he reply by email?
13:12:57 <Son_Goku> did he?
13:13:03 <pingou> he did
13:13:23 <pingou> yesterday, to your gmail
13:13:23 <Son_Goku> cool, he did give me rights
13:13:25 <Son_Goku> so I'll add you too
13:13:33 <pingou> wfm
13:13:50 <fm-pagure> pagure.pull-request.flag.updated -- jenkins #2052 updated the flags on pagure#4174 with: "Build successful (commit: fa1c111a)" https://pagure.io/pagure/pull-request/4174
13:13:53 <Son_Goku> so now we can *finally* get pagure in sync on EPEL7 with Fedora
13:14:12 <Son_Goku> which will mean that Fedora, CentOS, openSUSE Leap, openSUSE Tumbleweed, and Mageia 7 will have the latest Pagure versions
13:14:20 <Son_Goku> *CentOS 7 with EPEL
13:14:22 <pingou> we should blog about this :)
13:14:38 <Son_Goku> we should have a dev blog :)
13:15:06 <pingou> could be fun, but let's discuss this a little later
13:15:09 <Son_Goku> oh right, I forgot to mention this, but Pagure will be in openSUSE Leap 15.1 when it releases in a couple of months
13:15:17 <pingou> cool :)
13:15:23 <pingou> ngompa++
13:15:23 <zodbot> pingou: Karma for ngompa changed to 2 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
13:15:34 <Son_Goku> I think it Leap 15.1 releases in May during oSC
13:15:47 <Son_Goku> we should discuss having someone go to oSC in Nuremburg to give a talk about it
13:16:19 <pingou> good idea
13:16:34 <Son_Goku> CfP closes Feb 3
13:16:37 <Son_Goku> so we should do that soon
13:16:47 <pingou> aouch, soon yes
13:17:04 <Son_Goku> but yeah, it's exciting, it's in more places :D
13:17:16 <Son_Goku> we just need someone to package it for debian now :D
13:17:34 <Son_Goku> and in a way debian will take it (i.e. not my spec build using debbuild for debian :) )
13:17:42 <pingou> we had sergiodj working on it at one point
13:18:01 <Son_Goku> debian buster's freeze is soon, I was hoping we could get it in there
13:19:18 <pingou> should we move onto 5.3 ?
13:20:00 <Son_Goku> sure
13:20:08 <pingou> #topic State of 5.3
13:20:11 <pingou> #link https://pagure.io/pagure/roadmap/5.3/
13:20:25 <fm-pagure> pagure.pull-request.flag.updated -- jenkins #2051 updated the flags on pagure#4177 with: "Build successful (commit: cf4ca7f0)" https://pagure.io/pagure/pull-request/4177
13:20:27 <pingou> so 5.3 is already at 33% completion
13:20:29 <pingou> which is nice :)
13:20:45 <pingou> all the issues assigned to me have a PR up for review or ready locally
13:20:55 <fm-pagure> pagure.pull-request.flag.added -- jenkins #2054 flagged pagure#4179 with "Build in progress (commit: f08de6cf)" https://pagure.io/pagure/pull-request/4179
13:21:03 <pingou> which leaves 5 issues not assigned
13:21:04 <Son_Goku> I think I've reviewed all of them at this point
13:21:30 <pingou> fixing 4072 will fix 2874
13:21:38 <pingou> so that's 2 birds in 1 stone
13:21:53 <pingou> 3903 is basically up in the air
13:22:04 <fm-pagure> pagure.pull-request.flag.added -- jenkins #2055 flagged pagure#4185 with "Build in progress (commit: 78c4041f)" https://pagure.io/pagure/pull-request/4185
13:22:07 <pingou> 3976 more likely needs a cron job
13:22:22 <pingou> and 4183 is about the new python-redis
13:22:24 <Son_Goku> there's also this fun trivial PR that came as a result of me fixing things packaging for Fedora: https://pagure.io/pagure/pull-request/4185
13:22:36 <pingou> Son_Goku: I'll get on it after the meeting
13:22:42 <Son_Goku> cool
13:23:05 <Son_Goku> we're actually making good progress to have everything slated for 5.3 done within a week
13:23:21 <Son_Goku> which gives us time to start rolling it out to staging and validate it
13:24:00 <pingou> agreed
13:24:08 <pingou> there is also devconf and fosdem coming up
13:24:13 <pingou> where I'll be less available
13:24:26 <Son_Goku> are you giving talks about pagure at either?
13:24:32 <pingou> and I'd also like to work some more on pagure-taiga in the coming days
13:24:36 <pingou> Son_Goku: nope :(
13:24:47 <Son_Goku> pagure-taiga?
13:24:53 <Son_Goku> what is that?
13:24:58 <pingou> pagure-taiga aims at syncing back and forth issues/ticket between pagure and a taiga project
13:25:28 <pingou> using our usual celery-based system on the pagure side and taiga's webhook to update both ways
13:25:35 <Son_Goku> neat
13:25:40 <cverna> yes we should have taiga deployed soon in infra
13:25:54 <Son_Goku> so something I found out last night is that KDE is considering moving away from Phabricator
13:25:55 * cverna saw an infra ticket about that this morning
13:26:04 <pingou> since there seems to be quite some interest in having an official taiga instance, it would be nice to get this some more time
13:26:24 <Son_Goku> as a response to how successful GNOME has been with their changes
13:26:25 <pingou> Son_Goku: let's keep this for the open floor :)
13:26:31 <Son_Goku> sure
13:26:46 <Son_Goku> I was going to just say that might be interesting for larger projects like KDE :)
13:26:50 <pingou> for 5.3, are there volunteers for the 5 tickets we have un-assigned?
13:27:00 * pingou looks at bkabrda for 4072
13:27:19 <bkabrda> I'll do my best to get it done, but I can
13:27:26 <bkabrda> can't promise it 100 %
13:27:28 <Son_Goku> I'm currently looking at the redis one (4183)
13:27:55 <pingou> bkabrda: if you and karsten team up on it, would it increase the ^?
13:27:57 <Son_Goku> because it breaks Mageia and openSUSE right now
13:27:59 <pingou> the %
13:28:15 <bkabrda> karsten: do you think you could have a look at 4072?
13:28:52 <karsten> hooks ;-(    I'll take a look
13:29:09 <pingou> I'll likely take 3956
13:30:12 <pingou> if we cover these three tickets, 5.3 should be in a good shape
13:30:38 <pingou> and we have 3 weeks for them :)
13:31:58 <pingou> anything else for 5.3 ?
13:32:21 <Son_Goku> I think right now there isn't much else
13:32:30 <Son_Goku> just the quirks with the syntax highlighter and file views
13:32:41 <pingou> Son_Goku: did you see Ryan's PR from today?
13:32:46 <Son_Goku> not yet, no
13:32:52 <pingou> I think it'll improve things
13:33:08 <pingou> ok, let's look at 5.4 :)
13:33:11 <pingou> #topic Planning 5.4
13:33:13 <pingou> #link https://pagure.io/pagure/roadmap/5.4/
13:33:19 <pingou> we currently have 5 tickets
13:33:25 <pingou> what else do we want to have in two months? :)
13:33:38 <pingou> bcotton: you haven't said much, anything you'd like to see in pagure soon?
13:33:52 <bcotton> pingou: no, i'm just here to lurk (and also in another meeting right now)
13:34:06 <pingou> bcotton: ok, let us know if we can help :)
13:34:48 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4150 https://pagure.io/pagure/issue/4150
13:35:04 <pingou> adding ^ to 5.4 but I may do it for 5.3 as well
13:35:51 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4120 https://pagure.io/pagure/issue/4120
13:36:46 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4084 https://pagure.io/pagure/issue/4084
13:36:47 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#4084: "RFE - Add Take button to pull request template" https://pagure.io/pagure/issue/4084#comment-548523
13:37:14 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4033 https://pagure.io/pagure/issue/4033
13:38:09 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#4017: "Cannot merge pull requests" https://pagure.io/pagure/issue/4017#comment-548526
13:38:29 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#4005 https://pagure.io/pagure/issue/4005
13:38:54 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#3996 https://pagure.io/pagure/issue/3996
13:39:06 <Son_Goku> 5.4 is looking like primarily a bug fix release at this point
13:39:28 <fm-pagure> pagure.pull-request.flag.updated -- jenkins #2053 updated the flags on pagure#4179 with: "Build successful (commit: f08de6cf)" https://pagure.io/pagure/pull-request/4179
13:39:30 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#3992: "Circular import on logcom_1 and worker_1 containers" https://pagure.io/pagure/issue/3992#comment-548529
13:40:01 <pingou> Son_Goku: small RFEs are in
13:40:41 <fm-pagure> pagure.issue.tag.added -- pingou tagged ticket pagure#3939: JS and bug https://pagure.io/pagure/issue/3939
13:40:42 <fm-pagure> pagure.issue.edit -- pingou edited the milestone fields of ticket pagure#3939 https://pagure.io/pagure/issue/3939
13:41:35 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#3858: "CHECKSUMS file is not updated after a release" https://pagure.io/pagure/issue/3858#comment-548531
13:42:34 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#3799: ""Open PR" button loads indefinitely on Pagure" https://pagure.io/pagure/issue/3799#comment-548532
13:42:52 <pingou> we have 11 tickets planned for 5.4 atm
13:43:14 <pingou> if we get them done soon enough we can likely add some more
13:43:21 <pingou> does that sound reasonable?
13:43:26 <Son_Goku> sounds like a good idea
13:43:35 <Son_Goku> we can pluck from the backlog or future release milestones
13:43:58 <pingou> yup
13:44:04 <pingou> fixing the searches would be nice
13:44:27 <pingou> okido
13:44:29 <pingou> #topic Open floor
13:44:39 <pingou> anything more we want to discuss?
13:44:58 <Son_Goku> couple of things, I guess
13:45:15 <Son_Goku> as I briefly mentioned earlier, we should see about getting the word out more about Pagure and what it offers
13:45:40 <Son_Goku> which kind of slides into another point: nobody seems to know what our exact feature set is for doing comparisons between different projects
13:46:08 <pingou> Son_Goku: our docs also need quite some love
13:46:16 <pingou> esp around installing/deploying pagure
13:46:43 <Son_Goku> yeah, I actually wrote a readme for a quick start for prod deployments for the Mageia and openSUSE packages:
13:46:50 <pingou> Son_Goku: any suggestions on how we should do these?
13:47:00 <Son_Goku> * http://svnweb.mageia.org/packages/cauldron/pagure/current/SOURCES/pagure-README.Mageia?revision=1320176&view=co
13:47:04 <cverna> docs could be worked on if the 5.3 PRs are all done early
13:47:13 <Son_Goku> * https://build.opensuse.org/package/view_file/devel:tools:scm/pagure/pagure-README.SUSE?expand=1
13:47:58 <pingou> Son_Goku: do you think you could leverage this to make something like this somewhat generic and in pagure's docs?
13:48:02 <Son_Goku> pingou, well, at least for the feature set thing, it'd probably be a good idea to add a page that lists the various features of Pagure and that could help with filling out the docs on how to use them
13:48:10 <bookwar> i would suggest to focus on feature comparison as Son_Goku mentioned rather than install docs for now
13:48:16 <Son_Goku> yeah
13:48:34 <Son_Goku> installation isn't that difficult to figure out based on what is already there
13:48:42 <Son_Goku> but knowing what Pagure can do is a huge problem
13:48:45 <pingou> I'm happy to write doc if someone tell me what is needed :)
13:49:09 <Son_Goku> we got kind of screwed with Debian and GNOME comparisons because few people knew about the features in Pagure
13:49:30 <pingou> Son_Goku: is this something you could start on ?
13:49:54 <Son_Goku> I can try, I need to dedicate some time to poking around and figuring out what pagure can do
13:50:13 <Son_Goku> another thing is that I don't know how to set up the pagure mirror services, and they're not documented in the docs
13:50:22 <Son_Goku> so that probably needs to be fixed
13:50:47 <pingou> Son_Goku: 2 systemd service, one of which requirest a dedicated user
13:51:03 <fm-pagure> pagure.pull-request.flag.updated -- jenkins #2055 updated the flags on pagure#4185 with: "Build successful (commit: 78c4041f)" https://pagure.io/pagure/pull-request/4185
13:52:09 <Son_Goku> pingou, I can write up a feature set, once I figure out all the features
13:52:32 <pingou> Son_Goku: if you get started, feel free to poke me for help
13:52:35 <Son_Goku> we should also try to have some kind of comparison of offering of pagure.io vs github.com vs gitlab.com
13:52:44 <Son_Goku> but that can come slightly later
13:52:58 <pingou> true
13:52:58 <Son_Goku> it'd be nice to see if we can attract people to use pagure.io service more, as that helps with improving pagure as a whole
13:53:15 <Son_Goku> another thing we should do is fix up the pagure importer
13:53:34 <Son_Goku> it seems to be a slightly dead project with some moribund PRs hanging around too
13:53:35 <pingou> cverna: you were involved in that project at one point no?
13:54:00 <karsten> from what I heard having to do the Fedora CLA
13:54:08 <cverna> I did the import from trac
13:54:14 <karsten> is preventing some people from using pagure.io
13:54:26 <Son_Goku> pingou, didn't you fix pagure.io to not require FPCA?
13:54:30 <pingou> karsten: it hasn't been a requirement for a while :)
13:54:47 <cverna> when we moved from fedorahosted, vivek_ did the work related to github
13:54:50 <pingou> I think a couple of years :)
13:54:52 <Son_Goku> pagure.io and copr are the two major services that iirc don't require it
13:54:58 <cverna> I am not sure in which state it is now
13:55:19 <Son_Goku> in Fedora, we have python bindings for github and gitlab packaged
13:55:25 <pingou> the main issue with github is that pagure relies on email addresses which aren't exposed by github
13:55:38 <Son_Goku> so it'd be cool if someone took a look at extending that tool to support importing from both
13:55:48 <karsten> I'll try to find out why people have the impression that this is required. maybe some old docs
13:55:59 <pingou> karsten: definitely outdated :)
13:56:12 <Son_Goku> pingou, and this might circle back to an idea about having a blog or a site about pagure and pagure.io specifically
13:56:25 <pingou> Son_Goku: any suggestions for this?
13:56:37 <Son_Goku> gitlab has about.gitlab.com for that, and github has that blog link of theirs
13:56:37 <pingou> do we want a pagure.wordpress.org?
13:56:46 <Son_Goku> maybe
13:56:58 <Son_Goku> or do one better, have a website built using pagure to a pagure thing :)
13:57:45 <Son_Goku> about.gitlab.com is built using GitLab, so we could do something like blog.pagure.io or some other thing that works that way
13:58:12 <Son_Goku> which I think would kinda circle back to the static site handling RFE from a couple of years ago
13:58:15 <pingou> something like pelican or mynt or nikola in a pagure project?
13:58:18 <Son_Goku> yeah
13:58:29 <fm-pagure> pagure.issue.comment.added -- lenkaseg commented on ticket pagure#3992: "Circular import on logcom_1 and worker_1 containers" https://pagure.io/pagure/issue/3992#comment-548534
13:58:39 <Son_Goku> https://koji.build is done this way using nikola
13:58:42 <pingou> it could then show up at docs.pagure.org/pagure-blog
13:58:44 <Son_Goku> but we could use pelican :D
13:59:01 <pingou> or another domain
13:59:08 <Son_Goku> https://pagure.io/koji-site
13:59:35 <Son_Goku> they don't have CI here, but it's a thing at a least
13:59:38 <pingou> alright, let's look into that
14:00:28 <Son_Goku> here's GitLab's website project, for comparison: https://gitlab.com/gitlab-com/www-gitlab-com
14:00:40 <Son_Goku> that's what powers this site: https://about.gitlab.com/
14:01:14 <fm-pagure> pagure.issue.comment.added -- lenkaseg commented on ticket pagure#3799: ""Open PR" button loads indefinitely on Pagure" https://pagure.io/pagure/issue/3799#comment-548535
14:01:48 <pingou> https://github.com/hyde/hyde last comment 2016
14:02:21 <Son_Goku> I'm sure ryanlerch has some kind of theme for pelican or can trivially make one
14:02:31 <Son_Goku> so that we have fedora bootstrap on the website and stuff
14:02:44 <pingou> I'll email him
14:02:57 <pingou> #todo pingou email Ryan for help setting up a pagure website
14:03:07 <Son_Goku> pelican is active at least: https://github.com/getpelican/pelican
14:03:27 <Son_Goku> and it's packaged in fedora as python3-pelican
14:03:27 <pingou> https://github.com/grow/grow seems more active as well
14:03:44 <Son_Goku> that looks interesting
14:04:01 <pingou> https://github.com/grow/grow/blob/master/requirements.txt ...
14:04:20 <pingou> someone doesn't quite know how to manage these files..
14:04:57 <Son_Goku> it's also only Python 2 :(
14:05:31 <Son_Goku> at least according to setup.py :(
14:05:43 <pingou> https://github.com/mkdocs/mkdocs
14:06:09 <Son_Goku> mkdocs is nice and zippy
14:06:23 <Son_Goku> it'd probably be a good choice for the pagure docs as it is
14:06:51 <pingou> instead of sphinx?
14:07:29 <Son_Goku> mkdocs generates a nicer navigation and such, and plain sphinx seems to not give us docs that are easy to navigate
14:07:44 <Son_Goku> though that might just be the theme
14:07:48 <fm-pagure> pagure.issue.comment.added -- pingou commented on ticket pagure#3799: ""Open PR" button loads indefinitely on Pagure" https://pagure.io/pagure/issue/3799#comment-548536
14:08:53 <pingou> Son_Goku: do any of these support rss feed?
14:09:07 <Son_Goku> I know at least pelican and nikola do
14:09:16 <Son_Goku> since both have blog modes
14:09:53 <pingou> ok, we're past the hour
14:10:11 <pingou> I'll just close the meeting here but we can keep on discussing if people want to hang around
14:10:16 <pingou> thanks for coming everyone :)
14:10:18 <Son_Goku> sure
14:10:19 <pingou> #topic next-meetings
14:10:42 <pingou> #info next meeting February 8th 13:00 UTC
14:10:48 <pingou> #endmeeting