-
Notifications
You must be signed in to change notification settings - Fork 99
Developer Meetings
Gaurav Mishra edited this page Oct 30, 2024
·
48 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)
- Backup meeting: sw360 Zoom
- 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
- Empty
- New release 19.0.0-M1 tagged for the backend.
- #2659 created as first commit with snapshot after release tag.
- Front-end still lint errors in 2-3 sections and should be resolved soon.
- New release candidate for backend with tag 19.0.0. RC pull request to be created October 23 Action - @GMishx
- 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
- 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 ?
- 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.
- Anupam discusses #23330
- Discussion on open PRs.
- 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)
- 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
Chair: @Anupam Notes: @arunazhakesan
- 24 Open PRs - discussion on updates
- Afsah updates on PR#2221 &2220
- Shruthi demos & discusses Keyclock
Chair: @Anupam Notes: @arunazhakesan
- Open PR's are reviewed
- Dashboard feature is discussed. @heliocastro raises few concerns regarding the current logic of having an external script
Discussions
- How can attachments be managed across different SW360 instances? Alternatives for current approach.
- @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.
- 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.
- 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
-
Couchdb own find
- sw360-frontend: App routing ftw.
Chair: @Anupam Notes: @arunazhakesan
-
Discussed Topics
- Docker file - issue in dependency download
- Rename
lib-datahandlertodatahandler
- New Issues
- Merged Pull Requests
-
Discussed Topics
- https://github.com/eclipse/sw360/issues/1616
- ECC tab dont have dependesies info
- Disscution about version up will be hold on next arcitecture meeting
Chair: @Anupam Notes: @arunazhakesan
- New Issues
- Merged Pull Requests
-
Discussed Topics
- SW360 Client update required for ORT
- Nomination process for new committers
- Initial discussion on issue 1611
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,.
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.
-
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 ?)
-
Agenda Topics
- 10 minutes - Pull Request discussion
-
Agenda Topics
- 10 minutes - Pull Request discussion
-
feat(ui):filter active users
- No reviewer, but Hama will check it quickly before reviewer are assigned officially.
-
SPDX function
- Toshiba plan to split 3 PR, "New SPDX library", "Edit/show SPDX info", "Import SPDX files"
- Need to discuss about "Import SPDX files" more
- Update presentation pages in sw360 web site
- Kouki Hama is making roadmap project with this file
- Anupam will back next meeting.
-
Agenda Topics
-
10 minutes - Pull Request discussion
-
Possible SPDX opportunity due TOSHIBA upcoming pull request. Should be discussed as topic for architectural meeting
-
New Website is live. Working on documentation started
-
-
Agenda Topics
- 10 minutes - Pull Request discussion
-
Agenda Topics
- 10 minutes - Pull Request discussion
- CHORES - Agreed on archiving
- NEW WEBSITE - Agreed to go ahead with Pull Request
-
Agenda Topics
- 10 minutes - Pull Request discussion
-
Discussed topics
- @Le Tien presented Project and Release dependency network management - Decision when the PR series start to be merged, before next release or after
- @koukihama - Started populate the roadmap project
SET BRANCH CHANGE DATE: 06.07.22
-
Agenda Topics
- 10 minutes - Pull Request discussion
-
Agenda Topics
- 10 minutes - Pull Request discussion
- Katharina request the update of Visions on sw360 homepage
- Roadmap alignment still on track ( or road :-) )
-
Agenda Topics
- 10 minutes - Pull Request discussion
- @shi9qiu plan to introduce his new idea about management to components
- @helio Place to move sw360 info from Wiki ? dependency
-
Agenda Topics
- 10 minutes - Pull Request discussion
- Roadmap and Architecture meetings
-
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
-
Agenda Topics
- 10 minutes - Pull Request discussion
-
Agenda Topics
-
10 minutes - Pull Request discussion
-
Multiple subjects discussions
- Leverage on Gradle build
-
-
Agenda Topics
-
10 minutes - Pull Request discussion
-
Multiple subjects discussions
- Merge Siemens ( and other companies ) to sw360 main roadmap to become a single unique one
- Importance of purl now and possible inclusion
- Database move from couchdb and migration test client
- Liferay migration to new codebase
- Can we go to gradle ?
-
-
Agenda Topics
- 10 minutes - Pull Request discussion
- Component Release relationships and project types are hardcoded in java code. Issue & Comment in Slack ( @alpianon )
- Demo about new function for Department Management https://github.com/eclipse/sw360/issues/1439 (@tienlee & @koukihama )
- How to explain better the Eclipse process to people has a easy step in (All attendees in telco )
-
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 )
-
Agenda Topics:
- POC for new interface ( demo @helio )
- Self merge mistake and how to mitigate
- We keep the self care process. No need to request strict measures for Eclipse maintainers.
- New projects interface. Do you know that we have a Pull Request Board and an Issues Board. The previous Triage Bug meeting failed due not formal meeting date. Can we use Github ?
- Partially agreed. Need to put efforts on it.
-
Open Discussion
- Pull request: #1477 - Generate and save excel to file system, Download generated file with token - @Anupam mentioned possible workaround. No easy solution foresee yet
- Pull request: #1476 - modify translation for search function - (https://github.com/KoukiHama) remember the open PR. Minor changes should be easy to do verification
- Bug Triage meeting marked for 2022.04.25
-
- new issue: presented openidconnect: unable to fetch user issue. no solution so far, need further investigation
-
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?
- more info: https://sw360chat.slack.com/archives/C68C2RYS3/p1647268142179459
- will be on April 1st 2022
- details presented soon.
Chair: @Anupam Meeting Notes: @Helio
- CVE endpoints
- @helio will inquiry on OpenChain members
-
PR 1473 Project Vulnerability by external ID
- Assigned to: @Anupam
-
PR 1476 Docker Fossology decouple
- Assigned to @mcjaeger
- Status of Github Dependabot
- Reported WIP by @abdul
- Issue assigned: https://github.com/eclipse/sw360/issues/1481
- Reported WIP by @abdul
-
Bug 1478 Fossology Upload Scan
- Recognized as Fossology bug. A fossology bug should be open and assign the respective url
- Commiters 101: Merge on master process ( reviewers x timing ) ?
- Pull request is always need to be reviewed
- @mcjaeger Suggested to do a often cleanup of pull requests, setting date by this group
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