18:32:05 <bcotton> #startmeeting docs
18:32:05 <zodbot> Meeting started Wed Apr 20 18:32:05 2022 UTC.
18:32:05 <zodbot> This meeting is logged and archived in a public location.
18:32:05 <zodbot> The chair is bcotton. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
18:32:05 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:32:05 <zodbot> The meeting name has been set to 'docs'
18:32:06 <bcotton> #topic Roll call
18:32:14 * pboy 
18:32:28 <pboy> .hello2
18:32:29 <zodbot> pboy: pboy 'Peter Boy' <pboy@uni-bremen.de>
18:32:31 <darknao> .hi
18:32:32 <zodbot> darknao: darknao 'Francois Andrieu' <darknao@drkn.ninja>
18:35:40 <AdvikaSingh[m]> Hi
18:35:41 <bcotton> #chair pboy darknao
18:35:41 <zodbot> Current chairs: bcotton darknao pboy
18:35:45 <bcotton> welcome Advika Singh
18:35:52 <AnushkaJain[m]> h
18:35:53 <AnushkaJain[m]> Hi!
18:36:08 <bcotton> hi Anushka Jain
18:36:18 <bcotton> alrighty, let's get started
18:36:25 <bcotton> #topic Agenda
18:36:25 <bcotton> #info Announcements
18:36:25 <bcotton> #info Review action items
18:36:31 <bcotton> #info GitLab followup
18:36:31 <bcotton> #info Content plan proof of concept
18:36:31 <bcotton> #info Backlog grooming
18:36:31 <bcotton> #info Open floor
18:37:12 <bcotton> one quick process note: my daughter has a school thing, so i'll need to drop at about :20 past the hour, so we can either end there or someone else can take over and #endmeeting when we're done :-)
18:37:19 <bcotton> #topic Announcements
18:37:19 <bcotton> #info F36 Final release is targeted for 3 May
18:37:19 <bcotton> #info Outreachy applications must be submitted by 1600 UTC Friday
18:37:25 <bcotton> #help Contribute to the F36 release notes: https://discussion.fedoraproject.org/t/how-to-write-fedora-release-notes/38311
18:37:32 <bcotton> #info We're using the docs-fp-o repo to track meta-work
18:37:32 <bcotton> #link https://pagure.io/fedora-docs/docs-fp-o/issues
18:37:39 <bcotton> anything else announcement-shaped that I missed?
18:38:23 <bcotton> #topic Previous action items
18:38:34 <bcotton> #info bcotton and darknao to write a post about the /latest/ URL for the Community Blog
18:38:34 <bcotton> #info scope expanded, but a draft is written
18:38:34 <bcotton> #link https://discussion.fedoraproject.org/t/docs-update-article-for-fedora-magazine/38463
18:38:55 <pboy> nice text
18:39:15 <bcotton> i posted this thread about 15-20 minutes ago. we don't need to discuss it now, but if anyone has comments or suggestions, please add to the thread
18:39:19 <bcotton> thanks, pboy!
18:39:26 <bcotton> #info darknao to deploy search to prod
18:39:30 <bcotton> #info this is done!
18:39:34 <bcotton> #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:45 <darknao> I read it too, it's great :)
18:40:32 <pboy> Regarding fedora-web: I just did it for server (#3) and do it for docs after the meeting
18:40:49 <pboy> Time is always in short supply
18:41:15 <bcotton> great, thanks. i definitely understand time being in short supply
18:41:40 <AnushkaJain[m]> I read it just now, sounds like a plan:)
18:41:54 <AdvikaSingh[m]> I read it too, looks good!
18:42:55 <AnushkaJain[m]> Also, I had never seen HackMD before- this site looks so clean!
18:43:09 <AnushkaJain[m]> Could be an inspiration for the docs website xD
18:43:11 <bcotton> #topic GitLab followup
18:43:11 <bcotton> #link https://discussion.fedoraproject.org/t/gitlab-migration-plan/38092
18:43:33 <bcotton> i left this on the agenda as a status check. any blockers or help needed, darknao?
18:44:46 <darknao> the contributors guide has been fully migrated to gitlab now, both on stg and prod
18:45:18 <darknao> everything works just fine, including the translation
18:45:37 <bcotton> #info Contributors guide moved to GitLab in stage and production
18:45:38 <darknao> so we just need to pick the next repository to move
18:45:42 <bcotton> did we remove the old repo from pagure?
18:46:19 <darknao> it's not removed, but i've added a note on the main page with a link to the new repository
18:46:46 <bcotton> cool
18:46:53 <pboy> But we should remove some very old repos, e.g. server. That's missleading
18:48:02 <pboy> I mean, server in docs. :-)
18:49:11 <bcotton> yeah, i tend to agree it's probably better to remove old repos than leave them around. i guess there's potentially some value in leaving them for a bit so
18:50:09 <pboy> Yes, those we used until recently. But some are already  unused for several years now.
18:50:20 <bcotton> darknao: is it worth making a list of the repos we'd want to migrate and putting them in the thread (or maybe in issues) so we can figure out which ones need to wait until after the release, which we can do sooner, etc?
18:50:21 <darknao> agree. there is some very old repo around here, like this one https://pagure.io/docs-fp-o
18:51:07 <AnushkaJain[m]> Ben Cotton (he/him): sorry for interrupting, I wanted to know what do we do after our final applications are submitted i.e. after 22nd? do we continue to make contributions?
18:51:26 <darknao> bcotton: yes, that will be very helpful
18:51:27 <bcotton> Anushka Jain: you can, yes
18:52:09 <pboy> AnushkaJain[m]: I would very much appreciate
18:52:34 <AnushkaJain[m]> bcotton: Okk! Thanks, I thought we cannot make changes after we submit the application
18:53:01 <bcotton> Anushka Jain: check the outreachy docs. if you have more questions, let's address them after the meeting
18:53:17 <AnushkaJain[m]> pboy: Thanks:)
18:53:29 <bcotton> okay, i'll create docs-fp-o issues for each of the repos so we can track them. and then docs-fp-o can be the last to go :-)
18:53:49 <bcotton> #action bcotton to create docs-fp-o issues for repos to migrate to GitLab
18:54:00 <bcotton> anything else on gitlab for now?
18:55:03 <bcotton> #topic Content plan Proof of Concept
18:55:03 <bcotton> #link https://discussion.fedoraproject.org/t/a-proof-of-concept-poc-plan-for-new-content-proposal/37941
18:55:10 <bcotton> pboy, the floor is yours
18:55:33 <pboy> Thanks.
18:55:51 <pboy> I've made my ideas available at one of my domains. It was the easiest was for me (allthough I don't like it that way)
18:56:06 <pboy> http://commtalk.org/fedora/rawhide/user-doc-home/
18:56:27 <pboy> There is no public link to it, otherwise.
18:57:04 <pboy> I hope it makes as clear, what my ideas are. And how to implement it.
18:58:43 <bcotton> i like it at first glance. i need to look around a little more
18:59:00 <pboy> Of course.
18:59:17 <bcotton> is the source available? the "edit this page" link didn't work on the one i tried
18:59:26 <pboy> But before I spend more time I would like to get feedback
19:00:12 <pboy> bcotton: no, doesn't work We must get it into our site, somehow. I need darknao for that
19:00:27 <bcotton> okay
19:00:34 <pboy> (And darknao must be able to spend the time)
19:01:04 <darknao> should not be a problem, we can use the staging environment for that
19:01:22 <bcotton> that's one thing i'd like to look at, so we know what it will look like on the back end
19:02:21 <pboy> It will look a bit different. My local repo is not up-to-date with the latest ui.
19:03:38 <pboy> Maybe we'll leave it there for a few days and hope for feedback.
19:03:46 <pboy> And in parallel we're working on bringing it to Fedora backend.
19:04:01 <bcotton> sounds good
19:04:02 <pboy> And enable me to update it on our backend.
19:04:48 <bcotton> what i'm mostly interested in is how the different pieces are laid out so we can reduce duplicate content between places where, e.g. Workstation and Server are the same
19:05:13 <pboy> Workstation and server are not the same.
19:05:32 <pboy> different install procedure, differen file system and partiioning, etc
19:06:03 <bcotton> okay, fine
19:06:16 <bcotton> but Workstation and Silverblue will have some overlap
19:06:24 <pboy> The idea is: to provide the editions the opportunity, to link to or to link in from the anaconda reference.
19:06:44 <pboy> Workstation is file based, Silverblue image based (no anaconda at all)
19:06:56 <bcotton> that's not the point
19:07:04 <bcotton> fine, Workstation and KDE Plasma
19:07:10 <bcotton> or things that aren't the install guide
19:07:26 <bcotton> e.g. dnf works the same on all of the non-ostree variants
19:07:46 <pboy> yes, the idea is to have a comon docu for comon topics.
19:08:08 <pboy> e.g. wayland is for workstation, silverblue, etc
19:08:21 <pboy> or network manager, all variants use it.
19:08:49 <pboy> The new box could be "Fedora Tools"
19:09:23 <pboy> And we should provide _partials, so you can link to the text or use the _partials
19:09:34 <bcotton> right
19:09:48 <pboy> And we just need to update the _partials and anything is uptodate.
19:10:30 <pboy> We have it already that way with anaconda graphical
19:11:16 <bcotton> great!
19:12:11 <bcotton> anything else on this topic?
19:13:49 <bcotton> #topic Backlog grooming
19:13:49 <bcotton> #link https://pagure.io/fedora-docs/quick-docs/issues?status=Open&order_key=last_updated&order=asc
19:14:14 <bcotton> i thought we'd take a look at the quick-docs issues this time, since we did docs-fp-o the last few times we did this
19:14:31 <pboy> OK
19:14:33 <darknao> ok for me
19:14:49 <bcotton> #11 seems like we can close it as it doesn't really apply
19:15:14 <pboy> yeah, I don't understand it.
19:15:31 <pboy> Maybe it's old day, beta area.
19:15:56 <pboy> Do we have stg for quick docs?
19:16:32 <darknao> i don't think so, there is only one branch in this repo
19:16:59 <bcotton> they're published on stg, i think, just from the same branch as prod
19:17:15 <pboy> But the addres https://docs.stg.fedoraproject.org/en-US/quick-docs/ works
19:17:25 <bcotton> (which is another topic. it'd be nice to have a stg for tooling changes and a stg for content changes, but that's a matter for another time)
19:18:11 <pboy> And for quick doc we need a kind of "editor in chief" (I don't now the english term für Lector)
19:18:37 <bcotton> agreed, that would be helpful
19:18:47 <pboy> someone who oversees the content and looks for outdated and/or wrong content
19:18:57 <bcotton> nobody "owns" it now, so i think a lot of stuff goes un-addressed
19:19:13 <pboy> not good
19:19:32 <pboy> who has commit permission?
19:19:44 <bcotton> if we were having Flock this year, i'd want to a hackfest where we all sit in the same room and just tackle a bunch of these small issues
19:20:22 <bcotton> pboy https://pagure.io/group/fedora-docs and https://pagure.io/group/quick-docs-committers
19:21:08 <pboy> OK. we should select one as responsible.  :-)
19:21:28 <pboy> I think of bcotton ?  :-)
19:21:55 <bcotton> never heard of him
19:22:31 <pboy> Ona first look  many of them are not active anymore?
19:22:33 <bcotton> i can take it for now. i probably won't keep it long-term, but we can at least make some progress
19:23:23 <pboy> Yes, can't do everything. The day has 24 hours, it's hard to make longer
19:23:28 <bcotton> okay, i need to run. pboy or darknao , do you want to take the last few minutes?
19:24:04 <darknao> we can switch to open floor for the last 10 minutes
19:24:17 <pboy> +1
19:24:23 <bcotton> #topic Open floor
19:24:29 <bcotton> okay, don't volunteer me for anything else while i'm gone :-)
19:24:44 <darknao> sure :p
19:26:19 <pboy> darknao: Do you know, do I have permission to comment on the tickets? I think so?
19:26:28 <pboy> in quick doc
19:26:44 <darknao> anyone can comment on tickets
19:26:53 <pboy> OK.
19:27:30 <pboy> and what about creating and assigning tags?
19:28:03 <darknao> only repository admins can create tags I think, since it's in the settings area
19:28:19 <pboy> OK.
19:28:20 <AnushkaJain[m]> Hi!! I'd like some help on this- https://discussion.fedoraproject.org/t/classification-of-all-the-content-on-the-docs-website-contribute-if-you-can/38398/6
19:28:55 <pboy> I've a look on it. go on
19:29:08 <darknao> and for assigning tags, just look if you have the edit button showing on the right of "metadata"
19:29:17 <darknao> if you do, then you can assign tags
19:29:42 <AnushkaJain[m]> AnushkaJain[m]: Other than what pboy has already helped with! I want to know if there's a simpler way of classifying them
19:29:50 <pboy> Oh yes, the edit button works fo me
19:31:02 <pboy> AnushkaJain[m]: I think, the problem is to determine a useful category system.
19:31:26 <AnushkaJain[m]> That's true
19:31:28 <darknao> ok we are out of time, but we can continue on the regular channel
19:31:36 <pboy> And the details of the use case: what should be the usage
19:31:59 <darknao> Thanks everyone!
19:32:00 <AnushkaJain[m]> I'm stuck there, but I want to optimize and make sense of all the organic content on the docs
19:32:02 <AdvikaSingh[m]> AnushkaJain[m]: Hey, I am working on a similar issue, even I am trying to classification. Do you want to collaborate? Maybe we can help each other out?
19:32:08 <darknao> #endmeeting