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

[CSO Ch03] Preventing fragmentation due to large org structure #478

Open
jbeltranatl opened this issue Oct 29, 2019 · 0 comments
Open

[CSO Ch03] Preventing fragmentation due to large org structure #478

jbeltranatl opened this issue Oct 29, 2019 · 0 comments

Comments

@jbeltranatl
Copy link
Collaborator

Re: Org structure - We are a little bit worried that this many groups may fragment the community too much (number of meetings, etc.). One way could be to combine RA1 Core and RA1 Ops, RA2 Core and RA2 Ops, RI1 Core and RI1 Dev. Shouldn't RI and RC groups be represented in OPNFV directly, using the already existing structures there instead of in CNTT? (Note: To be defined in Overall Structure of CNTT.)

@rabiabdel rabiabdel added this to the Snezka milestone Nov 5, 2019
@rabiabdel rabiabdel added this to To Do in Governance - Overall Steering via automation Feb 11, 2020
@rabi-abdel rabi-abdel removed this from the Snezka milestone Feb 11, 2020
@rabi-abdel rabi-abdel added this to the M3 (Freeze Contributions) milestone Feb 25, 2020
@rabi-abdel rabi-abdel removed this from the M3 (Freeze Contributions) milestone Apr 29, 2020
@project-bot project-bot bot moved this from To Do to Backlog in Governance - Overall Steering May 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

4 participants