-
Notifications
You must be signed in to change notification settings - Fork 62
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
Steering Group Structure #356
Comments
I like the balance proposed here. I'll take it a step further and propose that the middle seat have two strict criteria— both that they are employed by an FSI and an active member of CCC (according to the CCC roles definition). We can tap FINOS for support filling the seats. |
@eddie-knight - in a table, have a got this right or did you mean seats 4/5/6 for the strict criteria that they are employed by an FSI and an active member of CCC (according to the CCC roles definition). Do we want the FI to also be FINOS member? If you did are we then have 4 FSI SteerCo members which I think is the wrong balance? |
Also do we want to put any additional criteria on CSP/Open seats? e.g FINOS membership? I think 2 of each should be for FINOS members. |
Your table captures what I was going for. We can have the entire steerco limited to FINOS members for all I care– I don't think it hurts anything, and it'll help to ensure steerco members have buy-in from their companies. |
okay @eddie-knight - lets get some input from @abdullahgarcia |
This issue was discussed on today's community call. The precise structure of the SteerCo is not yet determined, but the adoption of a SteerCo was decided by unanimous vote. |
Discussion with @eddie-knight today on the all project meeting on Steering Group.
My suggestion was that the steering group should consist of both CSP/Tech companies and FI's. Unlike CCC the ratio should be weighted towards CSP's / Tech firms.
For example with a seven member SteerCo
Three seats reserved for CSP's
Three Seats open to all
One seat reserved for FI (preferably with CCC connection).
@abdullahgarcia @eddie-knight - Comments please?
The text was updated successfully, but these errors were encountered: