16:04:17 <colindixon> #startmeeting docs
16:04:17 <odl_meetbot> Meeting started Wed Jan 27 16:04:17 2016 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:04:17 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:04:17 <odl_meetbot> The meeting name has been set to 'docs'
16:04:24 <colindixon> #topic agenda bashing
16:04:32 <colindixon> #info docs patch reviews
16:05:01 <colindixon> #info denise has a list of questions she wants to bring up
16:07:21 <colindixon> #topic docs patches
16:08:00 <colindixon> #link https://git.opendaylight.org/gerrit/#/q/project:docs+status:open+NOT+label:Code-Review%253C0 we have lots of patches that need review
16:08:15 <colindixon> #topic denise's questions
16:09:01 <colindixon> #link https://docs.google.com/document/d/1IA31oRAEO155fygbENCYb6QKKTg7G5lxtSlBOusXvNc/edit the new, higher-level getting started guide which Denise has been interating on
16:11:10 <colindixon> #info colindixon and Denise went over the first half (through near the end of the concepts and tools)) and made minor eits
16:15:03 <colindixon> #info denise and colindixon ask about the use of the world component vs. projects vs. features in the document
16:20:37 <colindixon> #info phrobb says his goal was to refer to features, colindixon says that was also his goal, but he and Denise thought that avoding talking about projects at all likely does users a disservice as they need to know what project a feature belongs to get help, file bugs and the like
16:22:22 <colindixon> #action zxiiro to talk to yangtools about removing maven 3.1 support to get this merged and then find a second project that we could play with, likely mdsal
16:22:23 <colindixon> #action colindixon to add being able to auto-generate YANG RE this as a requirment for Boron
16:22:24 <colindixon> #action colindixon to try to work on getting project categorization for this page https://wiki.opendaylight.org/view/Project_list
16:22:25 <colindixon> #action https://wiki.opendaylight.org/view/Docucentral colindixon to work with casey to start to populate this
16:22:55 <colindixon> #action denise will change component to either project or feature as appropriate
16:24:06 <colindixon> #Info denise asks about the Karaf web console, colindixon says he's never heard of anyone using it with OpenDaylight, and unless we can find somebody to show it working with ODL, we should drop it
16:25:48 <colindixon> #info denise asks about NeXT UI toolkit in OpenDaylight and if they exist and that they plan to ship with Beryllium and that it will be an alternate UI
16:26:26 <colindixon> #action anipbu to set up a meeting with denise, phrobb, CaseyODL, to get a demo from NEXT to figure out what's there and how to document it
16:27:21 <anipbu> Sorry, I have to leave at 8:30AM.  I will read the meeting notes after the meeting.
16:31:08 <colindixon> anipbu: thanks
16:31:14 <colindixon> #info denise asks about the big feature table
16:31:51 <colindixon> #info colindixon says that the columns now are "human readable name for the feature", "description of the feature", "OpenDaylight feature name", "compatibility information"
16:38:50 <colindixon> #info colindixon and phrobb say in their mind this big table should talk about only features, but maybe point out afterward that if you want help, you might want need to identify the project providing the feature, there should be another section some where that helps connect those dots
16:39:18 <colindixon> #info anipbu asks if we could shorten this table, colindixon says he doesn't see how to do it because we won't agree on what are the "common" or "important" feautres
16:40:49 <colindixon> #action colindixon and phrobb to help denis in updating this table, there's an e-mail about this
16:42:46 <colindixon> #action anipbu to work with colindixon and phrobb to see if some projects wanted to voluntarily list (some of) their features as experimental
16:53:16 <colindixon> #info colindixon asks if the compatibility column was clear, denise said it was to her and she liked it
16:54:20 <colindixon> #info colindixon notes that there are places where we will explicitly ask people to install multiple self+all features, e.g., SFC+GBP, and that's OK
16:54:56 <colindixon> #info colindixon says we should document feature uninstallation, which basically amounts to reinstalling ODL and starting from scratch, but we still need to document it
16:55:43 <colindixon> #Info when it comes to APIs and features, some projects do really well about documenting what they're about and their APIs, but others either have nothing or are inscrutable
16:56:42 <colindixon> #info Denise asks what to do for the projects with nothing or bad summaries
16:57:03 <colindixon> #info colindixon says everyone should at least have an overview paragraph in the user guide, maybe we could use that
16:57:54 <colindixon> #link https://www.opendaylight.org/whats-new-lithium Denise and CaseyODL think this is also a really good place
17:00:51 <colindixon> #Info colindixon notes that not all projects are there, e.g., yangtools is missing, also it needs updating for Beryllium, e.g., the controller doesn't actually act as controller now
17:02:19 <colindixon> #info phrobb says that this is the wording from his slide deck, but talk to Melissa about it
17:03:11 <colindixon> #endmeeting