Hi Pulsar Community, In an effort to make our Pulsar Community Meeting accessible to those who cannot make the meeting, I will start sending the meeting notes to this list.
Disclaimer: I am the main author of these notes. I took the notes while participating in the meeting discussions. It is possible that I missed or misunderstood information. If something is misattributed or misrepresented, please send a correction to this list and consider updating the Google doc. Source google doc: https://docs.google.com/document/d/19dXkVXeU2q_nHmkG8zURjKnYlvD96TbKf5KjYyASsOE I generated the notes by downloading the google doc and running the following command: pandoc --columns 72 -t plain \ ~/Downloads/Apache\ Pulsar\ Community\ Meeting\ Minutes.docx | \ perl -pi -0 -w -e "s/\n\n/\n/g" |less Our community meetings are recorded. I don't have a link to the recordings yet. Once I get that link, it'd be great to include that link in this summary for anyone who wants to listen to the original conversation. Thanks, Michael Notes: 2022/03/03, (8:30 AM PST) - Attendees: - Matteo - Michael - Dave - Lari - Christophe - Max - Andrey - AI (from the previous meeting) - ... - Agenda (Add the items you want to discuss below) - Discussions - How to take notes for community meetings (Michael) - Considered using Pulsar Wiki for distribution, but those present agreed that Google doc’s collaboration features are too valuable to lose. - Lari proposed using https://pandoc.org/ to convert notes from Google doc to well formed plaintext that will be easy to deliver on dev mailing list. - Michael to start sending community meeting notes to dev mailing list - How to handle NIC configuration (Michael) - Fail fast and Matteo agrees with that we can change to fail on start up (see https://github.com/apache/pulsar/pull/14537) - PIP 47 and clarification about linear upgrades (Michael) - We have some backwards compatibility tests, but Matteo is concerned that it is hard for guaranteeing the down grading when upgrading from past 4 versions as PIP 47 says should be possible. - We’d need more compatibility tests if we wanted to support the letter of PIP 47. - Linear upgrades is also how bookkeeper works, and Pulsar upgrades the bookkeeper in accordance. - Dave asked about the implication that users might need to upgrade linearly 3 or 4 times a year. Proposes making 2.7 an LTS and ensuring that users can go from 2.7 to 2.10 a possible upgrade/downgrade scenario for testing. An LTS could come with extra testing. Matteo raised a concern about an LTS delaying feature adoption by up to a year. Michael points out that these are trade offs dependent on prioritizing feature velocity. No conclusion reached regarding creating an LTS version. - The road map for future features–what is next for 2.11 (Dave) - Lari is interested in pushing PIP 62 through to completion. There is the Pulsar IO component and the Trino/Pulsar SQL component. Lari suggests that we could move forward with the original plan to just move the components out of the main repo, even though that will be temporary work. Matteo mentions that we could keep it in the repo but bundle it separately when creating distributions of Pulsar. Matteo also mentioned that there isn’t currently a centralized road map for future features. - Lari asks about the Docker repo and the limited number of users that can push docker images to the official “apachepulsar” repo. - Matteo: Docker dropped the number of accounts from 10 to 3. We’re grandfathered in with 10 currently, but adding a new one would trigger the new limit. Dave asks about switching to Apache artifactory. Discussed some tradeoffs, no conclusion reached. - Christophe asked about creating a Pulsar BOM and some of the implementation details of how to implement the BOM. - PIPs - - PRs - …...
