20:16:18 <colindixon> #startmeeting docs
20:16:18 <odl_meetbot> Meeting started Tue Feb 21 20:16:18 2017 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
20:16:18 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:16:18 <odl_meetbot> The meeting name has been set to 'docs'
20:16:24 <colindixon> #topic peer review of docs
20:16:46 <colindixon> #info how big should groups be?
20:17:01 <colindixon> #info at least 2 people, probably more for redundancy, 4 seems like a good number for now
20:17:07 <colindixon> #info who should go into a group
20:17:34 <colindixon> #info one axis: responsiveness: at least 2 responsive projeccts per group b/c that means people will actually ge reviews and not get punished
20:17:56 <colindixon> #info another axis: amount of docs: we don't want one project with a novel worth of docs and others with 100 words
20:20:14 <colindixon> #link https://lists.opendaylight.org/pipermail/documentation/2017-February/001102.html the e-mail kicking this offf
20:20:38 <colindixon> #info what do people review? just patches as they come in or all of the other project's docs new and old?
20:20:48 <colindixon> #info my guess is that the latter is a lot better and not much harder
20:21:04 <colindixon> #info zxiiro worries that we might end up with one person in each group doing all or almost all of the reviewing
20:22:00 <colindixon> #info colindixon says he's not sure how to deal with that, but maybe if we keep groups small-ish that's fine
20:22:58 <colindixon> #info colindixon notes that if we have fewer than half of projects being responsive, we may need larger groups than 4 if we still want to have 2 responsive projects per group
20:24:44 <colindixon> #info zxiiro suggests kicking this off at M1 or M2 would be better than later and we could do that in NItrogen
20:25:34 <colindixon> https://meetings.opendaylight.org/opendaylight-docs/2017/docs/
20:27:34 <colindixon> #info how do we want to bin project types, e.g., kernel vs. app vs. protocol vs. …
20:27:54 <colindixon> #info it probably makes sense to have similar projects in each docs group, jsut becuase they'll have some idea of the concerns
20:28:22 <colindixon> #info in the longer run, you might want some variation, but for now probably anything is fine
20:31:50 <colindixon> #endmeeting