#opendaylight-meeting Meeting
Meeting started by phrobb at 17:00:08 UTC
(full logs).
Meeting summary
-
- dmm (dmm,
17:00:15)
- https://wiki.opendaylight.org/view/TSC:Main#Meeting_Agenda
(dmm,
17:00:24)
- TSC members please #info in (phrobb, 17:00:57)
- Ed Warnicke (edwarnicke___,
17:03:01)
- Chris Wright (cdub,
17:03:31)
- vijoy (vijoy,
17:04:28)
- Kent Watsen (kwatsen,
17:04:59)
- Rob Dolin proxy for Rajeev Nagar
(Microsoft) (RobDolin,
17:05:10)
- Agenda Bashing (phrobb, 17:05:51)
- Chris Price joined (ChrsPriceAB,
17:06:08)
- If anyone has any comments for last week's
minutes, please make them in meeting, or on the TSC mailing
list (phrobb,
17:07:21)
- Creation Review - Documentation (phrobb, 17:07:50)
- ACTION: take
discussion and proposed revision of charter re election to list
(deadline 6/2/2014) (regXboi,
17:07:52)
- https://wiki.opendaylight.org/view/Project_Proposals:Documentation
(edwarnicke___,
17:08:06)
- dmm asks about documentation automation
(RobDolin_,
17:11:51)
- : q - how much automation/tooling
available? (phrobb,
17:11:54)
- regXboi asks how docs thrown off as side effect
of project build fits in to this doc plan (phrobb,
17:13:05)
- regXboi asks about build generated docs like
maven site generation (edwarnicke___,
17:13:09)
- regXboi volunteers to be a committed resource
for the documentation project if it includes auto-generated
documentation (RobDolin_,
17:17:10)
- dmm asks: will there be outgoing documentation
as well as technical documentation ? (RobDolin_,
17:18:33)
- Mathieu and Paul suggest this may be down the
road (RobDolin_,
17:18:53)
- regXboi has added himself as resource and
committer (regXboi,
17:20:46)
- AGREED: The
Documentation Project into Incubation (phrobb,
17:21:31)
- Creation Review Dynamic Resource Reservation (phrobb, 17:22:22)
- https://wiki.opendaylight.org/view/Project_Proposals:Dynamic_Resource_Reservation
(edwarnicke___,
17:25:49)
- point made that GBP may already provide the
northbound plugin for this project (regXboi,
17:36:42)
- question about what protocols would be used for
SB (regXboi,
17:38:26)
- answer there are multiple protocols that can be
used (regXboi,
17:39:26)
- statement that those points should be added to
the proposal (regXboi,
17:39:39)
- question about reuse of existing components
(specific topology manager) (regXboi,
17:39:57)
- answer is that it is still be considered
(regXboi,
17:40:18)
- slight digression about how to allow this
project to interwork with topology manager (regXboi,
17:41:42)
- Question before the TSC is whether to move the
Dynamic Resource Project to Incubation (RobDolin_,
17:43:29)
- AGREED: dynamic
resource project to incubation (regXboi,
17:43:46)
- Helium Release Schedule (phrobb, 17:44:08)
- https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan
(edwarnicke___,
17:44:13)
- changes being highlighted: no later than M2 as
part of the Gerrit/Jenkins merge process participating projects must
push their binary artifacts to the Nexus repo. (regXboi,
17:46:44)
- No uses of System.out.println in non testcase
code. (regXboi,
17:47:04)
- No dependencies on 3rd party (non-ODL) snapshot
versions (regXboi,
17:47:16)
- aspirations and intentions added as "stretch
goals" (regXboi,
17:49:12)
- regXboi (Ryan Moats, IBM) expresses a concern
with continuous documentation not being part of Helium (RobDolin_,
17:50:48)
- edwarnicke__ suggests that requiring continuous
documentation for Helium will be a high bar (RobDolin_,
17:53:06)
- dmm (David Meyer, Brocade) expresses agreement
with Ed (RobDolin_,
17:53:28)
- regXboi suggests if we're starting continuous
integration in M3, we should also have continuous
documentation (RobDolin_,
17:54:20)
- regXboi asks: If this is an approved draft
schedule, does this go into stone in such a way that we can't add
continuous documentation in M3? (RobDolin_,
17:55:44)
- regXboi's happy question - is this release plan
in stone, or can we mandate Continuous-docs later? - Answer from
edwarnicke___ "no we can change the criteria mid-stream (phrobb,
17:56:06)
- EdWarnicke__ suggests we could move commencing
user-facing documentation from M5 to M3 (RobDolin_,
17:57:15)
- cdub suggests that you can start documentation
even if you haven't locked-down APIs (RobDolin_,
18:02:39)
- the Documentation Project may be able to
provide recommendations to projects for docs to be produced
(phrobb,
18:04:38)
- AGREED: moving doc
start from M5->M3 (regXboi,
18:05:19)
- ACTION: Documentation
group to provide guidance to projects on documentation
produced (phrobb,
18:05:28)
- dmm suggests changing all TSC "musts" to
"Commits to" (phrobb,
18:09:09)
- concern that having Lithium Plan finalized in
M2 would lead to Lithium not having to implement continuous
documentation (regXboi,
18:11:15)
- edwarnicke__ points out this is more general
that just documentation, it may preclude including learnings from
Helium (regXboi,
18:12:46)
- cdub suggests we could push-out the Litinum
release plan to M4 or M5; and release planning cycles should be
easier as we gain more xperience. (RobDolin_,
18:12:59)
- edwarnicke__ is worried about having the
"bones" of lithium earlier in the process (regXboi,
18:14:14)
- so that new projects have an understanding of
the sechedule sooner rather than later (regXboi,
18:14:40)
- discussion of how to schedule Lithium in a way
that provides forward visibility to new projects (regXboi,
18:18:40)
- lenrow proposes putting out provisional
schedules for Lithium (and maybe Berrylium) (regXboi,
18:23:09)
- which corresponds to cdub's proposal
(regXboi,
18:23:21)
- colindixon points out that we have to get to an
annual template (regXboi,
18:23:44)
- correction: proposal from kwatsen, not
lenrow (regXboi,
18:24:17)
- edwarnicke__ pushes back that he wants time for
review and consideration (regXboi,
18:24:34)
- and community discussion (edwarnicke___,
18:24:44)
- regXboi asks if there is a proposal to put the
helium and lithium and subsequent release schedules on the public
page (regXboi,
18:31:25)
- http://www.opendaylight.org/resources/getting-started-guide
is currently linked from www.opendaylight.org (RobDolin_,
18:31:47)
- ACTION: we need to
put links on the opendaylight page to the schedule, mailing lists
and irc channel lists (regXboi,
18:31:59)
- discussion of provisional dates for service
releases (regXboi,
18:46:38)
- cdub argues that he doesn't want to set the
dates for stable releases, because things happen (colindixon,
18:48:28)
- edwarnicke___ wants to let developers plan
vacations after releases w/o worrying about having to ship stable
updates (colindixon,
18:48:52)
- AGREED: resolution is
to set the dates as provisional and that they can be modified as
needed, e.g., for critical bug fixes (colindixon,
18:49:58)
- colindixon is concerned how as a community we
enforce these deadlines as we didn't do it well in Hydrogen
(phrobb,
18:51:43)
- note that the TSC can let projects join after
M1 (within reason) for extenuating circumstances, e.g., IPR
review (colindixon,
18:53:48)
- edwarnicke___ notes that a project split into 2
projects may need until M3 to have their release plans
created/updated.. ie Project A splits into B & C, B & C need
to accomodate everything identified in the original project A
(phrobb,
18:54:47)
- cdub calls for a vote on the schedule
(RobDolin_,
19:00:12)
- Vote to adopt the Full Release plan for Helium
presented today (phrobb,
19:01:02)
- AGREED: the Full
Release Plan for Helium presented is approved (phrobb,
19:01:24)
Meeting ended at 19:02:03 UTC
(full logs).
Action items
- take discussion and proposed revision of charter re election to list (deadline 6/2/2014)
- Documentation group to provide guidance to projects on documentation produced
- we need to put links on the opendaylight page to the schedule, mailing lists and irc channel lists
People present (lines said)
- regXboi (60)
- networkstatic (43)
- RobDolin_ (29)
- phrobb (26)
- alagalah (26)
- edwarnicke___ (16)
- cdub (16)
- colindixon (14)
- dmm (8)
- odl_meetbot (4)
- vijoy (3)
- lenrow (2)
- ChrsPriceAB (2)
- RobDolin (2)
- mlemay (2)
- mrberner-mobile (1)
- kwatsen (1)
- phudgins (1)
Generated by MeetBot 0.1.4.