01:45:10 #startmeeting 01:45:10 Meeting started Fri Jan 17 01:45:10 2014 UTC. The chair is edwarnicke. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:45:10 Useful Commands: #action #agreed #help #info #idea #link #topic. 01:45:20 Welcome to the 5:45pm Hydrogen Release Meeting 01:45:27 Hello. 01:45:27 #topic rollcall 01:45:47 Hello 01:45:53 Please #info in with names and projects (if you are representing a project) 01:46:01 #info Hideyuki Tai for VTN 01:46:03 #info Andrew Grimberg for infrastructure support 01:46:10 #info dbainbri for self 01:46:16 hehe 01:47:06 dbainbri: I had no idea we had programing language representation ;) 01:47:13 Christine_: Are you here? 01:47:29 hi, I'm here. 01:47:39 Would you please #info in for the minutes? 01:48:13 RobDolin: We are doing rollcall, would you #info in? 01:48:19 #info Christine for SNMP4SDN 01:48:27 thanks, Ed 01:48:35 #info RobDolin 01:49:00 #topic review of outcome of 9am Meeting 01:49:36 I'd like to take a brief moment to go through the #agreed items from this mornings meeting, to see if you guys object (because its not really #agreed until we all agree) 01:49:54 #link https://meetings.opendaylight.org/opendaylight-meeting/2014/opendaylight-meeting.2014-01-16-17.00.html summary of this mornings meeting 01:49:56 sure :) 01:49:57 #info networkstatic for OVSDB 01:50:25 #info Brent :) for OVSDB 01:51:11 * networkstatic looks around awkwardly 01:51:22 * tykeal looks back at networkstatic 01:51:30 lol 01:51:42 Hey Brent and Ty :) 01:51:46 :) 01:51:48 #link https://wiki.opendaylight.org/view/Draft_Syslog_Level_Settings Log level recommendations, we agreed to change 'bundle' to 'module' for INFO, and to add messages received from or sent to the wire for TRACE 01:51:50 hehe hi guys :) 01:52:04 Is everybody here OK with those changes to log level recommendations? 01:52:43 #info Spreadsheet of work items is here: https://docs.google.com/spreadsheet/ccc?key=0AoSzir1BfjyWdDQyVElWNG9mcWxhblREckZjbjFxUVE#gid=1 01:52:51 Thx RobDolin :) 01:52:58 Ok. 01:53:01 * tykeal sighs 01:53:07 looks good here, one thing edwarnicke does a toString w/ formatting interest anyone? 01:53:07 use #link people ;) 01:53:08 Cool :) 01:53:16 whats link? 01:53:19 * tykeal feels like a grinch for saying it 01:53:23 :) 01:53:34 * networkstatic think tykeal is a grinch 01:53:37 #agreed Concur with 9am meeting on: change "bundle" to "module" in the log level recommendations 01:53:38 the command #link == #info except that it does hyperlinking 01:53:52 #agreed Concur with 9am meeting on: expand the scope of trace to include items such as logging messages received and others 01:53:56 it should be used if you've got a URL you're adding to the minutes 01:54:14 ahh, sorry, i rtfm :) 01:54:23 @tykeal - Thanks :) 01:54:31 #link Spreadsheet of work items is here: https://docs.google.com/spreadsheet/ccc?key=0AoSzir1BfjyWdDQyVElWNG9mcWxhblREckZjbjFxUVE#gid=1 01:54:39 We also agreed at the 9am meeting that individual projects can choose whether or not System.out.println is allowed in their Integration and unit tests, but in production running code it should not be used 01:54:39 haha... the rtfm doesn't actually say that, it's hard won experience over the last few meetings ;) 01:54:40 and 01:54:51 code that does not get run by launching the controller in the normal fashion can use system.out.println at the project's discretion, for example, to provide a CLI that runs outside the JVM 01:54:58 Is everyone OK with that? 01:55:04 edwarnicke: Ok on these, too. 01:55:17 +1 01:55:35 agree 01:56:09 #agreed Concur with 9am meeting that individual projects can choose whether or not System.out.println is allowed in their Integration and unit tests, but in production running code it should not be used 01:56:28 #agreed Concur with 9am meeting that code that does not get run by launching the controller in the normal fashion can use system.out.println at the project's discretion, for example, to provide a CLI that runs outside the JVM 01:57:17 There was also a brief discussion about treating System.err.println and e.printStackTrace the same way as System.out.println... everybody good with those (feel free to raise objetions if you have them) 01:57:52 Madhu: Would you #info in? 01:58:06 edwarnicke: no objection on it. 01:58:08 #info Madhu for ovsdb 01:58:23 networkstatic hey buddy 01:58:32 We also at the 9am put together https://docs.google.com/spreadsheet/ccc?key=0AoSzir1BfjyWdDQyVElWNG9mcWxhblREckZjbjFxUVE#gid=15 to report out to the TSC weekly 01:59:11 #topic per project status 01:59:14 Would it make sense to document the two log decisiosn we just agreed on at: https://wiki.opendaylight.org/view/Draft_Syslog_Level_Settings or some other location? 01:59:37 RobDolin: I believe we did up log 01:59:49 (I asked about them, and recorded concurence via #agreed) 02:00:10 RobDolin: I completely agree with you though that its not really #agreed till both meetings get a chance to weigh in 02:01:09 I think we have them well captured in the minutes and I like that you made sure that both meetings agreed, but I'm wondering if we should document somewhere on the wiki since digging through the minutes from these IRC sessions might be hard when we're wondering about these decisions in a month or two. 02:01:11 In an effort to expedite per project reporting, would the project representatives please #info the items the status of the items they are working on from the spreadsheet 02:01:25 (feel free to talk all at once :) ) 02:01:43 RobDolin: That's an excellent idea, would you do that? 02:01:55 +1 on RobDolin , good idea. 02:03:20 hideyuki, Christine_ , networkstatic , Madhu feel free to start #info-ing status on spreadsheet items any time now ;) 02:03:30 ok 02:03:32 edwarnicke: ok. 02:03:51 * Madhu looking 02:04:51 #info "Remove all uses of System.out.println" is DONE. https://git.opendaylight.org/gerrit/#/c/4258/ 02:05:00 #info ovsdb : all exceptions are logged as bugs and being addressed. 02:05:16 @EdWarnicke - Done; added "Guidelines" section at bottom of https://wiki.opendaylight.org/view/Draft_Syslog_Level_Settings to capture decisions in wiki /cc @Hideyuki 02:06:32 #info versions jenkins job is completed 02:06:37 #info VTN will remove System.err and printStackTrace. 02:06:50 #agreed to add decisions on the changes to https://wiki.opendaylight.org/view/Draft_Syslog_Level_Settings to the bottom of the page 02:06:50 #info OVSDB dependency convergence fixes are in 02:07:00 #info decisions on the changes to https://wiki.opendaylight.org/view/Draft_Syslog_Level_Settings to the bottom of the page added by RobDolin 02:07:06 #info OVSDB working on fixing the logs. 02:07:39 #info "Insert copyright/licence headers" is DONE on VTN. 02:07:49 #info OVSDB working on release readiness as per the recommended guideline process (such as tags etc...) 02:08:08 I'll change the status of "Insert copyright/licence headers" for VTN to "DONE" later. 02:08:15 hideyuki: Thank you :) 02:08:30 regarding the copyright 02:08:34 Folks, please make sure to update status on the spreadsheet and insert any relavent details in the 'Notes' column for each item :) 02:08:38 #info SNMP4SDN is removing all uses of System.out.println 02:08:39 Madhu: Yes? 02:08:41 we have added it to all the java files 02:08:53 how about the pom and other files. what is the final decision ? 02:09:11 is it required for all the non-java files as well ? 02:09:14 I think the current decision is to add it to all feasible files 02:09:29 feasible ? : anything that takes comments ? 02:09:36 including .gitigonre ? 02:09:39 If you have a case where you feel it should be otherwise, please feel free to raise it 02:09:46 including README files ? 02:09:46 LOL 02:09:53 lol. 02:09:56 definitely the README! ;) 02:10:00 .gitignore (i don't think so) 02:10:01 hideyuki: You raise some interesting possible exceptions :) 02:10:31 Can we agree that .gitignore and README should be exempt, and having so #agreed we will bounce it to the morning meetings to see how they feel? 02:10:44 +1 02:10:45 I believe there was some discussion about it in the .gitignore but as .gitignore accepts comments (# lines) there isn't any reason _not_ to add it there as well 02:10:49 +1 02:11:01 edwarnicke: isn't it also strange to see copyright in config ini files ? 02:11:13 and sample resources files ? 02:11:14 It would feel that way to me, yes 02:11:15 tykeal: this mail? https://lists.opendaylight.org/pipermail/discuss/2014-January/001071.html 02:11:31 hideyuki: that would be the one 02:11:34 So shall we add config.ini to our list 02:11:49 Madhu: Can you list the sample resource files you are thinking of? 02:12:23 edwarnicke: yes. we have a sample local.conf file in the resources/ folder 02:12:30 that can be used for openstack deployments 02:12:41 certainly not a copyright of open daylight :) 02:12:44 Shall we suggest simply not putting copyright notices in configuration files then? 02:12:48 it is copied from devstack 02:12:52 i think so 02:13:01 edwarnicke: Agreed on your suggestion. 02:13:02 What do other folks think? 02:13:08 Christine_: are you onboard? 02:13:12 edwarnicke: that's a very reasonable suggestion 02:13:15 also, i have sample files such as POSTMAN scripts :) 02:13:19 agree 02:13:30 its more on boarding stuffs 02:13:46 oh, yes. 02:13:50 #agreed copyright/license headers need not go into configuration files, .gitignore, or READMEs 02:13:53 it is easy to add of course. but very strange to do that 02:14:03 Madhu: Yeah, feels weird 02:14:04 agree with the discussion above. 02:14:05 edwarnicke: including .gitreview right? 02:14:26 I'd be happy to include that too :) 02:14:34 edwarnicke: OK! 02:14:38 i think one came from RackSpace didn't they? 02:14:47 that macnamara pushed 02:14:50 not sure 02:14:57 #agreed copyright/license headers need not go into .gitreview 02:15:07 edwarnicke: thank you! 02:15:31 Madhu: Back to your question... do we want to suggest that pom.xml files are configuration files for the build 02:15:32 ? 02:15:34 will drop Phil a reminder to not send those too :) 02:16:05 edwarnicke: yes. 02:16:25 Madhu: And thus pom.xml files do not need copyright/license headers? What do other folks think about that? 02:16:57 I think it's fine... 02:17:20 honestly, that one is sort of iffy to me 02:17:27 tykeal: Please voice your concerns 02:18:14 yes, those pom.xml files are configuration files to the builds, but they're also integral to the code in a way. They're built by the devs in the same way that a Makefile would be. Many Makefiles have copyright notices in them 02:18:29 Hmm... 02:19:54 that's my take at least 02:20:03 Could we agree to bounce this to the OpenDaylight Foundation Attorneys to ask if pom.xml files are copyrightable or not? 02:20:03 IANAL, but I have a lot of experience around this sort of stuff... and I wouldn't be surprised if they aren't copyrightable because they lack expressive content... 02:20:07 tykeal: Thank you for raising the point :) 02:20:51 sure, we can bring it up to the Attorneys 02:21:12 #agreed raise the question to the attorneys as to whether we need copyright/license headers in pom.xml files 02:21:16 #topic documentation 02:21:23 RobDolin: Are you still with us? 02:21:46 RobDolin: Would you be willing to lead the documentation topic of discussion? 02:22:44 Sure. 02:22:50 #info https://wiki.opendaylight.org/view/CrossProject:Hydrogen_Release_Work - Wiki pages for User Guide Template and Developer Guide Template are linked from there 02:23:17 Big thanks to @Kudo @Luis and the rest of the team who provided feedback. 02:23:32 There's an open question on the discuss email list if log documentation should go in the User Guide or the Developer Guide. 02:23:43 Do folks have strong opinions here? 02:23:52 You mean how to set log levels? 02:24:25 No comments so far on document templates. 02:24:28 @EdWarnicke - No, I think this is more of documentation for logs like what various log lines mean. 02:24:51 @Hideyuki - Cool. Thanks. 02:25:24 RobDolin: Still not following, but will look at the thread on the lists 02:25:54 thanks for the document templates, no comment so far 02:25:54 RobDolin: Do we have a place for folks to start working on their per project contributions to docs yet? 02:26:03 #info no comments on doc templates so far 02:26:06 @EdWarnicke - Sounds good; thanks. 02:26:12 @Christine - Thanks :) 02:26:42 Are we done on docs then for this meeting? 02:26:49 @EdWarnicke - AFAIK, some of the projects already have pretty robust documentation. 02:26:55 @RobDolin: Hi Rob personal opinion is the setting of log levels etc in the user guide and meaning in the dev guide. 02:27:19 chrisprice_: Welcome :) 02:27:21 #help Project team members, please take a look at the User Guide Template and Developer Guide Template and provided any feedback on discuss email list or edit the wiki pages. 02:27:43 #topic tomorrows 5:45pm meeting 02:27:48 @ChrisPrice - Thanks; that seems like a very reasonable approach. 02:28:03 There's an open question as to whether there should be a 5:45pm meeting tomorrow, since its Saturday in Asia 02:28:09 Thanks Ed, been following. 02:28:10 Do folks have an opinion? 02:28:33 hmm. 02:28:41 (I am inclined to cancel for tomorrow, and inquire about whether we need it on 5:45pm PST Sunday as that's Monday in Asia) 02:29:20 I can attend to the tomorrow meeting. 02:29:21 makes sense 02:29:25 ah 02:29:27 Actually Ed good proposal. (my attendance record leaves much to be desired though) 02:29:27 nm :) 02:29:39 Christine_: Thoughts? 02:29:39 I can't attend tomorrow's meeting because of weekend. 02:29:56 I cannot attend the meeting on 5:45pm PST Sunday... 02:30:07 hideyuki: OK 02:30:07 Christine_: you make a valid case as to edwarnicke point ;) 02:30:22 @EdWarnicke - I agreed with canceling Friday 5:45pm (Pacific) 02:30:30 Shall we resume the 5:45pm PST meetings 5:45pm PST on Monday then? 02:30:35 No, Let me correct. I can attend the meeting on 5:45pm PST Sunday... 02:30:41 hideyuki: Ah 02:30:42 Ok 02:30:53 I can't make a Sunday meeting easily 02:30:55 edwarnicke: Agreed on canceling on Friday 5.45 pm. 02:31:04 Would someone be willing to volunteer to lead the 5:45pm PST Sunday meeting? 02:31:24 (I promise you, if I can do it certainly any of you can ;) ) 02:31:49 i will but this is my first exposure to has tag mania 02:32:02 unless it needs to be TSC 02:32:03 nm 02:32:04 lol 02:32:08 Totally doesn't need to be TSC 02:32:21 @NetworkStatic - https://wiki.debian.org/MeetBot has a nice Howto section 02:32:27 #agreed to cancel 5:45pm PST Friday meeting 02:32:32 thanks Rob 02:32:38 #agreed to have 5:45pm PST Sunday meeting 02:32:46 networkstatic: tags are not new to u twitter man :) 02:32:49 #info networkstatic has volunteered to run 5:45pm PST Sunday meeting 02:33:03 lol, these mean something not #catsarecool 02:33:05 #topic any other topics before we close? 02:33:21 So... anything else before we close? 02:33:25 shall i bring up docker here? 02:33:26 Wait a seconds. 02:33:27 networkstatic: we shud add that to #meetbot. 02:33:30 dbainbri: Please :) 02:33:32 hehe 02:33:45 #topic docker 02:33:53 dbainbri: You have the floor :) 02:34:05 brought up. my plan is to at minimum generate docker images for the 3 packages. 02:34:07 Where should we create Developer Guide and User guide? 02:34:14 On wiki? or somewhere else? 02:34:25 have other thoughts are well around auto scaling, but that is likely post release. 02:34:46 hideyuki: I would think on wiki. I know colindixon was researching using Transclusion, could you email discuss asking him where he is with that? 02:35:09 #info dbainbri has volunteered to do docker for each of the three release editions 02:35:18 lol 02:35:21 edwarnicke: Thank you. I will send a email. 02:35:24 dbainbri: Please follow up with shague as I believe he is coordinating release artifact 02:35:27 way to volunteer :) 02:35:37 lol, there was some pre-meeting talk ;) 02:35:44 dbainbri: Did I volunteer you to fast? 02:36:02 no worries. 02:36:09 Cool 02:36:24 Anything else folks would like to raise before we close? 02:37:07 no more~ 02:37:17 +1 :) 02:37:19 Thank you to all participants :) 02:37:22 No for the meeting. But I have a question on Bugzilla to Andrew. After the close, I'll ask him. 02:37:22 #endmeeting