14:10:35 <Capesteve> #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings
14:10:35 <zodbot> Meeting started Mon Jul 16 14:10:35 2012 UTC.  The chair is Capesteve. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:10:35 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:10:45 <Capesteve> #meetingname Fedora Docs
14:10:45 <zodbot> The meeting name has been set to 'fedora_docs'
14:10:52 <Capesteve> #topic Roll Call
14:10:56 <Capesteve> me
14:10:59 * randomuser cheers
14:11:49 <Capesteve> As bcotten is not here, lets do what we can
14:13:29 <Capesteve> #topic Follow up on last week's action items
14:13:47 <Capesteve> Is sparks here?
14:13:59 <Capesteve> Sparks: ?
14:15:07 <Capesteve> I see in: http://meetbot.fedoraproject.org/fedora-meeting/2012-07-09/fedora_docs.2012-07-09-14.00.txt there was talk of the man page website
14:15:56 <Capesteve> ianweller: are you around?
14:18:12 <Capesteve> As the people from last weeks action items are not around I propose to close this section and move onto to the next topic
14:18:29 * jhradilek agrees.
14:19:20 <Capesteve> #topic guide status
14:20:00 <Capesteve> I will make an update to NetworkManger chapter this week. To fix the static routes section
14:20:46 <lnovich> I am working on the Virtualization Administration Guide - hope to have the whole guide out by Aug 1
14:22:27 <Capesteve> lnovich: ask for proof readers if you need to
14:23:17 <lnovich> the first draft will be hopefully ready by Aug 1, with other fixes and changes to follow...but who would like to read it?
14:23:19 <Capesteve> anybody else need help or think something needs doing in the guides?
14:24:30 <randomuser> my fileserver lit on fire; i can't work on any guides for a bit
14:25:03 <Capesteve> oh dear me
14:25:05 * jjmcd sorry for being late.  Recovering from hardware prob on main server
14:25:17 <jjmcd> Looks like a bad day for hardware
14:25:37 <Capesteve> jjmcd: we are in open floor discussion
14:25:46 <Capesteve> (04:23:18 PM) Capesteve: anybody else need help or think something needs doing in the guides?
14:25:56 <lnovich> I do have some questions
14:26:08 <Capesteve> lnovich: good
14:28:01 <Capesteve> lnovich: the drumroll is reaching a cresendo
14:29:39 <lnovich> ok most important as I take this present RHEL guide and make it ready to become a Fedora doc, are there any experts that I can ask specific questions to outside of Red Hat?
14:30:26 <Capesteve> lnovich: questions about the process of publishing or about the material?
14:30:34 <lnovich> no about the material
14:30:57 <lnovich> where some things may apply to RHEL that don't to Fedora or visa versa
14:31:17 <randomuser> are there non-redhat upstream contributors to the subject?
14:31:30 <lnovich> git and publican i understand
14:31:34 <Capesteve> lnovich: we think most of the visualization technical staff are in your area
14:31:50 <lnovich> the RH developers are all in my office
14:32:05 <lnovich> I would love to get some community attention though
14:33:32 <Capesteve> I suggest ping in one of the Brno lists with a specific question if you cannot find a answer in your local office lists
14:35:27 <Capesteve> Any other questions before we close?
14:35:56 <randomuser> i have a bz related question , when we get to the topic
14:36:09 <lnovich> ok im done ...you can move on
14:36:25 <Capesteve> #topic Outstanding BZ Tickets
14:36:41 <Capesteve> randomuser: please?
14:36:55 <randomuser> specifically https://bugzilla.redhat.com/show_bug.cgi?id=808103
14:37:48 <randomuser> the reporter is requesting a bugzilla link on the bottom of every page of every doc; we currently have an introductory section with a link
14:38:38 <Capesteve> sounds like a good idea, we could test it on our "own" pages
14:38:43 <randomuser> this was discussed at a previous meeting, http://meetbot.fedoraproject.org/fedora-meeting/2011-11-28/fedora_docs.2011-11-28-14.01.log.html - and the consensus was that it was unprofessional and overkill
14:38:51 <Capesteve> oh
14:39:22 <Capesteve> maybe a link to "How to fill in an ticket" page?
14:39:41 <lnovich> that can be part of the front matter content, no?
14:39:54 <lnovich> on every page is definately overkill
14:40:18 <randomuser> I think it's overkill
14:41:10 <lnovich> and if we over emphasize that there is a way to file a bug report the user will begin to believe that the software is too buggy to try
14:41:14 <randomuser> My question is, do we still have consensus, or do we need to put this on the agenda
14:42:05 <Capesteve> here: http://fedoraproject.org/wiki/FAQ#How_do_I_configure_network_connections.3F_How_does_Fedora_support_wireless_connections.3F
14:42:05 <Capesteve> it says:   Where can I report bugs or request features for software packages existing in Fedora?  Refer to the BugsAndFeatureRequests page for guidance on this.
14:42:23 <Capesteve> see: http://fedoraproject.org/wiki/BugsAndFeatureRequests
14:43:54 <Capesteve> and lots of links here: http://fedoraproject.org/en/get-help
14:44:55 <randomuser> Capesteve, so your opinion is that our users have enough guidance towards bugzilla without the confidence-undermining link at the bottom of every page
14:44:56 <randomuser> ?
14:45:44 <Capesteve> I think my opinion is that there is a low barrier to getting help of some sort
14:47:06 <randomuser> that really doesn't address the bug, however
14:47:31 <Capesteve> and I see "Help" on the RHS of the page
14:47:41 <Capesteve> just looking around
14:48:03 <randomuser> RHS??
14:48:16 <Capesteve> I think we have more important things todo
14:48:28 <Capesteve> RHS = Right Hand Side
14:48:31 <Capesteve> of the page
14:48:46 <Capesteve> e.g. http://fedoraproject.org/wiki/DocsProject
14:49:12 <randomuser> that's on the left here, and it is a wiki page
14:49:32 <randomuser> the bug reporter is asking for a direct link to a bz form at the bottom of every guide page
14:50:04 <randomuser> I brought it up to see if we had enough consensus to close the bug; perhaps we should table it for further discussion?
14:50:40 <Capesteve> I will vote to close it as its not worthwhile
14:52:35 <Capesteve> but its only "per guide", so could be done ...{checking with jhradelik}
14:53:37 <randomuser> i didn't think of that; i had envisioned it as a potential change to the overall guide template
14:53:51 <Capesteve> This needs to go into Publican brand
14:54:12 <Capesteve> sorry, I was thinking of the web pages themselves
14:54:40 <Capesteve> lets postpone to next week to allow us time to experiment
14:55:15 <Capesteve> we can take a vote then
14:55:27 <randomuser> don't put too much time into it, i don't think anyone wants it besides the reporter
14:55:30 <randomuser> :)
14:55:33 <Capesteve> OK
14:55:55 <Capesteve> lets close?
14:56:11 <randomuser> that's all I have
14:57:02 <Capesteve> thank you to all
14:57:07 <Capesteve> #topic closed meeting
14:57:21 <Capesteve> phew
15:00:01 <Capesteve> #endmeeting