14:00:09 <randomuser> #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings
14:00:09 <zodbot> Meeting started Mon Aug 19 14:00:09 2013 UTC.  The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:09 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:00:10 <randomuser> #meetingname Fedora Docs
14:00:10 <randomuser> #topic Roll Call
14:00:10 <zodbot> The meeting name has been set to 'fedora_docs'
14:00:14 * Capesteve is here
14:00:32 <randomuser> GDTY, Capesteve
14:00:37 * pbokoc 
14:00:50 <Capesteve> morning randomuser
14:01:22 <randomuser> this is my first day back from vacation, $dayjob will be fun
14:01:32 * Croberts here
14:01:35 <pkovar> same here
14:02:16 * jjmcd 
14:02:31 * threebean is here
14:02:52 <randomuser> welcome, threebean
14:02:59 <threebean> :)
14:05:25 <randomuser> quorum!
14:05:34 <randomuser> #topic Follow up on action items
14:06:00 <randomuser> It looks like lnovich isn't here at the moment to talk about badges
14:06:32 <randomuser> so, on to Changes
14:06:34 <threebean> oh, that's actually why I'm here.  I got an email last night asking about badges for docs contributions.
14:06:42 <threebean> err, sorry, not last night -- last week.
14:06:48 <randomuser> err... badges!
14:06:52 <randomuser> #topic Badges
14:07:14 <randomuser> well, i guess I should find out if you had questions or answers, threebean
14:07:53 <threebean> oh, well, I realize that docs was sorely left out of Fedora Badges and that some people were a little miffed at this.
14:08:04 <threebean> I just wanted to make myself available is people had ideas or things they wanted to do with it.
14:08:17 <threebean> "is people" -> "if people"
14:08:18 * jreznik is here listening for Badges, err, Changes :)
14:08:50 <randomuser> cool, thanks threebean
14:09:30 <randomuser> I would say commits to our repos would be a good metric, but I'm not sure if that talks fedmsg
14:09:37 <randomuser> (fedorahosted)
14:09:50 <threebean> I don't think it does, but we can turn that on easily; it only takes a few minutes.
14:10:45 <threebean> for that I just need someone to point me at the right repos and the right trac instances.
14:10:45 <randomuser> I like the idea of high goals, though; start with 1 commit but have the tiers cover a broad range
14:10:59 <threebean> cool :)
14:11:13 <randomuser> okay, someone will work up a proper ticket for you
14:11:25 <randomuser> or a couple :)
14:11:29 <threebean> +1 :)
14:11:42 <jjmcd> Prolly have something different for publishing
14:11:51 <randomuser> jjmcd, +1
14:11:53 <jjmcd> even tho it is also just a commit
14:12:01 <threebean> also, if anyone has particular ideas for particular badges, you can submit them at https://fedorahosted.org/fedora-badges/ <-- you get a badge for doing so.  ;)
14:12:34 <randomuser> threebean, what badge was issued for the idea of a badge for submitting badge ideas?
14:12:51 <threebean> https://badges.fedoraproject.org/badge/badge-muse-badge-ideas-i
14:13:29 * randomuser needs to have more coffee before attempting humor
14:13:42 <threebean> ha :)
14:13:58 <threebean> had to re-read ;p
14:14:37 <randomuser> threebean, I had to say it, so I would get the next level of meta-badge :)
14:15:09 <randomuser> anyone have badge ideas/questions for threebean before we move on?
14:16:30 <randomuser> okay, on to Changes then - thanks again, threebean
14:16:43 <randomuser> #topic Release Notes / Changes
14:16:56 <threebean> :)
14:17:06 <randomuser> I will probably do a lot of catching up with this process soon
14:17:30 <randomuser> jreznik, do you have any advice for us while you're around?
14:18:04 <randomuser> #link https://fedoraproject.org/wiki/Releases/20/ChangeSet
14:18:22 <randomuser> #info the Changes process for docs means an assigned bug for every change
14:18:48 <jreznik> randomuser: just - please, pickup changes you want to document or if you have better idea how to assign it - I can do it
14:19:09 <randomuser> ack
14:19:29 <randomuser> we need to get moving on this, and I regret not starting the procedural stuff sooner
14:20:12 <jreznik> randomuser: not a problem, I'm delayed with tracker BZs too :(
14:20:15 <randomuser> #info ideally assigned writers will also review other guides for affected content and file bugs as needed
14:21:01 <randomuser> out of curiosity, do you know any mass ticket creation magicks, jreznik
14:21:05 <randomuser> ..?
14:22:10 <jreznik> randomuser: bz? right now playing with it, I can provide my "semi-manual" scripts
14:22:26 <jreznik> a few lines in python
14:22:54 <randomuser> cool, I'll ping you out of band sometime
14:23:14 <jreznik> randomuser: sure, reminder for me - remove my password :D
14:23:28 <randomuser> anyone want to claim a Change ticket now?
14:23:33 <randomuser> jreznik, :)
14:24:43 <randomuser> okay, moving on then
14:24:48 <randomuser> #topic Guide Status
14:25:07 <randomuser> jsmith, ping?
14:25:59 <randomuser> there's an ARM guide out there, but it isn't getting a lot of traction
14:26:32 <randomuser> #info content needed for the ARM getting started guide
14:26:49 <randomuser> Croberts, you've been working on some guide stuff, right?
14:28:13 <Croberts> yes I have
14:28:29 <Croberts> I need to push it to the repo
14:28:50 <randomuser> unpushed changes, even!
14:28:52 <Croberts> I have been working on the bug that petr assigned to me
14:29:21 <Croberts> Yes I have updated the multiboot good more
14:29:29 <randomuser> cool
14:29:31 <randomuser> please push
14:29:35 <Croberts> ok
14:29:40 <randomuser> habitually, even
14:30:07 <Croberts> I pushed the updates for the docs.fp.o page to the draft branch, but its giving an error when looking at the page for some reason
14:30:18 <Croberts> I am not sure why, since I didnt change anything except add some text
14:30:28 <randomuser> looking at the page?
14:30:41 <Croberts> the Welcome.xml page
14:31:00 <randomuser> hrmm
14:31:23 <randomuser> what sort of error, from what application?
14:32:09 <Croberts> when I open the page in chrome/firefox to see the changes it gives me an error that it cant parse line 26, i dont have my laptop on but i think that is the error message
14:32:24 <randomuser> Croberts, okay, we can go over some things sometime
14:32:39 <Croberts> ok
14:33:57 <randomuser> pbokoc, jhradilek - did you happen to follow the thread on the list about upgrading?
14:34:33 <pbokoc> randomuser, I haven't
14:35:49 <randomuser> pbokoc, there's a wiki page that covers upgrading, and mattdm pointed out it was out of date
14:36:08 <pbokoc> right
14:36:20 <randomuser> that's mostly fixed, but it made me wonder if we should for out the upgrading content into another guide
14:36:37 <randomuser> idle thought, maybe, but i thought I'd throw it out there
14:37:45 <pbokoc> I'm not sure what you mean here - put a reference into the IG referring to the wiki page instead of documenting the upgrade process?
14:37:58 <randomuser> ha, no!
14:38:19 <randomuser> i meant something like upgrade-guide.git
14:38:28 <pbokoc> oh right
14:38:32 <randomuser> the wiki page is peripheral
14:40:39 <pbokoc> yeah. Well... separating content is generally good, but I don't really have time to maintain another, separate guide right now...
14:40:39 * randomuser shrugs
14:40:59 <randomuser> like i said, idle thought; we can move on
14:41:15 <randomuser> #topic Outstanding BZ Tickets
14:41:16 <pbokoc> I'll think about it and maybe at some point in the futurure... :)
14:41:29 <randomuser> #link http://tinyurl.com/lbrq84
14:42:13 <randomuser> ciupicri is here about https://bugzilla.redhat.com/show_bug.cgi?id=998327
14:42:46 <randomuser> there's a redirect to a translation that doesn't exist
14:43:21 <randomuser> in the docs.fp.o main page; anyone know if that bit of javascript is publican generated or other?
14:43:57 <pkovar> this is because we have ro instead on docs.fp.o
14:44:06 <pkovar> which is a bug
14:44:26 <randomuser> can you fix it, pkovar ?
14:45:03 <randomuser> i saw the script uses "ro" instead of "ro_RO"
14:45:16 <pkovar> i am afraid there is not an easy fix to this. someone would have to hack the website database, i think :-(
14:45:35 <randomuser> ouch
14:45:49 <randomuser> well, knowing that the logic comes from publican is a start
14:46:36 <pkovar> yeah, the problem is we have pushed "ro" translations instead of "ro_RO" in the past
14:46:54 <pkovar> no idea what exactly needs to be fixed
14:47:18 <randomuser> could be quite a project, then
14:47:20 <pkovar> but i guess migrating to publcian 3 could help here
14:47:24 <randomuser> :)
14:47:54 <pkovar> as we will probably need to republish everything anyway
14:49:23 <pkovar> then again, i have no idea what the current status of p3 migration is
14:49:26 <randomuser> ciupicri, publican is the publishing tool we use, and it also handles the website presentation
14:50:00 <randomuser> the newer version of the tool gives us an updated framework for docs.fp.o and will 'reset' many one-off things like this
14:51:01 <randomuser> so the fix might come as a republishing of all available content, or something more tactical
14:51:17 <Croberts> that is why i did not want to upload the welcome.xml to the master repo and screw the site up
14:52:03 <randomuser> Croberts, it's just best practices, until you're more familiar
14:52:25 <randomuser> the content in master doesn't get served to users; only web.git does
14:53:54 <randomuser> a few minutes left; any other bugs to discuss?
14:55:16 <randomuser> #topic Open Floor Discussion
14:55:38 <Croberts> Well I will upload my changes then to the repo you sent me
14:56:21 <randomuser> Croberts, the method you've been using is good
14:56:34 <Croberts> ok
14:56:47 <randomuser> you made a branch, and committed in that branch
14:57:28 <randomuser> when you have more commits, we [the group] can review and merge to master
14:57:59 <randomuser> as someone pointed out, it is a mission critical pile of copy