A modern programming language that makes developers happier.

kotlinlang

image.png

*AI Meeting notes from last week's meeting:*

*Quick recap*
The team met to discuss a potential collaboration with JetBrains on the Kotlin LSP project, exploring open-source features and navigating the project's closed-source components while addressing coordination challenges across different time zones. They discussed various implementation options for their project, including forking existing repositories or building from scratch, with plans to create a Google document to outline all possibilities. The team also addressed logistics around meeting times and repository management, with Hemram agreeing to continue research while the group works on finalizing their approach.

*Next steps*
• Shauvik to obtain Jetbrains license for Hemram for the commercial IntelliJ product.
• Shauvik to follow up with Jetbrains to get a representative to join the next meeting.
• Shauvik to create a survey in the Slack channel for preferred meeting times.
• Team to create a Google document listing all options for the project, including scope, advantages, and disadvantages.
• Andrew to share his notes on possible options, implementations, and feature priorities.
• Hemram to continue research on the different repository options.
• Team to make a decision on which repository option to pursue, potentially offline before the next meeting.
• Team to consolidate future discussions in the chosen GitHub repository once a decision is made.
*Summary*
Uber Engineer Introduces to Team
Matt, an engineer from Uber's New York office specializing in Android and Kotlin, introduced himself to the team. Shauvik and Idan discussed Idan's visit to JetBrains' office, but the conversation was cut off as Shauvik checked for another room and Andrew joined.
Kotlin LSP Collaboration Exploration
The team discussed a potential collaboration with JetBrains on the Kotlin LSP project, which is partially open-sourced. They explored the possibility of working on specific open-source features, such as a debugger, while navigating the complexities of the project's closed-source components. Shauvik proposed obtaining a license for Hemram to access IntelliJ, which would help in understanding the project scope. The team agreed to follow up with JetBrains for more details and to clarify logistics around the project's open-source components.

*Time Zone Coordination Challenges*
The meeting discussed coordination challenges due to time zone differences, particularly between European and Indian participants. Shauvik noted that a JetBrains representative couldn't attend due to holiday conflicts but would try to reschedule them for the next meeting. The group discussed potential collaboration with Brex, who had previously sponsored the initiative. Hemram expressed flexibility with meeting times, and Shauvik suggested conducting a survey in the channel to find a mutually convenient time zone for future meetings.

*Project Implementation Strategy Discussion*
The team discussed options for their project implementation, including forking existing repositories or building from scratch. Shauvik suggested creating a Google document to outline all options, their pros and cons, and potential trade-offs, allowing the team to make a decision in the next meeting. Andrew mentioned sharing his notes on possible implementations and feature priorities, while Saskota? recommended centralizing discussions in a single GitHub repository to maintain context and history. Hemram agreed to continue research and start work once a specific option is chosen. The team also discussed the possibility of transferring the repository to an organization later if needed.