Hi Gildas, Keep in mind that the in the charter we "approve" projects, not "approve projects" for a release. Once a project is approved, then it can indicate its desire to be part of a release. Hence, "approved projects for Beijing release" can create confusion and should be avoided.
BR, Steve From: Gildas Lanilis [mailto:gildas.lani...@huawei.com] Sent: 06 December 2017 19:34 To: Stephen Terrill <stephen.terr...@ericsson.com>; onap-tsc@lists.onap.org P <onap-tsc@lists.onap.org> Subject: RE: Project part of Wiki Hi, Thanks for bringing this up. Definitely, as we keep moving by adding new Projects and new Releases, we will need to get organized in presenting this properly. See my comments inline. Thanks, Gildas ONAP Release Manager 1 415 238 6287 From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Stephen Terrill Sent: Wednesday, December 06, 2017 2:56 AM To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> P <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: [onap-tsc] Project part of Wiki Hi, There is one topic that I wanted to raise for discussion. In the ONAP Wiki, where we have the ONAP projects; we have three parts sections: * "Projects for Beijing Release" [Gildas] available here<https://wiki.onap.org/display/DW/Projects+for+Beijing+Release>. This list summarizes the projects that had a project proposal approved for Amsterdam Release and wish to participate into Beijing Release. * "Approved projects for Amsterdm Release". [Gildas] available here<https://wiki.onap.org/display/DW/Approved+Projects+for+Amsterdam+Release>. This list all projects that have been approved to be a part of the ONAP Platform. This list was created as the project proposal were approved back in June during Beijing F2F. * "deffered/depreicated" etc. [Gildas] These lists are currently empty and are placeholder for historic purposes. We should in the wiki the history of projects and which release(s) they have contributed into. However, we have two lifecycles in ONAP. The projects have a lifecyle; and then we have the release lifecycle. This means that: * We have approved projects irrespective of a release. * Of these, projects that will contribute into the release. For this purpose, I consider at appropropriate that we have in the same list an item of "Approved projects" - Which is really the "Aproved projects for Amsterdam Release". This is where we have all of the approved projects, irrespective of the release. Then we can have a list of the projects in each release. This is where we have the projects that will contribute to that particular release. Thoughts? [Gildas] As we will review the 10 New Project Proposal<https://wiki.onap.org/display/DW/Proposed+Projects> during next week F2F, I will create a page "Approved projects for Beijing Release". That will define the project scope for Beijing. Independently of their release contribution, we can create a list of all approved projects. BR, Steve [Ericsson]<http://www.ericsson.com/> STEPHEN TERRILL Technology Specialist DUIC, Systems and Technology Development Unit IP & Cloud Business Unit, IT & Cloud Products Ericsson Ericsson R&D Center, via de los Poblados 13 28033, Madrid, Spain Phone +34 339 3005 Mobile +34 609 168 515 stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com> www.ericsson.com<http://www.ericsson.com> [http://www.ericsson.com/current_campaign]<http://www.ericsson.com/current_campaign> Legal entity: Ericsson EspaƱa S.A, compay registration number ESA288568603. This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer<http://www.ericsson.com/email_disclaimer>
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc