15:00:18 <bcotton> #startmeeting Council (2020-03-04)
15:00:18 <zodbot> Meeting started Wed Mar  4 15:00:18 2020 UTC.
15:00:18 <zodbot> This meeting is logged and archived in a public location.
15:00:18 <zodbot> The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:18 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:18 <zodbot> The meeting name has been set to 'council_(2020-03-04)'
15:00:20 <bcotton> #meetingname council
15:00:20 <zodbot> The meeting name has been set to 'council'
15:00:31 <bcotton> #chair jonatoni riecatnor contyk dgilmore mattdm sumantrom tyll bcotton pbrobinson asamalik
15:00:31 <zodbot> Current chairs: asamalik bcotton contyk dgilmore jonatoni mattdm pbrobinson riecatnor sumantrom tyll
15:00:33 <bcotton> #topic Introductions, Welcomes
15:00:37 <contyk> .hello psabata
15:00:39 <zodbot> contyk: psabata 'Petr Ĺ abata' <psabata@redhat.com>
15:00:42 <dgilmore> hola
15:01:46 <bcotton> good $daypart, contyk, dgilmore
15:02:09 <dgilmore> How are you doing today bcotton
15:02:12 <dgilmore> ?
15:02:38 <bcotton> dgilmore: i'm in sunny san diego, so i can't complain. you?
15:05:28 <bcotton> okay, i guess we'll start. this should be short :-)
15:05:39 <bcotton> #topic Today's agenda
15:05:41 <bcotton> #info 289 - Improving the 3rd party repo experience
15:05:42 <bcotton> #info Infrastructure update
15:05:43 <bcotton> #info Your topics here!
15:06:24 <bcotton> #topic Improving the 3rd party repo experience
15:06:26 <bcotton> #link https://pagure.io/Fedora-Council/tickets/issue/289
15:06:44 <bcotton> Either of you want to discuss this? Seems straightforward enough, and there's been no comments on the ticket
15:07:07 * pbrobinson is here
15:07:10 * contyk looks
15:07:17 <bcotton> welcome, pbrobinson
15:07:21 * riecatnor also looking
15:08:18 <bcotton> welcome, riecatnor
15:08:58 <tyll> .helly till
15:09:01 <tyll> .hello till
15:09:02 <zodbot> tyll: till 'Till Maas' <opensource@till.name>
15:09:13 <contyk> I fail to see how installing disabled repos is better than having users to install a package that enables them.
15:09:26 <contyk> Although I'm not familiar with the UI principles there.
15:09:29 <contyk> Perhaps it makes sense.
15:10:03 <bcotton> welcome tyll
15:10:14 <pbrobinson> and I've found the enabled repos slow down slower machines quite a bit, there's a lot of usecases like cloud and containers where those repos are never needed
15:10:16 <bcotton> contyk: it's a bit of a lower-friction process as i understand it
15:10:41 <contyk> I can imagine there is some UI for managing repos, so you probably see them available, just disabled.
15:10:50 <contyk> While with the package you must know it exists and such.
15:10:56 <contyk> If that's so, sure, I'm +1.
15:11:05 <bcotton> pbrobinson: this would still require the user to opt in to those repos, so that shouldn't be a problem unless the user makes it a problem
15:11:08 <bcotton> contyk: exactly
15:11:31 <pbrobinson> bcotton: the cisco one is now enabled automatically as far as I understand it
15:12:33 <bcotton> pbrobinson: i think that's right, but that's outside the scope of this request (Google Chrome, Steam, the proprietary NVIDIA driver, and PyCharm. )
15:13:10 <pbrobinson> ah, OK, I'm guessing that's a "enable in gnome software" change then?
15:14:49 <bcotton> essentially. the package will be on disk in workstation, but disabled. gnome-initial-setup will have a checkbox for enabling them at install-time
15:18:33 <bcotton> any other comments? if not, add your votes in the ticket. this seems appropriate for lazy consensus
15:19:15 <bcotton> #topic Infrastructure update
15:19:49 <bcotton> #info GDPR concerns are going to make CPE's initial plan of handing over apps unworkable
15:20:32 <bcotton> #info We've requested some more information from CPE and then we'll have to sit down and figure out priorities and how to manage them
15:20:38 <bcotton> riecatnor: anything you want to say here?
15:20:59 <riecatnor> Sure
15:21:38 <dgilmore> What are the issues?
15:22:44 <riecatnor> We(Matthew, Ben, myself) are going to work on prioritizing the apps CPE wants to discontinue maintenance and development on. Using that list, we will work with OSPO to get things hosted with them.
15:22:47 <bcotton> dgilmore: basically we couldn't give any historical data away, so the apps would all start from a blank slate
15:23:47 <riecatnor> OSPO is aware of the situation and we are working to get the important things to a long term home
15:24:36 <dgilmore> OSPO?
15:24:41 <riecatnor> Open source program office
15:24:59 <riecatnor> My dept :)
15:25:13 <dgilmore> Okay, that's a new one to me
15:25:16 <dgilmore> :)
15:25:20 <riecatnor> formerly known as osas
15:25:48 <dgilmore> I missed the change :(
15:26:01 <riecatnor> Too many to catch them all I bet :)
15:27:17 <dgilmore> Would it be the worst thing if we started some things over?
15:27:53 <tyll> most important question: will we loose our badges?
15:27:58 <riecatnor> Nope! And that is actually the plan for Badges. We have an Outreachy internship coming up for badges where we set up a badgr instance. We also connected with the badgr team
15:28:12 <dgilmore> It wouldn't be the first time we have had to give up some historical data in a migration.
15:28:32 <dgilmore> We have had backups of the historical data stored if needed
15:28:44 <bcotton> depends on the app. losing historical calendar events is meh. badges would be rough
15:28:53 <riecatnor> We are doing away with tahrir in favor of using badgr..https://www.badgr.org/
15:28:55 <dgilmore> Agreed
15:29:24 <dgilmore> I still want a llama herder badge
15:29:33 <riecatnor> The idea is that with the move we will also keep all of our historical data for badges
15:29:45 <riecatnor> So let's stay hopeful! :)
15:32:45 <riecatnor> That is all I have except it's a work in progress, updates will be given
15:33:54 <bcotton> thanks, riecatnor
15:34:10 <riecatnor> yer welcome bcotton
15:34:12 <bcotton> #topic Do we have anything to announce?
15:34:14 <bcotton> #info This is a regular check to make sure we're communicating to the contributor (via CommBlog) and user (via Magazine) communities
15:34:23 * bcotton isn't aware of anything, but i'm required to ask
15:35:12 <riecatnor> I have a blog post almost done, keeps getting pushed off by other things :/
15:35:40 <bcotton> that's going to be on my tombstone when i die
15:37:32 <riecatnor> :D so true
15:37:47 <bcotton> #topic Next meeting
15:37:49 <bcotton> #info The next Fedora Council meeting is 11 March. It's the monthly video meeting. This time with special guest Aoife Moloney from the Community Platform Engineering team
15:38:02 <bcotton> did we decide not to use Jitsi this time?
15:38:11 <dgilmore> We did
15:38:37 <bcotton> #action mattdm to provide the URL of the meeting
15:38:46 <dgilmore> I thought mattdm said we would use Hangouts due to the technical issues we had with jitsi
15:38:56 <bcotton> that's what i remember, too
15:39:02 <bcotton> but i don't trust my memory
15:39:22 <dgilmore> Maybe between us we can get it right, but maybe not
15:39:37 <bcotton> we can at least be confident in our wrongness
15:39:53 <bcotton> #topic Open floor
15:42:42 <bcotton> last call!
15:43:52 <bcotton> okay, thanks everyone!
15:43:55 <bcotton> #endmeeting