Thanks Jiashu for kicking off the discussion.

+1 from my side.

Best,
Yuxin


Yu Li <[email protected]> 于2024年5月29日周三 14:17写道:

> +1. Thanks for the efforts, Jiashu!
>
> Best Regards,
> Yu
>
> On Wed, 29 May 2024 at 13:55, Xintong Song <[email protected]> wrote:
> >
> > Big +1! Thanks for bringing this up, Jiashu.
> >
> > From my experiences with Apache Flink / Paimon, the wiki-based proposal
> > management works quite well.
> >
> > Another important improvement that I see in the CIP process is that it
> > enforces a public discussion and a formal vote on mailing list for
> > important changes to the project. I think this is a good practice of
> > open-communication and consensus decision making of the Apache Way.
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Wed, May 29, 2024 at 11:19 AM rexxiong <[email protected]> wrote:
> >
> > > Hello, Celeborn community,
> > >
> > > In the past, when Celeborn introduced new major features or significant
> > > changes, we typically used Google Docs to launch proposals. However, a
> > > major issue with Google Docs is the difficulty in centrally managing
> these
> > > proposals. Therefore, after referring to other communities and based on
> > > discussions with several PMCs offline, it appears that Apache
> Confluence
> > > could be a viable alternative for our needs. With that in mind, I would
> > > like to invite all of you to share your thoughts, experiences, and
> > > preferences regarding the use of Apache Confluence versus Google Docs
> for
> > > our proposal management. Your feedback will be invaluable in helping us
> > > make an informed decision that best meets the needs of our community.
> > >
> > > Meanwhile, I have archived previous proposals and written the Celeborn
> > > Improvement Proposal (CIP) process
> > > <
> > >
> https://cwiki.apache.org/confluence/display/CELEBORN/Celeborn+Improvement+Proposals
> > > >
> > > on Confluence.
> > >
> > > What do you think? Looking forward to your thoughts on this proposal.
> > >
> > >
> > > Thanks,
> > > Jiashu Xiong
> > >
>

Reply via email to