13:21:07 #startmeeting CPE PO Office Hours 13:21:07 Meeting started Thu Jul 9 13:21:07 2020 UTC. 13:21:07 This meeting is logged and archived in a public location. 13:21:07 The chair is amoloney. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:21:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:21:07 The meeting name has been set to 'cpe_po_office_hours' 13:21:25 #info About the CPE team: https://docs.fedoraproject.org/en-US/cpe/ 13:21:35 #topic Open Floor 13:21:55 .hello nphilipp 13:21:56 nils: nphilipp 'Nils Philippsen' 13:21:59 amoloney: so how many distro releases did CPE did last quarter? XD 13:23:34 apparently 3 😇 13:24:19 amoloney: hey, if you count stream, I say more :) 13:25:05 .hello zlopez 13:25:06 mkonecny: zlopez 'Michal Konečný' 13:26:04 siddharthvipul_: very true :) 13:26:13 we are on a roll as a team! 13:30:18 Not sure if we should count rolling versions, in this case we could count each compose build 13:30:45 mkonecny: hey, more happiness 13:31:39 The number of releases will be very high for one quarter then :-D 13:32:30 mkonecny: exactly :greedy look: 13:36:13 But then we need to count every compose for classically released distros, too. Don't we? 13:36:58 Hi all, as an fyi I sent this mail yesterday 13:36:59 https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/UNWTLOI2U4VKAU4IKJZGZLZ2DTMPEFBW/ 13:37:12 it would be great if you could take a few mins to review it 13:38:06 the mail is targeted towards feedback on projects and initiatives being briefed into our team, not bugs and issues 13:39:11 looks good 13:39:50 what's BAU again? 13:40:29 (not that it matters much as it's only an example, but still) 13:40:36 Maybe expand it in the HackMD doc 13:40:59 nils: Business As Usual 13:41:33 Ah I always forget this one. 13:49:00 business as usual :) 13:54:25 If anyone has any feedback on our current way of working initiatives, please feel free to reach out to me on or off list by the end of July 13:55:10 I would like to capture all feedback and share it again with people and incorporate as much as I can where it makes sense to, before finally publishing it as a CPE initiatives policy 13:55:31 That way we will have had your direct help forming this together 13:56:20 amoloney: in last community happiness meeting, Marie, Sarah, and I were discussing some kind of survey from community to see if they are following what we are trying 13:56:29 are you aware of this discussion? 13:56:50 also, mboddu was there (sorry for skipping your name) 13:57:42 yes and no 13:58:17 that sounds good but I am interested in gaining feedback and input from the communities from a purely project/new initiative level 13:59:07 I did some research on which survey tool will be nice and limesurvey popped up 13:59:15 my understanding was you conversations were around improving the CPE comms to the communities and awareness of our work as a whole, and not just projects, but also bug fixes, issue tracking and other sustaining and infra work 13:59:56 amoloney: yeah, things like what is CPE, if the know where to reach out, if they know how new initiatives are selected and actually any questions we can think makes sense 14:00:09 to ensure that all the things we are trying is not going nowhere 14:00:19 both sets of feedback are useful to have though! I want to nail down our teams initiatives/project scheduling policy and it would be great to see where the perceived gaps are in community engagement from the team as a whole 14:00:29 I will catch up with you later about this :) 14:00:34 siddharthvipul: I was half minded during that meeting, its okay to skip my name :) 14:01:21 If we are counting all releases, then rawhide, FCOS, container releases.... 14:01:22 Thats it for today folks, thanks for participating and the transcripts will be sent as part of the weekly email over the weekend for people wanting to read it :) 14:01:26 #endmeeting