Just to provide some additional data points to JB's point about contributions that are not code, me (and other PPMC members) have been involved in the Polaris community for quite some time now, and we have been brainstorming ideas and driving important designs to lay a good foundation for the project to grow. Some of the proposals we put up in Apache Iceberg like the one for securable objects [1] are direct outcomes of those discussions with the Polaris community, and were proposed to work with its brand new role based access control model. We would like to continue to work on both Iceberg and Polaris sides to provide a production-ready reference implementation of the Iceberg catalog, and keep driving innovations in the whole data lake/lakehouse/warehouse catalog space through this mechanism.
-Jack [1] https://docs.google.com/document/d/1KmIDbPuN6IYF0nWs9ostXIB9F4b8iH3zZO0hjgs1lm4/edit On Wed, Jul 31, 2024 at 5:26 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Hi > > Project Nessie (https://projectnessie.org/) is a catalog for data > lakes, also implementing the Apache Iceberg REST spec. > Nessie has some unique features like git-inspired data version > control, multi-table transaction, catalog level versioning, etc. > In order to build a larger community and provide a great experience to > users, Nessie community decided to contribute Nessie features in > Polaris. > > Regards > JB > > On Wed, Jul 31, 2024 at 2:18 PM roryqi <ror...@apache.org> wrote: > > > > Just curious. What's the relationship between Nessie and Polaris? > > > > Jean-Baptiste Onofré <j...@nanthrax.net> 于2024年7月31日周三 20:09写道： > > > > > Hi Justin, > > > > > > Thanks for your email. Much appreciated! > > > > > > I agree with the requirements to join the incubator, I share the same > > > vision. > > > > > > The codebase is there, public, under the Apache license. So, I think > > > we are good here :) > > > > > > About the community, it's a small one, but present, vibrant, and eager > > > to grow. We have a lot of enthusiasm around this proposal (and also > > > Polaris open source). I think it would be a great podling. > > > > > > The split between PPMC / ocmmitters is unusual because of the > > > community build goal. The team had a lot of feedback and interest from > > > different parties, including some Apache projects. > > > When I prepared the proposal with the team (that included people > > > listed in the PPMC), we wanted to involve anyone helping the project > > > to grow. It's not necessary code contributions, it's everything to: > > > 1. Help in the design (for instance Jack Ye is helping on the Apache > > > Iceberg REST impl vision) > > > 2. Help to grow the community by including other communities (for > > > instance Anoop proposed to bridge with Apache XTable, John with Apache > > > Kafka, Robert with Project Nessie) > > > 3. Mentor committers and other PPMC (that's my role mostly :)) in > > > addition of the regular mentor. For instance, Tyler could be a great > > > mentor thanks to his experience on Apache Beam. > > > > > > So about the commits: > > > - Polaris started on a private repo at Snowflake including code that > > > it was not possible to push open source (Snowflake specific). So, we > > > had to change the history to remove these commits and have a clean > > > open source codebase > > > - You are right, not all PPMC members have committed on the repo, same > > > about the committers. The reason they are there is that either: > > > 1. Their contributions are not code > > > 2. Their contributions are not yet there, but they plan to > contribute > > > I think it happens pretty often to have people listed in the initial > > > committers without commit (for instance, I think on Gravitino, Ashish > > > Singh is on the initial committer list without a commit afair). > > > > > > I understand your comment, and it's important to me. > > > If it's a concern for you, I'm happy to rework the initial committer > > > list with the team (also removing PPMC list to use the default layout) > > > and grow the PPMC/committers when in the incubator. > > > > > > Thoughts ? > > > > > > Regards > > > JB > > > > > > On Wed, Jul 31, 2024 at 5:47 AM Justin Mclean < > jus...@classsoftware.com> > > > wrote: > > > > > > > > Hi, > > > > > > > > In general, projects joining the incubator need two things: > > > > - A codebase > > > > - a community around it > > > > > > > > While this isn't a hard requirement, building either while in > incubation > > > can be difficult. > > > > > > > > The first issue I see is it’s not clear to me that there is a > community > > > here. > > > > > > > > The split between PPMC / committers is also unusual. > > > > > > > > It also seems there’s a disconnect between the people who have > > > contributed to the project and those on the initial PMC/committer > list. I > > > understand history has been lost. Is there any reason why history > wasn’t > > > preserved? But given it comes from a single vendor, I would assume > that the > > > commits in the new repo would then give an accurate representation of > who > > > is involved from outside that vendor since the plan/announcement to > make it > > > open source. However looking at the commits, 80%+ of the people > involved > > > come from that single vendor which and most of the proposed > PPMC/committers > > > have no activity in the project. How have these people contributed? > > > > > > > > Looking closer, other than jbonofre or snazy, I can see these commits > > > from non-Snowflake people, and that is it. > > > > anoopj - 1 commit (fixing a basic typo) > > > > ajantha-bhat - 2 commits (minor doc changes) > > > > > > > > From the information provided, it seems that a lot of the proposed > PMCs > > > have not been involved with the project at all. Mentors are there to > help a > > > project, adding extra existing PMC members to the PPMC to just help > out is > > > also rather unusual. So both the PPMC/committer split and the > composition > > > seem problematic to me. > > > > > > > > Kind Regards, > > > > Justin > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
