13:00:04 #startmeeting FPgM office hours 13:00:04 Meeting started Wed Jul 15 13:00:04 2020 UTC. 13:00:04 This meeting is logged and archived in a public location. 13:00:04 The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:00:04 The meeting name has been set to 'fpgm_office_hours' 13:00:05 #info This is an open floor meeting to discuss anything program management related (elections, changes, schedule, etc) 13:00:15 #topic Announcements 13:00:22 #info The Fedora Social Hour is tomorrow: https://riot.im/app/#/room/#fedora-social-hour:matrix.org 13:00:24 #info The Self-Contained Change proposal deadline is 21 July 13:00:25 #info The F33 mass rebuild begins 22 July 13:00:34 #info The Fedora Social Hour is tomorrow: https://riot.im/app/#/room/#fedora-social-hour:matrix.org 13:00:35 #info The Self-Contained Change proposal deadline is 21 July 13:00:37 #info The F33 mass rebuild begins 22 July 13:00:38 grumble 13:00:40 #undo 13:00:40 Removing item from minutes: INFO by bcotton at 13:00:37 : The F33 mass rebuild begins 22 July 13:00:41 #undo 13:00:41 Removing item from minutes: INFO by bcotton at 13:00:35 : The Self-Contained Change proposal deadline is 21 July 13:00:43 #undo 13:00:43 Removing item from minutes: INFO by bcotton at 13:00:34 : The Fedora Social Hour is tomorrow: https://riot.im/app/#/room/#fedora-social-hour:matrix.org 13:00:52 #link https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html 13:00:53 #info The Nest With Fedora CfP is now open: https://communityblog.fedoraproject.org/nest-with-fedora-cfp-open/ 13:00:54 #help The Fedora Ambassadors Revamp needs volunteers for the organizing task force: https://fedoraproject.org/wiki/Fedora_Ambassadors_Revamp_2020 13:01:00 #info Fedora documentation is now multilingual: https://communityblog.fedoraproject.org/fedora-documentation-is-now-multilingual/ 13:01:01 #info The Fedora Council meeting has moved to Thursdays: https://apps.fedoraproject.org/calendar/meeting/9781/ 13:01:08 #topic Open floor 13:17:23 coucou bcotton 13:19:44 welcome, jibec! 13:20:21 I saw you, alone in this big virtual office, I decided to stop by to say hello ;) 13:20:25 merci 13:20:34 i didn't bring any snack this week ;-) 13:20:58 don't worry, I just bought a new bottle, we can share it anyway 13:21:05 jibec++ 13:21:06 bcotton: Karma for jibecfed changed to 4 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 13:21:52 I asked a few weeks ago on DEVEL mailing list the following question: does a tool exists to track the progress of a project accross multiple bug tracker? 13:22:26 typical usecase for me: reduce maintenance cost of https://fedoraproject.org/wiki/L10N_Move_to_Weblate#List_of_projects_and_status 13:22:46 i don't think i saw that thread, sorry 13:23:05 so you're wanting to aggregate status accross multiple pagure repos? or also bugzilla, github, etc? 13:24:02 yes, I want to aggregate statuses across multiple sources: pagure, bugzilla, github, etc. 13:24:41 * jibec pulls out the corkscrew 13:25:33 make it a tall pour ;-) 13:26:15 i'm not aware of anything that would do that easily. something rudimentary could be done relatively simply with a few hours of python against the various APIs 13:26:27 "relatively" being the key word here 13:28:00 ok, too bad 13:28:03 * jibec serves three glasses (one or bcotton, one for himself and one for the next) 13:28:15 santé ! 13:28:21 cheers! 13:29:10 i'll dig around a little bit. there are certainly tools that have integrations with at least bugzilla and github. but not necessarily without a lot of overhead you don't want 13:29:34 yep, I'm sure it exists really complex tools :p 13:29:43 nevermind 13:29:50 have a nice day ben 13:30:19 there is lots of solution for a few dozen of k€, and if you pay enough, we can also bring custom problems along the solutions :p 13:30:51 :d 13:30:53 * jibec pretends he's late, empties the glass and disappears like a 🌠 13:30:57 thanks, jibec, you too 13:31:15 * bcotton tries really hard not to add that to the pile of project's he'll get to any day now 13:32:46 misc: since you're here, i had a question i thought of last night. do we have a test/stage/whatever wordpress site for the community blog? if not, would it be possible to stand one up temporarily? 13:33:28 i want to make some changes to the theme we use on the site, but i'd rather not test it in production. i'm not ready for it yet, but when i am, i wouldn't need it to be the whole thing, just a small instance that i can throw some test data on to play around with 13:33:38 bcotton: we don't, but we can add one 13:33:54 cool! i'll let you know when that card bubbles to the top of the pile :-) 13:33:55 let me see 13:34:08 I am just unsure on what staging would be 13:34:16 like a copy that get resynced, etc 13:34:42 (we do have one for the magazine, not sure if people use that) 13:35:37 https://wpengine.com/resources/what-is-a-staging-site-why-have-one/ explain the feature, so if that's what you look for, ping my team and we can make it happen (if you do not have access) 13:39:20 for this specific instance, i wouldn't need a db sync or anything 13:39:36 i'd just log in with my FAS account, create a few dummy articles real quick and then upload the theme 13:40:09 and then we'd tear it down when i'm done, because we don't make changes to the site often enough to justify keeping it around 13:40:54 yeah, I need to verify the FAS side, if that's a different url it might break 13:40:55 i'd just install it locally, but i want to make sure it works with FAS accounts 13:41:31 ok. worst case, i do it locally, because for what i want to do, FAS-vs-local shouldn't matter, but I want to minimize the risk :-) 13:41:39 let's do a stage env, and see how it go 13:42:14 (rather than scheduling a pre meeting to decide when we meeting to have a specification for a stage server...) 13:42:30 lol 13:43:28 okay. i'll let you know when i have the changes ready to test. i don't want to have the instance sitting around ignored for potential cost and safety reasons 13:43:38 so https://fedoracomstg.wpengine.com should be here "shortly" 13:44:19 let's see how fast it go, and if that let people use FAS, then we can drop and recreate it 13:44:30 misc++ 13:44:55 by the way, is there a preferred way to request stuff from your team (e.g. a ticket system or anything), or is it just "email someone and we'll get to it" 13:47:16 misc: staging site works with FAS login :-) 13:48:07 bcotton: depend if the overhead for the request is higher than the request or not, I am not attached to ping on irc, cause it get faster to discuss, 13:48:17 but we also have a incoming request form for large stuff 13:48:47 (like "we want to start this new Nuclear Host Linux in 2 week, can you help" *cough*) 13:49:20 :-D 13:49:26 okay, i can work with that 13:49:39 (but since requests go from "not urgent and not clear" to "everything is burning", I personally do not think requesting ticket help for the whole range of requests, so I am not mandating) 13:50:10 makes sense 13:52:06 in doubt, mail to the whole team make sure to reach at least someone (I think we have a alias we use from time to time, but not enough I can find it right now :/ ) 13:52:29 hah, no worries. i can always make riecatnor pass messages for me ;-) 14:01:41 #endmeeting