15:07:21 <catohornet1> #startmeeting Robot Happy Hour
15:07:21 <odl_meetbot> Meeting started Wed Apr  8 15:07:21 2015 UTC.  The chair is catohornet1. Information about MeetBot at http://ci.openstack.org/meetbot.html.
15:07:21 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:07:21 <odl_meetbot> The meeting name has been set to 'robot_happy_hour'
15:08:34 <catohornet1> Good morning! Any questions or things anyone would like to discuss?
15:14:27 <vrpolak> I only have one comment to discussion from the previous week, about license texts. I put it to Documentation part of my suite. https://git.opendaylight.org/gerrit/#/c/17242/5/test/csit/suites/bgpcep/basicpcep/basicpcep.robot
15:16:22 <catohornet1> Taking a look..
15:23:51 <catohornet1> vrpolak: I believe  you have to take Ćopyright Cisco out.
15:25:19 <PhilShea> I've noticed a few cases of company copyright. If I'm working on some code with a copyright, it's OK to take it out then?
15:26:26 <PhilShea> Also, should we put our name in the code, or is that redundant, since git documents who worked on a piece of code?
15:28:25 <vrpolak> catohornet1: And why is that? There is "and others" there and Eclipse License v1.0. I was under impression that this allows anyone to do further edits. And most of Java source files from Cisco developers in ODL use the same combinations of Copyrigh and License.
15:29:05 <catohornet1> Iḿ checking with Linux Foundation
15:29:22 <vrpolak> But I admit I have not read the Eclipse Public License v1.0, maybe there is something that makes Java different from Robot.
15:31:59 <catohornet1> It may be that itś okay to include this information. Iḿ receiving confirmation.
15:37:55 <catohornet1> Including the license information and Copyright is okay as long as explicit rights statement allowing use if the code.
15:38:37 <catohornet1> of the code, in this case the code  in the test cases.
15:42:27 <vrpolak> PhilShea: I have seen author specified mostly in Python code only. In my Python code (imported to Robot suite as Library) I used both Java-style and Python-style license segments, (I think only one should be used, but I am not sure which one.)  https://git.opendaylight.org/gerrit/#/c/17242/5/test/csit/libraries/HsfJson/hsfl.py
15:50:04 <odp-gerritbot> Navin Agrawal proposed a change to integration: fixing alphabatical order for capwap in feature repository. thanks to Vratkfor the review comment.  https://git.opendaylight.org/gerrit/17938
15:54:03 <catohornet1> PhilShea: You can put it there if you want. Be prepared to be contacted when consumers have issues or questions. :)
15:55:48 <catohornet1> Has anyone experimented with a different IDE for robot since last conversation?
15:58:07 <vrpolak> catohornet1: Not yet. So far, using ordinary text editor and then normalizing by opening&saving from RIDE is good enough.
15:59:07 <catohornet1> vrpolak: That method is certainly effective.
16:00:21 <catohornet1> We are working to increase the number of projects with system tests in integration. If youŕe having issues please let us all know via the email list.
16:00:28 <vrpolak> Comment on lack of other comments: I have seen work on upgrading Requests library to latest version (build from sources), but I decided to stop thinking about library versions until we have VM with Centos7 (hopefully very soon).
16:03:27 <catohornet1> Understood
16:10:23 <catohornet1> Next week I will include  tips about testsuite format from the Robot userś guide.
16:12:36 <catohornet1> Thanks everyone and chat with you next week.
16:12:50 <catohornet1> #endmeeting