Project Lead Circle [2024-12-20]

[antonkri]

Agenda

• Organizational:
  • No PL meeting on 27th of Dec & 3rd of Jan due to holidays (agreed)
  • First PL meeting in 2025: 10th of Jan (agreed)
  • Election of Project Lead Circle Assistant (moved to 10th of Jan)
• WebPage: current status (https://eclipse-score.github.io/)
  • "Getting Involved" instead of Contribution.md (Done)
  • Restructuring of the the documentation landing page (Done)
  • new 4. box (Kachel): "Project Plan & Contribution Request" we should have a link to the list of all active Contribution Requests (Done).
  • Who is continuously responsible for our "extern" representation? -> @johannes-esr (to be confirmed).
  • Overview of open Contribution Requests, that can be taken over by the people who want to join (Contribution Request as "Guiding Principle")
  • "One Pager" on the WebPage, how to start contributing to SCORE and that the existing Contribution Requests are the best choice to start. List of open Contribution Requests should be prominent on the WebPage. Another option would be, that people could come with their own repo, so that we can look into it. This should be also part of the "One Pager" -> Task for the Technical Lead Circle (@antonkri to create a ticket in Technical Lead Circle LOP project).
• We need to present our SW Dev Process in Eclipse Process SIG mid of February next year -> @antonkri put it as milestone to the project
• SCORE Logo & Name
  • Rename SCORE to S-CORE (see https://github.com/orgs/eclipse-score/discussions/83)
    • renaming of logo, on web page and in the documentation should be enough
    • open for every version of logo (https://github.com/orgs/eclipse-score/discussions/47) tickets by eclipse to check the trademark topics -> @FScholPer
    • to be checked by every PL, whether renaming is ok
    • to propose a new S-CORE logo based on SCORE logo (bottom left) -> @qor-lb
• Current status: Initial set-up of the SCORE project (https://github.com/orgs/eclipse-score/projects/1)
  • Feature Requests should be updated with the information from technical workshop (in GitHub Issue).
  • Review of Feature Requests status based on the following project: https://github.com/orgs/eclipse-score/projects/4/views/1
  • Technical Lead circle should approve all Contribution Requests and present them later in the PL Circle
• Extra project for Feature Requests (approved: https://github.com/orgs/eclipse-score/projects/4/views/1)
• SCORE component list (SCORE Release & Component Overview #65)
• Nomination of people for Communities
  • to be named by everyone till 10.01.2024
  • SW Architecture community: https://github.com/orgs/eclipse-score/discussions/93
• Discussion Template (agreed)
• Should we schedule eclipse sdv community meeting "score for all" once in 8 weeks for everyone to update with the latest information with a public calendar -> @antonkri put on agenda for the next year and create a ticket in Technical Lead Circle LOP project to discuss what should be presented and discussed in such a meeting and also to prepare a meeting. Due Date for the first proposal: 17.01.2025. Soon to come on the WebPage (@johannes-esr). Do we need a "WebPage Community"?