00:01:13 <paulz> #startmeeting
00:01:13 <odl_meetbot> Meeting started Wed Apr  9 00:01:13 2014 UTC.  The chair is paulz. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:01:13 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
00:01:41 <mlemay_> Do you have "updates" in the agenda?
00:02:15 <paulz> Here's what I have on the agenda... some updates sound great!
00:02:21 <paulz> #link https://wiki.opendaylight.org/view/CrossProject:Documentation_Group
00:02:27 <colinmcn_> Colin here
00:02:31 <paulz> Hi Colin
00:02:47 <colinmcn_> Hello Paul
00:02:49 <mlemay_> Hi Colin
00:02:58 <paulz> #topic  Intros for any new folks
00:03:02 <kwatsen> Kent here, but poping in and out
00:03:32 <paulz> Hi Kent, thanks for joining us!
00:03:33 <mlemay_> Hi I'm Mathieu Lemay (Inocybe Technologies)
00:03:44 <mlemay_> nice to meet you
00:04:18 <paulz> Paul Zimmerman (Cisco) here
00:05:13 <paulz> Other folks can chime in when they can, I'll move to the next topic
00:05:19 <mlemay_> ok
00:05:24 <paulz> #topic Actions from last time
00:05:34 <paulz> I had an action: Paul to talk with Ed & Phil about the server for hosting the docs
00:06:08 <paulz> I got Andrew G's name and added Mathieu to the message as he knows best what's going on with the tooling
00:07:03 <paulz> Mathieu, Andrew had some specifics about how he thought the server should be set up. Any issues there?
00:08:10 <mlemay_> I don't know if it's going to work
00:08:15 <mlemay_> but I'll try it first
00:08:21 <mlemay_> I need to give it a shot
00:08:23 <mlemay_> and see
00:08:43 <paulz> For everyone else, here's what Andrew wanted
00:08:44 <paulz> Andrew wanted a format that would work with a maven site-deploy. It's easier for him to put up a special "docs" repo for our project to push into that way and then he can just configure a front end proxy to deal with rewriting requests for docs.opendaylight.org to the nexus backend
00:09:12 <mlemay_> on that I think we could recommend / assist projects publishing their API + JAvasoc
00:09:16 <mlemay_> *Javadoc
00:09:24 <mlemay_> have a standardized template of some sort
00:09:53 <mlemay_> I know Ryan (regXboi) from OpenDOVE actually worked on site deploy versioning
00:10:11 <paulz> That's definitely an imporant part of the doc set, so that would be good.
00:10:35 <paulz> There are more parts, though... the programmer's guides and config, etc... that seems more challenging for versioning.
00:11:02 <mlemay_> (wonderful.. http://www.rackspace.com/sitemap404.php?url=/writers-guide/content/ch_preface.html%20site:docs.rackspace.com) is now 404 (was the plugin docs)
00:11:26 <mlemay_> correct
00:13:11 <paulz> So Mathieu, can I give you an action to see if Andrew's requirements meet our workflow requirements?
00:14:34 <mlemay_> yes
00:14:35 <mlemay_> sure
00:14:44 <mlemay_> I'll give it a shot with Andrew
00:15:14 <paulz> #action Mathieu to verify Andrew's server requirements work with ODL doc toolchain
00:15:20 <paulz> Cool! Thanks.
00:15:34 <mlemay_> hi nan
00:15:39 <paulz> The other action was completed, I think... akim to sync with mlemay on mvn install issue
00:15:40 <nzhou> hi guys
00:15:50 <paulz> Hi!
00:15:52 <nzhou> sorry being late
00:16:06 <nzhou> pls continue
00:16:11 <mlemay> paulz: yup
00:16:18 <mlemay> for that action item
00:16:37 <mlemay> I think Akim got it compiling last week
00:16:39 <akim> hi, sorry im here
00:16:49 <mlemay> so had it compiling?
00:16:50 <akim> mlemay, yeah got it to work, thanks for the help
00:16:56 <mlemay> ok
00:17:01 <akim> i only looked at it that day you talked to me
00:17:05 <mlemay> ok
00:17:06 <akim> havent touched it since unfortunately
00:17:18 <akim> but i think you guys needed some help on the index styling?
00:17:43 <mlemay> correct may I put out some "things to do?"
00:17:50 <akim> yes please
00:17:52 <paulz> Yes, please!
00:18:35 <paulz> Can you give them the #action prefix (or do I need to do that as the host? Not sure)
00:18:38 <mlemay> If possible fix the awful other xml guides so that I can apply docbook2asciidoc to them would be on the top of my list ;)
00:18:56 <mlemay> usually only hosts can do it
00:18:59 <mlemay> I think
00:19:14 <paulz> OK... what do you mean by fix the xml giudes?
00:19:36 <paulz> Does the content need to be cleaned up somehow?
00:19:41 <mlemay> (the howto-openstack and user-guide)
00:19:42 <mlemay> yes
00:19:46 <mlemay> content needs a cleanup
00:19:54 <mlemay> especially the xml:id for sections
00:20:14 <mlemay> xml:id has to be specified otherwise the toolchain chokes.. these have to be unique
00:20:33 <gjs_cisco> I’ve got the toolchain setup. I can do cleanup with some guidance on how to get this cleanup started
00:20:34 <mlemay> and my writer was a newbie so he simply cut&pasted so it's all wrong and I didn't get a chance to clean that up
00:20:54 <mlemay> ok great sure for the guidance and thanks for volunteering
00:21:04 <mlemay> after at least we'll get all of you out of xml hell :P
00:21:15 <paulz> #action gjs to sync with mlemay on doc cleanup
00:21:22 <gjs_cisco> Ok, I’m willing to slog through the mess :)
00:22:16 <paulz> Thanks, Greg!
00:22:18 <mlemay> and we'll convert it all to asciidoc , my update is I should be done with asciidocsupport
00:22:30 <mlemay> got the bugs fixed
00:22:35 <mlemay> so I only need to assemble it now
00:23:07 <mlemay> thanks Greg for the help
00:23:21 <mlemay> ok back to agenda... sorry paul
00:23:24 <gjs_cisco> No prob. I’ll be in touch
00:24:10 <paulz> No this is perfect! So once Greg has the docs cleaned up, you (Mathieu) will test the assembly... action?
00:24:25 <mlemay> action will be
00:24:31 <mlemay> convert guides to asciidoc
00:24:39 <paulz> Great!
00:24:44 <mlemay> then I think people will be able to start writing
00:24:51 <mlemay> (in a human way)
00:24:57 <paulz> #action mlemay to convert guides to asciidoc
00:25:37 <mlemay> k
00:25:46 <paulz> That actually handled one of our later topics...
00:25:55 <paulz> Ok, next item...
00:26:08 <paulz> #topic Proposal Status
00:26:43 <paulz> Heard from David Meyer... we're on the TSC agenda on Thursday
00:27:11 <nzhou> That's good
00:27:12 <paulz> 10am Pacific, if you can make it... I plan to be there, and I hope they get to us before 11 as I have a tough conflict
00:27:15 <mlemay> ok nice
00:27:22 <mlemay> I might present my project too
00:27:27 <mlemay> (reservation)
00:27:30 <paulz> Great! Busy day!
00:27:40 <mlemay> but sure it's a 2 in one ;)
00:27:47 <mlemay> I'll definitely be there for docs too
00:27:50 <mlemay> (so important)
00:27:56 <paulz> Awesome... appreciate it!
00:28:24 <paulz> Any comments or questions on the proposal?
00:28:45 <mlemay> Nope
00:29:09 <mlemay> looking forward to having the environment up so we can commit directly :)
00:29:19 <paulz> Here's the link for the call-in for anyone interested...
00:29:23 <paulz> #link https://wiki.opendaylight.org/view/TSC:Main
00:30:06 <paulz> OK, the next topic I had we mostly covered, but I'll put it up anyway
00:30:11 <paulz> #topic Toolchain setup
00:30:22 <paulz> So we have several actions here already
00:30:48 <paulz> Any other thoughts on this topic?
00:31:04 <nzhou> thanks paul
00:31:25 <paulz> Oh, Greg updated the repository setup instructions
00:31:42 <paulz> #link https://wiki.opendaylight.org/view/CrossProject:Documentation_Group:Tools
00:32:07 <paulz> If folks haven't done it, it would be good to set up their repositories in preparation for diving in...
00:32:34 <mlemay> Yes I noticed
00:32:39 <mlemay> thanks alot Greg
00:32:48 <mlemay> we'll fix it when we have our repo
00:32:57 <mlemay> I guess it should be a matter of days
00:33:11 <nzhou> really great
00:33:30 <paulz> Should people wait until the rest of the tooling is set up?
00:34:10 <gjs_cisco> People can use the instructions to get set up. Once I figure out the editing/publishing part, I’ll yupdate the wiki
00:35:10 <paulz> Thanks!!
00:35:15 <mlemay> ok
00:35:19 <mlemay> great
00:35:30 <mlemay> no they can get started now a bit if they wish
00:35:38 <mlemay> as long as content is asciidoc
00:35:50 <mlemay> I can merge the work in very easily
00:35:57 <paulz> Gotcha
00:36:41 <mlemay> http://asciidoctor.org/docs/asciidoc-writers-guide/
00:37:00 <paulz> Nice!
00:37:38 <nzhou> if I am using windows, howto clone the repositories? anyone knows?
00:37:58 <mlemay> also glossary is a ripoff from Openstack so we might want to get it started properly for ODL
00:38:05 <mlemay> yes
00:38:23 <mlemay> http://msysgit.github.io/
00:38:30 <paulz> I used Greg's instructions for my Windows machine and it seemed to work...
00:38:48 <nzhou> thanks :)
00:39:03 <gjs_cisco> I believe the commands are the same regardless of your OS
00:39:50 <paulz> Ah, Mathieu, that is a perfect segue into the next topic... anything else on toolchain?
00:40:45 <mlemay> yes correct... well apart from asciidoc no.. feel free to send me styling suggestions
00:40:51 <mlemay> or stylesheets
00:40:55 <mlemay> and I,ll bring them in
00:41:05 <mlemay> I need to sort out the maven deploy thing
00:41:12 <mlemay> and maybe the index page
00:41:22 <mlemay> any idea on the index page :
00:41:24 <mlemay> like this:
00:41:46 <mlemay> this is generate:
00:41:51 <mlemay> *generated: http://docs.rackspace.com/
00:42:12 <mlemay> do we what something like that for projects?
00:42:17 <mlemay> should projects have small logos?
00:42:24 <mlemay> (just throwing out ideas)
00:43:03 <paulz> Oooo... that page does look pretty good...
00:43:56 <paulz> how about a team action to give ideas on the index page. I'll put up a wiki page (likely tomorrow) to collect some ideas and everyone will have the action to review by next meeting.
00:45:25 <mlemay> yes sure
00:45:30 <paulz> #action paulz to create wiki page to collect ideas for index page
00:45:41 <paulz> #action team to review index page ideas by next meeting.
00:45:53 <mlemay> should it flow with ODL website?
00:46:02 <mlemay> (look and feel wise / navigation?)
00:46:50 <paulz> I think it should retain some consistency with the ODL site, but can have some unique attributes as well since it has a unique purpose
00:46:57 <mlemay> also how many orgs will want to reuse the work for their internal organisation documentation / rebranding?
00:47:18 <mlemay> just wondering how high priority that is
00:49:07 <paulz> regarding reuse, probably several orgs will want it... priority-wise, good question... we should have a model in place so that we are organizing the content properly from day 1, but it will take some time to build out the content...
00:50:30 <paulz> Colin, any thoughts on prioritizing the index page?
00:51:30 <mlemay> ok looks like I have some basic time ahead to improve stylesheet branding and have an extension mechanism ... for now we'll have to live with ODL brand for a bit
00:52:28 <paulz> I guess my opinion is that the tooling/asciidoc is a higher priority as we can't get started without it. After that, the doc organization should be in place, so we have a model to work from as far as content types, etc.
00:52:52 <paulz> Then, it would be content development, and then the actual index page build
00:53:51 <mlemay> ok
00:53:56 <mlemay> works for me
00:54:24 <mlemay> sounds like a plan
00:54:28 <mlemay> anything else?
00:54:53 <paulz> Cool! We're almost out of time... I had one more topic, but it can probably be tabled for next time (can't get into it until we can build docs)
00:55:34 <paulz> Well, I'll add a quick note anyway
00:55:34 <kwatsen> I wanted to discuss putting design docs on the wiki (e.g., templates)
00:55:46 <kwatsen> but this too can wait
00:55:59 <paulz> OK, let's put that on the agenda for next time
00:56:10 <kwatsen> k
00:56:28 <paulz> #action paulz to have Content ownership and design docs/templates on the agenda for next time
00:57:02 <paulz> Alright, anything else for either today or next time?
00:57:27 <mlemay> I'm good my
00:57:36 <mlemay> *myself
00:59:19 <paulz> OK, no other comments, I guess we can wrap it for today!
00:59:30 <paulz> Thanks, everyone!!
00:59:57 <gjs_cisco> Bye
01:00:16 <paulz> #endmeeting