17:00:37 #startmeeting fedora-server 17:00:37 Meeting started Wed Dec 7 17:00:37 2022 UTC. 17:00:37 This meeting is logged and archived in a public location. 17:00:37 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:00:37 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:37 The meeting name has been set to 'fedora-server' 17:00:45 #topic Welcome / roll call 17:00:52 Welcome everybody. 17:00:59 .hello2 17:01:00 mowest: mowest 'Steve Daley' 17:01:02 Let's see who is here. 17:01:04 .hello2 17:01:06 eseyman: eseyman 'Emmanuel Seyman' 17:01:15 * eseyman makes it with seconds to spare 17:02:12 Can't stay long, special Christmas lunch today at work, and this is lunch hour in the US Eastern time zone 17:02:14 .hello2 17:02:15 cooltshirtguy: cooltshirtguy 'Jason Beard' 17:02:43 Welcome again 17:03:02 Then let's start now. I'll post the agenda 17:03:10 #topic Agenda 17:03:33 #info 1. Discussion of the meeting start time 17:03:51 yeah, we really need to change this, imho 17:03:52 #info 2. Server critical path definition proposal 17:04:20 #info 3. Server WG work program for upcoming year 17:04:33 #info 4. Open Floor 17:04:46 Anything to add? 17:05:03 Red Hat is in the Eastern Time zone of the US, so perhaps we could catch a few more of the Red Hat people with an hour later. 17:05:31 pboy: I suspect that's quite enough as is 17:05:41 mowest Yes, hopefully 17:05:47 #topic 1. Discussion of the meeting start time 17:06:11 .hello2 17:06:12 jwhimpel: jwhimpel 'John Himpel' 17:06:24 Would do you think to follow some other teams and to shift to 1 hour later? 17:06:39 Would - What 17:06:41 Yes, please if that time slot is open. 17:06:48 That would work a bit better for me. 17:07:00 Yes, it is. 17:07:11 For me, too 17:07:27 +1 for an hour later 17:07:37 i'm indifferent 17:07:51 the current schedule is fine for summer but impratical during winter 17:07:56 cooltshirtguy would it be OK for you? 17:08:04 it's fine 17:08:17 Ok, then 17:08:43 #agreed We'll start our meeting one hour later during winter time. 17:09:31 #topic 2. Server critical path definition proposal 17:09:53 I suppose, we missed that because of our meeting gap 17:10:54 adamw Are you online? Ir there anything to do about this topic? (I guess not). 17:12:35 "Merged 15 days ago" 17:13:04 OK, so it's done. 17:14:00 It's a bit unfortunate. 17:14:23 "this adds a Server critpath definition which is basically the 17:14:24 freeipa-server group, plus cockpit and postgresql." 17:14:55 honestly, this is fine by me 17:15:26 one could argue apache should be in there but apache's depchain is quite large 17:15:35 Yes, but it is a bit few. We have much more items. 17:16:11 E.g.we have Virtualization, Containerization, both quite important for Server 17:16:45 free-ipa is more of a marginal use 17:16:46 mind you, perl being in critpath had cons but no pros so I'm glad it isn't in there anymore 17:17:11 pboy: agreed for birt and containers 17:17:16 s/birt/virt 17:18:03 But may be we an open the discussion again when we discussed and decided our release and quality criteria 17:18:53 yes, I don't think revisiting this is going to be a problem 17:19:07 By the way, I like perl. Was a great time doing everything about system admin in perl 17:19:36 Full of surprises, after a year coming back to an issue. :-) 17:19:53 OK, let's switch 17:20:20 #topic 3. Server WG work program for upcoming year 17:20:35 Well, the floor is open. 17:20:46 What do you think? 17:21:19 What documentation for F37 still needs to be reviewed? 17:21:45 I believe we had decided to choose 5 items and do them well instead of trying to do everything at once 17:22:20 Yes, we wanted to choose the 5 oldest articles. 17:22:38 Did anyone find time recently to help diagnose my issue with letsencrypt certs and wildfly? The problem is in how to change the config files to support ssl. 17:23:15 nope, I'll put it on my todo list for this weekend. 17:23:22 jwhimpel A big sorry! It's on my todo, and first priority now after F39 is out. 17:23:26 Thanks!! 17:23:39 jwhimpel: same 17:23:42 F39 -> F37. .-) 17:24:01 wow we jumped versions fast 17:24:06 sorry but recovering from Covid took longer than I had hoped for 17:24:26 Let's put this as the first topic next meeting. 17:24:40 covid-- 17:24:45 pboy: agreed 17:25:16 I'm breaking for lunch, tag me if there is something that I can help out with that is docs related. 17:25:19 I'll monitor the mailing list for questions. 17:25:33 I'm planning to work on Ansible/wildfly and on Reviewing installation media. 17:25:47 mowest Have a nice evening 17:26:58 And I'm considering if we should add an OSTree installation alternative to our Default file based install 17:28:12 I'm trying to find out how much work it is, probably starting with a VM image version. 17:28:26 SuSE had made it nicely. 17:28:34 What do you think about it? 17:29:47 no opinion 17:29:53 I really don't have anything on it as a I havent used it 17:30:50 I suppose I myself wouldn't use it. It's my curiosity. 17:31:21 So it's certainly not a hight priority item. 17:33:00 What about the web page revamp effort? 17:33:15 I think, we can't postpone it anymore. 17:33:24 Can anyone warm up to this? 17:33:51 It's not so much about graphics, but about text and a good presentation of Server. 17:35:41 I wouldn't even know where to start 17:35:47 are we talking about https://getfedora.org/fr/server/ ? 17:36:22 eseyman yes, a new version for that. 17:36:48 as an example for the new design and presentation: https://design.penpot.app/#/view/d0c3eb90-430d-11ed-9050-cf2300df1f4f?page-id=d0c3eb91-430d-11ed-9050-cf2300df1f4f§ion=interactions&index=0&share-id=637865d0-43c0-11ed-9050-cf2300df1f4f 17:37:46 For my taste, this is too much marketing and not enough substance. 17:38:13 The new Workstation page is even more marketing 17:38:32 well that's fancy 17:38:46 the coreos page 17:38:59 put politely, I guess I'm not the target audience 17:40:04 me to. :-) 17:40:15 the real question is what is our target audience 17:40:23 see Workstation: first cut was https://design.penpot.app/#/view/d24b8550-780f-11ec-b805-69e39b8fc2b7?page-id=d994e860-780f-11ec-b805-69e39b8fc2b7§ion=interactions&index=0&share-id=7959a5c0-94c1-11ec-bd38-efdb6fa63305 17:40:47 "The leading Linux desktop" hm.... 17:41:07 I can see how one would argue that 17:41:08 without documentation. (I just can't resist) 17:41:31 it shines compared to the coreos one 17:42:12 yes, but for server I would prefer more substantial information and text. 17:42:15 I'm willing to review the getfedora.org/server/ site. Currently the design of our page is very similar to Workstation, I think consistancy in design is important. 17:42:59 mowest +1 ! 17:43:44 it could use more color 17:43:55 mowest I'll put together some information I've collected of the last year. But I need some days. 17:44:01 The mockup you pointed to for CoreOS is very different in design. I'm not a designer, but I can review and propose some different text and make suggestions of for graphics. 17:45:12 eseyman yes that would be my suggestion for graphics enhancements is more color favoring shades of blue since that color seems to be in the Fedora colorwheel. 17:45:16 mowest That would be great! Our designers are good. But maybe, sometimes they get carried away with fancy graphics. 17:45:44 Our role is, I think, to keep an eye on the substance. 17:45:55 and maybe not to get too fancy 17:45:57 I would also look at decreasing the amount of text and focus on a few key features. 17:46:38 That's OK for me. Concentration of the most important items. 17:48:07 I woofed down Christmas work lunch quick, everyone got through the line quicker than I thought, so they were cleaning up when I arrived. But I got back here faster as a result. 17:48:33 very good for us ! 17:49:25 Well, there remains the question or release testing and probably a test week. 17:49:54 Maybe, we postpone it to F39? 17:50:21 Or is there someone to take the hat? 17:51:21 I like the idea of a test week. Where would we report our "bugs"/issues though? I ended up doing some testing but ran into an issue and posted on Fedora Discussion and I got crickets or no responses at all during the F37 beta. 17:51:44 mowest that's one of the issues. 17:52:16 If we had a test week and the appropriate web site, we had a central and dedicated page to report results and issues 17:52:18 I had an issue with pipewire and got crickets in askfedora 17:52:31 I would love to but am commited to too much already 17:53:28 cooltshirtguy askfedora is fine! But for release testing, I think we need something more focused. 17:53:49 agreed 17:54:00 eseyman what a pitty. 17:54:01 I've always seen Ask Fedora as the spot to post user issues, and I thought Fedora Discussion was a quicker connection to the actual Fedora devs, but perhaps I'm mistaken in that view. 17:54:27 mowest you are not, IMHO 17:55:27 mowest, that sounds about right 17:55:37 Well, I think we have a good plan, and a realistic one. 17:56:03 I spoke briefly with Ben Cotton in person at Ohio Linux Fest last week, and he recognized this issue too, but neither of us had a solution to propose. 17:56:11 does other groups have a test page? can we request for us. not sure how the process, just asking questions 17:56:51 *1 for us 17:57:00 cooltshirtguy. Yes, e.g. CoreOS and IoT wait, I look for links 17:57:21 CoreOS. https://testdays.fedoraproject.org/events/131 17:57:29 I was wondering how we get one of those fancy test pages too. 17:57:43 IoT https://testdays.fedoraproject.org/events/132 17:58:31 mowest: this mostly requires giving a test suite to Fedora QA 17:58:45 and letting them roll with it 17:59:00 mowest. We should make a plan and then propose is to adamw. They will help us to set up the page und to write the tests for items, that can to tested automatically 17:59:47 We'll get help with the technical details. but we must provide the substance 18:00:12 And we don't have to have everything complete from the beginning. 18:00:33 We can stafrt with some items and expand with the following releases. 18:01:18 pboy: sorry, just saw the ping. we can always add *more* things to critpath. i always assumed httpd was in there already, but surprisingly, it isn't. it's sort of implicitly required by cockpit and freeipa, though - unless you do a lot of tweaking to run them on nginx instead - so i'd support adding it... 18:02:01 adamw from me no nginx. I'm fine with apache. :-) 18:02:08 thanks for the info! 18:02:19 adamw: can we revisit this down the path? 18:02:28 oh, hmm, i guess cockpit doesn't actually use httpd, it's a web server directly. yeah, sure 18:04:26 I just see, we are running out of time. 18:05:21 I would like to switch to open floor. at least for a short time. 18:06:14 #topic. 4. Open Floor 18:06:33 Anything to discuss here? 18:07:30 I have seen a graphic that shows the Red Hat pipeline as Fedora being first to innovate followed by CentOS Stream branching off of a Fedora version to stablize and roll towards the next Red Hat Enterprise. With that in mind is there a tech that we should be testing now for the benefit of that pipeline down the line? 18:07:58 Something we could work on for F38? 18:08:31 Perhaps a file system change, or a stack for containers... 18:08:58 mowest Yes, that's the traditional role of Fedora, and especially Server. 18:08:59 I want to concentrate on indentity management for the coming weeks 18:09:40 eseyman very good, we have currently a weak point there 18:10:06 mowest that a good topic to discuss not to far in the future. 18:10:16 Is there a link where I could learn more about indentity management? I'm unsure what this is. 18:11:00 I mostly learnt this stuff by doing it 18:11:18 i would think free-ipa has some stuff 18:12:05 it's one of the main features, yes 18:12:43 pboy I would be very interested in this being one of our "5" things for F38 or F39. I would love to trial and test something that helps downstream from Fedora. 18:13:58 mowest I agree! Let's discuss that further. 18:14:14 We are about 15 Mins overdue now. 18:14:33 I think we should close and continue next meeting or on mailing list. 18:14:37 Goodbye thanks pboy for a good meeting. 18:14:40 yes 18:14:56 I summerize our planning on mailing list. 18:15:04 Thanks everybody! 18:15:16 #endmeeting