I've seen other projects following a more formal process to propose change -- Kafka's got KIP (Kafka Improvement Proposal), YuniKorn's got YIP, Spark: SPIP, Pulsar: PIP, RocketMQ: RIP, and I think it makes sense.
Having design docs in Markdown format isn't a barrier. There are tools to convert Google Docs to Markdown. But Google Docs are great for brainstorming and interactive editing. I'd rather have half baked design ideas up for discussion before having a "frozen" version attached in a pull request. On Sat, Mar 15, 2025 at 12:59 PM Abhishek Pal < pal.abhishek03012...@gmail.com> wrote: > Thanks Attila for your input. > While this has been there - I am not sure if it is being actively followed. > > I think it might be better in such a case, to enforce checks for design > changes so that devs mandatorily update design docs as part of such PRs. > > Thanks > > On Sat, 15 Mar 2025 at 23:43, Attila Doroszlai <adorosz...@apache.org> > wrote: > > > Hi Wei-Chiu, Abishek, > > > > We had this process [1] for a few years now that design docs should be > > created as markdown in hadoop-hdds/docs/content/design via pull > > request (some examples at [2]). Rendered versions are available on > > the website [3]. > > > > [1] > > > https://ozone.apache.org/docs/edge/design/ozone-enhancement-proposals.html > > [2] > > https://github.com/apache/ozone/pulls?q=is%3Apr+is%3Aopen+label%3Adesign > > [3] https://ozone.apache.org/docs/edge/design.html > > > > -Attila > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org > > For additional commands, e-mail: dev-h...@ozone.apache.org > > > > >
