Hi Jack, I think it would make sense to convert this to a PR, so it can be version tracked in the future (and that way it avoids another review if the intent is to transitition github)?
Thanks, Micah On Tue, Jun 25, 2024 at 9:07 AM Jack Ye <yezhao...@gmail.com> wrote: > Hi everyone, > > Thanks for the feedback in the bylaws document discussion thread! As > suggested, I have removed all the topics that require further debates, and > created this new doc to serve as the initial version that we can review and > later vote. > > > https://docs.google.com/document/d/1S3igb5NqSlYE3dq_qRsP3X2gwhe54fx-Sxq5hqyOe6I/edit > > I will organize new devlist threads to discuss other topics to amend the > guidelines step by step, once this initial version is in. > > A few additional changes that I have already incorporated: > 1. modified the name from "bylaws" to "community guidelines", following > the latest ASF guideline > 2. renamed "lazy majority" and "lazy 2/3 majority" to "majority approval" > and "2/3 majority approval" > 3. changed "Propose Removing Committer", "Propose Removing PMC Member" to > consensus approval, and added "Propose PMC Chair Change" decision following > the default Apache project community guidelines. > 4. changed "Release Product" voting period to 5 days instead of 3 days > excluding weekends. > 5. clarified the copyright of code in Apache Iceberg codebases > > The most important thing is probably to agree upon the 2/3 majority > approval for modifying the project guidelines, so we can have a consistent > voting method going forward. This initial introduction of the bylaws will > be voted using consensus approval. > > Please take a look and comment about any additional changes needed, and I > will host a vote in 3 days. > > Best, > Jack Ye > > > > >
