Location: Virtual, invite sent individually

Date and time: 22nd November 2021 , 17:00 CET

Since adaptTo 2021 was still virtual, we did not host an in-person Sling Committer's round table. Though a little late, we are still planning to do an online meetup this year. Topics will be announced at the start of the meeting. The meeting will include video, so it's recommended ( but not required ) to join using a webcam or something similar. The meeting will not be recorded, but minutes will be written and sent to dev@sling.apache.org .

And, just like at the in-person round table, feel free to grab a beverage of your choice ( alcoholic or not ). It would be fun if people can (briefly) show a special thing from where they are, beverage, food, chocolate, a weird fruit or something like that.

If you intend to participate, please add your name below and and send Robert Munteanu your email address. If you're already a committer you can skip the mailing step, since your apache.org email address is already public. If you don't have edit rights for the page, skip the edit.

Participants:


Topic Proposals

  1. How to prevent default servlets (mainly POST default servlet) from kicking in: SLING-6767 - Getting issue details... STATUS , SLING-9531 - Getting issue details... STATUS
  2. Status of migration to OSGi R6 annotations and new plugins (bnd-maven-plugin), https://ci-builds.apache.org/job/Sling/view/Monitor/
  3. Status of Sling 12:

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due
    Refresh

  4. Simpler Sling Starter releases.
    What can we do to make Sling Starter releases simple? Let's make a thought exercise and plan for releasing once per week.
  5. Overhauls of Integration tests.
    How can we move integration tests (from launchpad-integration-tests) closer to the modules they are testing?
  6. HTL Whitespace removal: SLING-4443 - Getting issue details... STATUS , discuss different implementation approaches
  7. Support for Java 8

Meeting notes

1. How to prevent default servlets (mainly POST default servlet) from kicking in?

Multiple variants were discussed, with the consensus arriving at implementing a new POST operation that handles this.

3. Status of Sling 12

  • Mostly blocked by finalising the feature model migration work. Most important topic - what is the recommended way to launch the Sling Starter?
    • simple docker run
    • download feature launcher  and execute with a remote feature file
    • kickstart jar (not yet implemented)
    • clone starter from GitHub and launch
      • perhaps with a default launcher based on the maven-exec-plugin 
    • should we present multiple options to users, e.g. docker run for one-off and archetype generation for starting projects?


6. HTL Whitespace removal

The discussion converged around a new HTL command that will provide this. Other scripting engines, like Thymeleaf, presumably have this capability so we don't need to implement something for every engine.

7. Support for Java 8

  • no concrete proposal on when it should happen
  • it's important to increment the minor version of a bundle when changing requirements.
    • Java version change
    • Supported OSGi specs version, e.g. R6 → R7
      Example: SLING-10725 - Getting issue details... STATUS
  • How can we make sure we don't accidentally drop support for old versions?
    • counter-question: for how long do we want to keep supporting old OSGi/Java versions?
  • No labels