[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dash-dev] Contributing Eclipse CARE utility to Eclipse the Dash project
|
Hiho good people,
Thanks a lot Sakshi for your interest and feedback!
We do see Eclipse CARE as a way to assess (and implement) the handbook, so we're fully aligned here. As you could see, this is the very beginning and we still have a long road ahead tho.
I will start working soon on a 7-points /KPIs assessment, hopefully bringing more clarity on the analysis and results. Also, the presentation of the results will be on the next sprint (outputting raw json is not the best UI ever.. ;-).
As soon as the repository is imported (or maybe even now?), you should be able to create issues. Please feel absolutely free to ask/comment/suggest anything there!
That way we could use the issue tracker to define a shared roadmap for better alignement and collaboration. Any input is more than welcome! :-)
Have a beautiful day, cheers!
—
Boris Baldassari
Open Source Consultant | Eclipse Foundation Europe GmbH
M:+33 648038289
> Le 20 mars 2026 à 21:06, André Gomes via dash-dev <dash-dev@xxxxxxxxxxx> a écrit :
>
> Hi Sakshi,
>
> Thanks a lot for the valuable feedback.
> •
> Performance: This is expected when running without authentication, as GitHub’s API rate limits are quite restrictive. I’ve added a note to the README about this and clarified that you can use environment variables (like GH_TOKEN) if you prefer to avoid using a config file.
> • Module Loading: You’re right, there was an error in the README. Due to the package structure, the parent module is care. To run only the recommended files, you would specify --modules care.legal.recommended_files. Please note that this isn't fully implemented yet, so the tool will still run all modules for now.
> These updates are currently in the dev branch, and we’re aiming to merge them next week. Have a great weekend!
>
> Best regards,
>
> —
> André Gomes, PhD
> Research Project Manager | Eclipse Foundation Europe GmbHM: +351 912 540 814 | eclipse.org | X | LinkedIn
> Berliner Allee 47, 64295 Darmstadt
> Handelsregister: Darmstadt HRB 92821
> Managing Directors: Gaël Blondelle, Mike Milinkovich, Michael Plagge
>
>
> On Fri, Mar 20, 2026 at 6:22 PM Sakshi Chavan via dash-dev <dash-dev@xxxxxxxxxxx> wrote:
> Hi Boris and Wayne,
> I spent some time today testing eclipse-care on Windows. I found two issues that might be helpful for development:
> • Performance: The full analysis hangs on the copyright_headers check for technology.dash. I suspect the file scanning is hitting a bottleneck on Windows.
> • Module Loading: I tried running only the recommended files using --modules legal.recommended_files as per the README, but I received a No module named 'legal' error. I verified that the legal folder and recommended_files.py exist in my Python site-packages, so this might be an issue with how the CLI handles module imports.
> I'm happy to help test any fixes or provide more details!
> Best regards,
> Sakshi Chavan
>
> On Fri, 20 Mar 2026 at 21:45, Sakshi Chavan <sakshichavan61116@xxxxxxxxx> wrote:
> Hi Boris, André, and Wayne,
> This sounds like an excellent addition to the Dash project!
> As I am currently proposing the restructuring of the Eclipse Project Handbook for GSoC 2026, I see a very strong connection here. The Handbook defines the 'best practices' and policies, while Eclipse CARE provides the automation to verify them.
> I would love to explore the code and see how the recommendations in CARE align with the Handbook content. I'll be looking into the repository and documentation today to see where I can help with early testing or documentation improvements.
> Best regards,
> Sakshi Chavan
>
> On Fri, 20 Mar 2026 at 18:49, Wayne Beaton via dash-dev <dash-dev@xxxxxxxxxxx> wrote:
> +1
>
> Wayne
>
> On Fri, 20 Mar 2026 at 06:34, Boris Baldassari via dash-dev <dash-dev@xxxxxxxxxxx> wrote:
> Hiho good people,
>
> André Gomes and myself have started writing a utility to help assess best practices in Eclipse projects.
> It's called Eclipse CLI Assessment and Recommendation Engine, or Eclipse CARE for short.
>
> From the readme:
>
> --8<---------------------
> Eclipse CARE lets you assess any Eclipse project regarding Eclipse open source best practices, and get recommendations for improvement.
> Its features include:
> • Recommended files (e.g. README, LICENSE, SECURITY, etc.) in repositories (Implemented).
> • Copyright headers checks (Implemented).
> • IP and license management (Coming Soon).
> • Headers generator (Coming Soon).
> --8<---------------------
>
> We would like to contribute the code and associated resources to the Eclipse Dash project -- that is, moving the GitLab repository [1] into the Eclipse Dash GitLab group.
>
> It's still in a very early stage, but we already have code, tests, docs in [1], CI is running (and green) at [3], and the package is also available on Pypi [4].
>
> [1] https://gitlab.eclipse.org/eclipsefdn/emo-team/eclipse-care
> [2] https://gitlab.eclipse.org/eclipse/technology/dash
> [3] https://foundation.eclipse.org/ci/infra/job/eclipse-metrics/job/Eclipse%20CARE%20Full%20repo/
> [4] https://pypi.org/project/eclipse-care/
>
>
> Would that be ok with you, good people? Any comment or remark before we proceed?
>
> I plan to request the official integration in one week's time, if nobody opposes it before then.
>
> Thank you, have a wonderful day and end of the week! :-)
>
>
> —
> Boris Baldassari
> Open Source Consultant | Eclipse Foundation Europe GmbH
> M:+33 648038289
>
> _______________________________________________
> dash-dev mailing list
> dash-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/dash-dev
>
>
> --
> Wayne Beaton (he/him)
> Head of Open Source Projects | Eclipse Foundation
> _______________________________________________
> dash-dev mailing list
> dash-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/dash-dev
> _______________________________________________
> dash-dev mailing list
> dash-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/dash-dev
> _______________________________________________
> dash-dev mailing list
> dash-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/dash-dev
