Replies: 14 comments 57 replies
-
Idea!Title: Sample project idea 1Goal: Example Automate the process of model training using pipelining.Detailed explanation about the project idea. What is expected, if there is already any workflow, etc to be added here. Bellow are rating out of 3.
Contact : @GMishx |
Beta Was this translation helpful? Give feedback.
-
IdeaLicense Change Detection This would be combined effort between SW360 and FOSSology As the software evolves in time, so does their licensing. A scenario where a package (say "mylib-v1.2") was scanned by FOSSology and cleaned by a clearing team. The new version of the package (say "mylib-v1.5") was released and uploaded again to FOSSology for clearing. Now, another metric can be generated showing the files from both packages against the change in licensing per file (addition, removal, change of license or new file). This either can be shown in FOSSology itself, but also when doing an initial scan report (ISR), triggered from SW360. Then it would be very visible for the requester if there are changes in the new version of the release or not. Also the diff could be shown in the CLI files. It can generated a table like:
|
Beta Was this translation helpful? Give feedback.
-
Idea!Title: Improve integration with FOSSologyGoal: Use extended REST API of FOSSology to improve the "Send to FOSSology" featureSW360 already have ways to interact with FOSSology, however the interaction as of now is very limited. The idea is to expand on this interaction and make use of extended REST API of FOSSology and have features like:
Relevant information:
Contact : @GMishx |
Beta Was this translation helpful? Give feedback.
-
Idea!Title: Thrift layer removalGoal: Remove thrift layer for communication with DatabaseRemove thrift layer which is used to interact with DB as it is not required and makes the installation process of SW360 unnecessarily complex. This change will help project moving forward with modern architectures like micro-services.
Contact : @GMishx @smrutis1 @heliocastro |
Beta Was this translation helpful? Give feedback.
-
#Idea! Title: Have (unit) tests for all REST API endpointsGoal: It must not happen that a REST API endpoint 'just' does not workEvery REST API endpoint needs a test and all these test have to run before a new FOSSology release is done. |
Beta Was this translation helpful? Give feedback.
-
Idea!Title: SBOM based recommendationGoal: Recommendation of packages based on SBOM of a projectWhen a user imports a SBOM file, the tool will share the information about the cleared & uncleared packages used in that project based on existing knowledge available in SW360. In addition to that if any package is uncleared,
Bellow are rating out of 3.
|
Beta Was this translation helpful? Give feedback.
-
Idea!Title: Creating Project as a service in Sw360Goal: Idea is to create a project as a microserviceThe idea is t separate out Project and related modules as separate microservices which can then be used by multiple BU/Org for better customization and still allowing reusing common component repository
|
Beta Was this translation helpful? Give feedback.
-
Idea: Update Official Documentation PageMotivationThe current official documentation page (https://eclipse.dev/sw360/) lacks clear instructions regarding environment configurations and upgrade procedures for recent software versions. This discrepancy often confuses users and negatively affects productivity during installation or updating processes. Keeping the official documentation accurate and up-to-date helps attract new users and fosters an active user community. Moreover, documentation updates do not require direct changes to the software source code, allowing contributors to undertake this task concurrently with other development or testing activities, thus lowering the barriers for OSS contributions. Proposed Changes
Notes
|
Beta Was this translation helpful? Give feedback.
-
I’m Vishnu Murthy, a Pre Final year B.Tech student at KL University, and I'm highly interested in contributing to SW360 for GSoC. My expertise includes Java, Spring Boot, React, and AWS, aligning well with the project’s tech stack. |
Beta Was this translation helpful? Give feedback.
-
please provide format of proposal |
Beta Was this translation helpful? Give feedback.
-
Hi, I’m Kanhaiya, a Java & Spring Boot developer interested in contributing to SW360 for GSoC 2025. I’d love to get started. Can someone guide me on setting up the project and picking a beginner-friendly issue? |
Beta Was this translation helpful? Give feedback.
-
i am troubling to download org.eclipse.sw360 dependancies |
Beta Was this translation helpful? Give feedback.
-
If anyone has the proposal format, please share it. Thank you! |
Beta Was this translation helpful? Give feedback.
-
Respected @GMishx @heliocastro @KoukiHama , Go thorugh the News section implementation to my localhost #115 Thanks |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all!
SW360 as an org is planning to apply for Google Summer of Code this year. In preparation to do so, we are creating this discussion to gather ideas for the GSoC-2025 projects.
Since 2022, there are some changes made by Google in the program. You can read more about it on their website. But as a summary,
Please feel free to drop any questions here (or start a new discussion) you have regarding the program, you want to submit a proposal idea, you want to be mentor in the program, etc.
While submitting a project idea, please tag it to be "Medium" or "Large" sized and who you'll prefer working on it "student" or "professional".
Some resources from Google:
You can also check the detailed documentation of previous students from FOSSology GSoC-2024.
Here is the list of the people who would be volunteering as mentors & org-admins for GSoC-2025.
Want to mentor this GSoC-2025 ? Please contact OrgAdmins.
Beta Was this translation helpful? Give feedback.
All reactions