Skip to content

Developer Meetings

Jump to bottom
Arun Azhakesan edited this page Oct 23, 2024 · 46 revisions
  • When: Every Wednesday
  • Time:
    • 11:00 CET/CEST ( Central European Time )
    • 14:30 IST ( India Standard Time )
    • 18:00 JST ( Japan Standard Time )
    • 02:00 AM PST ( Pacific Standard Time )
  • Where: sw360 Developer Weekly Meeting (Jitsi)
  • First regular 10 minutes will be reserved for discuss specific open bugs/features requests as upon mention ahead on the regular agenda

Pull Request Board | Issues Board

Meeting Minutes

Open Agenda ( To be discussed in the next meeting )

  • Empty

2024.10.23

  • New release candidate for backend with tag 19.0.0. RC pull request to be created October 23 Action - @gaurav
    • Will follow the sematic versioning for fixes and features. Eg: 19.0.X for fixes and 19.X.0 for features
  • New Release candidate for front end with tag 0.1.0. Target date is Nov 13th. Action - @helio

2024.08.14

  • Nouveau ? Straight to Postgres ? The cost of migrate to new CouchDb Nouveau and maintenance and testing is no small. The changes affect even current databases. Should we consider move to Postgres ?
  • ORM ? Do Cloudant still makes sense ?

2024.03.13

  • Anupam raises question about couch DB compaction, and deploy SW360 from scratch outside docker.
  • Helio gave updates from ORT community days and the possibility of having SW360 to be extended to support more use cases.
  • Arun proposes to have offline meeting of project leads to plan the follow up steps.
  • Team agrees to consider an additional community day during the next OSS conference in Europe. (Sept in Austria)
  • Gaurav demonstrates Couch DB related changes and updates required for Sw360.

2024.02.28

  • Anupam discusses #23330
  • Discussion on open PRs.

2024.02.07

  • Arun proposes to have volunteers for taking notes for Wednesday community calls.
  • Discussed issue #2298 from ADV
  • closed few PRs & Issues from the list
  • Helio suggests not to merge any new UI enhancements until new version
  • @smruthi presents possibile reference to new repo structure (related to discussion #2295)

2024.01.24

  • Release management - needs to be discussed, agreed and documented.
  • Versioning of REST API
  • Expecting a lot of breaking changes in version 19 with NextJS.
    • No Liferay and
    • No Postgres
    • Java 17 (minimum)
    • Keycloak authentication
  • No major changes in backend until v 19.
  • Cariad, in future will contribute the security fixes upstream. Helio is working on it.
  • Need to check the open security issues for SW360. Should discuss this in next meeting 2024.01.31 @ag4ums

2023.11.29

Chair: @Anupam Notes: @arunazhakesan

  • 24 Open PRs - discussion on updates
  • Afsah updates on PR#2221 &2220
  • Shruthi demos & discusses Keyclock

2023.11.15

Chair: @Anupam Notes: @arunazhakesan

  1. Open PR's are reviewed
  2. Dashboard feature is discussed. @heliocastro raises few concerns regarding the current logic of having an external script

Discussions

  1. How can attachments be managed across different SW360 instances? Alternatives for current approach.
  2. @heliocastro mentions the need to break the main branch for bringing in new changes. For update from V.18 to V.19. Will have a follow up meeting to decide the specifics of release management. @anupam mentions the lack of resources to support a maintenance branch.
  3. Test cases for SW360 should be implemented. @heliocastro suggests that to do automated test cases for UI only after change from Liferay. Also suggests to try it via docker container. @anupam suggests to have a validation test to be done outside sw360. The need to document the What & How of test use case.

2022.10.12

  • Status of package PR
    • Demo was given by Abdul
    • Is in internal review to optimization
    • Enable import from CycloneDX
    • Maybe we add information of which package manager
  • sw360: Lucene must go ...
    • Couchdb own find
      • Verify indexes usage and necessity of reindex before user return
  • sw360-frontend: App routing ftw.

2022.10.12

Chair: @Anupam Notes: @arunazhakesan

2022.08.24

Chair: @Kouki Notes: @Kouki

2022.08.17

Chair: @Anupam Notes: @arunazhakesan

2022.08.10

Chair: @Anupam Notes: @arunazhakesan

  • New Issues
  • Merged Pull Requests
  • Discussed Topics
    • Proposal from Arun regarding implementing GDPR compliance for SW360 tool. Further discussion to be done on the core aspects of user management that gets affected when this feature is implemented,.

2022.08.03

Chair: @Anupam Notes: @arunazhakesan

  • No New Issues since 2022.07.27
  • No new Merged pull requests since 2022.07.27
  • ** Discussed Topics**
    • Proposal from Arun regarding a public instance of SW360 (without Project module) to share clearing information to larger audience. Further discussion to be done on the final plan.

2022.07.27

Chair: @Anupam Notes: @helio

  • New Issues

  • Merged pull requests

  • Agenda Topics

    • 10 minutes - Pull Request discussion
    • Warnings and sanitize code: Current codebase is issuing several simple warnings and should be considered a taskforce to clean up this to make easy modernization of sw360.
    • Liferay migration and do a merge + stabilization stage instead of wait to solve
    • Slack and new rules
    • @katharina - Documentation - We have a possible technical writer
    • New contributors - How speed up adoption - Who is in charge (anynone ?)

2022.07.20

Chair: @Anupam Notes: @helio

2022.07.13

Chair: @Kouki Notes: @Kouki

2022.07.06

Chair: @Anupam Notes: @helio

2022.06.29

Chair: @Anupam Notes: @helio

2022.06.22

Chair: @Anupam Notes: @helio

2022.06.15

Chair: @Anupam Notes: @helio

SET BRANCH CHANGE DATE: 06.07.22

2022.06.08

Chair: @Anupam Notes: @helio

2022.06.01

Chair: @Anupam Notes: @helio

2022.05.25

Chair: @Anupam Notes: @helio

2022.05.18

Chair: @Anupam Notes: @helio

  • New Issues

  • Merged pull requests

  • Agenda Topics

  • Discussed topics

    • Postponed roadmap alignment due general holidays starting on Europe
    • Architecture meeting will be done 30 minutes before regular meeting. @Anupam will senfd invite

    HOT TOPIC Two weeks notice from NOW to rename branch from master to main

2022.05.11

Chair: @Anupam Notes:@helio

2022.05.04

Chair: @Anupam Notes: @helio

2022.04.27

Chair: @Anupam Notes:@helio

2022.04.06

Chair: @Anupam Notes:@helio

2022.03.30

Chair: @Anupam Notes:@helio

  • New Issues

  • Merged pull requests

  • Agenda Topics:

    • 10 minutes - Pull Request discussion
    • Reduce the amount of ways to deploy sw360 ? ( Review )
    • @helio - Request from openchain members what they are using
    • Simple way to mark spontaneous meetings. Jitsi platform is stable, and good center of contact. We need now a formal way to set on demand meetings.
    • Change of meeting time due CEST ( Central European Summer Time )

2022.03.23

Chair: @Anupam Notes:@helio

2022.03.16

Chair:@Helio Notes:@Michael

  • New Issues

    • new issue: presented openidconnect: unable to fetch user issue. no solution so far, need further investigation

  • Merged pull requests

  • News: new interface (action: replace liferay)

    • Helio talks about the new interface working, will be shown soon
    • almost all tabs covered
    • based on https://svelte.dev/ for building elements
    • based on tailwind for layout and appearance
    • (Helio shows explains code structure of the implementation)
    • initial goal: assess if that is a viable to way to go ahead

  • There isa meeting proposed for talking about How do people use sw360?

2022.03.09

Chair: @Anupam Meeting Notes: @Helio

2022.03.02

Chair: @Anupam Meeting Notes: @Helio

  • Merged pull requests
  • Pull request 1274 - Decided to left it open @Anupam
  • Angular UI - Code is old and not simply portable to modern NodeJS. Second attempt will be done with old release to evaluate properly if it is still valid to use it. @Helio
  • SPDX report Toshiba has advanced on their fork branch. Not yet ready for pull request. @Kouki Hama
  • sw360 Process Meeting @Katharina Ettinger
    • Setting the sw360 exchange at April 1st @ Katharina
    • Communicate to the tooling group @Anupam
    • Communicate to OpenChain @Helio
Clone this wiki locally