18:31:49 #startmeeting docs 18:31:49 Meeting started Wed Apr 13 18:31:49 2022 UTC. 18:31:49 This meeting is logged and archived in a public location. 18:31:49 The chair is bcotton. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:31:49 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:31:49 The meeting name has been set to 'docs' 18:31:57 #topic Roll call 18:32:02 who's here today? 18:32:03 .hello shaunm 18:32:04 shaunm[m]: shaunm 'Shaun McCance' 18:32:04 .hello2 18:32:07 pboy: pboy 'Peter Boy' 18:32:14 .hi 18:32:15 darknao: darknao 'Francois Andrieu' 18:33:32 #chair shaunm pboy darknao 18:33:32 Current chairs: bcotton darknao pboy shaunm 18:35:27 okay, let's start! 18:35:41 #topic Agenda 18:35:48 #info Announcements... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/94254ed65a5fc911eb7df72804ce830c7228dc43) 18:35:57 #topic Announcements 18:35:57 #info F36 Final release is targeted for 26 April 18:36:13 note that this is target date #1 now, not the early target date of 19 April 18:36:23 #info We're receiving applicants for our Outreachy proposal. Please welcome them and help them get settled in 18:36:23 #info We're using the docs-fp-o repo to track meta-work 18:36:23 #link https://pagure.io/fedora-docs/docs-fp-o/issues 18:36:31 any other announcements? 18:37:14 #topic Previous action items 18:37:14 #info bcotton to retire the Telegram group 18:37:15 #info this is done! 18:37:23 #info bcotton and darknao to write a post about the /latest/ URL for the Community Blog 18:37:23 this one is on my list still 18:37:33 it's low-priority, but i don't want to forget about it 18:37:43 #info pbokoc to write a “how to do release notes” guide that he’ll post in the forum 18:38:04 has anyone heard from pbokoc lately? 18:38:43 He is listed as online 18:39:27 Oh yeah sorry, I keep forgetting. I'll do that now. 18:40:23 pbokoc++ 18:40:28 #info he'll do it now :-) 18:40:44 okay, on to 18:40:50 #topic GitLab followup 18:40:50 #info darknao to start discussion of GitLab migration plan for follow-up next week 18:40:50 #link https://discussion.fedoraproject.org/t/gitlab-migration-plan/38092 18:42:42 so the contributors-guide has been migrated already 18:42:52 and docs.stg is using the new repo 18:43:06 #info contributors-guide is migrated to gitlab, docs.stg is using the new location 18:43:40 I don't see anything not working, so I'll probably do the same on prod later today or tomorrow 18:45:25 great. anything else on this topic? 18:45:31 I also moved the docs-bundle-ui, and it's deployed on stg too 18:47:28 speaking of the ui-bundle, can we all agree on deploying the search feature on prod anytime soon? 18:47:59 i think the general consensus was that we should go ahead with it. any objections? 18:48:00 yes please! 18:48:08 +1 18:48:27 #agreed the search feature is ready for prod 18:48:33 #action darknao to deploy search to prod 18:48:35 oooh -- search feature! 18:48:57 yes, we meet modern times now :-) 18:49:46 ok will do that in the next days 18:50:07 great 18:50:12 nothing else from me regarding gitlab migration 18:50:20 darknao +1 18:50:44 oh actually, there is one last thing 18:50:59 :-) learnt at apple? 18:51:19 Or Columbo :-) 18:51:47 i already posted about this, but I've implemented a CI on the ui-bundle repo, so the bundle archive is automatically build at each commit 18:52:09 which allow us to get a "stable" url with always the latest version 18:52:23 awesome 18:52:34 so we should update the doc template repository to use that one instead 18:53:00 and we don't need to get asamalik to upload a new zip file every time it changes :-D 18:53:11 that too :) 18:53:37 i was thinking it'd be nice to let folks know somehow...but i'm not sure there's a great way to do that apart from submitting a PR to every repo listed in site.yml 18:53:54 obviously on the server it'd be fine, but people might want it for local previews, too 18:55:16 Do we have to do something special to get it? E.G. server that is on a non-doc repo? 18:56:04 update the site.yml in your repo and you'll get it on local builds. the prod/stg builds will get it automatically as part of the regular build process 18:56:51 So our server repo will get it automatically? 18:57:04 the repo won't. the rendered version will 18:57:21 OK. thanks. I'll try to get it. :-) 18:57:49 each repo will need to update their own site.yml, just like we did for antora 3.0 migration not so long ago 18:58:23 Hm, I remember we got antora 3.0 automatically. I didn't update anything. 18:58:55 Or at least I don't remember 18:59:26 (and not all docs repo got that update btw) 19:00:14 pboy: https://pagure.io/fedora-server/c/295efb4eb504673ef19a5f6467f73a1ee5a07082 19:00:20 is the new version anywhere on pagure or only gitlab? 19:01:07 Hm, I'll look at that. (I mean the pagure commit) 19:01:22 the new ui-bundle? the latest version is only on gitlab 19:01:41 OK. time get my gitlab account up and running. 19:02:45 alrighty, on to the next topic 19:02:46 #topic Visibility on website 19:02:46 #link https://discussion.fedoraproject.org/t/we-urgently-need-better-visibility-of-docs-specifically-on-getfedora-fedora-36/37951 19:04:15 As I said, IoT has the improvement already, how do we get it for server and docs landing page as well? 19:04:58 "someone" can submit pull requests to https://pagure.io/fedora-web/websites with the changes 19:05:51 Well, who has the technical knowwledge to build the PR? 19:06:41 But beforehand, do we agree, that we want the improvement in visability? 19:07:26 i think visibility is good 19:07:38 +1 for visibility 19:08:02 i've done some websites work, so i have the technical knowledge in theory, although mostly i manage to do just enough to not break things :-) 19:08:36 if you're familiar with python and html, changes like we're discussing aren't particularly hard to figure out, once you look around the repo a bit 19:08:59 Hi everyone! I'm Anushka, an Outreachy applicant 19:08:59 Sorry, I got disconnected because I thought we're not invited to the meet- and went for a game of badminton 😅 19:09:20 welcome, Anushka Jain 19:09:43 I can probably help with the website changes, I just need to figure out what exactly needs to be done 19:09:59 Same to me, but I've no idea at all how the pages are build and how to fit something in. 19:10:26 Thankyou! Ben Cotton (he/him): just half an hour ago I had a chat with the design team about the website redesign:) 19:10:48 Hi everyone! I am Advika, I am an Outreachy applicant and a UI/UX designer. I would love to help in the design problems! 19:10:54 darknao: At the IoT getfedora page you see an additional "sub-footer". with links to IoT documentation, mailing list, etc. 19:11:19 pboy: if you want to file issues in that repo, darknao and/or i can work on them if someone else from the websites team don't get to it first 19:11:27 Yeah I just saw that, maybe we can do the same for the other editions 19:12:01 Yes, maybe AnushkaJain[m] can help, too? 19:12:03 welcome, Advika Singh 19:12:35 Thank you Ben Cotton (he/him) 19:12:38 or Advika Singh? 19:12:50 okay, so how about this 19:12:53 pboy: Would love to help! 19:13:20 #action pboy to open issues against fedora-web/websites for docs visibility and put the links in the thread so Docs contributors can help implement 19:13:27 that sound good? 19:13:33 Yep 19:13:54 sound great 19:13:54 this way, it's documented what needs to be done and assignees can be tracked 19:13:55 bcotton: Sounds great! 19:14:01 Well, I can oben an issue, yes. But not create a pull request. 19:14:16 Hi, I am Oluwaseun an outreachy applicant... I'd be happy to help too 19:14:17 we can even tag it as easyfix 19:14:55 OK. I'll start with that later or tomorrow (it's late evening hier in Europe) 19:15:08 pboy: someone from the website team might be able to handle the pr work 19:15:20 Let's hope so. 19:15:54 I think, after discussion with Mo, they've a new interface and a new header for the website, which aims at increasing visibility ( of fedora products, as well as contributions) should we take that into consideration as well 19:15:54 (I was referring to me :p) 19:15:59 excellent 19:16:32 s/contributions/how to contribute/ 19:16:34 anything else on the visibility topic? 19:16:42 The server link and teh docs page linkt, anissue each or for both at the same time? 19:16:53 Oh, my keyboard 19:17:10 pboy: i'd say one each, for clarity 19:17:23 Thanks, Ill do 19:17:50 and for workstation, we might just refer to `/latest` for now until there are Workstation-specific docs 19:18:06 OK, but latest what? 19:18:13 the installation guide? 19:18:46 or the lease page? 19:18:47 pboy: https://docs.fedoraproject.org/en-US/fedora/latest/ 19:19:14 OK, that's the release page. 19:19:38 seems slightly better than dropping them on the docs front page :-) 19:19:48 Indeed, yes 19:20:08 alrighty... 19:20:11 #topic Open floor 19:20:31 anything else for today's meeting or shall we adjourn to our usual channels? 19:20:45 nothing from me at the moment 19:21:57 welcome again to all outreachy applicants o/ 19:22:07 🎉 19:22:11 Thank you so much! 19:22:13 me too! 19:22:23 Ben Cotton (he/him): I have a question 19:22:23 Thank you! 19:22:30 Thank you , I hope to be of great help ! 19:22:32 Anushka Jain: go ahead 19:22:36 it was unfortunately a bit short 19:23:01 not your help! but hte welcome! 19:23:38 Since the design team is working on a revamp, should we think about the docs website as a part of the revamp( which would absolutely fit better) or we can think of docs as a separate entity? 19:24:11 * of docs website as a, * separate entity? Following the same design system i.e. 19:24:26 imo it's a separate entity, but ideally most visitors would come via the revamped website 19:25:01 It's a little confusing to me, since pboy is also referring to the current getfedora website only. 19:25:26 I'm pragmatically referring the the pages as they are now. 19:25:35 yeah, that's about improving what exists now, not what will exist in the undetermined future 19:25:40 Without any structurell idea. 19:25:46 Okkkk! 19:26:02 I can ask this to Mo also once? 19:26:43 I think, the revamp project is a huge work and will time longer the less time 19:26:55 So we need interim solutions. 19:27:02 Even though a change in the current website would be of help to the users as well- I see you're talking about spontaneous changes 19:27:26 I'm, yes 19:27:48 Got it! You'd need some design mockups for that? 19:27:55 I could help there 19:28:38 For the modifications we just discussed, let's see, what the outcome of the issue is. 19:28:56 Sure. 19:29:32 pboy: By interim solutions, you mean minor design changes that could increase feasibility and usability? 19:29:35 But we may want do do some more modifications, and then a mockup would be nice. But that depends on some ongoing content work. 19:30:04 AdvikaSingh[m]: yes! 19:31:44 pboy: That seems interesting work, would love to contribute to that. 19:32:15 Thanks, I would appreciate (and I think all of us). 19:34:04 Got it, I've no more questions! 19:36:42 OK, thanks everyone! 19:37:13 #endmeeting