16:01:34 #startmeeting fpc 16:01:34 Meeting started Thu Sep 20 16:01:34 2018 UTC. 16:01:34 This meeting is logged and archived in a public location. 16:01:34 The chair is geppetto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:34 The meeting name has been set to 'fpc' 16:01:42 #meetingname fpc 16:01:42 The meeting name has been set to 'fpc' 16:01:42 #topic Roll Call 16:01:49 hi 16:02:34 #chair redit 16:02:34 Current chairs: geppetto redit 16:02:34 #chair redi 16:02:34 Current chairs: geppetto redi redit 16:06:40 * limburgher is here 16:07:01 #chair limburgher 16:07:01 Current chairs: geppetto limburgher redi redit 16:07:06 .hello bex 16:07:07 bexelbie: bex 'Brian (bex) Exelbierd' 16:08:35 #unchair redit 16:08:35 Current chairs: geppetto limburgher redi 16:09:59 Hey, folks. 16:10:03 Busy day here in the office. 16:10:04 #chair tibbs 16:10:04 Current chairs: geppetto limburgher redi tibbs 16:10:15 tibbs: no problem … probably no meeting 16:10:21 no new tickets anyway 16:10:36 #topic Open Floor 16:11:03 Anything anyone wants to talk about? 16:11:33 Yes, I wonder if there is a way to handle Fedora Java libraries bundled for EPEL in an official way. 16:11:37 I took care of all of the pending writeups and the announcement last week, so that's all done. 16:12:06 sdgathman: That would probably be more up to the EPEL folks. 16:12:13 * bexelbie understand that ignatenkobrain wants to talk about the git version of the packaging guidelines 16:12:23 tibbs: thanks 16:12:58 I mean, I know that having prebuilt jars would still violate loads of requirements. 16:13:23 But bundling is just bundling and is already covered by existing guidelines. 16:13:44 I'll just hope that EPEL8 has new enough libs to build without bundling. 16:13:56 So I'm assuming you're asking about some very java-specific thing and thus I don't know what we could tell you anyway. 16:14:05 .hello2 16:14:08 ignatenkobrain: ignatenkobrain 'Igor Gnatenko' 16:15:01 .hello2 16:15:02 x3mboy: x3mboy 'Eduard Lucena' 16:15:10 Hi guys 16:15:12 I'm fully here 16:15:20 I would like to 16:15:40 tibbs: I learned where to go to pursue it. Thanks. 16:15:50 #chair ignatenkobrain 16:15:50 Current chairs: geppetto ignatenkobrain limburgher redi tibbs 16:16:09 .fpc 727 16:16:11 ignatenkobrain: Issue #727: convert guidelines to git and restructured text - packaging-committee - Pagure - https://pagure.io/packaging-committee/issue/727 16:16:17 I would like to talk about this one 16:18:27 Ok, I think we have 5 now 16:18:31 I worry about fancy new systems like antora 16:18:37 active development now, but what about in 2 years? 16:18:44 but in principle I'm all for the migration 16:19:30 #topic #727 convert guidelines to git and restructured text 16:20:08 ! 16:20:46 so we've made some progress with bexelbie on it 16:20:48 but there are a lot of things to do 16:20:55 and zbyszek was not happy about antora due to some things 16:21:04 so I would like to discuss if we want to continue moving this way as we do now and what is critical for me to fix asap? 16:23:43 wdyt? 16:24:16 I don't care about antora versus, well, anything else really. I won't even complain about asciidoc or whatever it's called instead of RST. I just want to know how I'll be editing things in the future. 16:24:41 I think fundamentally it would be dumb for us to try to break from whatever the rest of the documentation team is doing. 16:24:45 yeah, any of them is ok really. I like sphinx based on the tiny bit I've used it 16:24:49 if we're only 5 does that mean we lose quorum if I leave? :-\ 16:25:26 I don't think we have any real decision to make here. We're just waiting on someone to tell us how this new system is going to work.[ 16:25:30 Consistency is valuable. 16:25:31 hmm 16:26:05 tibbs: ok, so next question is `where do we want to have guidelines to be stored?` 16:26:15 which repo? 16:26:54 I'd assumed that would be dictated by the system, but if it can just live in pagure then why not the packaging-committee pagure instance we already have and use? 16:27:02 Seems rational. 16:27:26 makes sense to me too 16:27:43 gotta step away, sorry. back asap, but might not be before the end of the hour 16:28:46 someone proposed to use packaging-guidelines repo... both have advantages and disadvantages 16:28:55 "someone"? 16:29:03 zbyszek 16:29:18 it is logical because people would search for guidelines in pagure... 16:29:20 Who... has no stake in this. 16:29:36 but it's harder because we would have 2 repos 16:29:50 Well we're not going to maintain two ticketing instances. 16:30:02 then let's put it into packaging-committee 16:30:04 That would just be dumb. 16:30:21 history in git in my repo looks fine? 16:30:44 https://pagure.io/fork/ignatenkobrain/packaging-committee/commits/guidelines 16:30:50 it is possible to put the guidelines below the root dir of the repo if that would help with organization of files 16:30:51 By using asciidoc with Antora, the Pagure instance can be used to store the docs and works like a standard git repo 16:31:21 I realized that git-mediawiki didn't convert all revisions so I'm going to re-do this part. but just wanted to ensure that history looks good 16:31:52 Looks good except of course that it's missing two years of changes. 16:32:08 tibbs: yes, I didn't spot this earlier. my fault 16:32:12 I will redo it today 16:32:38 And sadly we have no access to the old moin history. 16:34:13 bexelbie: I will ping you once I push to packaging-committee repo so that you change settings in your top-level project 16:34:33 ignatenkobrain__, certainly - let me know if you need my help with putting the files belowt he root dir 16:34:42 council-docs does it with several sets of things as a model 16:34:43 It would indeed be good to put the guidelines somewhere below the root if at all possible. 16:34:57 bexelbie: if you could describe me this in tg, would be awesome 16:35:15 mkdir foo; put all the stuff in foo :P 16:35:35 build.sh, preview.sh, and site.yml should also be there 16:35:47 * ignatenkobrain__ shrugs 16:36:12 bexelbie: I have better than those .sh, I have makefile which doesn't run `sudo docker` but rather just `podman` :P 16:36:15 And I'd like to know at some point how I can preview this stuff locally. 16:36:37 tibbs, ./build.sh && ./preview.sh 16:36:48 tibbs: basically run `make && make serve` and open localhost:8000 16:42:23 Ok, anything else? 16:42:35 We have a timeline for a finish line? 16:42:49 just to recap: I'm going to push updated version with all updates from wiki tonight 16:42:57 and then we will slowly fix all remaining issues 16:43:08 so until monday docs.fp.o should be more or less usable 16:44:18 But the bottom line is that we should not be touching the wiki at this point. 16:44:57 yes, let's do everything in git since tonight 16:45:02 and make wiki read-only 16:45:16 then once we are comfortable with docs, we will do redirects from wiki 16:46:25 #action Nobody should touch the wiki, at this point. 16:46:41 Ok 16:51:12 #endmeeting