jbonofre commented on code in PR #9932: URL: https://github.com/apache/iceberg/pull/9932#discussion_r1525150129
########## site/docs/contribute.md: ########## @@ -46,6 +46,42 @@ The Iceberg community prefers to receive contributions as [Github pull requests] * If a PR is posted for visibility and isn't necessarily ready for review or merging, be sure to convert the PR to a draft +## Apache Iceberg Improvement Proposals + +### What is an improvement proposal? + +An improvement proposal is a major change to Apache Iceberg that may require changes to an existing specification, creation +of a new specification, or significant changes to any of the existing Iceberg implementations. Changes that are large in +scope need to be considered carefully and incorporate feedback from many community stakeholders. + +### What should a proposal include? + +1. A GitHub issue created using the `Apache Iceberg Improvement Proposal` template +2. A document including the following: + * Motivation for the change + * Implementation proposal + * Breaking changes/incompatibilities + * Alternatives considered +3. A discussion thread initiated in the dev list with the Subject: '[DISCUSS] <proposal title\>' + +### Who can submit a proposal? + +Anyone can submit a proposal, but be considerate and submit only if you plan on contributing to the implementation. + +### Where can I find current proposals? + +Current proposals are tracked in GitHub issues with the label [Proposal][iceberg-proposals] + +### How are proposals adopted? + +Once general consensus has been reached, a vote should be raised on the dev list. The vote follows the ASF Review Comment: Yeah, I agree for spec/major change. My question was more for proposed new features. But yeah, better to have a vote. I'm just a little bit concerned by potential veto vote. Imagine if we have only +1 and just one -1 from a PMC member, the change/addition can be vetoed. But you are right, we should work on consensus before the vote :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
