Re: [onap-tsc] Project part of Wiki

2017-12-09 Thread Ramki Krishnan 
In the Cloud Native world, in open source efforts such as Kubernetes, all new 
*proposed* project proposals have to go through a *incubation* phase 
(https://github.com/kubernetes/community/blob/master/incubator.md) before 
becoming an *approved* project. The proposed project proposals either graduate, 
merge or retire based on well specified criteria described in the 
aforementioned link.

This process is something for us to think about as we are approving new ONAP 
projects.

--
Thanks,
Ramki

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Christopher Donley (Chris)
Sent: Wednesday, December 6, 2017 9:33 AM
To: eric.deb...@orange.com; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Project part of Wiki

I think we should have four sections for projects:

  *   Draft (a sandbox for developing proposals)
  *   Proposed (for TSC review - once someone sends the required email to the 
TSC)
  *   Approved (all currently approved projects, independent of releases)
  *   Closed (all projects that have completed, been abandoned, etc.)
This should be independent of participation in any release, and would make it 
easy to find projects.

Perhaps we could track projects participating in the release under the Releases 
section (not project section), such as on the Release Status page 
(https://wiki.onap.org/display/DW/Release+Status<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Release-2BStatus=DwMFAg=uilaK90D4TOVoH58JNXRgQ=bCmYL3bSEMwtZqPWSHINtvRWIlUeuM66MeOgvaAueQU=jPD5uUcSljiF7HnkEwBSvY9wuvjuDTM8NK7nIbQlPVk=mkFxvGsQYvejXBGPij6yI8YByjVyxRvwje6Sn5pwqF0=>).

Chris

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of 
eric.deb...@orange.com<mailto:eric.deb...@orange.com>
Sent: Wednesday, December 06, 2017 8:39 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] Project part of Wiki

Hello

I think the Wiki should only list the projects for Beijing Release.

The list of projects per (old) release should only be described on the 
Readthedocs.

Best Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Project part of Wiki

2017-12-07 Thread Stephen Terrill 
Hi Gildas,

Great work.  As usual, your responsiveness is impressive.

BR,

Steve

From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: 07 December 2017 01:06
To: Stephen Terrill ; onap-tsc@lists.onap.org P 

Subject: RE: Project part of Wiki

Hi Steve,

I have updated the wiki accordingly to reflect this discussion.

Under the top "ONAP Project" section, there is a link toward the list of 
"Approved Projects". This list is independent of any release. Next week during 
Santa Clara F2F, as new project proposal will be approved, I will update the 
"Approved Projects".

Also, under the top "Release Planning and Management" section, there are 2 
links:

  1.  "Project Status in Amsterdam Release", that provides the list of projects 
part of Amsterdam as well as their status at each milestones.
  2.  "Project Status in Beijing Release", that provides the list of projects 
part of Beijing. Currently, for these project I have provided a link toward 
their Intention to participate into Beijing.

Hope this helps and brings clarity. Let me know if you have any question, I 
will be glad to help.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Wednesday, December 06, 2017 1:57 PM
To: Gildas Lanilis 
>; 
onap-tsc@lists.onap.org P 
>
Subject: RE: Project part of Wiki

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 
>; 
onap-tsc@lists.onap.org P 
>
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] On Behalf Of Stephen Terrill
Sent: Wednesday, December 06, 2017 2:56 AM
To: onap-tsc@lists.onap.org P 
>
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. 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. 
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 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]
STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid,

Re: [onap-tsc] Project part of Wiki

2017-12-06 Thread Gildas Lanilis 
Hi Steve,

I have updated the wiki accordingly to reflect this discussion.

Under the top "ONAP Project" section, there is a link toward the list of 
"Approved Projects". This list is independent of any release. Next week during 
Santa Clara F2F, as new project proposal will be approved, I will update the 
"Approved Projects".

Also, under the top "Release Planning and Management" section, there are 2 
links:

1)  "Project Status in Amsterdam Release", that provides the list of 
projects part of Amsterdam as well as their status at each milestones.

2)  "Project Status in Beijing Release", that provides the list of projects 
part of Beijing. Currently, for these project I have provided a link toward 
their Intention to participate into Beijing.

Hope this helps and brings clarity. Let me know if you have any question, I 
will be glad to help.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Wednesday, December 06, 2017 1:57 PM
To: Gildas Lanilis ; onap-tsc@lists.onap.org P 

Subject: RE: Project part of Wiki

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 
>; 
onap-tsc@lists.onap.org P 
>
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] On Behalf Of Stephen Terrill
Sent: Wednesday, December 06, 2017 2:56 AM
To: onap-tsc@lists.onap.org P 
>
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. 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. 
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 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]
STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com
www.ericsson.com


[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

Re: [onap-tsc] Project part of Wiki

2017-12-06 Thread Michael O'Brien 
The Amsterdam project page is where all the "live" ongoing Beijing projects are 
(content, meeting minutes, design pages, Beijing epic pages...)- we should just 
move them over to Beijing - as I agree it is odd to go into the Amsterdam 
folder.



From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of HU, BIN
Sent: Wednesday, December 6, 2017 13:35
To: Christopher Donley (Chris) <christopher.don...@huawei.com>; 
eric.deb...@orange.com; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Project part of Wiki

Here is how OPNFV manages wiki page of projects, and layout is as follows:

*OPNFV Projects

*Project ABC's<https://wiki.opnfv.org/display/DEV/Projects+Abc> page 
helps you understand how we run projects and coordinate our activities in OPNFV

*OPNFV Project 
Lifecycle<http://www.opnfv.org/developers/technical-project-governance/project-lifecycle>
 page describes the project categories and lifecycle management

*Project 
Directory<https://wiki.opnfv.org/display/PROJ/Project+Directory> page lists all 
current projects that are approved by Technical Steering Committee

*Project 
Proposals<https://wiki.opnfv.org/display/PROJ/Project+Proposals> page lists all 
newly proposed projects, which are pending community review and / or TSC 
approval

*See the Project Proposal 
Template<https://wiki.opnfv.org/display/PROJ/Template>

*See the 
Checklist<https://wiki.opnfv.org/display/DEV/Project+Proposal+Creation+Review+Checklist>
 for project proposal & creation review.

*See the Project Wiki Page 
Template<https://wiki.opnfv.org/display/DEV/Project+Page+Template> for creating 
your project wiki page once the proposal is approved by TSC

*Cross Collaboration Group

*Security Group<https://wiki.opnfv.org/display/security/Security+Home>

*Archived 
Projects<https://wiki.opnfv.org/display/PROJ/Archived+Projects>

Just some food for thoughts on this topic.
Thanks
Bin

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Christopher Donley (Chris)
Sent: Wednesday, December 06, 2017 9:33 AM
To: eric.deb...@orange.com<mailto:eric.deb...@orange.com>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Project part of Wiki

I think we should have four sections for projects:

*Draft (a sandbox for developing proposals)

*Proposed (for TSC review - once someone sends the required email to 
the TSC)

*Approved (all currently approved projects, independent of releases)

*Closed (all projects that have completed, been abandoned, etc.)
This should be independent of participation in any release, and would make it 
easy to find projects.

Perhaps we could track projects participating in the release under the Releases 
section (not project section), such as on the Release Status page 
(https://wiki.onap.org/display/DW/Release+Status<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Release-2BStatus=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=jdpy75e0Q1BZlEOux3J4s-3_sGQG-gA2yOCot9yUwEQ=lG7sVpcOZBrpkXqvuwPlVUp3yvbKws01qZQfj_YvFAA=>).

Chris

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of 
eric.deb...@orange.com<mailto:eric.deb...@orange.com>
Sent: Wednesday, December 06, 2017 8:39 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] Project part of Wiki

Hello

I think the Wiki should only list the projects for Beijing Release.

The list of projects per (old) release should only be described on the 
Readthedocs.

Best Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
This message and the information contained herein is proprietary and 
confidential

Re: [onap-tsc] Project part of Wiki

2017-12-06 Thread Stephen Terrill 
Hi,

One final comment on this - the charter states the following:

Note 1: Project proposals are posted in the "Proposed Projects" section of the 
ONAP wiki.  Approved projects are posted to the "Approved Projects" section of 
the ONAP wiki.

Note 2: The proposal submitter can decide to remove projects in "proposal" 
state that do not progress to incubation state.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
Sent: 06 December 2017 23:00
To: eric.deb...@orange.com; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Project part of Wiki

Hi,

Just keep in mind, approved projects exist irrespective of the release.  If we 
took the approach of only describing projects for the X release, then new 
projects that are not part of the release will not be visible.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of 
eric.deb...@orange.com<mailto:eric.deb...@orange.com>
Sent: 06 December 2017 17:39
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] Project part of Wiki

Hello

I think the Wiki should only list the projects for Beijing Release.

The list of projects per (old) release should only be described on the 
Readthedocs.

Best Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Project part of Wiki

2017-12-06 Thread Stephen Terrill 
Hi,

Just keep in mind, approved projects exist irrespective of the release.  If we 
took the approach of only describing projects for the X release, then new 
projects that are not part of the release will not be visible.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of eric.deb...@orange.com
Sent: 06 December 2017 17:39
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Project part of Wiki

Hello

I think the Wiki should only list the projects for Beijing Release.

The list of projects per (old) release should only be described on the 
Readthedocs.

Best Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Project part of Wiki

2017-12-06 Thread Stephen Terrill 
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 ; onap-tsc@lists.onap.org P 

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] On Behalf Of Stephen Terrill
Sent: Wednesday, December 06, 2017 2:56 AM
To: onap-tsc@lists.onap.org P 
>
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. 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. 
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 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]
STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com
www.ericsson.com


[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

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Project part of Wiki

2017-12-06 Thread Gildas Lanilis 
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] 
On Behalf Of Stephen Terrill
Sent: Wednesday, December 06, 2017 2:56 AM
To: onap-tsc@lists.onap.org P 
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. 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. 
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 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]
STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com
www.ericsson.com


[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

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Project part of Wiki

2017-12-06 Thread Christopher Donley (Chris) 
I think we should have four sections for projects:

*Draft (a sandbox for developing proposals)

*Proposed (for TSC review - once someone sends the required email to 
the TSC)

*Approved (all currently approved projects, independent of releases)

*Closed (all projects that have completed, been abandoned, etc.)
This should be independent of participation in any release, and would make it 
easy to find projects.

Perhaps we could track projects participating in the release under the Releases 
section (not project section), such as on the Release Status page 
(https://wiki.onap.org/display/DW/Release+Status).

Chris

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of eric.deb...@orange.com
Sent: Wednesday, December 06, 2017 8:39 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Project part of Wiki

Hello

I think the Wiki should only list the projects for Beijing Release.

The list of projects per (old) release should only be described on the 
Readthedocs.

Best Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Project part of Wiki

2017-12-06 Thread Vul, Alex 
Eric,

What is the motivation for this? What problem are you trying to solve? I think 
it would be good to archive old projects and their supporting materials on the 
Wiki, in a separate place from the Beijing projects, in case we want to 
reference them or refer to them in the future. I don't see how that harms 
anything...

Alex Vul
Intel Corporation



From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of nagaraja s.r
Sent: Wednesday, December 6, 2017 9:02 AM
To: eric.deb...@orange.com; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Project part of Wiki

+1


From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of 
eric.deb...@orange.com<mailto:eric.deb...@orange.com>
Sent: Wednesday, December 6, 2017 10:09 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] Project part of Wiki

Hello

I think the Wiki should only list the projects for Beijing Release.

The list of projects per (old) release should only be described on the 
Readthedocs.

Best Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Project part of Wiki

2017-12-06 Thread nagaraja s . r 
+1


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of eric.deb...@orange.com
Sent: Wednesday, December 6, 2017 10:09 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Project part of Wiki

Hello

I think the Wiki should only list the projects for Beijing Release.

The list of projects per (old) release should only be described on the 
Readthedocs.

Best Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Project part of Wiki

2017-12-06 Thread Phil Robb 
+1 to your suggestion Stephen.

Phil.

On Wed, Dec 6, 2017 at 4:55 AM, Stephen Terrill <
stephen.terr...@ericsson.com> wrote:

> 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”
>- “Approved projects for Amsterdm Release”.
>- “deffered/depreicated” etc.
>
>
>
> 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?
>
>
>
> BR,
>
>
>
> Steve
>
>
>
>
>
>
>
> [image: Ericsson] 
>
> *STEPHEN TERRILL *
> Technology Specialist
> DUIC, Systems and Technology
> Development Unit IP & Cloud
>
> Business Unit, IT & Cloud Products
>
>
> *Ericsson*
> Ericsson R Center, via de los Poblados 13
> 28033, Madrid, Spain
> Phone +34 339 3005
> Mobile +34 609 168 515 <+34%20609%2016%2085%2015>
> stephen.terr...@ericsson.com
> www.ericsson.com
>
>
>
> [image: 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
>
>
>
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc
>
>


-- 
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc