18:00:02 <nirik> #startmeeting Infrastructure (2018-04-19)
18:00:03 <zodbot> Meeting started Thu Apr 19 18:00:02 2018 UTC.  The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:03 <zodbot> The meeting name has been set to 'infrastructure_(2018-04-19)'
18:00:03 <nirik> #meetingname infrastructure
18:00:03 <zodbot> The meeting name has been set to 'infrastructure'
18:00:03 <nirik> #topic aloha
18:00:03 <nirik> #chair smooge relrod nirik pingou puiterwijk tflink
18:00:03 <zodbot> Current chairs: nirik pingou puiterwijk relrod smooge tflink
18:00:18 <nirik> morning everyone. who's around for a fun packed infra meeting?
18:00:21 <bowlofeggs> .hello2
18:00:22 * aikidouke here
18:00:22 <zodbot> bowlofeggs: Something blew up, please try again
18:00:25 <keitellf> .hello2
18:00:26 <zodbot> keitellf: Something blew up, please try again
18:00:31 <nirik> nice.
18:00:32 <keitellf> odd
18:00:38 <bowlofeggs> greetings fellow beings of fedora infrastructure
18:00:44 <keitellf> greetings
18:00:50 <puiterwijk> hello
18:00:54 <marc84> hi everyone
18:00:58 <tflink> hello
18:01:03 * cverna waves
18:01:10 <clime> hello
18:01:15 <bowlofeggs> zodbot: you don't know me, you don't know what i'm about
18:01:31 <nirik> #topic New folks introductions
18:01:31 <nirik> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
18:01:38 <nirik> any new folks around this week?
18:01:43 <zodbot> bowlofeggs: I sure do, Randy
18:02:27 <nirik> 😔
18:02:32 <keitellf> Is zodbot becoming... sentient?
18:02:53 * nirik pictures the red 'eye' of hal 9000
18:03:16 <zodbot> nirik: I'm not that bad! I just try to be helpful.
18:03:43 <nirik> ok, lets move on to status then...
18:03:47 <nirik> #info Infrastructure hackfest was last week: https://fedoraproject.org/wiki/Infrastructure_Hackathon_2018
18:03:47 <nirik> #info Fedora 28 Final freeze is in effect!
18:03:47 <nirik> #info new bodhi release - 3.6.0
18:03:47 <nirik> #info new pagure in staging 4.0
18:03:47 <nirik> #info new priority fields in infrastructure issues, please use them!
18:04:11 <nirik> any other status/info/tidbits?
18:04:19 <bowlofeggs> lol zodbot u silly
18:04:40 <puiterwijk> #info We are trying an oncall system. Rather than pinging a random person, please ask .oncall to see who of the sysadmins is on the books to answer
18:04:47 <nirik> perhaps zodbot would share their least favorite ice cream flavor? ;)
18:05:00 <bowlofeggs> technically bodhi 3.6.0 didn't quite work, so we're workign on a 3.6.1 and we reverted the web servers to 3.5.2 (the backends are still 3.6.0)
18:05:03 <zodbot> nirik: Of course that's strawberry.
18:05:41 <nirik> puiterwijk: yeah, I should send out a note about that...
18:06:05 <clime> zodbot: can you pass the Turing test?
18:06:13 <clime> sry, needed to ask
18:06:24 <zodbot> Who knows? I don't think anyone tried me yet.
18:06:26 <nirik> bowlofeggs: is there an eta for 3.6.1? and/or moving back to openshift web servers?
18:06:38 <nirik> I know there's pressure to get the waive button working.
18:06:41 <nirik> and test reporting
18:07:02 <bowlofeggs> nirik: i'm working on it today - i was hoping to have it in stg today but it needs a more complicated refactor than i realized
18:07:21 <nirik> fair enough.
18:07:28 <puiterwijk> Do note that we've gotten it to run on apache inside openshift now. So that should stabilize things too.
18:07:29 <bowlofeggs> nirik: the bigger issue was alwaysy in bodhi actually, but the way we deployed it in openshfit kinda exaserbated it
18:07:35 <bowlofeggs> yeah that will help a lot
18:07:42 * nirik nods.
18:07:48 <puiterwijk> Before, we used gunicorn, which is... a lot more strict with errors
18:07:49 <bowlofeggs> bdohi in vms http 500s like 75% of the time whcih i never noticed
18:07:59 <bowlofeggs> so that's what i'm trying to fix with 3.6.1
18:08:06 <puiterwijk> gunicorn will entirely nuke a child if it has an uncaught exception.
18:08:13 <bowlofeggs> oh and there was an actual regression in 3.6.0 too that patrick fixed
18:08:14 <puiterwijk> Lots of violence was happening
18:08:24 <bowlofeggs> the other issues i think have been in bodhi a long time and we just never noticed
18:08:29 <nirik> a little bit of the ultra-violence. ;)
18:08:32 <bowlofeggs> because our proxy servers and httpd just made it ok
18:08:39 <bowlofeggs> haha i just watched that movie recently
18:08:58 <bowlofeggs> anyways, i think it'll be good once i get this refactor done
18:09:02 <nirik> anyhow, sounds good...
18:09:11 <bowlofeggs> i'm glad we put it in openshift because it revealed this problem
18:09:15 <bowlofeggs> i'd have never noticed it myself
18:09:15 <bowlofeggs> haha
18:09:40 <nirik> puiterwijk: do you think you are likely to get any cycles to work on the new cloud again soon? that and gitspanner seem to be the things everyone really really really wants...
18:09:57 <puiterwijk> nirik: yes, I hope so. I think things are slowing down this week somewhat finally
18:10:14 <nirik> yeah, don't jinx it tho! :)
18:10:16 <puiterwijk> So I'm planning to work on things later today and tomorrow, after catching up from a week not being here, and new bodhi stuff
18:10:23 <puiterwijk> nirik: I'm goingto send them your way!
18:10:25 <puiterwijk> .oncall
18:10:25 <zodbot> nirik (Kevin Fenzi) is totally oncall
18:10:30 <nirik> I will try and do my best to run interference for you.
18:10:32 * nirik nods
18:10:45 <puiterwijk> Thanks for that
18:11:00 <nirik> #topic Tickets
18:11:11 <bowlofeggs> tickets! get your tickets!
18:11:14 <nirik> I wanted to quickly note the new priority's on tickets...
18:11:29 <nirik> I posted to the list about them, but please if you touch a ticket make sure it ends up in the right bucket.
18:11:51 <nirik> I went through some of the backlog yesterday, will try and get more today
18:11:54 <bowlofeggs> ...which is always the urgent bucket, right? :)
18:12:02 <nirik> right. :) not.
18:12:04 <bowlofeggs> haha
18:12:29 <nirik> So new tickets land in 'needs review' This is for when we have not yet seen/assessed the ticket yet.
18:13:03 <nirik> Then they move to Waiting asignee, Waiting reporter, Waiting external , Urgent
18:13:23 <nirik> and next meeting
18:13:46 <nirik> so if they are waiting on asignee, we know we need to do it and just waiting for whoever to process it.
18:14:06 <nirik> waiting on reporter means we asked a question/need more info, so we want the reporter to reply to us
18:14:23 <nirik> waiting external is waiting on some external event... like f28 release or some other complex thing to be done
18:15:09 <nirik> and meeting means we want to talk about it in the next meeting before doing anything
18:15:38 <nirik> I think with this we can have a clearer picture of the backlog... and what we need to work on vs what we can ignore until we have more info
18:16:03 <nirik> any questions on that?
18:16:11 <cverna> I think it would be nice, if when we move the ticket from needs review to waiting asignee we put some pointer of what needs to be done
18:16:21 <cverna> so someone can pick it up
18:16:28 <cverna> for example an apprentice
18:16:30 <nirik> yep. I agree...
18:17:16 <nirik> this means that issues are not really good for 'should we do this thing' or 'how can we design xyz'
18:17:31 <nirik> but I think those are mailing list/meeting/face to face discussions...
18:17:38 <nirik> issues should be descrete tasks
18:18:12 <nirik> #topic Meeting time / ideas to spiff up the meeting - kevin
18:18:24 <nirik> so I started a discussion about meeting time on the list...
18:18:53 <nirik> I guess we could just bite the bullet and run a whenisgood for everyone who thinks they might attend.
18:19:13 * aikidouke is currently good with anything from 0300 UTC to 1900 UTC
18:19:42 <puiterwijk> nirik: or framadate. Slightly less pretty, but FOSS :)
18:19:53 <nirik> puiterwijk: haven;'t heard of that oone...
18:19:54 <bowlofeggs> nirik: how about 03:00 PDT?
18:20:03 <puiterwijk> bowlofeggs: ... UTC please?
18:20:08 <bowlofeggs> haha
18:20:08 <puiterwijk> We have international colleagues
18:20:09 <aikidouke> nirik: is the problem not many ppl attend or ??
18:20:25 <bowlofeggs> puiterwijk: i put PDT because that's where nirik lives - i.e., 03:00 for nirik :)
18:20:26 <nirik> aikidouke: well, this current time is late for eu... so for example it's bad for pingou
18:20:38 * aikidouke nods
18:20:38 <nirik> bowlofeggs: I am not usually up at 3am...
18:20:48 <clime> I am eu. It's quite good for me
18:21:08 * puiterwijk thinks the current time is fine. But then my working hours are... flexible :)
18:21:09 <clime> 14UTC would be also but that's maybe too soon I guess
18:21:17 <bowlofeggs> i'm pretty available, but yeah i think a framadate or whenisgood would be good
18:21:27 <puiterwijk> 14UTC is awkward for west coast US
18:21:30 <nirik> 14UTC makes it pretty early for me, but I guess I can do it if needed.
18:21:38 <nirik> 7am or so
18:21:49 <clime> oh, ok, that's very soon
18:21:53 <clime> *early
18:22:07 <bowlofeggs> what about the mars colony? we should make sure it's a good time for them too, for elon's sake
18:22:18 <bowlofeggs> and how are we gonna solve the IRC lag?
18:22:36 <puiterwijk> bowlofeggs: we don't, we just run the meeting for 2 days so they have time to reply
18:22:37 <nirik> :)
18:22:41 <aikidouke> sounds like we need a "whenizleastpainful"
18:22:55 <nirik> how about someone who has used framadate make one and mail the list how to add info to it?
18:23:04 <bowlofeggs> haha
18:23:09 <nirik> then we revisit on list and move to the 'best' time for people?
18:24:09 <nirik> I guess I can poke at framadate... how hard can it be?
18:24:17 <puiterwijk> It's really simple.
18:24:25 <puiterwijk> Just, as said, slightly more painful than whenisgood
18:25:09 <puiterwijk> (but, pull requests appreciated I've been told!)
18:26:21 <nirik> ok.
18:26:35 <nirik> #action nirik to send out a framadate or something
18:26:55 <puiterwijk> nirik: just don't click on any of the links of other projects they have without help from pingou.... A lot of their sites are in French :D
18:27:04 <nirik> bowlofeggs: you had RATs on here, but pingou isn't around today... could we do it next week? or out of meeting?
18:27:05 * pingou runs away
18:27:07 <aikidouke> mon dieu
18:27:17 <nirik> ha
18:28:08 <nirik> ok, perhaps pingou is here?
18:28:30 <nirik> #topic RATS - bowlofeggs / pingou
18:28:39 <pingou> nirik: not really, but we discussed about it earlier with bowlofeggs so I think he can speak for both of us
18:29:17 <nirik> ok. I know there's two approaches, but I personally don't know enough to choose any... as always, the people doing the work should choose...
18:29:21 <bowlofeggs> yeah we talked about it a bit today
18:29:43 <bowlofeggs> i think we came to an agreement to make it a library between us
18:29:59 <bowlofeggs> but i think it'd still be good to get feedback from others if there are more opinions
18:30:11 <nirik> who else will be interfacing with this? qa ?
18:30:30 <bowlofeggs> at this point, bodhi and pagure are known to interact with it
18:30:38 <bowlofeggs> it will interact with QA, but probably not the reverse
18:30:53 <tflink> what's rats? I'm only familiar with that in the ancient-qa-project sense
18:31:17 <clime> I am also curious what it is.
18:31:20 <nirik> they are these small cheese eating rodents... they make great pets
18:31:20 <bowlofeggs> tflink: Run Another Test Service
18:31:23 <bowlofeggs> haha
18:31:29 <tflink> ok, thanks
18:31:34 <bowlofeggs> i did have a pet rat about 18 years ago
18:31:36 <nirik> 🐀
18:31:43 * aikidouke thought it was a remote access trojan
18:31:45 <tflink> the old one is Rawhide Acceptance Test Suite
18:31:52 <bowlofeggs> so the problem to solve is that we need a way for users to ask for tests to be re-run
18:32:04 <puiterwijk> Overloading names! What could possibly go wrong!
18:32:09 <bowlofeggs> initially we wanted it in bodhi, like a button "re run this test"
18:32:14 <tflink> eh, qa's RATS has been dead for years
18:32:19 <nirik> and if we make it a library isn't it then RATL?
18:32:50 <bowlofeggs> but then pingou realized that we wanted to do this in both bodhi and pagure, and so it became clear that a third project made sense to share code
18:33:06 <bowlofeggs> but the debate was whether it should be a service or a library
18:33:25 <puiterwijk> i.e. RATS vs RATL
18:33:28 <bowlofeggs> nirik: yeah i guess the library makes the name kinda weird
18:34:08 <bowlofeggs> to summarize my argument for a library: it's simpler and still gets the job done - it's one less thing to monitor and respond to when it goes down
18:34:53 <aikidouke> name aside, would a library be more flexible than a service?
18:35:12 <bowlofeggs> i think they are each pretty flexible, so i think that aspect is probably comparable
18:36:14 <bowlofeggs> oh and i guess i didn't explain what is complicated enough to even make sharing code sensible: there are three different test systems and they will each have different ways to retrigger them
18:36:22 <bowlofeggs> so it's not as simple as sending a single fedmsg
18:36:46 <nirik> ok
18:37:07 <bowlofeggs> (openqa, taskotron, and the CI pipeline)
18:37:16 <pingou> (pipelines even now)
18:37:23 <cverna> i think having one less service to look after is always nice
18:37:23 <nirik> anything else on this then? or shall we just wait a bit for more feedback and move forward
18:37:39 <bowlofeggs> i don't have anything else
18:39:09 <nirik> #topic Apprentice Open office minutes
18:39:18 <nirik> Any apprentices with questions, comments, etc?
18:39:27 <puiterwijk> Hah. Switched from hour to minutes? :)
18:39:36 <nirik> aikidouke: you go to talk about libravatar in a min?
18:39:43 <nirik> puiterwijk: life comes at you fast!
18:39:52 <aikidouke> I am good - although I thought smooge would want to be around?
18:39:55 <bowlofeggs> hahah
18:40:03 <nirik> he's semi-out this week...
18:40:22 <nirik> we can go ahead or wait for next week? whatever you prefer?
18:40:25 <aikidouke> ok, I'm ready to go at your discretion :)
18:40:44 <bowlofeggs> i'm interested in this topic too
18:40:48 <nirik> #topic Learn about:libravatar - #aikidouke
18:40:51 <nirik> take it away! :)
18:40:57 <aikidouke> alright then - thanks nirik
18:41:22 <aikidouke> So Libravatar is a django 1.4 app
18:41:31 <nirik> 1.4? yikes
18:41:38 <aikidouke> django v1.4 has been unsupported since 2015
18:42:32 <nirik> 😱
18:42:34 <aikidouke> it also uses python 2.7, the python imaging library PIL, py dns 2.3.6
18:42:55 <aikidouke> jQuery, and few other smaller libs
18:42:57 <puiterwijk> PIL? Oh man. This is getting better and better
18:43:11 <aikidouke> the jQuery version is 1.7.2 and is unmaintained
18:43:16 <bowlofeggs> PyDNS is also super broken upstream
18:43:20 <aikidouke> the newest version is 3.3.1
18:43:32 <bowlofeggs> the fedora version carries several patches, but upstream seems dead
18:43:38 <aikidouke> bowlofeggs is correct
18:43:58 * bowlofeggs recently had to patch it for py3
18:44:23 <aikidouke> so there is a new branch of py3dns I found on launchpad, but that may just be someone from ubuntu patching it themselves
18:45:00 <bowlofeggs> do we know what other orgs use libravatar than fedora?
18:45:13 <bowlofeggs> like, do other distros use it too? could we collaborate with them if so?
18:45:21 <aikidouke> other libraries include; gearman, bcrypt, python open ID, requests
18:45:22 <nirik> well, given how low the stats are, it sounds like no one uses it.
18:45:56 <aikidouke> bowlofeggs: I dont know of any, and there hasnt been much traffic on libravatar's shutdown/takeover page
18:45:59 <bowlofeggs> we have plans to switch to a new ID service backed by freeipa - could that system host photos for this purpose?
18:46:06 <clime> I would like to help with rewrite and deployment.
18:46:24 <clime> I think whatever new will be written can just base on that code.
18:46:29 <aikidouke> bowlofeggs: I dont know that answer
18:46:46 <puiterwijk> bowlofeggs: not really. Technically, yes. But practically, we don't really want that
18:47:04 <bowlofeggs> i wonder if it's more work to modernize libravatar and host it than to make something simpler
18:47:18 <bowlofeggs> libravatar does a lot of things we wouldn't necessarily use (like federation)
18:47:30 <bowlofeggs> afaik, our needs are just some place to host a photo
18:47:30 <puiterwijk> bowlofeggs: but I'm not against writing a small thing for it which uses the same frontend
18:47:35 <bowlofeggs> we could use fedora people for this too
18:47:47 <nirik> wel, that only works for cla+1...
18:47:48 <bowlofeggs> we have a photo thing in fedorapeople for the planet blogs
18:47:50 <puiterwijk> Yeah, we talked about just telling people to put a ~/.myphoto.jpg on fpeople
18:47:53 <aikidouke> clime, there are also integrations with a few picture resizing/compression utilities like PNG crush pngcrush.com, advanceCOMP, GIFsicle, and YUIcompressor
18:48:11 <clime> yup ok
18:48:17 <bowlofeggs> i guess technically libravatar also sizes the photos for us
18:48:22 <bowlofeggs> whcih is nice too
18:48:42 <nirik> a lot of it's code is likely the ui to upload/resize things
18:48:46 <aikidouke> if someone wanted to do a rewrite, there is about 2000 actual lines of python in 22 files, 50 html templates
18:48:47 <bowlofeggs> yeah
18:48:58 <bowlofeggs> oh that's not that much code actually
18:49:05 <bowlofeggs> it sounded like it'd be more than that to me
18:49:06 <aikidouke> nirik: that seems to be the case
18:49:37 <nirik> we could also just fallback to gravatar for now, and if/when someone has rewritten this move to it...
18:49:48 <bowlofeggs> true
18:49:51 <nirik> (but of course if you take off the pressure it likely never gets done)
18:49:52 <bowlofeggs> though gravatar tracks users
18:50:05 <bowlofeggs> i don't know if i like putting tracking things into bodhi for example
18:50:09 <aikidouke> as far as translations go, libravatar has been translated to 16 languages, but notably, hindi and both chinese langs are not included
18:50:20 <bowlofeggs> well, i guess we don't know what gravatar does, but their privacy policy is extremely thin
18:50:29 <nirik> bowlofeggs: do note that libravatar falls back to gravatar already
18:50:34 <bowlofeggs> so i assume they are tracking since they don't promise much privacy
18:50:38 <bowlofeggs> oh i didn' tknow that
18:50:54 <bowlofeggs> nirik: are you sure?
18:51:05 <aikidouke> yup - I didn't do much research with that, but it does fall back to gravatar
18:51:11 <bowlofeggs> nirik: because i neve rhad a working photo until i set libravatar up and i did have a gravatar photo
18:51:38 <bowlofeggs> so i've not seen that happen in my experience, but i don't know if there was something odd about my account or something
18:51:46 <bowlofeggs> i've also been meaning to get rid of gravatar because of tracking
18:51:57 <nirik> perhaps they changed it. I could have sworn it did once.
18:52:22 <clime> I think it still does but we could perhaps switch that part off?
18:52:29 <pingou> and 12 GB of 302 redirects to Gravatar)
18:52:32 <pingou> https://feeding.cloud.geek.nz/posts/looking-back-on-starting-libravatar/
18:52:38 <nirik> ah "Note that if an image is not found in the Libravatar database and the hash algorithm used was MD5, then Libravatar will first redirect to Gravatar in case the image exists there."
18:52:40 <aikidouke> bowlofeggs: there are 39 separate references to gravatar in the code
18:52:46 <puiterwijk> bowlofeggs: "Note that if an image is not found in the Libravatar database and the hash algorithm used was MD5, then Libravatar will first redirect to Gravatar in case the image exists there. Then it will honour the default parameter."
18:53:09 <pingou> integration with other sites and projects (Fedora, Debian, Mozilla, Linux kernel, Gitlab, Liberapay and many others)
18:53:09 <bowlofeggs> strange, wonder why it didn't do taht for me
18:53:12 <puiterwijk> Yeah, what nirik said
18:53:31 <puiterwijk> bowlofeggs: I think that at least in Bodhi, we use the openid id, which gravatar doesn't have I think
18:53:34 <pingou> so it is used by others, I guess it needs someone to step up
18:53:46 <puiterwijk> So for Bodhi, the fallback to gravatar doesn't work
18:53:54 <clime> well, I can take the rewrite if there is like a ticket for it.
18:53:55 <bowlofeggs> puiterwijk: that might explain my experience
18:54:09 <clime> I would be happy to code again in Django.
18:54:12 <bowlofeggs> so maybe it'd be good to invite the other projects to participate with us?
18:54:19 <nirik> well, I am not sure we have cycles to tell anyone to work on this... but if a group of folks want to, great!
18:54:33 <bowlofeggs> yeah +1
18:54:40 <nirik> I am not sure django is a great choice... something more long term stable might be better?
18:54:41 <bowlofeggs> if clime wants to keep it alive i'm +1
18:54:51 <clime> thanks!
18:54:58 <bowlofeggs> i don't mind django personally
18:54:59 <aikidouke> so - a few points to ponder if we are wanting to host it
18:54:59 <puiterwijk> bowlofeggs: is that a "+1 I'll also contribute and co-maintain"?
18:55:05 <bowlofeggs> at least it's not pyramid :)
18:55:28 <bowlofeggs> puiterwijk: hahah i'm not sure i can commit to contribute at this point, sadly
18:55:28 <nirik> well, having to keep up with the latest version all the time is a treadmill for something like this...
18:55:29 <pingou> https://wiki.libravatar.org/shutdown-coordination/ is pointing out that digital ocean may be willing to help for hosting
18:55:34 <pingou> (if contacted)
18:55:42 <bowlofeggs> more i'm thankful that clime offered :)
18:55:59 <bowlofeggs> nirik: fair
18:56:00 <aikidouke> would we have to police the images that get hosted as avatars?
18:56:05 <puiterwijk> Also, I'm not sure I'd be all for hosting this in Fedora core Infra, but if clime wants to do this on e.g. a cloud instance, by all means.
18:56:06 <nirik> IMHO, we should not really host it in it's current version... it seems like a security nightmare waiting to happen
18:56:19 <puiterwijk> nirik: yeah, agreed.
18:56:25 <puiterwijk> aikidouke: that's indeed another issue...
18:56:31 <pingou> clime: there is a debian person on that page that seem interested in helping
18:56:43 <bowlofeggs> for policing, we could require the CLA+1
18:56:47 <clime> well, I would like to do it on cloud instance first. Then probably ask again about a plan.
18:56:55 <bowlofeggs> and yes, we should police, but should not let random people upload photos
18:56:57 <puiterwijk> bowlofeggs: if we require CLA+1, we might just as well do fpeople...
18:57:03 <clime> pingou: okay, I will try to contact him.
18:57:04 <bowlofeggs> puiterwijk: also true
18:57:14 <clime> Would it be possible to make an Infra Ticket for it
18:57:23 <aikidouke> not only that, but, if we are hosting images - can't trojans, viruses, and other nasties be encoded in the jpg format?
18:57:26 <nirik> clime: for the cloud instance? sure...
18:57:27 <clime> to which I could be assigned? (so that I have something to show to my manager :))
18:57:31 <pingou> looking at the page, I think we should look at contributing to that effort and not host it ourselves
18:57:53 <puiterwijk> Yeah, I'm all for pingou here.
18:57:58 <nirik> clime: ah... sure, I guess we could do something there... or make a new project for it entirely?
18:57:59 <puiterwijk> Let's first see if the current plans get off the ground.
18:58:00 <bowlofeggs> one thing i worry about is say we get it running and rely on it, and then we lose interest - that could be bad too
18:58:04 * aikidouke will stop with the sky is falling stuff
18:58:09 <pingou> clime: "Investigate replacement/updating/maintenance" of libravatar?
18:58:28 <clime> well, might be
18:58:28 <nirik> aikidouke: indeed they could. Not sure what the current code does for that.
18:58:39 <clime> I will probably just try to make it work somewhere in the cloud.
18:58:44 <bowlofeggs> if digital ocean wants to host/admin it that would save us from the burden of policing it
18:58:48 <puiterwijk> nirik: it uses PIL.... Which has had some pretty funny vulnerabilities last year, if I recall correctly.
18:58:52 <aikidouke> nirik: I think not much
18:58:58 <clime> I would be happy if we didn't completely exclude the option of hosting somewhere at least for now....
18:59:01 <puiterwijk> Things like "code execution by misinterpreting files"
18:59:13 <nirik> fun. so we are coming on the end of our time...
18:59:18 <pingou> clime: would that title for the ticket satisfy you?
18:59:28 <nirik> what do we want to do here? discuss more out of meeting/list?
18:59:29 <aikidouke> and thats about the end of my rainbow nirik
18:59:39 <aikidouke> :)
18:59:46 <clime> pingou: well, it can be also just: "Modernize and deploy test instance of libravatar"
18:59:53 <bowlofeggs> could we compare the option of hosting/saving libravatar to the option of just using fedora people?
18:59:57 * nirik kinda hates 'lets figure this out tickets' but if clime really wants one...
19:00:22 <pingou> nirik: managerial umbrealla? :)
19:00:41 <aikidouke> can I suggest we see if clime can get assistance from the person from debian and what the rewrite really looks like, then maybe get an update in a month or so?
19:00:41 <clime> nirik: I will really just start rewriting it. I cannot really get a better chance to get it to know it anyway.
19:01:12 <aikidouke> or whatever timeframe..
19:01:35 <nirik> clime: ok, perhaps setup a pagure.io project for the re-write and tell the other interested people about it?
19:01:41 <nirik> then we can figure out where it could run
19:01:44 <clime> maybe it can be replacement/updating/maintenance" of libravatar without the "investigate" part :)
19:01:47 <clime> ok
19:02:14 <clime> thank you!
19:02:24 <aikidouke> nirik: can we talk about whats going on with FAS next time?
19:02:46 <nirik> sure.
19:02:50 <puiterwijk> aikidouke: you can also ping me with questions out of meeting.
19:02:59 <aikidouke> ty puiterwijk
19:02:59 <nirik> #topic Open Floor
19:03:07 <nirik> anyone have anything quickly for open floor?
19:03:20 <puiterwijk> You have -4 minutes
19:03:31 <aikidouke> maybe a nice rug to bring the room together? *sorry*
19:03:59 <nirik> that rug really did tie the room together. ;)
19:04:07 <nirik> ok, thanks for coming everyone!
19:04:11 <nirik> #endmeeting