2022-05-23 00:25:42
by administrator
, took 26
seconds.Information 19 |
Metrics 87 |
Attributes 17 |
Recommendations 27 |
Quality Model |
Mnemo | Value | |
---|---|---|
BZ_URL | https://bugs.eclipse.org/bugs//buglist.cgi?product=EASE | |
GIT_URL | https://git.eclipse.org/r/ease/org.eclipse.ease.core.git | |
MLS_USR_CAT_URL | https://api.eclipse.org/forums/category/1 | |
MLS_USR_DESC | ease community discussions | |
MLS_USR_NAME | Advanced Scripting Environment (EASE) | |
MLS_USR_URL | https://www.eclipse.org/forums/index.php/f/292/ | |
PMI_BUGZILLA_COMPONENT | ||
PMI_BUGZILLA_CREATE_URL | https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EASE | |
PMI_BUGZILLA_PRODUCT | EASE | |
PMI_BUGZILLA_QUERY_URL | https://bugs.eclipse.org/bugs/buglist.cgi?product=EASE | |
PROJECT_CI_URL | https://ci.eclipse.org/ease/job/ease.build.nightly/ | |
PROJECT_DESC | <p>Eclipse EASE™ allows the execution of script code (using scripting languages such as JS, Python, ...) within the context of the Eclipse Platform/RCP. As they are running in the same JRE as Eclipse itself, these scripts have direct access to any class of your application and may interact with your workbench.</p> <p>Through keywords within header data, scripts might be integrated seamlessly into the UI as toolbar and/or menu contributions. Thus the functionality could be extended by providing scripts only. No need to build, export and install a new feature, just provide a script and add it to your application at runtime.</p> <p>Scripting allows to easily extend an existing application, helps in automating everyday tasks and aids in rapid prototyping during application development. </p> <p>Following goals for the project have been defined:</p> <ol><li>Execute scripts within the running IDE.</li> <li>Support multiple script languages via a generic service that creates (multiple) script interpreters.</li> <li>Scripts are capable of interacting with the IDE, like accessing classes on the Eclipse/JRE classpath and calling methods upon them.</li> <li>Seamless integration of scripts into UI</li> <li>Scripts should be attachable to toolbars and menus</li> <li>Debuggers are aware of the script language/Java classes co-existence by providing variables access</li> <li>Provide means to sign scripts.</li> </ol> | |
PROJECT_DOWNLOAD_URL | https://www.eclipse.org/ease/download/ | |
PROJECT_ID | technology.ease | |
PROJECT_MAIN_URL | http://www.eclipse.org/ease | |
PROJECT_MLS_DEV_URL | https://dev.eclipse.org/mailman/listinfo/ease-dev | |
PROJECT_NAME | Eclipse Advanced Scripting Environment (Eclipse EASE ™) | |
PROJECT_SCM_URL | https://git.eclipse.org/r/plugins/gitiles/ease/org.eclipse.ease.scripts | |
PROJECT_WIKI_URL | https://wiki.eclipse.org/EASE |
Name | Mnemo | Description | Value | Indicator |
---|---|---|---|---|
Number of jobs | CI_JOBS | The total number of jobs defined on the CI engine. | 27 | |
Number of failed jobs one week | CI_JOBS_FAILED_1W | The number of jobs that failed during last week on the CI engine. | 19 | 1 |
Number of green jobs | CI_JOBS_GREEN | The number of green (successful) jobs on the CI engine. | 7 | |
Ratio of green jobs | CI_JOBS_GREEN_RATIO | The number of green (successful) jobs on the CI engine, divided by the total number of jobs. | 25 | 2 |
Number of red jobs | CI_JOBS_RED | The number of red (failed) jobs on the CI engine. | 19 | |
Number of yellow jobs | CI_JOBS_YELLOW | The number of yellow (unstable) jobs on the CI engine. | 1 | |
Governance documentation | DOC_GOV | Is there a documentation explaining how decisions are made? | 1 | 5 |
Board transparency | GOV_BOARD_PUBLIC | Are the minutes of the board publicly available? | 1 | 5 |
ITS Authors | ITS_AUTHORS | Number of different authors who created issues during the lifetime of the project. | 65 | |
ITS authors last month | ITS_AUTHORS_1M | Number of authors who created issues during last month. If today is 2017-02-01 then the range is from 2017-01-01 to 2017-02-01. | 1 | 1 |
ITS authors last week | ITS_AUTHORS_1W | Number of authors who created issues during last week. If today is Wed. 2017-02-01 then the range is from Wed. 2017-01-25 to Wed. 2017-02-01. | 1 | |
ITS authors last year | ITS_AUTHORS_1Y | Number of authors who created issues during last year. If today is 2017-02-01 then the range is from 2016-02-01 to 2017-02-01. | 4 | |
ITS issues created last month | ITS_CREATED_1M | Number of issues created during last month. If today is 2017-02-01 then the range is from 2017-01-01 to 2017-02-01. | 9 | |
ITS issues created last week | ITS_CREATED_1W | Number of issues created during last week. If today is Wed. 2017-02-01 then the range is from Wed. 2017-01-25 to Wed. 2017-02-01. | 1 | |
ITS issues created last year | ITS_CREATED_1Y | Number of issues created during last year. If today is 2017-02-01 then the range is from 2016-02-01 to 2017-02-01. | 33 | |
ITS diversity ratio | ITS_DIVERSITY_RATIO_1Y | The ration of bugs divided by the number of submitters, over a period of one year. | 8 | 3 |
ITS Total issues | ITS_ISSUES_ALL | Number of issues registered in the database, whatever their state is. | 953 | |
ITS Open issues | ITS_OPEN | Number of issues with a state 'open' at the time of analysis. | 111 | |
ITS Old open issues | ITS_OPEN_OLD | Number of dead issues, i.e. issues that are in state open and have not been updated for a long time (one year). | 0 | |
ITS Open issues (%) | ITS_OPEN_PERCENT | Percentage of open issues compared to the overall number of issues registered in the system. | 12 | |
ITS Pending issues | ITS_OPEN_UNASSIGNED | Number of issues in state open with no assignee (i.e. pending). | 0 | |
ITS issues updated last month | ITS_UPDATED_1M | Number of issues updated during last month. If today is 2017-02-01 then the range is from 2017-01-01 to 2017-02-01. | 15 | 4 |
ITS issues updated last week | ITS_UPDATED_1W | Number of issues updated during last week. If today is Wed. 2017-02-01 then the range is from Wed. 2017-01-25 to Wed. 2017-02-01. | 1 | |
ITS issues updated last year | ITS_UPDATED_1Y | Number of issues updated during last year. If today is 2017-02-01 then the range is from 2016-02-01 to 2017-02-01. | 51 | |
User ML Authors | MLS_USR_AUTHORS | The total number of different identities found in the User mailing list. | 47 | |
User ML Authors one month | MLS_USR_AUTHORS_1M | The total number of different identities found in the User mailing list during last month. | 1 | 2 |
User ML Authors one week | MLS_USR_AUTHORS_1W | The total number of different identities found in the User mailing list during last week. | 0 | |
User ML Authors one year | MLS_USR_AUTHORS_1Y | The total number of different identities found in the User mailing list during last year. | 6 | |
User ML diversity ratio | MLS_USR_DIVERSITY_RATIO_1Y | The ration of posts divided by the number of authors, over a period of one year. | 2 | 2 |
User ML Posts | MLS_USR_POSTS | The total number of posts found in the User mailing list. | 74 | |
User ML Posts one month | MLS_USR_POSTS_1M | The total number of posts found in the User mailing list during last month. | 1 | 1 |
User ML Posts one week | MLS_USR_POSTS_1W | The total number of posts found in the User mailing list during last week. | 0 | |
User ML Posts one year | MLS_USR_POSTS_1Y | The total number of posts found in the User mailing list during last year. | 17 | |
User ML Threads | MLS_USR_THREADS | The total number of threads (one question followed by zero or more answers) found in the User mailing list. | 74 | |
User ML Threads one month | MLS_USR_THREADS_1M | The total number of threads (one question followed by zero or more answers) found in the User mailing list during last month. | 1 | 1 |
User ML Threads one week | MLS_USR_THREADS_1W | The total number of threads (one question followed by zero or more answers) found in the User mailing list during last week. | 0 | |
User ML Threads one year | MLS_USR_THREADS_1Y | The total number of threads (one question followed by zero or more answers) found in the User mailing list during last year. | 5 | |
Dependency check | OSS_DEP_CHECK | Analysis of dependencies to identify old, vulnerable dependencies, as provided by tools like dependency-check or JFrog/Nexus. | 1 | 5 |
Escalation procedure | OSS_ESCALATE | Is there an easy and visible way for anybody to report toxic behaviour or unfair practices? | 1 | 5 |
Inclusion initiative | OSS_INCLUSION | Is there a formal procedure to help people join and benefit from the community, whoever they are? | 1 | 5 |
Access information | PROJECT_ACCESS_INFO | Is the access info (downloads, update sites..) correctly filled in the PMI records? | 1 | 3 |
CI access | PROJECT_CI_ACCESS | Is the continuous integration info correctly filled in the PMI records? | 0 | 4 |
CI information | PROJECT_CI_INFO | Is the continuous integration info correctly filled in the PMI records? | 1 | 5 |
DL access | PROJECT_DL_ACCESS | Is the access info (downloads, update sites..) correctly filled in the PMI records? | 1 | 5 |
DL information | PROJECT_DL_INFO | Is the access info (downloads, update sites..) correctly filled in the PMI records? | 1 | 5 |
Doc access | PROJECT_DOC_ACCESS | Is the documentation info correctly filled in the PMI records? | 0 | 4 |
Docs information | PROJECT_DOC_INFO | Is the documentation info correctly filled in the PMI records? | 4 | 5 |
Getting started | PROJECT_GETTINGSTARTED_INFO | Is the documentation info correctly filled in the PMI records? | 0 | 4 |
ITS access | PROJECT_ITS_ACCESS | Is the bugzilla info correctly filled in the PMI records? | 0 | 4 |
ITS information | PROJECT_ITS_INFO | Is the bugzilla info correctly filled in the PMI records? | 5 | 5 |
MLS access | PROJECT_MLS_ACCESS | Is the communication channel for the team info correctly filled in the PMI records? | 0 | 4 |
MLS information | PROJECT_MLS_INFO | Is the communication channel for the team info correctly filled in the PMI records? | 0 | 3 |
Number of releases | PROJECT_REL_VOL | The number of releases recorded in the PMI. | 8 | 4 |
SCM access | PROJECT_SCM_ACCESS | Is the source_repo info correctly filled in the PMI records? | 1 | 5 |
SCM information | PROJECT_SCM_INFO | Is the source_repo info correctly filled in the PMI records? | 1 | 4 |
SCM authors | SCM_AUTHORS | Total number of identities found as authors of commits in source code management repository. | 24 | |
SCM authors one month | SCM_AUTHORS_1M | Total number of identities found as authors of commits in source code management repositories dated during the last month. | 1 | 2 |
SCM authors one week | SCM_AUTHORS_1W | Total number of identities found as authors of commits in source code management repositories dated during the last week. | 0 | |
SCM authors one year | SCM_AUTHORS_1Y | Total number of identities found as authors of commits in source code management repositories dated during the last year. | 2 | |
SCM Branches | SCM_BRANCHES | Number of branches as returned by `git branch --all`. | 7 | |
SCM Commits | SCM_COMMITS | Total number of commits in source code management repositories. | 1139 | |
SCM Commits one month | SCM_COMMITS_1M | Total number of commits in source code management repositories dated during the last month. | 11 | 3 |
SCM Commits one week | SCM_COMMITS_1W | Total number of commits in source code management repositories dated during the last week. | 0 | |
SCM Commits one year | SCM_COMMITS_1Y | Total number of commits in source code management repositories dated during the last year. | 52 | |
SCM committers | SCM_COMMITTERS | Total number of identities found as committers of commits in source code management repository. | 19 | |
SCM committers one month | SCM_COMMITTERS_1M | Total number of identities found as committers of commits in source code management repositories dated during the last month. | 1 | |
SCM committers one week | SCM_COMMITTERS_1W | Total number of identities found as committers of commits in source code management repositories dated during the last week. | 0 | |
SCM committers one year | SCM_COMMITTERS_1Y | Total number of identities found as committers of commits in source code management repositories dated during the last year. | 2 | |
SCM diversity ratio | SCM_DIVERSITY_RATIO_1Y | The ration of commits divided by the number of authors, over a period of one year. | 26 | 5 |
SCM Changed Lines | SCM_MOD_LINES | Total number of changed lines (added, removed, changed) in source code management repositories. | 625622 | |
SCM Changed Lines one month | SCM_MOD_LINES_1M | Total number of changed lines (added, removed, changed) in source code management repositories dated during the last month. | 2885 | 5 |
SCM Changed Lines one week | SCM_MOD_LINES_1W | Total number of changed lines (added, removed, changed) in source code management repositories dated during the last week. | 0 | |
SCM Changed Lines one year | SCM_MOD_LINES_1Y | Total number of changed lines (added, removed, changed) in source code management repositories dated during the last year. | 22297 | |
Authors | SC_AUTHORS_VOL | Number of authors detected in the code. | 3 | |
Number of copyrights | SC_COPYRIGHTS_VOL | Number of copyrights detected by Scancode in the code base. | 26 | |
Total number of files analysed | SC_FILES_VOL | Total number of files analysed (and documented) by Scancode. Metric is the number of files provided in the list of analysed files returned by Scancode. | 2455 | |
Automatically generated files | SC_GENERATED_VOL | Number of files tagged as automatically generated, as detected by Scancode. | 51 | |
Code of Conduct | SC_HAS_CODEOFCONDUCT | The number of files considered as a code of conduct, as detected by Scancode. These can be any initiative and written document to regulate the behaviour of individuals | 1 | 5 |
Has contributing | SC_HAS_CONTRIBUTING | The number of files considered as a contributing or development guide, as detected by Scancode. | 1 | 5 |
Has licence | SC_HAS_LICENCE | The number of files considered as legal (i.e. licences), as detected by Scancode. | 2 | 5 |
Has Readme | SC_HAS_README | The number of files considered as a readme, as detected by Scancode. | 1 | 5 |
Number of copyright holders | SC_HOLDERS_VOL | Number of copyright holders detected in the code. | 26 | |
Licences check | SC_LIC_CHECK | Unwanted licences in the code, as provided by tools like ScanCode (or Black Duck or..). | 5 | 3 |
Programming languages | SC_PROGS_VOL | Number of programming languages detected in the code. | 10 | |
Special files | SC_SPECIAL_FILES | Number of legal, license, readmes, manifests, copyright and other files for key, top-level files. | 126 |
Name | Mnemo | Description | Value | Confidence |
---|---|---|---|---|
Activity | QM_ACTIVITY | The activity of the project's ecosystem, as measured on the mailing lists and configuration management system. | 2.8 | 5 / 5 |
Collaboration | QM_AGG_COLLAB | Are the required pieces of basic documentation available? | 4.8 | 4 / 4 |
Decisions | QM_AGG_DECISIONS | How public and open is the project's decision-making process? | 5.0 | 2 / 2 |
Information | QM_AGG_DOC | Is the project well documented? | 4.5 | 6 / 6 |
Engagement | QM_AGG_ENGAGEMENT | How the community is invited to participate, and how much is it heard when talking? | 3.3 | 3 / 4 |
Ethics | QM_AGG_ETHICS | Is the project compliant regarding OSS' ethics? | 5.0 | 3 / 3 |
Intellectual Property Management | QM_AGG_IP | How is intellectual property handled in the project? Is there an IP log? Are the project and the Eclipse Foundation safe regarding IP? | 4.0 | 2 / 2 |
Openness | QM_AGG_OPENNESS | Is the project open and transparent? | 4.3 | 6 / 6 |
OSS Core | QM_AGG_OSS_CORE | The conformance of the project to the core Open-Soure Software principles and good practices. | 4.7 | 19 / 19 |
Diversity | QM_DIVERSITY | The diversity of the project's ecosystem, as measured on the mailing lists and configuration management system. | 1.7 | 3 / 3 |
Documentation | QM_DOC | The maturity of code. | 4.2 | 4 / 4 |
Ecosystem | QM_ECOSYSTEM | The sustainability of the ecosystem evolving around the project. | 3.0 | 16 / 17 |
Process | QM_PROCESS | The maturity of the process used to run the project. | 3.5 | 11 / 11 |
Eclipse Maturity | QM_QUALITY | The overall Maturity of the project. | 3.7 | 46 / 47 |
Build and Release Management | QM_REL_ENG | Does the project apply best practices regarding Build and Release management? | 3.0 | 2 / 2 |
Configuration Management | QM_SCM | The maturity of the project regarding access and usage of the configuration management system. | 3.0 | 3 / 3 |
Support | QM_SUPPORT | The amount of knowledge provided when someone asks for support. | 2.3 | 3 / 3 |
Type | Severity | Description |
---|---|---|
PMI_EMPTY_USER_ML | High | The user mailing list URL is empty in the PMI. It helps people know where to ask questions if they want to use the product and should be filled. |
PMI_EMPTY_UPDATE | High | The update site URL is empty in the PMI. People need it if they want to use the product, and it should be filled. |
PMI_NOK_CI | High | The Hudson CI engine URL [https://ci.eclipse.org/ease/job/ease.build.nightly/] in the PMI is not detected as the root of a Hudson instance. |
CI_FAILING_JOBS | High | Job ease.build.core has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.build.nightly has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.maintenance.downloadarea has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.gerrit has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2018-09 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2018-12 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2019-03 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2019-06 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2019-09 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2019-12 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2020-03 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2020-06 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2020-09 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2020-12 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2021-06 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2021-09 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.2021-12 has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.oxygen has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
CI_FAILING_JOBS | High | Job ease.verify.core.target.photon has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it. |
Plugin | Description | URL |
---|---|---|
Bugzilla | Bar plot of all components defined for project in Bugzilla (HTML) | /projects/technology.ease/Bugzilla/bugzilla_components.html |
Bugzilla | Evolution of Bugzilla issues submission | /projects/technology.ease/Bugzilla/bugzilla_evol_summary.html |
Bugzilla | Bar plot of all versions defined for project in Bugzilla (HTML). | /projects/technology.ease/Bugzilla/bugzilla_versions.html |
EclipseForums | Timeline of posts | /projects/technology.ease/EclipseForums/eclipse_forums_plot.html |
EclipseForums | Wordcloud of threads subjects (PNG) | /projects/technology.ease/EclipseForums/eclipse_forums_wordcloud.png |
EclipseForums | Wordcloud of threads subjects (SVG) | /projects/technology.ease/EclipseForums/eclipse_forums_wordcloud.svg |
Git | HTML export of Git authors evolution. | /projects/technology.ease/Git/git_evol_authors.html |
Git | PNG export of Git SCM authors evolution. | /projects/technology.ease/Git/git_evol_authors.png |
Git | SVG export of Git SCM authors evolution. | /projects/technology.ease/Git/git_evol_authors.svg |
Git | HTML export of Git commits evolution. | /projects/technology.ease/Git/git_evol_commits.html |
Git | PNG export of Git SCM commits evolution. | /projects/technology.ease/Git/git_evol_commits.png |
Git | SVG export of Git SCM commits evolution. | /projects/technology.ease/Git/git_evol_commits.svg |
Git | HTML export of Git SCM evolution summary. | /projects/technology.ease/Git/git_evol_summary.html |
Git | HTML export of Git main metrics. | /projects/technology.ease/Git/git_summary.html |
Jenkins | Pie chart of jobs statuses (HTML) | /projects/technology.ease/Jenkins/jenkins_pie.html |
ProjectSummary | A badge to display current value of main quality attribute on an external web site (uses shields.io) | /projects/technology.ease/ProjectSummary/badge_attr_alambic.svg |
ProjectSummary | A badge to display current value of main quality attribute on an external web site (uses shields.io) | /projects/technology.ease/ProjectSummary/badge_attr_root.svg |
ProjectSummary | A HTML snippet that displays downloads for main data. | /projects/technology.ease/ProjectSummary/badge_downloads |
ProjectSummary | A HTML snippet that displays a list of plugins for the project. | /projects/technology.ease/ProjectSummary/badge_plugins |
ProjectSummary | A HTML snippet that displays the name and description of the project. | /projects/technology.ease/ProjectSummary/badge_project_main |
ProjectSummary | A HTML snippet to display main quality attributes and their values. | /projects/technology.ease/ProjectSummary/badge_psum_attrs.html |
ProjectSummary | A HTML snippet that displays main quality attributes. | /projects/technology.ease/ProjectSummary/badge_qm |
ProjectSummary | A HTML snippet that displays the quality model visualisation. | /projects/technology.ease/ProjectSummary/badge_qm_viz |
ProjectSummary | A HTML snippet to display main quality attributes and their values. | /projects/technology.ease/ProjectSummary/psum_attrs.html |
Scancode | Pie chart of authors detected in the codebase. | /projects/technology.ease/Scancode/scancode_authors.html |
Scancode | Pie chart of copyrights detected in the codebase. | /projects/technology.ease/Scancode/scancode_copyrights.html |
Scancode | Pie chart of holders detected in the codebase. | /projects/technology.ease/Scancode/scancode_holders.html |
Scancode | Pie chart of licences detected in the codebase. | /projects/technology.ease/Scancode/scancode_licences.html |
Scancode | Pie chart of programming languages detected in the codebase. | /projects/technology.ease/Scancode/scancode_programming_languages.html |
Last analysis was on 2022-05-23 00:25:42.
Page generated by Alambic 3.3.3-dev on Mon May 23 21:04:57 2022.