15:31:39 <pbokoc> #startmeeting Docs Project Meeting
15:31:39 <zodbot> Meeting started Wed Apr 11 15:31:39 2018 UTC.  The chair is pbokoc. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:31:39 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:31:39 <zodbot> The meeting name has been set to 'docs_project_meeting'
15:31:56 <pbokoc> #meetingname Fedora Docs
15:31:56 <zodbot> The meeting name has been set to 'fedora_docs'
15:32:03 <pbokoc> #topic Roll Call
15:32:11 <pbokoc> #chair bexelbie
15:32:11 <zodbot> Current chairs: bexelbie pbokoc
15:32:57 <shaunm> hi
15:33:18 <x3mboy> .hello2
15:33:19 <zodbot> x3mboy: x3mboy 'Eduard Lucena' <eduardlucena@gmail.com>
15:34:00 <bexelbie> o/
15:34:02 <bexelbie> .hello
15:34:04 <bexelbie> .hello bex
15:34:04 <zodbot> bexelbie: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
15:34:07 <zodbot> bexelbie: bex 'Brian (bex) Exelbierd' <bexelbie@redhat.com>
15:34:08 <bexelbie> thank you for starting pbokoc
15:34:08 <shaunm> .hello
15:34:09 <zodbot> shaunm: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
15:35:36 <bexelbie> if your fas is the same you can say .hello2
15:35:57 <pbokoc> .hello2
15:35:58 <zodbot> pbokoc: pbokoc 'None' <pbokoc@redhat.com>
15:36:04 <pbokoc> that's right!
15:36:16 <pbokoc> alright, I don't think anyone else is showing up
15:36:30 <pbokoc> #topic Release Notes
15:37:02 <pbokoc> so, I closed the issue that sclark opened asking about branching. There is now a f28 branch, because f28 branched from rawhide as well, so we might as well too
15:37:14 <bexelbie> +1
15:37:25 <pbokoc> #info Please open any merge requests for F28 release notes against branch "f28"
15:37:58 <pbokoc> I also merged outstanding requests that were against master (2 of them)
15:38:27 <pbokoc> and I opened an issue to create a template for "blank" relnotes that we'll use in the future after branching
15:38:42 <pbokoc> and assigned myself to an issue about the README being outdated
15:38:50 <pbokoc> but that's not top priority now, what we really need is
15:39:04 <pbokoc> #info Write release notes! Instructions are in issues
15:39:39 <pbokoc> bexelbie, by the way, you're the relnotes repo owner. I was wondering, if you go to Settings at https://pagure.io/fedora-docs/release-notes/settings
15:40:09 <pbokoc> do you see an option to add a new "issue type"? It's a field you see when creating an issue
15:40:19 * bexelbie goes to look
15:40:57 <bexelbie> pbokoc, do you mean the templates?
15:40:59 <pbokoc> in relnotes there are currently two available types, "default" and "change". I wanted to add more (we could use one for stuff like the "update readme" thing), but I don't think I have the permissions
15:41:29 <pbokoc> bexelbie, I have no idea how the terminology works in pagure. I want a new option in the Type drop-down here: https://pagure.io/fedora-docs/release-notes/new_issue
15:41:35 <bexelbie> pbokoc, you should be able to in the templates dir of the issue repo: ssh://git@pagure.io/tickets/fedora-docs/release-notes.git
15:41:40 <pbokoc> bexelbie, oh wait, yeah, that's a template
15:41:48 <pbokoc> aha!
15:42:03 <pbokoc> oh, that's cool
15:42:23 <bexelbie> :D
15:42:28 <pbokoc> if a bit unfortunately named
15:42:54 <pbokoc> alright, in that case we probably don't need a new type since there's no point in templating "housekeeping" issues, but we could use some new tags. I'll think about what exactly
15:43:18 <pbokoc> the point is, looking at the current issue list, it's a mess, f28+f29 changes and housekeeping. We're going to need to filter that
15:43:35 <pbokoc> anyway, that's it from me for release notes - anyone have anything else?
15:44:57 <x3mlinux> Yes
15:45:08 <bexelbie> me too
15:45:08 <x3mlinux> On release notes no, sorry
15:45:14 <bexelbie> but not on release notes for me
15:45:27 <pbokoc> alright, what next - bexelbie, do you want to talk about Antora?
15:45:40 <bexelbie> yes
15:45:43 <pbokoc> #topic New publishing toolchain
15:45:44 <bexelbie> but I can go after x3mlinux
15:45:48 <bexelbie> or now ..
15:45:53 <bexelbie> So I've been playing with Antora
15:45:53 <pbokoc> my bad :D
15:46:03 <bexelbie> x3mlinux, are you ok with waiting?
15:46:25 <x3mlinux> Yes, i am ok
15:46:35 <bexelbie> I've had a lot of help from asamalik and some great conversations with rkratky
15:46:43 <bexelbie> I have a 50% PoC
15:46:45 <bexelbie> https://bex.fedorapeople.org/antora-test/fedora/rawhide/install-guide/index.html
15:46:46 <bexelbie> #link https://bex.fedorapeople.org/antora-test/fedora/rawhide/install-guide/index.html
15:46:53 <bexelbie> Note: The menus don't work and the UI is wonky
15:46:58 <bexelbie> that is why it is 50% :P
15:47:15 <bexelbie> if you click in the lower left corner you'll get a weird menu that lets go look at the council docs, and some others
15:47:26 <bexelbie> for the install-guide and sysadmin-guide you have multiple versions
15:47:40 <bexelbie> I am working on getting some proper designer assistance
15:47:54 <bexelbie> my next goals are: 1) Finish up the PoC UI
15:48:15 <bexelbie> 2) See if we can figure out something better for the Quick Docs (there have been some tweets about this with Antora/MojaveLinux)
15:48:21 <bexelbie> 3) Get translations working
15:48:24 <bexelbie> those are not in priority order
15:48:36 <bexelbie> I am continuing to try to work on this during my Fridays
15:49:00 <bexelbie> and the door remains open, virtual or otherwise.  There isn't much in the way of directed tasks unfortunately so you need to show up wiht an agenda or the willingness to hack around
15:49:05 <pbokoc> bexelbie, is there a way for me to look at the backend? I'm assuming it has an interface for managing modules/projects and publishing instead of having to do everything on a command line
15:49:14 <x3mlinux> What kind of help do you need here?
15:49:48 <bexelbie> pbokoc, it is pushed to the my forks of the docs repos in the antora_* branches
15:49:59 <bexelbie> also I can walk through it at the beginning of Friday -- that has become a pattern too :)
15:50:23 <bexelbie> x3mlinux, mostly people who want to figure out how to make it build things, not writing.  So we need folks to explore creating those three priorities.  It is some code and some configuration and testing
15:50:37 <bexelbie> I am trying hard to NOT write new code, and so far have been successful
15:51:26 <x3mlinux> Ok, i can look at it on Fridays too
15:51:38 <pbokoc> hmpf, mornings really don't work for me
15:51:43 <x3mlinux> Also, I will try not to touch code
15:51:46 <x3mlinux> Not yet
15:52:14 <bexelbie> x3mlinux, sounds good
15:52:23 <bexelbie> pbokoc, it's flexible :)
15:52:33 <bexelbie> x3mlinux, if you ahve time friday ping me and I'll turn on a bjn
15:52:40 <bexelbie> same for anyone else not local to me
15:52:46 <pbokoc> yeah alright, we'll figure something out
15:53:39 <bexelbie> that's all I have
15:53:45 <pbokoc> #topic Open Floor
15:53:49 <pbokoc> x3mlinux, now's your time to shine
15:55:32 <x3mlinux> I'm looking for a way to make the PR reviews faster
15:55:47 <x3mlinux> At least for quick-docs
15:56:28 <pbokoc> well, I think what's blocking that is people, e.g. me - and there isn't a way around that unless we want to just merge without reviews
15:56:57 <bexelbie> I am also a blocker there
15:57:05 <bexelbie> I am going to add a PR review session to my friday hacks for this reason
15:57:13 <bexelbie> is weekly reviews enough for now?
15:57:20 * bexelbie assumes he will be successful :D
15:57:26 <pbokoc> I don't want to say too much but it should get better on my end in about 3 months, but right now, work is crazy and I don't have a whole lot of free time outside work either
15:57:50 <x3mlinux> Weekly works for me
15:58:04 <x3mlinux> But maybe we can add more people with rights to merge
15:59:34 <pbokoc> sure, but who else is there? I don't necessarily have a problem with giving you permissions x3mlinux, but it's still generally a bad idea for one person to review and merge their own commits
15:59:54 <bexelbie> I wonder if sassm would also be good to add
16:00:01 <bexelbie> he can't make meetings but he seems active
16:00:06 <bexelbie> .members docs
16:00:07 <zodbot> bexelbie: Members of docs: aalam adamwill agent86 alick amani ameesters andrmart anross apbrar atmnpatel averi b00blik balajig8 baltazaar bancinco bbbush +bcotton beckerde @bex bouska bradbailey caillon camberwell chrismurphy chuck ciupicri coffeeking couf cprofitt crantila cspicer dale davidz ddomingo delouw diegobz dmaxel dmparker donnie dsilas elf elladeon erivero eslobodo fab fbolton fozz fweimer gadgetwisdom (3 more messages)
16:00:13 <bexelbie> we should probably clean that up
16:00:29 <pbokoc> wow, what a blast from the past
16:00:45 <pbokoc> "b00blik" :D
16:01:07 <pbokoc> also, we're out of time, so why don't we meditate on this in the docs channel
16:01:08 <bexelbie> I'll email the list and see about trimming this back
16:01:14 <bexelbie> we can also look at adding new folks
16:01:18 <bexelbie> +1
16:01:22 <x3mlinux> pbokoc, I'm not asking for permissiond to review my own changes, I agree with you that this doesn't make sense
16:02:02 <pbokoc> x3mlinux, yeah, I understand, but the problem is that we simply don't have many active members, so there isn't really anyone to add to reviewers
16:02:04 <pbokoc> anyway
16:02:04 <x3mlinux> But we are adding more and more PRs and all of them are conflicting because all need to edit the _topic.yaml
16:02:19 <pbokoc> oh yeah, that's gonna be fun to solve
16:02:21 <pbokoc> anyway
16:02:24 <pbokoc> #endmeeting