Re: [OpenDaylight Discuss] pre-M2 release meeting minutes
OK. I’ve got a sort of mock-up of a status page for milestones and releases.
At the top are three gauges which go from -40 to +40 There are 31 projects listed, so the reality is this should go from -31 to +31, but I left some slack. The first gauge is Delivered Deliverables. The second, Project Status and the third, Dependencies
To get the numbers, first I:
· took each listed project from the wiki (two lists – projects list and release plan list. I added the extra projects from the release plans page at the bottom of the spreadsheet). I listed them in column 1 of sheet 1.
· The second column lists the deliverables listed in the release plans for M2 for each project. I colored the cell based on reports of assumed state of combined deliverables based on status and dependencies.
· The third column is status and reflects only what is or is not currently in the release plans.
· The fourth column is dependencies required in M2 (as much as I could figure out.)
· On the second sheet, the first column is the gauges I wanted to display
· The second column is the value to show. I did this one by hand, but the formula is this:
o Every green cell (or cell contents) = +1
o Every yellow cell =0
o Every red cell =-1
o The cells in the second column of the sheet2 are the sums of the colors from the matching columns in sheet 1
This is only a mock-up, but the power of just seeing in these two methods the presumed state of ODL is very powerful. Each project could maintain their own spreadsheet, the spreadsheet being the release plan, and they could change the status based on their weekly meetings, input from integration, etc. By linking the spreadsheets to this one, the ODL teams could have a general status spreadsheet on a main wiki page, with each project having their detailed statuses in spreadsheets on their project pages.
All of this assumes, of course that Google docs will display in media wiki and that multiple sheets can have linking cells. But, if it can this could be really useful.
From: Ed Warnicke (eaw) [mailto:eaw@...]
Sent: Friday, June 06, 2014 11:57 AM
To: Rochelle.RochelleGrober; Colin Dixon; <discuss@...>
Subject: RE: [OpenDaylight Discuss] pre-M2 release meeting minutes
Not sure if this will help or not, but each project has a maven group id (like org.opendaylight.controller) so you
could in principle autoscan for the dependencies (both direct and indirect) using a little maven tooling.
But I think that the interesting thing is really what *development* folks are counting on from other projects,
not what they currently use... not sure how to get that.
From: Rochelle.RochelleGrober [rochelle.grober@...]
I did a little research already and plan to get to the mockup tomorrow. There are lots of interesting things people are doing with dashboards, so I think the mockup will provide lots of food for thought.
I think that besides project status, the most important thing to track right now is the project dependencies and their status. Autogenerating the map should be possible if each project maintains a list of their outside project dependencies.
I’ll see if I can post a Google doc tomorrow. If not tomorrow, Monday.
From: Ed Warnicke (eaw) [mailto:eaw@...]
Reporting out on #actions from that... I've opened a helpdesk request for a mediawiki plugin to embed
google docs in Mediawiki (#5664).
Has anyone heard from rockyg on his mockup action?
Colin, did some of this get captured on a wiki page?
[discuss-bounces@...] on behalf of Colin Dixon [colin@...]
Replying to keep things on the discuss list. Yes, I think we should be able to make this work in mediawiki.
On Wed, Jun 4, 2014 at 5:44 PM, Rochelle.RochelleGrober <rochelle.grober@...> wrote:
Just wanted to add that mediawiki has over 2200 extensions , including googledocs, phpspreadsheets, insertable tables, bugzilla plugin, testopia plugin, etc., many of which generate data visualizations. I’m thinking that a few of us should get together on an IRC and determine which extensions we think would be worth getting Infra to install/configure to help us with integration and tracking of project statuses.
On Behalf Of Colin Dixon
The high level readout was the following:
Presumably more e-mails (to project leads) will follow.