15:32:10 <phrobb> #startmeeting Pre-M2 Developer Meeting
15:32:10 <odl_meetbot> Meeting started Wed Jun  4 15:32:10 2014 UTC.  The chair is phrobb. Information about MeetBot at http://ci.openstack.org/meetbot.html.
15:32:10 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:32:10 <odl_meetbot> The meeting name has been set to 'pre_m2_developer_meeting'
15:32:27 <regXboi> I can't believe I'm saying this, but please chair me
15:32:28 <colindixon> thanks!
15:32:34 <phrobb> Sorry abhijit, you jumped the gun a bit.
15:32:53 <phrobb> chair regXboi colindixon edwarnicke
15:33:00 <abhijitkumbhare> Sorry - thought meeting had already started
15:33:08 <regXboi> phrobb: #chair maybe?
15:33:15 <phrobb> #chair regXboi colindixon edwarnicke
15:33:15 <odl_meetbot> Current chairs: colindixon edwarnicke phrobb regXboi
15:33:18 <regXboi> thx
15:33:31 <regXboi> ok, what's the agenda?
15:33:36 <colindixon> rollcall first?
15:33:44 <regXboi> #topic rollcall
15:33:50 <regXboi> would folks #info in?
15:33:53 <phrobb> #info Representatives from each project please #info the project you are representing
15:33:57 <sarathbg> #info sarath for VTN
15:33:59 <Madhu> #info Madhu for OVSDB
15:34:00 <oflibMichal> #info oflibMichal for the openflowjava
15:34:02 <dkutenic> #info Dana for bgpcep
15:34:02 <dkehnx> #info dkehnx for opflex
15:34:05 <paulz> #info Paul Zimmerman for docs
15:34:06 <regXboi> #info regXboi for .... well I'm not sure what
15:34:10 <ChristineH> #info ChristineH for SNMP4SDN
15:34:16 <liemmn> #info liemmn for AAA
15:34:21 <abhijitkumbhare> #info Abhijit Kumbhare for OpenFlow plugin
15:34:26 <ttkacik> #info ttkacik for YANGtools
15:34:30 <edwarnicke> #info edwarnicke for controller
15:34:35 <Priyanka_> #info Priyanka for Southbound plugin to the OpenContrail Platform
15:34:43 <colindixon> #info colindixon for TTP
15:34:52 <regXboi> #info regXboi for ... I guess sfc and gbp
15:35:01 <regXboi> since I don't see those covered
15:35:08 <xsited> #info xsited (Thomas Kee) for PCMM
15:35:33 <regXboi> what projects are we missing?
15:35:41 <colindixon> toolkit
15:36:00 <Madhu> I can cover toolkit till akim arives
15:36:04 <regXboi> or I should say what projects that have announced for helium are we missing
15:36:06 <regXboi> :)
15:36:08 <colindixon> but, Madhu and I can cover
15:36:23 <abhijitkumbhare> Integration test?
15:36:47 <colindixon> reservation is missing
15:37:05 <colindixon> secure bootstrap
15:37:23 <regXboi> do we have anybody comfortable with covering those?
15:37:36 <colindixon> brockners: you’re here for seucre boostrap?
15:37:51 <vina> #info vina  for lispflowmapping
15:37:56 <abhijitkumbhare> I am just pinging Luis for Integration
15:38:03 <regXboi> I dropped into #opendaylight and put up a notice
15:38:06 <rovarga_> #info rovarga_ yangtools/bgpcep
15:38:57 <phrobb> For each project checkin shall we go alphabetical down the table on the Simultaneous Release page?
15:39:00 <edwarnicke> phrobb: Do we know who we still need of the Helium folks?
15:39:23 <deepankar> info deepankar forSDNi
15:39:25 <regXboi> simultaneous release page link for the minutes?
15:39:39 <edwarnicke> deepankar: try #info ... it shows up magically in the meeting minutes :)
15:39:45 <colindixon> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan simultaneous release plan
15:39:49 <phrobb> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan#Participating_Projects
15:39:55 <edwarnicke> regXboi: I think that sounds good, perhaps in the section we have for these meetings?
15:40:20 <deepankar> #info deepankar for SDNi
15:40:21 <edwarnicke> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan#Simultaneous_Release_Developer_Meetings - suggestion for section in which to link the meeting minutes
15:40:32 <LuisGomez> #info Luis from Integration
15:40:39 <regXboi> do we have someone from dlux?
15:40:52 <regXboi> how about l2switch?
15:41:10 <regXboi> openflow proto library?
15:41:12 <colindixon> we’re still missing (by my count) dLux, D4A, l2switch, secure network bootstrap
15:41:19 <colindixon> rovarga_ is here for ofproto
15:41:26 <regXboi> got it
15:41:36 <regXboi> reservation?
15:41:37 <phrobb> Thanks for scrubbing the list regXboi can you try to ping those representatives while we start the report out from each project?
15:41:47 <colindixon> frankbrockners: I think is here for secure network bootstrap, but hasn’t chimed in
15:41:51 <regXboi> will do once I finish...
15:42:12 <phrobb> D4A is on holiday.  I can provide a brief status for them when the time comes
15:42:29 <edwarnicke> frankbrockners: could you #info in?
15:42:29 <colindixon> regXboi: reservation is a good catch
15:42:43 <brockners> yup- frank is here for SNBI
15:43:06 <regXboi> pinged mlemay
15:43:08 <colindixon> brockners: can you say “#info brockners for secure network boostrap” or something like it
15:43:10 <colindixon> for the minutes
15:43:15 <Daniel_Bartos_OF> For OF Proto Library see above .... <oflibMichal> #info oflibMichal for the openflowjava
15:43:41 <colindixon> still missing dLux, reservation, and l2switch
15:43:43 <regXboi> we have packet cable PCMM?
15:43:49 <colindixon> regXboi: yup
15:43:53 <colindixon> xsited:
15:43:58 <phrobb> #topic AAA Service Update - Liem, can you tell us the status of AAA Service?… Is your release plan final with all tasks/features identified and have you determined any all dependancies with other projects and are they on board with your needs?
15:44:02 <edwarnicke> I'm looking for l2switch guys
15:44:08 <regXboi> mlemay is coming for reservation
15:44:16 <colindixon> kk
15:44:20 <colindixon> phrobb: take us away
15:44:39 <edwarnicke> Alex Fan is on his way for l2switch
15:44:48 <rafat> #info for Rafat for SDNi
15:45:16 <phrobb> topic is on AAA.  Can the Representative for AAA provide an update on their project?… see the topic
15:45:19 <rafat> I am not able to join the link..
15:45:24 <mlemay_> @all .. sorry for being late..
15:45:30 <colindixon> rafat: I think it’s just IRC
15:45:34 <rafat> Any alternate option..for joining the video link
15:45:34 <regXboi> mlemay_ : #info in :)
15:45:35 <brockners> #info brockners for secure network boostrap
15:45:41 <regXboi> rafat: irc only
15:45:47 <colindixon> liemmn: can we get a readout?
15:45:52 <edwarnicke> Could I suggest a good first topic might be figuring out a good way to make Milestone status clear and visible?
15:45:58 <edwarnicke> I think its an easy quick win :)
15:46:29 <regXboi> edwarnicke: +1
15:46:37 <edwarnicke> #link https://wiki.opendaylight.org/view/BGP-LS/PCEP:Hydrogen_Release_Plan#Release_Milestones - example we might draw from
15:47:35 <mlemay_> #info Mathieu is present to reprensent reservation project
15:47:37 <edwarnicke> For me, I think 'Done' a Bug, Deferred to Milestone #, or 'Dropped' are very useful statuses to have... very open to other thoughts from folks :)
15:48:07 <colindixon> #info (unrelated to current topic) edwarnicke proposes that we put a status next to release milestones (similar to the link above)
15:48:24 <colindixon> I agree that would be useful
15:48:28 <edwarnicke> colindixon: Actually, I suggested we make talking about a good way to do that the topic...
15:48:49 <edwarnicke> (mostly because its durable and hopefully a little easier than a linear readout)
15:48:52 <colindixon> edwarnicke: feel free to add an addendum
15:49:00 <colindixon> edwarnicke: I agree
15:49:07 <edwarnicke> As to mechanism... I am actually hugely open... I'd just like us to figure out something good :)
15:49:09 <phrobb> edwarnicke:  would you mind going first for controller, given it's a key componenent and you can set the tone?
15:49:43 <edwarnicke> phrobb: I am happy to... but I *really* think that figuring out a better way than meeting minutes to grab the info durably is important
15:50:01 <edwarnicke> And will make for a much much easier meeting, and reporting in general
15:50:09 <edwarnicke> (see comment about hating linear readouts).
15:50:21 <edwarnicke> Then we can actually focus on conversation around those statuses and what we want to do about it
15:50:37 <abhijitkumbhare> Would it make sense to have a wiki for the M2 status - and have the projects go and update it first?
15:50:45 <edwarnicke> What do other folks other than edwarnicke colindixon phrobb regXboi thing? (I feel like I'm talking to much ;) )
15:50:53 <abhijitkumbhare> And then have a meeting / email questions
15:50:59 <colindixon> edwarnicke: not a bad idea for later meetings, but for now maybe we should do some fast linear readout
15:51:03 <edwarnicke> abhijitkumbhare: Good thought... what do others think?
15:51:20 <colindixon> abhijitkumbhare: for the last release I liked google spreadsheets for tracking status and having a summary sheet that was color coded
15:51:33 <abhijitkumbhare> Yes - that’s better colindixon
15:52:17 <colindixon> so, that does beg the question, what’s the most productive use fo the next 38 minutes
15:52:21 <abhijitkumbhare> we can have a single spreadsheet (single tab I mean) - with just a list of all the projects
15:52:33 <vina> +1 on adding a status column to release plan
15:52:37 <edwarnicke> colindixon: I also like google spreadsheets for tracking status... how should we relate that to the current milestone info in the release plans... I'd kind of like to see it knitted together somehow
15:52:38 <abhijitkumbhare> and then the projects go about filling that info in
15:53:28 <mlemay_> yes its a good idea
15:53:39 <frankbrockners> adding status to the release plan is a good idea - but better done in a spreadsheet than on wiki - which is a pain to edit and update
15:53:39 <edwarnicke> So... folks other than edwarnicke colindixon abhijitkumbhare regXboi vina ... thoughts? (not meaning to suppress thoughts from those folks... please feel free to speak.. just want to hear more opinions :) )
15:53:56 <edwarnicke> frankbrockners: Good point about the pain of editing wiki tables
15:54:21 <LuisGomez> spread sheet looks good to me
15:54:30 <edwarnicke> So... one thing I like very much about having a 'page' folks can go to for release plans is that it makes at a glance examination easier... do we have ideas on how we might preserve that?
15:54:44 <edwarnicke> Is there a way to embed a google docs spreadsheet in a wiki page for example?
15:54:59 <regXboi> edwarnicke: can't we just do a link?
15:55:06 <regXboi> or did you want more than that?
15:56:05 <edwarnicke> regXboi: So... I'm not so much expressing any kind of go/nogo opinion at this point... just observing that a link traversal makes things slightly less consumable for folks looking at plans.  My initial gut is that 'reduce editing pain for folks maintaining' data trumps that concern... but I was hoping someone would have an idea for a middle way
15:56:17 * edwarnicke is fishing for good ideas :)
15:56:23 * regXboi gets it
15:56:50 <regXboi> what type of wiki do we use again?
15:57:06 <edwarnicke> regXboi: mediawiki
15:57:08 <colindixon> regXboi: mediawiki
15:57:11 <brockners> really depends on the wiki - and whether someone is up for writing a nice macro - confluence for example allows you to render a wiki page from a spreadsheet -- though not sure about mediawiki
15:57:17 <edwarnicke> #link - http://www.mediawikiwidgets.org/Google_Spreadsheet - one possibility
15:57:41 <edwarnicke> #link http://www.mediawikiwidgets.org/Widget:Google_Document - another possiblity
15:58:01 <regXboi> edwarnicke: I'm willing to make some time this afternoon to work with you and try both of those out
15:58:11 <regXboi> on a sample wiki page and let folks look and decide
15:58:21 <mlemay_> ok
15:58:24 <regXboi> unless somebody wants to try it now :)
15:58:26 <colindixon> so, in the meantime, people who are here fore projects, please look at your release plan and your M1/M2 deliverables and figure out your status report for the M2 date on monday
15:58:44 <edwarnicke> regXboi: I think we would need agrimberg or aricg to install the mediawiki plugin
15:58:53 <catohornet1> I agree mediawiki is more flexible.
15:58:59 <colindixon> edwarnicke, regXboi: I think we need LF people to isnstall the plugin
15:59:19 <edwarnicke> catohornet1: please say more (not disagreeing... just feeling like it would be useful to hear an expanded version of your opinion :) )
15:59:24 <regXboi> do we have the widget:google spreadsheet page?
16:00:24 <Chilung> +1 for embed google doc into wiki.
16:01:17 <edwarnicke> Chilung: And thoughts on the status column?
16:01:27 <colindixon> #action edwarnicke and regXboi to explore if we can add a google spreadsheet into a wiki page to make it easy to update/track the status of projects as they go through milestones
16:02:35 <edwarnicke> How do folks feel about a status column?  And a set of at least recommendations on possible values in it.  I don't want to constrain folks from expressing what they need to express there, but might be nice to not have 27 different ways to say 'Done' :)
16:03:11 <colindixon> edwarnicke: I’m in favor of it, I think that most folks will find it annying to add that column to their tables
16:03:30 <deepankar> +1 embed google doc
16:03:37 <Chilung> may be google spreadsheet on top to highlight status and embed google doc for release plan or release note.
16:03:47 <rockyg> Red, yellow, green works well for quick info
16:03:54 <edwarnicke> colindixon: I agree wrt the wiki tables, I think the hope is by shifting to google docs it gets easy :)
16:04:03 <edwarnicke> rockyg: Ooh... I *like* colors
16:04:11 <edwarnicke> rockyg: Especially red yellow green
16:04:14 <abhijitkumbhare> +1 to recommendations
16:04:26 <Daniel_Bartos_OF> For OF Proto LIbrary Hydrogen Release we had: https://wiki.opendaylight.org/view/Openflow_Protocol_Library:PROJECT_Plan_2013
16:04:28 <edwarnicke> Makes for a very very good visual at-a-glance picture :)
16:04:29 <Chilung> +1 for colors: red yellow green
16:04:36 <catohornet1> there are more options when creating wiki pages. Especially with images. I think adding the ability to use raw HTML may help. imho. The wiki environment we currently use seems to be pretty basic in functionality.
16:04:49 <rockyg> Exactly edwarnicki.  Dashboard.
16:04:51 <Daniel_Bartos_OF> it was simple and worked fine for us and anybody interested to see status of detail tasks / milestones
16:05:32 <rockyg> lazy question; which wiki do you guys use?
16:05:37 <edwarnicke> rockyg: What would your feelings be about colors plus some simple text? (things like 'Done' or 'Bug ####' or 'Dropped' or 'Deferred to M#' ?
16:05:47 <edwarnicke> rockyg: We use mediawiki
16:06:27 <abhijitkumbhare> edwarnicke: +1 to  colors plus some simple text? (things like 'Done' or 'Bug ####' or 'Dropped' or 'Deferred to M#'
16:06:37 <rockyg> arrrgh.  Oh well.  Other wickis give you more easy abilities.  Words with colors are good if they are limited to one to to.  Bug number should actually link to bug.
16:06:45 <mlemay_> sounds liek a good idea with me
16:06:46 <paulq> #info paulq for service function chaining
16:07:01 <regXboi> paulq: thanks... now I can drop to just gbp :)
16:07:08 <edwarnicke> rockyg: Yeah... parargraphs are usually a bit much in a cell :)
16:07:19 <phrobb> I'm also concerned that we adequately capture cross project dependencies. Can we make sure something is added to the status to ensure any/all communication/collaboration is taking place?
16:08:07 <edwarnicke> phrobb: Thats a good idea... ideas on doing that fro folks?
16:08:29 <edwarnicke> from
16:09:27 <rockyg> Again, a column, for dependencies, but it can have a linked list of projects and colors red yellow green for status
16:09:33 <colindixon> projects have to list expected dependencies
16:09:38 <regXboi> I'm thinking that status on wiki is good... but google spreadsheet for capturing cross project is better, because it's simpler to link
16:09:38 <colindixon> in theire release plan
16:09:49 <regXboi> so I'm thinking both at this point
16:10:22 <rockyg> High level dashboard no wiki with detailed info in googledoc
16:10:58 <edwarnicke> rockyg: Maybe a column for 'Informed' so for things that aren't green we can have a simple 'name of project as link to email to *-dev mailer' for reference?
16:11:11 <liemmn> +1 on colors.  Can we define what the colors mean?  for example, green -> all good, yellow -> running behind, red -> blocked
16:11:13 <rockyg> ooh.  I like that
16:11:20 <mlemay_> yes it’s a good idea
16:11:52 <rockyg> Red can be blocked or in trouble.  When you see red, you know action is needed somewhere.
16:12:16 <Chilung> +1 on colors. green -> all good, yellow -> running behind, red -> blocked or in trouble
16:12:21 <edwarnicke> liemmn: rockyg Red could also be 'Dropped'
16:12:33 <phrobb> yes often yellow is behind but can recover alone, red is behind and blocked or needs help to recover
16:12:35 <rockyg> Yes, dropped too
16:13:14 <colindixon> liemmn: I would think dropped would want to be something different from “in trouble, but still trying to make it happen”
16:13:16 <edwarnicke> In my mind yellow is sort of a 'deferred'... and it would also be good to capture 'expected new delivery Milestone' in a simple way
16:13:50 <Chilung> how about grey or black for dropped. one color more.
16:13:59 <edwarnicke> colindixon: Mulling that thought... so 'Red' is sort of communicating 'still trying but at risk of not making it' ?
16:14:07 * liemmn thinking...  Maybe we need a different color for "dropped"... It serves as a flag if someone is counting on that feature and gives them a heads-up.
16:14:09 <rockyg> guys, I'm gonna see if I can do a strawman in Twiki.  There are just so many plugins available, it might make life easy enough that people will keep it updated.
16:14:14 <colindixon> colindixon: that’s by though
16:14:21 * edwarnicke resists the temptation to suggest a pirate flag for dropped... ;)
16:14:29 <colindixon> rockyg: the issue is that we *use* mediawiki
16:14:30 * liemmn lol
16:14:59 <rockyg> I know.  So, if everything could get migrated, would you consider changing?
16:15:30 <rovarga_> I think this belongs to the infrastructure mailinglist ...
16:15:31 <regXboi> rockyg: an issue is will LF support it
16:15:38 <regXboi> rovarga_: +1
16:15:39 <colindixon> rockyg: um… it’s possible, but I’d not bet on it
16:15:39 <edwarnicke> rockyg: Not wanting to shut you down... but could we call that an orthogonal conversation and maybe take it to the lists?
16:15:40 <rockyg> For dropped, how about the dead face with ex'ed out eyes and tongue hanging out?
16:15:56 <edwarnicke> rockyg: Mr Yuck? ;)
16:16:02 <rockyg> Yeah!
16:16:08 <paulq> dropped: just how crossed out / strikethrough
16:16:13 <regXboi> folks: some of us have another meeting at the bottom of the hour
16:16:29 <regXboi> just a time check here
16:16:29 <edwarnicke> OK... so, could someone summarize the current suggestions that seem to have some traction?
16:17:50 <rockyg> When does infra meet?
16:18:14 <colindixon> so, this is the ~10 minute warning
16:18:17 * edwarnicke plink plink plink
16:18:31 <edwarnicke> Could someone summarize the suggestions that seem to have some traction?
16:19:09 <rockyg> Sounds like maybe I should volunteer.  I'll get to it this week.
16:19:13 * edwarnicke also notes that embedding google docs spreadsheets could allow someone to pull together an M# status at a glance wiki page... which might also be a good thing)
16:19:39 <Chilung> +1
16:19:41 <regXboi> I'm not sure what they were... I saw google doc/spreadhseet
16:19:51 <colindixon> #topic suggestions for milestone readouts
16:19:52 <phrobb> I have heard red/yellow/green statuses for each Milestone deliverable with a google doc for detail
16:20:17 <edwarnicke> What did other folks hear?
16:20:21 <colindixon> #info everyone seemed to like the red/yellow/green status for milstone deliverables, possibly with a fourth color/logo for dropped
16:20:37 <rockyg> links to detailed project staztuses
16:20:39 <colindixon> spreadsheet >> wiki table
16:20:42 <Chilung> green -> all good, yellow -> running behind, red -> blocked or in trouble
16:21:00 <Chilung> green -> all good, yellow -> running behind, red -> blocked or in trouble, black -> dropped
16:21:12 <liemmn> +1 on paulq: dropped: just how crossed out / strikethrough
16:21:24 <edwarnicke> liemmn: I kind of like strikethrough too
16:21:31 <phrobb> Do we have suggestions for the columns of the spreadsheet/wiki table?
16:21:33 <colindixon> #info the general thought with colors was, green => good, yellow => delayed, but can fix without help (should include a new target date), red => blocked or need help
16:21:35 <brockners> Could we do both - "color" and "one word decription" -- remember, not everyone is able to differentiate green and red
16:21:48 <edwarnicke> phrobb: I would suggest current milestone columns + status at this time
16:21:59 <edwarnicke> brockners: Excellent point
16:22:03 <Chilung> +1 strikethrough
16:22:06 <rockyg> + dependent project list
16:22:26 <rockyg> How about link to bug list?
16:22:39 <edwarnicke> rockyg: Good point... I would also like to capture evidence of engaging with that dependent project if possible... good to be able to see where someone was informed
16:22:46 <rockyg> Or count of critical bugs still oprn?
16:22:53 <edwarnicke> rockyg: Say more about the bug list idea...
16:22:55 <colindixon> #info brockners points out that we should have one word descriptions, “done”, “delayed”, “blocked”, “trouble”, “dropped” (ideally we’d use these to auto-color the spreadsheet)
16:23:06 <phrobb> #info in addition to colors, include strikethrough text for items that have been dropped
16:23:32 <rockyg> By at least having a count of bugs you wouldn't ship with, everyone gets an idea of how much effort is needed to get shippable.
16:23:40 <colindixon> #info this is to help with the fact that (a notrivial) part of the population has difficulty telling red and green apart
16:24:08 <Chilung> strikethrough is more readable than color.
16:24:17 <rockyg> You pick red and green shades that are different.  Same with yellow.  So colorblind can also differentiate.
16:24:38 <rockyg> Strikethorough for dropped is good, I think
16:24:41 <edwarnicke> Since we have 7 minutes left... could we get someone to volunteer to try to put together a 'recommendations' page to capture these thoughts on the wiki.  And someone else to volunteer to drive getting gdoc embedding going for the wiki (I know infra has to do the work... but good to have someone own it)
16:25:00 <edwarnicke> rockyg: Specifics on good red/green shades welcome :)
16:25:33 <rockyg> I'll get here.  I just have to find the right useability ref. page.
16:25:56 <colindixon> #info ideally, projects would also add a status column to their milestone deliverables on their release plans, a good example is the BGP-LS/PCEP page
16:26:00 <rockyg> How about i mock up a dashboard in google doc?
16:26:01 <colindixon> #link https://wiki.opendaylight.org/view/BGP-LS/PCEP:Hydrogen_Release_Plan#Release_Milestones the example
16:26:28 <colindixon> #info we also need a way to track cross-project dependencies and make sure that communication is happening where it needs to be
16:26:44 <phrobb> #action phrobb to work with infrastructure on getting embedded goggle doc in mediawiki
16:26:50 <edwarnicke> rockyg: Would be most welcome... mind being #actioned ?
16:26:58 <rockyg> Go ahead.
16:27:42 <rockyg> #action rockyg mockup of dashboard for milestone statuses in ggogle doc.
16:27:45 <edwarnicke> #action rockyg has volunteered to "... mock up a dashboard in google doc"
16:28:05 <edwarnicke> (are either rockyg or edwarnicke chaired?)
16:28:13 <rockyg> not me.
16:28:21 <regXboi> edwarnicke: you are
16:28:25 <phrobb> edwarnicke:  is chaired I believe
16:28:47 <colindixon> #action colindixon to summarize the recommendations on the wiki
16:29:33 <phrobb> Should I set up a follow on meeting in a week (or sooner)?
16:29:44 <regXboi> phrobb: sooner, I think
16:29:53 <regXboi> like on 6/10 maybe
16:29:59 <edwarnicke> phrobb: What would the agenda be?  I am a little loath to kill folks with meetings.
16:30:17 <regXboi> I'd like to see the mashup by 6/10 before I go on pt
16:30:48 <edwarnicke> mashup?
16:30:50 <colindixon> edwarnicke, phrobb: if nothing else a quick check on progress of projects
16:30:57 <regXboi> folks... I Think we need this for another meeting... can we close this up?
16:31:19 <phrobb> edwarnicke:  I'm thinking we need to agree on the mockups etc for reporting we've discussed then actually review everyone's statuses once they are populated.
16:31:58 <colindixon> agree
16:32:22 <edwarnicke> phrobb: I was thinking of them just as recommendations to make folks lives easier... do it well and folks will tend to follow, do it badly and they won't.
16:32:35 <rockyg> ++
16:32:47 <edwarnicke> As an example, easiest way I can think of to report on M2 on Monday would be to email pointing to the milestones with status and calling out any yellows or reds
16:33:41 <Daniel_Bartos_OF> +1
16:33:41 <Chilung> The time slot of this meeting is more suitable for the guys in Taiwan (11:30 pm-12:30 am). Now we are in 12:30 am. Better than 2:00 am or 4:00 am.
16:33:41 <colindixon> edwarnicke: I’d tend to agree if we can actually extract e-mails in a timely fashion
16:35:06 <rockyg> should we call this meeting and continue elsewhere?
16:35:23 <phrobb> rockyg:  +1
16:35:43 <colindixon> #endmeeting