17:00:57 #startmeeting fedora-server 17:00:57 Meeting started Wed Mar 31 17:00:57 2021 UTC. 17:00:57 This meeting is logged and archived in a public location. 17:00:57 The chair is pboyHB. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:57 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:57 The meeting name has been set to 'fedora-server' 17:01:04 fedora-meeting-1 looks like it has a meeting conflict :p (I know it's not the Rust SIG meeting :p) 17:01:09 .hello salimma 17:01:10 michel_slm: salimma 'Michel Alexandre Salim' 17:01:17 hi everyone! 17:01:24 .hello abbra 17:01:26 We should give a few minutes for folks to show up 17:01:26 ab: abbra 'None' 17:01:36 .hello2 17:01:37 copperi: copperi 'Jan Kuparinen' 17:01:39 #info please say either .hello2 or .hello (the latter if your nick here is not your fasname) 17:01:57 .hello jwhimpel 17:01:58 jdubby: jwhimpel 'John Himpel' 17:01:59 I’ll post the agenda next 17:02:20 #topic Agenda 17:02:28 .hi 17:02:28 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/JMZY2TI3W6QMKDPNSZ2SRQN5QDW46A4A/ 17:02:28 dcavalca: dcavalca 'Davide Cavalca' 17:02:37 1. PRD Update Section 3: Fedora Server Mission 17:02:42 * nirik is fighting some fires today. ;( ping me if I can help with anything. 17:02:48 2. PRD Update Section 4: Market Opportunity 17:02:57 3. PRD Update Section 6: Server Edition Objectives & 6.1 Additional Obj. 17:03:04 4. New Documentation: menue items# 17:03:12 5. New Documentation: how/when going online 17:03:20 6. New Documentation: landing page (proposal) 17:03:26 7. Open Floor 17:03:34 Any additions? 17:04:25 #topic PRD Update Section 3: Fedora Server Mission 17:04:33 #link https://hackmd.io/@x3mboy/By5OkH71O 17:04:43 I would like to discuss the PRD a maximum of 2/3 of our time and dedicate the remaining time to docs. 17:04:51 The goal is to push both projects forward. 17:04:58 Last meeting we discussed Section 4.1 but didn’t discuss and decide about section 3 (nor section 4.0) 17:05:08 As to further proceeding: The current plan is: We will transfer the results of our discussion into a "one page" version, which we can then finally discuss and decide on 17:05:20 floor is open 17:08:58 Well, from my side, I would like to Change the ordering, first user, second developer 17:10:38 I see no objections ? 17:11:29 #agreed Section 3, change order, first user, second developer 17:11:30 if there's no objection in a meeting, should we just assume the text is OK? rather than waiting for people to actually +1 the text 17:11:40 ah, I see that's what we're doing :) 17:11:57 yeah, fwiw section 3 looks great to me 17:12:08 What about the arguments (not the wording) 17:12:53 So, there is no objection about the argument / the message to bring 17:13:53 We need a native speaker to revise the wording (e.g. that "at short notive term ") 17:14:00 as I said last time, I think the "server of the future" messaging is great and makes it very clear where Server is positioned 17:14:06 so that's a +1 for me 17:14:39 #agreed content of sectoipn 3 17:15:43 the wording is not fixed yet, right, just the message? "at short notice" at the very end seems slightly vague, but I don't really have an objection 17:16:02 we can postpone the revision of the wording until later. This concerns all sections. 17:16:31 #topic PRD Update Section 4: Market Opportunity 17:17:09 Again: what about the argument, the message (not hte wording again) 17:18:57 #agreed Section 4, content and argument. Revision of the wording later 17:19:23 +1 17:19:29 +1 17:19:38 TL;DR targeting early adopters 17:20:15 michel_slm: +1 17:20:41 is #5 missing from the list? 17:20:46 #agreed Adding target early adopters 17:21:40 michel_slm: The inevitable: Can you put a phrase in the comment? 17:21:43 (oh, early adopters are already mentioned in the current text, just saying that seems to be the theme of the section 4 argument) 17:22:20 second paragraph has it 17:22:25 yeah, fwiw that's my read as well (which I think is fine) 17:22:43 Oh yes, I see. (I forgot my own text, tut.tut.tut) 17:23:37 Anything elase, otherwise I switch topic (we are very quick today) 17:24:38 #topic PRD Update Section 6: Server Edition Objectives & 6.1 Additional Obj. 17:25:10 There are no comments yet. Any idea here? 17:25:54 What about the arguments? (It's quite a lot). 17:25:55 in general, they look good, though I added one comment that we lack FreeIPA in the infrastructure part. This should also apply to other sections, for example personas consistenly lack own infrastructure there. 17:26:33 we have many hobbysts and small companies running FreeIPA on Fedora as their infra 17:27:39 yeah, I think adding FreeIPA in the same breath as DNS and DHCP probably makes sense. Esp given it also seems to require some effort to upkeep in the past (with the Java 11 migration) 17:27:56 ab: Is FreeIPA a general objective or rather an important service, comparable with Apache? 17:29:07 most people are not going to run RDE on a server they will ssh in 17:29:11 pboyHB: both. We have been discussing Fedora Server at Flocks in past in terms of it being a primary definition of FreeIPA-based secure infrastructure for enterprise/home deployments 17:29:46 ab: I have you here on my note asking if you could contribute to our doc with FreeIPA (that's not a threat. :-) ) 17:30:18 pboyHB: my primary issue is a lack of time for that (I wish I had some for my sleep too) 17:30:34 * michel_slm wishes he gets more sleep too 17:30:48 ab: welcome in the club. But ok. 17:32:21 We may add a topic like "provide basic services" and add DNS, DHCP, FreeIPA and probably others. 17:32:46 we can start with that, yes 17:33:09 right now the changes in the right column look more like notes than the final text 17:33:25 #agreed. Add topic about basic services (DNS, DHCP, FreeIPA and others) 17:34:12 OK, any other missing argument or message? 17:34:28 pboyHB: a working FreeIPA deployment is a blocker criteria for Fedora Server releases, btw. 17:35:26 ab: OK, we may check if it still is. 17:35:40 ab: do you have a link to the blocker criteria? might be worth having it referenced in the logs 17:36:39 https://fedoraproject.org/wiki/Basic_Release_Criteria#FreeIPA_server_requirements 17:37:44 it needs some uplifting because we also need to include replica operation into that as we test for it in OpenQA already but that's extension of the existing requirement 17:38:24 there are more criteria about Server Edition, btw. 17:39:38 https://fedoraproject.org/wiki/Basic_Release_Criteria#Server_Edition_requirements 17:39:38 The page it rather recent (Jan. 2021) so it can't actually be obsolete. 17:39:50 here's all the server requirements it seems, including FreeIPA 17:40:19 ah, it's just the section immediately surrounding it 17:41:40 yep 17:41:50 I suppose, we should discuss that on one of our next meetings. 17:43:07 Back to PRD. I'll aggree the content, if here are no further ideas. 17:44:09 #agreed content section 6, with addition of "basic services" as discussed. 17:44:24 #topic New Documentation: menue items 17:44:34 #link https://docs.fedoraproject.org/en-US/fedora-server/ 17:44:45 Something missing? / something superfluous? 17:46:47 looks nice after briefly perusing it. Fedora Server Documentation needs to be consistently capitalized in the navigation bar 17:47:35 michel_slm: thanks for the hint. 17:48:23 If no further ideas, I'll agree the navigation items. adn switch topic 17:49:26 #agreed intended navigation items as current preview 17:49:37 #topic New Documentation: how/when going online 17:50:35 We should go online as soon as possible and need a self-sustaining partial content. e.p: landing page, installation virualization Container. 17:50:59 These texts can be completed in 2-4 weeks. 17:51:26 Is that too little? Are we embarrassing ourselves with it? 17:52:59 While it certainly will not be comprehensive, for now let's focus on accurate and complete 17:53:07 I think it looks fine and we can iterate as we go along. maybe... add a pointer to the old docs and mentioned they're being brought over? 17:53:30 (and mention they might not be accurate). if we think we can iterate quickly though, maybe don't bother linking to the wiki 17:53:48 michel_slm: Issue is, there is not much old docs. 17:54:12 do we have upstream documentation we can link to? 17:54:55 ab: as good as nothing. And that is largely outdated 17:55:03 in FreeIPA case we had a chapter in Fedora but then RHEL documentation writers decided to only work in a single place and instead of duplicating effort we direct to RHEL documentation 17:55:24 there was basically zero community contribution for documentation 17:55:33 Ok: we should discuss that in 2 weeks and see, what we have 17:55:43 #topic Open Floor 17:55:53 Just as an info about our recent cloud coop discussion Fedora Cloud had had a meeting yesterday with no of part. > 0 17:56:07 And we can feel honored: As Dusty put it: „the server WG has approached us again about possible collaboration/merging. There seems to be more interest this time.“ 17:56:23 more interest from their side? nice 17:57:09 michel_slm: I supose it is meant the other way around. https://meetbot.fedoraproject.org/fedora-meeting-1/2021-03-30/fedora_cloud_meeting.2021-03-30-16.00.log.html 17:57:53 Nevertheless, I think it is a positive trend 17:58:09 yeah! 17:58:10 #info Ben Cotton compiled a change set listing all changes F33 > F34. Please check 17:58:19 #link https://fedoraproject.org/wiki/Releases/34/ChangeSet 17:58:23 I thought we're always interested, we just couldn't reach them previously :) 17:58:31 At a first glance I didn’t detect potential issius for existing Fedora server instances, beside oomd as already discussed. 17:58:39 What about Installation issue with nextcloud, any progress? 17:59:29 haven't checked. also relevant for server: btrfs compression, zram, and... huh, Stratis 17:59:31 'deprecate nscd' is one of those that might be relevant to the server 17:59:42 not sure if anyone deploys Fedora Server with stratis+xfs but that's a possibility 17:59:42 postgresql bump 17:59:51 bind 9.16 18:00:03 O.o 18:00:09 https://bugzilla.redhat.com/show_bug.cgi?id=1941014 18:00:13 I guess I have the timezone wrong for this 18:00:19 Eighth_Doctor: yes. ;) 18:00:20 looks like nextcloud is being fixed. it's a leftover unused dependency 18:00:37 Conan Kudo: daylight saving must die 18:01:03 Well, time is up. I forgot to ask about a chair next week. Who is willing? 18:01:54 I can 18:02:29 #agreed next chair michel_slm 18:02:40 do we keep agenda items in pagure? if not, should we? 18:02:54 Thanks pboyHB 18:03:11 Currently we don't, but use mailing list. Pagure is a good idea. 18:03:21 michel: it has been on wiki at some point 18:03:43 but could be better on Pagure 18:03:55 ah. let me see if I have the right permissions for Pagure, and if I can't get that sorted I can keep using the mailing list for next week 18:04:13 off to get food and then fix a server issue (ha). thanks pboyHB 18:04:15 michel: I'll add you 18:04:21 copperi: +1 18:04:22 copperi: thanks! 18:04:40 #endmeeting