RFC 676: Contributor-Council-Charter.md #679
Conversation
haubles
changed the title
|
|
Co-authored-by: Jason Butz <[email protected]>
| NDA. | ||
| * The five elected community representatives serve one-year terms. There is no limit to the number of subsequent terms a Council member may serve. | ||
| Depending on community input, the AWS CDK team may decide to allocate a certain number of Council seats to specific community groups, such as the | ||
| Open Construct Foundation, or Enterprise Customers. The rest of the seats would be undesignated. |
There was a problem hiding this comment.
A little confused on the wording here. Are these special interest group seats in addition to the five elected members?
| ## Purpose of the Council | ||
|
|
||
| To improve visibility into CDK, increase feedback opportunities, and build a stronger, more inclusive community, the AWS CDK team proposes forming a | ||
| Contributor Council. |
There was a problem hiding this comment.
Was it just the CDK team 100% exclusively?
|
|
||
| 1. **Maintain AWS supportability.** In order for AWS to provide on-call resources tasked with resolving high-impact bugs or issues in CDK for | ||
| customers and the community, AWS must ensure that its standards for processes—for example, security reviews—are met. Therefore, AWS controls | ||
| the CDK release process. |
There was a problem hiding this comment.
How will AWS support the code that is being written by the community that will be part of the library? It seems it needs a lot more people and also it will need to write the code in the first place. If it does'tn have resource to write the code, how can you support the code.
There was a problem hiding this comment.
That is already the case, and I do not understand how that changes due to the council.
| the CDK release process. | ||
| 2. **Increase community influence**. The community’s input and active engagement is essential for the long-term health and success of the CDK | ||
| project. Therefore, AWS is committed to creating more robust and clearly-defined channels for soliciting community feedback, and acting on that | ||
| feedback. We are committed to increasing opportunities and building new processes for accepting more community contributions to the codebase. |
There was a problem hiding this comment.
The community contributions could be placed in an alternative library, that customers, ( i'm thinking of enteprise customers who pay for support ) would know that is not AWS written code.
There was a problem hiding this comment.
That is not how OSS works. What you are advocating for is a source-available product instead.
| feedback. We are committed to increasing opportunities and building new processes for accepting more community contributions to the codebase. | ||
| 3. **Provide visibility into AWS-led initiatives.** We will provide the CDK’s community with visibility into our roadmap and AWS-led contributions. | ||
| We will give the community a voice and a hand in our decision-making processes. We must communicate our roadmaps, plans, and decisions openly and | ||
| promptly, and deliver on them consistently, for the long-term success of CDK. |
There was a problem hiding this comment.
the AWS CDK team, has done this sucessfully in the past.
|
|
||
| The Council will meet monthly to start, but may increase or decrease meeting frequency at its discretion. Similarly, the length of the meetings will | ||
| be determined by the Council and can be increased or decreased at the Council’s discretion. We anticipate Council members will spend less than 5 | ||
| hours a month on Council activities. |
There was a problem hiding this comment.
Will the non AWS people be paid? Will the AWS people do this as part of their job? or is it an extra.
|
|
||
| * The Council will review and debate RFCs/features, feature docs, or new processes brought forth by the CDK community and AWS. AWS may not be able | ||
| to report on all AWS-led projects when we are bound by legal requirements, customer agreements, or when it would put AWS at a competitive | ||
| disadvantage to report on some project. |
There was a problem hiding this comment.
which is the situaiton today.
| * The Council will review and debate RFCs/features, feature docs, or new processes brought forth by the CDK community and AWS. AWS may not be able | ||
| to report on all AWS-led projects when we are bound by legal requirements, customer agreements, or when it would put AWS at a competitive | ||
| disadvantage to report on some project. | ||
| * Anyone in the CDK community may propose topics for discussion by the Council. The agenda is finalized one week before each meeting to allow time |
There was a problem hiding this comment.
need to define community.
| for pre-reading and preparation. Proposers are invited to the meeting to present and advocate for their change. If they are unable to attend, | ||
| their attendance is not required for the Council to make a decision. | ||
| * The Council discusses the change’s appropriateness, merits, scope of work, and whether the change can be community-led or if it will be built by | ||
| internal Amazon resources. |
There was a problem hiding this comment.
if the community dtermines its AWS built does AWS have to build it, or can that be overiden? Surely this is just a request?
| internal Amazon resources. | ||
| * Decisions are completed and recorded through the following mechanism: | ||
| * Each Council member enters an opinion on whether the feature is viable including a short explanation. The opinions and reasons behind them are | ||
| recorded on the change proposal. Opinion submissions follow the [Chatham House Rule](https://www.ibabs.com/en/glossary/chatham-house-rule/#:~:text=The%20Chatham%20House%20Rule%20reads,') |
There was a problem hiding this comment.
Chatham House has as many bad reasons to be avoided as good reasons to be used.
| recorded on the change proposal. Opinion submissions follow the [Chatham House Rule](https://www.ibabs.com/en/glossary/chatham-house-rule/#:~:text=The%20Chatham%20House%20Rule%20reads,') | ||
| by default, though Council members may choose to sign them. | ||
| * If the change is deemed appropriate for inclusion in CDK by the Council, the AWS CDK Product team decides whether the feature will be built by | ||
| AWS and adds it to their feature backlog, or if the feature will be offered to the community for implementation. |
There was a problem hiding this comment.
So really the decision above is just a request
|
|
||
| The Council is led by two Chairpersons. They do not submit opinions in the decision-making process: | ||
|
|
||
| * One Co-Chair and the facilitator of Council sessions will come from the AWS Open Source Strategy & Marketing (OSSM) team. |
There was a problem hiding this comment.
Is this where this entire idea has come from teh OSSM team?
| Amazon will have five permanent members on the Council, which AWS may rotate as necessary. They will represent various AWS teams with vested | ||
| interests in CDK to bring a multiplicity of viewpoints and experiences to Council debate (Engineering, Support, OSSM). | ||
|
|
||
| The community will have five elected members on the Council. |
There was a problem hiding this comment.
Elections bring a lot of un-needed drama. Just appoint them.
| * In order to participate in the full-breadth of conversation related to CDK and the project’s roadmap, Council members will be required to sign an | ||
| NDA. | ||
| * The five elected community representatives serve one-year terms. There is no limit to the number of subsequent terms a Council member may serve. | ||
| Depending on community input, the AWS CDK team may decide to allocate a certain number of Council seats to specific community groups, such as the |
There was a problem hiding this comment.
are the appointed seats in addition or part of the five. This is unclear.
There was a problem hiding this comment.
It is still five, as the AWS seats should not be outnumbered
| Depending on community input, the AWS CDK team may decide to allocate a certain number of Council seats to specific community groups, such as the | ||
| Open Construct Foundation, or Enterprise Customers. The rest of the seats would be undesignated. | ||
| * We expect Council members to regularly attend Council meetings. If a Council member has two unannounced absences in a row, they will be removed | ||
| and the Council will decide how to replace them. |
There was a problem hiding this comment.
if they are elected, you really cant' do this.
|
|
||
| ## What are we launching today? | ||
|
|
||
| Today, AWS announces the formation of a Contributor Council, which will serve as a trusted advisor to AWS on CDK’s vision, direction, and |
There was a problem hiding this comment.
your not launching anything today. This is not a product release. Your asking for feedback on an idea.
There was a problem hiding this comment.
That wording comes from the AWS way of writing these docs. The PR/FAQ
|
|
||
| Today, AWS announces the formation of a Contributor Council, which will serve as a trusted advisor to AWS on CDK’s vision, direction, and | ||
| day-to-day maintenance/management. It marks our first step toward greater engagement and transparency with the entire community on project strategy | ||
| and operations. |
There was a problem hiding this comment.
This entire process has been far from transparent for a lot of people.
| and operations. | ||
|
|
||
| This RFC also kicks off a period of community input about the Council and its Charter, which will last for 30 days. On February 10, 2025, we will | ||
| incorporate the feedback and ratify the Charter by merging it to the CDK repository. |
There was a problem hiding this comment.
all feedback? or just feedback you like
| community. | ||
|
|
||
| We are also sharing our desire to partner with community members and organizations like the Open Constructs Foundation (OCF) to form working groups. | ||
|
|
There was a problem hiding this comment.
This is a good idea. Its much much more what i'd expect AWS to do. Engage with people who have an interest in their product. I suspect if you do this, you'll solve the problem and not create the problems this council will create.
| ## Why should I participate in the Contributor Council? | ||
|
|
||
| The CDK Contributor Council provides an opportunity for community-elected representatives to provide input to and directly influence the AWS | ||
| decision-making process. |
There was a problem hiding this comment.
no more than you can today, by talking to aws. Ulimately this council has zero decision making power but to make recommednations.
|
|
||
| ### Phase One — Community Input | ||
|
|
||
| * This RFC PR kicks off a 30-day period of community input. |
There was a problem hiding this comment.
exept the input started qutie a long time before this
This is a request for comments about the proposed AWS CDK Contributor Council. See Tracking Issue #676 for discussion of the proposal.
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache-2.0 license