Project Lead Circle [2025-01-10]

[antonkri]

Go through the points and tasks of the previous PL Cirlce, as due to christmas vacation most of the usual participants were not there.

Agenda

• Organizational:
  • Election of Project Lead Circle Assistant (moved to 10th of Jan)
  • Anton Krivoborodov was elected.
• 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 (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 (One Pager for Contribution #141 ).
• We need to present our SW Dev Process in Eclipse Process SIG mid of February next year
  • @grandyholger will take care of organizing the meeting/slot in Process SIG
  • @antonkri will create a ticket, @markert-r will take over the lead
  • Content
    • Present what should be done in Open Source to qualify/certify SW Development process & corresponding solution
    • How do we do this? What was already done -> short presentation (open source tools and so on)
    • Explain general approach: every module is SEooC, we audit our sw dev process, we make assessment of one module as an example. The complete assessment of the final product should be done by the distributor.
    • Agree on responsibility and working mode, what would be discussed in SIG, what would be discussed in the context of 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
    • @FScholPer will start a request by Eclipse SDV to check the name (S-CORE) trademark topic.
    • to be checked by every PL, confirmed. To be changed in written text, but not organization/project names or in source code, as this will mean also changing of the links. Technical Circle should document where it should be changed and where not (@antonkri to create a ticket).
    • 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
• Kick-off 15.01.2025 for all architectural communities (pro feature) to prepare Feature requests and align contributions.
  • Contributions from multiple companies as open source (branches of incubation repos) will be reviewed on 11.02.2025-13.02.2025 to look into the solution and to choose the best possible solution as basis for the SCORE.
  • As location we could choose ULM as it is best fit for everyone.
• 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 13.01.2025, first meetings should be scheduled for next week (CW3)
  • 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
  • Due Date for the first townhall meeting: end of Februar.
  • first proposal of agenda: end of January.
  • Communication channels -> @johannes-esr
    • mailing list for ad-hoc messages
    • news on SCORE web page (Town-Hall, Audit statement, new release ...)
    • we need communication concept where do we communicate what
    • Do we need a "WebPage/Communication Community"?