[onap-tsc] [onap-discuss] ONAP Project: Registration for May Developer Event

2017-04-18 Thread Yang, Bin
ject: Re: [onap-tsc] [onap-discuss] ONAP Project: Registration for May Developer Event Architecture Deep Dive, Code Merge Strategy, Release Planning and some initial discussions on project proposals are all good topics for the May F2F. However, if at all possible, I would like to request that we

[onap-tsc] [onap-discuss] ONAP Project: Registration for May Developer Event

2017-04-12 Thread Gadiyar, Rajesh
Re: [onap-tsc] [onap-discuss] ONAP Project: Registration for May Developer Event Hi Annie & TSC members, I would like to propose some kind of a hackathon during the Developer event in order to really make it a developer-focused event. I believe that architecture, code merger strategy

[onap-tsc] [onap-discuss] ONAP Project: Registration for May Developer Event

2017-04-11 Thread GILBERT, MAZIN E (MAZIN E)
Thanks Helen. I encourage everyone to share any proposed items you would like covered in the May F2F meeting inline with the mission of the meeting. The key objective of the meeting is outlined by Annie. Our goal is to interlock on functional architecture, use cases and execution plan to go and

[onap-tsc] [onap-discuss] ONAP Project: Registration for May Developer Event

2017-04-11 Thread Yunxia Chen
Hi, Good TSC members, I would suggest that we could have a session discuss about ?System Integration and Testing?. With the merged community and more than 4 millionaire LOC, we need to get some consensus among developers: 1. Is code style enforcement needed for release 1? If yes, what and

[onap-tsc] [onap-discuss] ONAP Project: Registration for May Developer Event

2017-04-11 Thread Sauvageau, David
Hi Annie & TSC members, I would like to propose some kind of a hackathon during the Developer event in order to really make it a developer-focused event. I believe that architecture, code merger strategy and release planning is definitely required for that session but if we are to regroup 75-10