18:30:35 #startmeeting docs 18:30:35 Meeting started Wed Apr 27 18:30:35 2022 UTC. 18:30:35 This meeting is logged and archived in a public location. 18:30:35 The chair is bcotton. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:30:35 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:30:35 The meeting name has been set to 'docs' 18:30:40 #topic Roll call 18:30:46 which Doc-tors are in? 18:30:46 .hello shaunm 18:30:47 shaunm[m]: shaunm 'Shaun McCance' 18:30:50 #chair shaunm 18:30:50 Current chairs: bcotton shaunm 18:30:53 .hello2 18:30:53 pboy: pboy 'Peter Boy' 18:30:56 .hi 18:30:57 darknao: darknao 'Francois Andrieu' 18:31:04 #chair pboy darknao 18:31:04 Current chairs: bcotton darknao pboy shaunm 18:31:05 Hello! 18:31:10 welcome everyone! 18:31:33 Hello everyone!👋 18:31:45 .hello copperi 18:31:46 copperi[m]: copperi 'Jan Kuparinen' 18:34:19 * bcotton puts hair fire out long enough to run this meeting :-) 18:34:27 #topic Agenda 18:34:27 #info Announcements 18:34:27 #info Review action items 18:35:07 #info GitLab migration 18:35:07 #info Content plan proof of concept 18:35:07 #infoDocs visibility on Getfedora 18:35:18 #topic Announcements 18:35:18 #info F36 Final release is targeted for 3 May 18:35:30 this....is a bit tenuous at the moment, but i'm still hopeful 18:35:37 (hence the hair being on fire today) 18:35:51 in any case... 18:35:52 #help Contribute to the F36 release notes: https://discussion.fedoraproject.org/t/how-to-write-fedora-release-notes/38311 18:36:19 we have a lot of release notes left to write 18:36:21 #link https://pagure.io/fedora-docs/release-notes/issues?status=Open&milestone=F36 18:36:57 any other announcements? 18:38:59 seeing none... 18:39:00 #topic Previous action items 18:39:00 #info bcotton to create docs-fp-o issues for repos to migrate to GitLab 18:39:00 not done yet :-( 18:39:00 #action bcotton to create docs-fp-o issues for repos to migrate to GitLab 18:39:05 i should have lots of time on Friday to sit down and do this. if it's not done by next week's meeting, i invite everyone to be very disappointed in me 18:39:07 #info pboy to open issues against fedora-web/websites for docs visibility and put the links in the thread so Docs contributors can help implement 18:39:09 this is done, so let's move to the related topic... 18:39:10 #topic Visibility on website 18:39:10 #link https://discussion.fedoraproject.org/t/we-urgently-need-better-visibility-of-docs-specifically-on-getfedora-fedora-36/37951 18:39:14 #link https://pagure.io/fedora-web/websites/issue/242 18:39:14 #link https://pagure.io/fedora-web/websites/issue/243 18:39:48 Darknao did the work, it's great 18:39:51 Aah perhaps , I can help with the visibility? 18:39:58 Whoops 18:40:27 yes, you can see the proposed changes on stg.getfedora.org 18:40:57 I'm very happy with it. 18:41:12 Looks really good! 18:41:55 #link https://stg.getfedora.org 18:42:17 nice 18:42:20 I also added the same banner on the workstation edition 18:42:43 featuring the /latest/ url :p 18:43:12 :-) 18:43:23 I opened a thread on workstation list some days ago about their preference. No reaction at all. No interest? 18:44:02 So I guess, their is at least no objection and we can publish it. 18:45:04 that works for me 18:45:12 pboy: Could you send a link? I must have missed it :( 18:45:35 i'll leave the final decision to Websites & Apps, but IMO this can go live now and not be batched with the release changes 18:45:38 I can do later, I've it not at hand 18:46:05 proposed =action= bcotton makes it published. :-) 18:46:20 i can take care of that 18:46:45 darknao +1 18:46:46 PR is already there, I'll merge it later this week 18:47:06 #action darknao to merge the websites PR that adds Docs visibility 18:47:11 anything else on this topic before we move on? 18:49:09 #topic GitLab followup 18:49:09 #link https://discussion.fedoraproject.org/t/gitlab-migration-plan/38092 18:49:29 well since i haven't created the issues yet, i'm not sure there's much to say here. darknao, do you have anything? 18:49:39 nothing to report 18:50:59 cool! 18:51:15 #topic Content plan Proof of Concept 18:51:15 #link https://discussion.fedoraproject.org/t/a-proof-of-concept-poc-plan-for-new-content-proposal/37941 18:51:22 pboy, the floor is yours 18:51:30 Thanks. 18:51:54 I think, we should discuss it we want to go that way. 18:52:06 Until now, I got no feedback. 18:53:05 -We are missing user doc for Workstation edition 18:53:05 pboy: I found some quick docs that could be a part of the workstation edition 18:53:27 I marked it in the sheet👀 18:53:44 Yes, I hoped we could find something there. 18:54:10 But we should discuss with workstation group, if we want to go that way 18:54:21 True 18:55:31 There's still a lot of those articles I haven't gone through. I had a backlog because of some exams😅 18:55:34 I liked the general approach. I think it would be good to start getting buy in from Workstation 18:56:03 What should they contribute? 18:56:45 if nothing else, some feedback on the concept and a general agreement that this is the way we want to go 18:57:04 and ideally, they'd contribute to the necessary changes 18:57:15 OK. 18:57:27 Probably we ask the editions? 18:58:04 Maybe, we can see your fedora magazin article as a general announcement? 18:58:33 Yeah. I think if we get Server and Workstation, that's a good starting point. IoT will probably be fine with it, but we'll have to help them with the implementation 18:58:46 Ooh, that's a good idea, yeah 18:59:13 And what about editions to be, e.g. cloud. They have no documentation at all, not even snippets 18:59:14 I'd also like to see the KDE SIG join in, as they're our biggest not-an-edition user base 18:59:45 I think, we can't wait for all of them. We should be prepared to help when some of them awake. 19:00:26 Right. I don't want to block on them, but if we can get early momentum from their help, then that'll move us along faster 19:00:49 Agreed. 19:01:00 How to do? 19:01:08 And what to show? 19:01:30 Maybe we could have an office hours session or two after the release. And also join the meetings for the target teams 19:02:02 OK, that's a good idea. 19:02:43 I think we can refer to the magazin article where everyone can find the concept. 19:03:08 pboy: Does providing documentation template help this case? like letting them know what they'd be expected to write on a basic level.. 19:03:42 Yes, as a help offering. 19:03:43 pboy, do you want to schedule the office hours? it'd be best if you were around. i (and others?) can help covering team meetings 19:04:36 Yes, I could do. 19:04:58 #action pboy to schedule office hours for the content plan 19:05:20 #info pboy, bcotton, and anyone else will attend meetings of the target teams to introduce the plan 19:07:41 anything else on this topic? 19:08:47 #topic Open floor 19:09:02 Yes. 19:09:23 I would like to know, what is the current status with the internal program? And how does it continue? 19:09:24 #undo 19:09:24 Removing item from minutes: 19:09:33 #topic Open floor 19:10:17 #info The Outreachy application deadline was last week. Applicants can continue to contribute. Candidate selection is due 4 May 19:10:51 #link https://www.outreachy.org/docs/applicant/#outreachy-schedule 19:10:58 https://pagure.io/design/issue/816#comment-794302- I wanted to discuss a bit about this issue. 19:11:04 Background: I had interesting discussion with AnushkaJain[m] and it would be nice, we could do something with those ideas. 19:11:39 i'll be reaching out privately to our experienced contributors for any feedback they may have on applicants 19:11:58 OK 19:13:59 there's nothing stopping us from moving forward with ideas now, whether or not the candidate is selected (assuming they're willing to work on it without the benefit of the internship stipend, of course) 19:14:40 AnushkaJain[m]: Initially, we chose tips, notes and warnings. As attached below. 19:14:40 But then, after seeing red hat's style guide we decided to drop tips for important 19:15:07 * AnushkaJain[m] uploaded an image: (39KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/ECdvfXnOVGgFcbseYhvQUaWE/658f8102a7b036f5e7d3683fbd6ee6fea6d0688952a25e31b20ee7ae00471b39-Screenshot_from_2022-04-26_15-17-27.png > 19:15:09 * AnushkaJain[m] uploaded an image: (42KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/PnyoygNpMjPOqVibkzVxrZsl/Screenshot%20from%202022-04-27%2014-25-02_20220427235711.png > 19:15:25 Hm. I think Red Hat's style guide is wrong in this case :p 19:15:46 Ohkk. So should we keep tips? 19:16:12 Also, the second warning is what we're thinking to go with.. 19:16:36 not necessarily. i'm not the emperor of docs :-) it's something we can decide collectively 19:16:50 AnushkaJain[m] Your ideas and plannings were much more wide-ranging as those details. :-) 19:16:50 we should consider what our current adminitions are and how to best categorize them 19:17:16 five different types of admonitions are a lot. three is better, i think, we just need to figure out what the buckets are 19:17:37 i like the style, though, particularly for the second warning. it stands out much better 19:17:45 Yes. I even had a thought of dropping it to two- notes and warnings 19:18:24 But, I guess it's upto the authors to tell which ones are required. 19:18:30 that could work, too 19:19:27 Had this thought because we have a repetitive blue colour and no other fedora colour is mild enough to become a part of this style guide 19:20:20 i could see green for tip if we go that route, maybe 19:20:36 I made one 19:20:46 but the more i think about it, the more i like the idea of a notes-and-warnings-only approach 19:20:49 But it's not nice on the eyes 19:21:24 * AnushkaJain[m] uploaded an image: (94KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/CgxZSGxLudsngQSICvlWPmeq/Admonitions-1_20220428005107.png > 19:21:50 hm. yeah. i see that 19:22:08 Looks nice, forwarding 19:23:27 So what's the future of this ticket then😅 19:23:48 Should we have a poll for this? 19:23:59 I had created a colour pallette that complimented the red hat colour schemes , perhaps you could use that? 19:24:13 You could do a poll in Discussion, yeah. 19:24:29 It has simple subtle tones , that i guess would go. 19:24:29 AdvikaSingh[m]: No, I'm using the Fedora colour palette for consistency 😅 19:24:45 once we're decided, i'll add the results to the style guide draft and we'll need to update the style in the antora theme 19:24:48 AnushkaJain[m]: My apologies, it is the fedora colour palette 19:25:20 Ok, I'll create a poll then!😄 19:25:37 I understand consistency is important, but changing the hues could increase branding and help sort this problem too 19:25:52 AdvikaSingh[m]: Yeah, what I mean to say is that we're using the same ui guidelines everywhere. 19:26:27 AnushkaJain[m]: I get that, i am referring to the same thing you are 19:26:35 AdvikaSingh[m]: That'd be a call for the design team I believe 19:27:18 Alrighty, we're near the end of the hour. Anything else for today? 19:27:18 But Máirín told me they're not using pastel/lighter hues anywhere at the moment 19:27:44 My issue is resolved. Thankyou! 19:28:15 Thanks! 19:28:26 Thanks everyone! 19:28:37 #endmeeting