Hi DeWayne,
I am interested in and already committed to contributing to this project.
I am afraid that I am confused since there are two alternatives on the proposal
page, but it said in release 1 the project will only demonstrate option 1( Only
depend on App-C project)
Since we are interested in contributing option 2, I doubt it is still open for
discussion? Or shall we document it in a separate project proposal instead?
Best Regards
Maopeng
原始邮件
发件人： ＜[email protected]＞
收件人： ＜[email protected]＞
日 期 ：2017年05月15日 01:32
主 题 ：[onap-tsc] Service Orchestrator project proposal
ONAP TSC, We would like to formally propose the SO (Service Orchestrator)
project for ONAP. The proposal wiki page, which includes details of the project
description, project scopes, and proposed repo names, can be found at:
https://wiki.onap.org/display/DW/Service+Orchestrator. The SO team consists
of representatives from Cloudify, AT&T, Huawei, China Mobile, Ericsson, Orange,
Amdocs, Nokia, and ZTE.
Thanks,
DeWayne Filppi
Director Solution Architecture
Gigaspaces/Cloudify
[email protected]
714.512.1706
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc
