Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TSC] What do we need from other communities and when #1475

Closed
rabi-abdel opened this issue Apr 15, 2020 · 2 comments · Fixed by #1478
Closed

[TSC] What do we need from other communities and when #1475

rabi-abdel opened this issue Apr 15, 2020 · 2 comments · Fixed by #1478
Labels
Archive Archive Item

Comments

@rabi-abdel
Copy link
Collaborator

https://wiki.opnfv.org/display/DEV/Working+Progress+Page
Basic topics includes project allocation, release management, issue tracking. I think currently CNTT may consider these as OPNFV’s things, however without figuring out what CNTT requires, OPNFV can hardly make any movement. Taking release management as an example. CNTT currently release documents 4 times a year, however RI and RC release can be confusing since it is not bounded to a certain OPNFV release (OP

@ASawwaf
Copy link
Collaborator

ASawwaf commented Apr 28, 2020

@rabi-abdel , we need to cover all other communitieSS , with different coverage for CNTT

for sure CNTT-OPNFV mapping/dependency is huge but on the other side, we need to have a wide view on others as we start with TIP

So this PR is good to have a clear interlocking between all SDO ( Input -Output )

@rabi-abdel
Copy link
Collaborator Author

@ASawwaf Yes, I think we can tackling them one by one.

@rabi-abdel rabi-abdel added the Archive Archive Item label May 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Archive Archive Item
Projects
None yet
2 participants