Thanks for raising this Patrick. The CEP concept is still new and it was intentional that it would evolve more as CEPs came in. I've got some feedback and questions inline.
> Last week in our Cassandra Kubernetes SIG it was clear that we are coming > up on the completion of the specifications for CEP-2. The path we on look > something like this: > > - Agree to the overall specifications for a Cassandra Kubernetes Operator > with as much details as possible on the required features. > - One or more groups donating code as an initial commit. > - Jira and commit activity on common Cassandra Kubernetes operator. > > The two main questions that have come up as a result: > > 1. What constitutes a completed CEP? Is this something the PMC votes on or > how does this get approved as a part of the project My understanding so far is that a CEP shall have a lifecycle something like: draft -> raised -> discussion -> proposed -> accepted - > implementing -> done And it sounds like you are closing in the draft phase and raising it for further discussion? (Though there's some overlap between "draft -> raised" and "discussion -> proposed", hopefully that ambiguity is less of a concern when the lifecycle is seen as flexible and re-iterative, i.e. not waterfall.) Part of the CEP's proposal should be (imho)… - what groups are going to donate what code, - what is the initial scope and goal, - how those donated code bases are going to go through the IP Clearance process, - list of people that are: authors, have been involved, and/or identified as stakeholders. Again this is but my opinion, but the current proposal of "A new repository as a sub-project for Apache Cassandra specifically for a Kubernetes Operator" is too thin/ambiguous (despite all the great work that's been done behind it). If making the proposal something more concrete is difficult, maybe it would be better to include a prototype (or initial codebase) as part of CEP-2, giving folk something more concrete, and some proven code collaboration, to vote on and accept. So… Is the plan that separate codebases will be cleared and donated, and then within a Cassandra sub-project merged together? Or shall these multiple projects be worked on outside of the project, and form part of the CEP's proposal and then be cleared and donated? Can/Should the "Cassandra Kubernetes Operator SIG" confluence doc be a subpage to the CEP-2 page? And can we also get a brief agenda and summary of the meetings? (Recorded meetings lack searchability or easy referencing.) > 1. What constitutes a completed CEP? Is this something the PMC votes on or > how does this get approved as a part of the project Good question. To date the CEP requires a [DISCUSS] ML thread (on the finish defined proposal) and then a [VOTE] ML thread. Consensus is required on the vote. > 2. What are the procedures for code donation at this scale? It's likely > that more than one group will be participating with a large amount of code. Code donations need to go through the Incubator's IP Clearance process. https://incubator.apache.org/ip-clearance/ cheers, Mick --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
