15:12:24 #startmeeting Fedora Docs Website Status Meeting 15:12:24 Meeting started Mon Jul 28 15:12:24 2014 UTC. The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:12:24 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:12:52 let's start with a... status update? 15:12:53 * rkratky closing windows to keep out the storm 15:14:03 ok, i'm here 15:15:55 so, we have the vanilla site up and running on a VM 15:16:06 #info we have the vanilla site up and running on a VM 15:16:39 #info the VM is ansible managed and will automatically pull in any docs tagged into the el6-docs koji tag 15:17:24 #info rkratky and yruseva have been working on customizing the front end and landing page 15:17:33 good so far? 15:17:45 i guess 15:18:30 er 15:18:53 so, my update is I haven't done much :) 15:18:59 sorry, I've been covered with work 15:19:07 but it's alright now 15:19:24 so plan is I draw it and rkratky creates the stylesheet 15:19:24 no worries, life happens :) 15:20:16 is this for the existing html, then? 15:20:21 yruseva, yep, that's the plan, but i'm worried about integrating it on the site itself 15:21:03 randomuser, i haven't really had the time to look at koji, so i'm in no position to fix the html :-( 15:21:23 heh 15:21:36 hm, that confuses me too 15:21:45 i think the html in question would live in publican-fedora 15:21:46 I've only done CSS on static pages.. 15:21:47 the brand 15:22:22 as i said before, i believe i know what's wrong with it (doesn't pull the proper css files), but i've no idea what to do with 15:22:32 Sorry to interrupt your meeting, but is there a page that documents this project so I can read it and catch up on the goals and tech involved? 15:22:33 ...it 15:22:48 bexelbie, somewhat, hang on 15:22:53 randomuser, ty 15:22:57 randomuser, and no rush 15:23:33 bexelbie, https://jfearn.fedorapeople.org/en-US/Publican/4.1/html/Users_Guide/index.html 15:23:52 publican is the tool that builds the html from docbook and constructs the site 15:24:17 randomuser, that's the publican user guide. Is the new website you're working on a publican built website from rpms? 15:24:32 we have a publican "brand" that comes from the publican-fedora and publican-fedora-web packages that provides customizing stuff 15:25:13 bexelbie, yes, publican generates SRPMs which are built in koji; that's all the delivery/publishing mechanism, and that part is mostly worked out 15:25:35 bexelbie, and this is to design the publican built web that takes those srpms and deploys them? 15:26:02 randomuser, rkratky yruseva again, sorry to take over your meeting with basic questions 15:26:11 nope np 15:26:23 if you're going to help, I'm glad to take the time :) 15:26:51 randomuser, I am not making any promises at the moment -- I am just evaluating your direction and my ideas/abilities :) 15:26:57 * bexelbie is not a designer though 15:28:25 bexelbie, also http://fedoraproject.org/wiki/Publishing_a_document_with_Publican#Publishing_using_Koji_.28Using_Publican_.3E.3D_4.29 and http://fedoraproject.org/wiki/Automating_publishing 15:28:45 we've got the deployment sorted out, and now want the front end to be better 15:29:13 so I'll try to make it prettier 15:29:57 #link https://admin.fedoraproject.org/docs-backend/en-US/ 15:30:01 that's how it is mostly stock 15:30:32 #link https://rkratky.fedorapeople.org/docsweb/mockup/en-US/index.html 15:30:55 ^^ this is rkratky and yruseva's improvements so far, correct? 15:32:01 more like rkratky's 15:32:48 * rkratky is battling the elements again, sorry 15:33:48 ok, back again 15:35:04 rkratky, you were saying something about a CSS file ? 15:35:52 randomuser, it took some tweaking to get the website working offline - had to modify the html files. and i'm not sure how to do that in the packages 15:36:15 rkratky, was it a relative paths thing? 15:36:29 * rkratky checks 15:37:10 i have a few sed invocations in my bash_history on the backend 15:37:44 because it deploys with an absolute path for some resources, ie `https://docs.fedoraproject.org/en-US/resource.css 15:38:33 randomuser, i don't think it was, but i'm, not sure now - it's been three weeks. i need to make a diff 15:39:20 okay, we'll table that issue for now 15:39:59 any other problems, besides the CSS path ? 15:41:51 not on my end. i think i got the hang of the css structure now, so i can make it happen when yruseva gives me the graphics 15:42:06 yep 15:42:27 * yruseva promises to deliver something nice..soon 15:43:09 randomuser, what's the schedule for this thing? 15:43:10 rkratky, I'm looking more into the bash_history here, trying to remember... there's some symlinking of CSS from /usr/share/publican too 15:43:44 if that's something that actually needs to be done and not just my fumbling, we can do it in the brand rpm 15:45:05 i'll find out what it was that i actually had to do 15:45:15 okay 15:45:27 let's talk about a schedule 15:48:34 yep, what are we aiming for? 15:48:38 F21 beta release is set for the end of August 15:48:44 how much can we get done by then 15:48:45 ? 15:49:23 keep in mind that whatever you figure out, i'll have to package up 15:50:32 well, for my part, it shouldn't be more than an afternoon's work, so i'm pretty confident 15:50:54 niiice 15:51:33 I'll give myself two weeks, I don't wanna overpromise :) 15:52:05 yruseva, so you're doing some PNGs? 15:52:24 or general mockups? 15:52:30 mockups for now 15:52:57 what about the slideshow? 15:53:01 PNGs are not a problem but the general layout comes first 15:53:31 O.o 15:53:53 I guess I've forgotten, could you remind me what it was about? 15:54:17 there's a slideshow at the top of the landing page that we don't have content for 15:54:50 I didn't figure out how to get content there, but the mockup has somethign 15:55:02 randomuser, i'd worry about that when the rest is done 15:55:36 okay, we can revisit that 15:55:38 yeah, i know how to display content, but it's just a gimmick. i don't think we really need it that much 15:57:00 rkratky, how does it work? would we create images for that, or is it html? 15:57:16 I'm wondering if someone else might be able to work on the content in parallel 15:57:21 randomuser, html (thank god) 15:58:56 i think the question is _what_ to put there. the rest shouldn't be that hard 16:00:22 maybe 4 slides to commonly referenced docs and one to our join page? 16:00:35 but as you said, probably not important right now 16:02:38 can we say a week for yruseva to come up with a mockup, a week for rkratky to style it, a week for me to work out deployment, and a week for testing? 16:02:56 I'm OK with this 16:02:59 that would put us at the last week in august 16:03:00 randomuser, sounds reasonable 16:03:33 great 16:04:03 do we want to meet again about it, at some point? 16:05:46 maybe, the week of 11AUG just to bring me up to speed for my part? 16:08:24 yes, sure 16:09:18 rkratky, yruseva do we want to schedule a time now, or closer to the date? 16:10:00 let's do it later, there might be some pop-up meetings I still don't know about :) 16:10:27 that happens to you too? :P 16:10:34 i'd prefer now. one thing though. i may be out of here from aug-18 till aug-21 16:10:56 heh, ok. just let me know some time in advance 16:11:48 let's say tentatively for around the same time of day as this; sometime after the 11 August docs meeting 16:12:37 ok 16:13:04 #info yruseva will work on mockups during week of 28JUL 16:13:24 #info rkratky will work on CSS to match mockups week of 4 AUG 16:13:43 #info we will meet to review sometime in week of 11AUG 16:13:49 randomuser, it happens sometimes :) 16:13:59 #info randomuser will work on deployment week of 11 AUG 16:14:05 randomuser, ok, sounds good 16:14:30 #info week of 18 AUG will be testing, coordination with infra 16:15:00 #info changeover planned for week of 15 aug 16:15:14 alright, we have a plan, win! 16:15:25 anything else to cover now? 16:15:51 nothing from me. thanks guys. good effort so far :-) 16:17:57 okay, thanks for taking the time for this meeting, rkratky and yruseva 16:18:06 and for working on the site, of course 16:18:20 #endmeeting