nevzheng commented on issue #3680:
URL: https://github.com/apache/iceberg-rust/issues/3680#issuecomment-6831316075
I'd like to propose one more item for Q4:
### Define the proposal / RFC lifecycle
**The ask**
- A tracking issue and discussion, with the outcome being a short doc in the
contributor guide.
- Interested so far: @nevzheng, @mbutrovich, @liurenjie1024, @dannycjones.
Anyone else is welcome.
- Why now: RFCs live as PRs under `docs/rfcs/`, but we haven't agreed on
when one is needed, when it merges or closes, or how it relates to the
implementation afterwards.
- #2183 (client-side encryption) is still open even though the feature has
shipped.
- The file format RFC from earlier this year raises the same question as
that work moves forward: what happens to the RFC next?
**Questions I think the discussion should answer (with my current leanings)**
- What is an RFC for?
- I see it as an alignment tool and a record, as well as a design:
authors, contributors and maintainers agree on direction before the work starts.
- When is one needed?
- My lean: maintainer discretion, with L / XL / XXL changes as a rough
guideline. Smaller changes can rely on good issues and PR descriptions.
- Asking for one should be lightweight. A maintainer or reviewer should be
able to say something as simple as:
> "Hey, I'm having a hard time understanding the goal here. Could we get
an RFC/proposal and an issue to align on this? Thanks!"
- How detailed should it be up front?
- My lean: start high level, and leave room for detailed design appendices
and discussion as follow-ups or as the project progresses. Spark's SPIP is one
model: https://spark.apache.org/improvement-proposals.html
- When does it merge or close, and what happens when the implementation
diverges?
- No strong view yet. Renjie's point from the sync, that divergence is
normal, seems like the right starting assumption.
Happy to help draft a first pass.
Sent from my 🤖 (Claude, Opus 5.5 + Fable 5.2) Nevin
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]