20:01:18 #startmeeting FPgM office hours 20:01:18 Meeting started Wed May 19 20:01:18 2021 UTC. 20:01:18 This meeting is logged and archived in a public location. 20:01:18 The chair is bcotton_. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:01:18 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:01:18 The meeting name has been set to 'fpgm_office_hours' 20:01:26 #info This is an open floor meeting to discuss anything program management related (elections, changes, schedule, etc) 20:01:34 .hi 20:01:35 dtometzki: dtometzki 'Damian Tometzki' 20:01:44 #chair grahamwhiteuk dtometzki glb ramyaparimi pawelzelawski q5sys siddharthvipul 20:01:44 Current chairs: bcotton_ dtometzki glb grahamwhiteuk pawelzelawski q5sys ramyaparimi siddharthvipul 20:01:49 #topic Announcements 20:01:55 #info The Fedora Social Hour is tomorrow: https://element.io/app/#/room/#fedora-social-hour:matrix.org 20:01:56 #info The Nest CfP is open: https://communityblog.fedoraproject.org/announcing-dates-cfp-for-nest-with-fedora/ 20:02:02 #info The CPE team is hiring three positions to work on Fedora and CentOS infrastructure: https://communityblog.fedoraproject.org/community-platform-engineering-is-hiring/ 20:02:07 #info Fedora Linux 32 will reach end of life on Tuesday 25 May. 20:02:12 #info Critical path updates are now gated on openQA tests: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/QSOC3EZ6PGYD35IBLAEK6K6INI2IPEIG/ 20:02:17 #info F34 election voting begins tomorrow 20:02:22 #info If your team wants support from the Fedora Program Management Team, file an isssue: https://pagure.io/fedora-pgm/pgm_team/issues?template=support_request 20:02:27 #topic Open floor to discuss anything program management related (elections, changes, schedule, etc) 20:04:12 bcotton_, x3mboy asked to join the team. Do you know ? 20:04:25 dtometzki: no, i didn't see that 20:05:07 it was yesterday in fedora-pgm 20:06:27 ah okay. i'll add him to the stuff 20:06:39 can we anything do to prepare all the trainings ? 20:08:34 not unless there's one you can deliver 20:08:44 I will inform about the trainings in the infra team meeting. Is that ok ? 20:09:03 this week has been ...suboptimal, but i'll hopefully make a lot more progress next week 20:09:32 I'm here 20:09:32 i suppose. i'm not sure how useful they'll find it, but the sessions won't be secret :-) 20:09:49 Sorry., not sure if it's my connection, the client or what, but element is failing a lot 20:10:15 apparently the lack of freenode staff has made the bridge a little more fragile (which is why i joined from an IRC native client for the meeting) 20:11:39 perhaps anyone is intrested 20:12:14 Let's see if it works better 20:12:19 .hello x3mboy 20:12:20 x3mboy1: x3mboy 'Eduard Lucena' 20:12:23 .fasinfo x3mboy 20:12:24 x3mboy1: User: x3mboy, Name: Eduard Lucena, email: eduardlucena@gmail.com, Creation: 2011-11-28, IRC Nick: x3mboy, Timezone: America/Santiago, Locale: en, GPG key ID: DCDC2FFE, Status: active 20:12:27 x3mboy1: Approved Groups: council sysadmin-teleirc cla_fpca cla_done ambassadors magazine docs fedorabugs diversity-team commops @marketing mindshare fedora-socialmedia @fedora-cl @fedora-join hosted-content +advocates @i3-sig 20:12:27 yeah 20:13:02 x3mboy1: you should use x4mboy as your alternate nick :-D 20:14:44 LOL 20:15:01 My alternate is x3mlinux, but it doesn't work 20:15:04 Not sure why 20:24:04 The meeting is stll on 20:24:25 I already talk my point this morning about the README.md in the pagure repo 20:24:31 Nothing left in my side 20:25:23 yeah, these meeting are generally 5 minutes of copy/paste announcements and 50 minutes of silence :-) 20:26:58 i really dont know if all team members know about the meetings 20:27:23 Sorry to pipe up a bit late but reading back, is there a schedule planned for the training? 20:30:36 GrahamWhiteUK: not yet 20:31:36 Cool beans, just wanted to check I haven't missed something. 20:32:02 basically i'll start putting together some material and then schedule them as they're ready 20:32:33 I figure they'll mostly be viewed after the fact, since scheduling a time when everyone is available will be hard 20:33:05 but i'll do them live for whoever can attend so that there's at least some chance for q&a 20:33:12 And you should put task to act on 20:33:18 And there we can contribute 20:33:25 e.g.: chair a meeting 20:33:33 Like you did with priotk for the 20:33:46 prioritized bugs* 20:34:23 x3mboy1: do you mean like just having rotating chairs for the pgm office hours? or something else 20:38:02 I mean, that to be able to help as a team, we need task to work on 20:38:28 Chairing is one task, but it could be any task 20:38:38 right. that's why i was hoping to have like 3-4 people interested :-) 20:38:56 right now, the best thing to do is find teams that want pgm team support 20:39:04 otherwise, there won't be enough work to go around 20:46:21 I get it 20:58:34 okay, 13 hours is enough for today :-) 20:58:45 have a good day/night, everyone! 20:58:48 #endmeeting