#opendaylight-docs: docs

Meeting summary

1. agenda bashing (colindixon, 15:02:10)
   1. so far colindixon is the only person here, so I'll wait 5 minutes, then just cover recent events in docs w.r.t. the release plan and then head out (colindixon, 15:02:45)
   
   
2. Beryllium progress (colindixon, 15:06:08)
   1. https://wiki.opendaylight.org/view/Documentation/Release_Plans/Beryllium_Release_Plan our release plan (colindixon, 15:06:33)
   2. colindixon has made some progress on remote importing of AsciiDoc, but it's not completed yet (colindixon, 15:07:27)
   3. the next deadline is M3 on 10/15 at which point it should be done, we should expect new projects to have patches pushed to the docs repo tomorrow (offset 1) and 10/15 (offset 2) (colindixon, 15:10:01)
   4. we will need some help reviewing those outlines (colindixon, 15:10:14)
   
   
3. new landing page (colindixon, 15:10:20)
   1. https://wiki.opendaylight.org/view/Documentation/Meetings (colindixon, 15:10:42)
   2. odl-casey presents his new front page for the wiki on the staging wiki (colindixon, 15:11:01)
   3. it folds in many (if not all of the discussion from) the previous meeting with three columns (colindixon, 15:11:35)
   4. odl-casey notes that he only has one documentation link (at the top with home, get software, blogs, etc.) (colindixon, 15:12:14)
   5. odl-casey says that he wants to bring this to the TWS and/or the TSC to make sure we're not missing anything (colindixon, 15:14:19)
   6. colindixon asks where "get support" and "talk to us!" will point, odl-casey says "get support" would go to ask and "talk to us!" woud go to IRC (colindixon, 15:15:09)
   7. colindixon suggests maybe being explicit with that to minimize suprise and maximize the likelihood of people getting the right place (colindixon, 15:16:58)
   8. the obvious next step would be to make sure all the listed items actually have good landing pages (colindixon, 15:22:05)
   9. https://wiki.opendaylight.org/view/File:Draft-new-wiki-front-page.png here's a screenshot of the current setup (colindixon, 15:22:16)
   10. colindixon suggests going from least to most advanced developer tasks in the developers column, e.g., start at hello world with REST, move to contributing a patch (colindixon, 15:23:08)
   
   
4. missing landing pages (colindixon, 15:23:40)
   1. do we have a tutorials landing page? odl-casey says not yet (colindixon, 15:23:54)
   2. colindixon misunderstood what use cases meant, it apparently was intended to mean the case studies (colindixon, 15:28:49)
   3. phrobb further says we have user stories (colindixon, 15:29:05)
   4. colindixon says his understanding is that use cases are abstract ways you can use the s/w to do things, case studies are the things we've talked about like with cornell, user stories are genuinely ambigous sometimes meaning case studies and other times meaning the technical term for planning agile development (colindixon, 15:31:45)
   5. colindixon suggests that we use the term "case studies" for what we currently seem to mean "user stories" and "use cases" (colindixon, 15:33:26)
   6. phrobb says that the plan is to change "user stories" to "case studies" in marketing literature (colindixon, 15:35:29)
   7. colindixon says his thought on what might be next woudl be to spend 30 seconds on each "link" to see if it needs more discussion or if we know where it will point and we like it (colindixon, 15:38:10)
   8. for those that need more discussion, we need to figure if the page exists and if not, what shoudl go there (colindixon, 15:38:45)
   9. https://wiki.opendaylight.org/view/Documentation/Meetings (colindixon, 15:42:43)

Action items

1. (none)

People present (lines said)

1. colindixon (36)
2. dneary (7)
3. odl_meetbot (5)
4. phrobb (0)