Mnemo |
Value |
BZ_URL |
https://bugs.eclipse.org/bugs//buglist.cgi?product=Apogy |
GIT_URL |
https://git.eclipse.org/r/apogy/apogy.git |
MLS_USR_CAT_URL |
https://api.eclipse.org/forums/category/1 |
MLS_USR_DESC |
apogy community discussions |
MLS_USR_NAME |
Eclipse Apogy |
MLS_USR_URL |
https://www.eclipse.org/forums/index.php/f/401/ |
PMI_BUGZILLA_COMPONENT |
General |
PMI_BUGZILLA_CREATE_URL |
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Apogy |
PMI_BUGZILLA_PRODUCT |
Apogy |
PMI_BUGZILLA_QUERY_URL |
https://bugs.eclipse.org/bugs/buglist.cgi?product=Apogy&component=General |
PMI_UPDATESITE_URL |
https://apogy.gitlab.io/ca-gc-asc_csa-apogy-ots/ |
PROJECT_CI_URL |
https://ci.eclipse.org/apogy/ |
PROJECT_DESC |
<p class="rtecenter"><a href="https://www.youtube.com/watch?reload=9&v=-zb8EgQdXdc&feature=youtu.be">Apogy Demonstration (Youtube)</a></p>
<p>This project provides a multi-mission operations and planning software framework. <em><strong>Eclipse Apogy</strong></em> uses Eclipse Modeling Framework models to define the systems being controlled, the environment in which these systems are operated, the operations being carried out and the corresponding data produced during operations.</p>
<p class="rteleft" dir="rtl">Integrating a rover in <em><strong>Apogy</strong></em> is as simple as creating an EMF model that represent its interface and telemetry) and defined its topology (i.e. how the physical components are attached together and how the degrees-of-freedom are mapped to the telemetry). Once these two steps are completed, one can visualize the rover in 3D in its environment (showing cameras field of view in 3D, using the generic 3D tools to measure distance, record trajectory, measure sun angle, etc), create commands and display telemetry (camera views with overlays, filters and tools, recording and playback of data, etc) without having to write a single line of code ! This means that the operator can already start configuring his/her control station, even if there is no real rover to command at that point. Implementing the necessary interface between the generated EMF classes and the hardware (which is usually straightforward) is all that remain to complete the integration and benefit from the many tools already available in <em><strong>Apogy</strong></em></p>
|
PROJECT_DOC_URL |
http://wiki.eclipse.org/apogy |
PROJECT_DOWNLOAD_URL |
http://download.eclipse.org/apogy/release/R0_6/latest/ |
PROJECT_GETTINGSTARTED_URL |
https://wiki.eclipse.org/Apogy/GettingStarted |
PROJECT_ID |
technology.apogy |
PROJECT_MLS_DEV_URL |
https://accounts.eclipse.org/mailing-list/apogy-dev |
PROJECT_MLS_USR_URL |
http://eclipse.org/forums/eclipse.apogy |
PROJECT_NAME |
Eclipse Apogy |
PROJECT_SCM_URL |
https://git.eclipse.org/r/plugins/gitiles/apogy/apogy |
Name |
Mnemo |
Description |
Value |
Indicator |
Number of jobs |
CI_JOBS |
The total number of jobs defined on the CI engine. |
8 |
|
Number of failed jobs one week |
CI_JOBS_FAILED_1W |
The number of jobs that failed during last week on the CI engine. |
2 |
4 |
Number of green jobs |
CI_JOBS_GREEN |
The number of green (successful) jobs on the CI engine. |
4 |
|
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. |
66 |
3 |
Number of red jobs |
CI_JOBS_RED |
The number of red (failed) jobs on the CI engine. |
2 |
|
Number of yellow jobs |
CI_JOBS_YELLOW |
The number of yellow (unstable) jobs on the CI engine. |
0 |
|
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. |
3 |
|
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. |
0 |
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. |
0 |
|
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. |
0 |
|
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. |
0 |
|
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. |
0 |
|
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. |
0 |
|
ITS diversity ratio |
ITS_DIVERSITY_RATIO_1Y |
The ration of bugs divided by the number of submitters, over a period of one year. |
0 |
1 |
ITS Total issues |
ITS_ISSUES_ALL |
Number of issues registered in the database, whatever their state is. |
78 |
|
ITS Open issues |
ITS_OPEN |
Number of issues with a state 'open' at the time of analysis. |
49 |
|
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. |
63 |
|
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. |
0 |
1 |
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. |
0 |
|
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. |
0 |
|
User ML Authors |
MLS_USR_AUTHORS |
The total number of different identities found in the User mailing list. |
2 |
|
User ML Authors one month |
MLS_USR_AUTHORS_1M |
The total number of different identities found in the User mailing list during last month. |
0 |
1 |
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. |
0 |
|
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. |
0 |
1 |
User ML Posts |
MLS_USR_POSTS |
The total number of posts found in the User mailing list. |
2 |
|
User ML Posts one month |
MLS_USR_POSTS_1M |
The total number of posts found in the User mailing list during last month. |
0 |
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. |
0 |
|
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. |
2 |
|
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. |
0 |
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. |
0 |
|
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? |
3 |
5 |
CI access |
PROJECT_CI_ACCESS |
Is the continuous integration info correctly filled in the PMI records? |
1 |
5 |
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? |
1 |
5 |
Docs information |
PROJECT_DOC_INFO |
Is the documentation info correctly filled in the PMI records? |
3 |
5 |
Getting started |
PROJECT_GETTINGSTARTED_INFO |
Is the documentation info correctly filled in the PMI records? |
1 |
5 |
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? |
1 |
5 |
MLS information |
PROJECT_MLS_INFO |
Is the communication channel for the team info correctly filled in the PMI records? |
1 |
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. |
2 |
|
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. |
0 |
1 |
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. |
1 |
|
SCM Branches |
SCM_BRANCHES |
Number of branches as returned by `git branch --all`. |
34 |
|
SCM Commits |
SCM_COMMITS |
Total number of commits in source code management repositories. |
1166 |
|
SCM Commits one month |
SCM_COMMITS_1M |
Total number of commits in source code management repositories dated during the last month. |
0 |
1 |
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. |
2 |
|
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. |
0 |
|
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. |
1 |
|
SCM diversity ratio |
SCM_DIVERSITY_RATIO_1Y |
The ration of commits divided by the number of authors, over a period of one year. |
52 |
5 |
SCM Changed Lines |
SCM_MOD_LINES |
Total number of changed lines (added, removed, changed) in source code management repositories. |
13876875 |
|
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. |
0 |
1 |
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. |
132210 |
|
Authors |
SC_AUTHORS_VOL |
Number of authors detected in the code. |
11 |
|
Number of copyrights |
SC_COPYRIGHTS_VOL |
Number of copyrights detected by Scancode in the code base. |
9 |
|
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. |
26042 |
|
Automatically generated files |
SC_GENERATED_VOL |
Number of files tagged as automatically generated, as detected by Scancode. |
200 |
|
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 |
0 |
4 |
Has contributing |
SC_HAS_CONTRIBUTING |
The number of files considered as a contributing or development guide, as detected by Scancode. |
0 |
4 |
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. |
0 |
4 |
Number of copyright holders |
SC_HOLDERS_VOL |
Number of copyright holders detected in the code. |
8 |
|
Licences check |
SC_LIC_CHECK |
Unwanted licences in the code, as provided by tools like ScanCode (or Black Duck or..). |
18 |
1 |
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. |
880 |
|
Plugin |
Description |
URL |
Bugzilla |
bugzilla_components.csv The list of components that have at least one bug registered against them (CSV). |
/projects/technology.apogy/Bugzilla/bugzilla_components.csv |
Bugzilla |
bugzilla_evol.csv The evolution of issues created and authors by day (CSV). |
/projects/technology.apogy/Bugzilla/bugzilla_evol.csv |
Bugzilla |
bugzilla_issues.csv The list of issues, with fields 'id, summary, status, assignee, reporter, due_date, created_at, updated_at' (CSV). |
/projects/technology.apogy/Bugzilla/bugzilla_issues.csv |
Bugzilla |
bugzilla_issues_open.csv The list of open issues, with fields 'id, summary, status, assignee, reporter, due_date, created_at, updated_at' (CSV). |
/projects/technology.apogy/Bugzilla/bugzilla_issues_open.csv |
Bugzilla |
bugzilla_issues_open_unassigned.csv The list of open and unassigned issues, with fields 'id, summary, status, assignee, reporter, due_date, created_at, updated_at' (CSV). |
/projects/technology.apogy/Bugzilla/bugzilla_issues_open_unassigned.csv |
Bugzilla |
bugzilla_milestones.csv The list of milestones that have at least one bug targeted for (CSV). |
/projects/technology.apogy/Bugzilla/bugzilla_milestones.csv |
Bugzilla |
bugzilla_versions.csv The list of software versions that have at least one bug registered against them (CSV). |
/projects/technology.apogy/Bugzilla/bugzilla_versions.csv |
Bugzilla |
import_bugzilla.json The original file of current information, downloaded from the Bugzilla server (JSON). |
/projects/technology.apogy/Bugzilla/import_bugzilla.json |
Bugzilla |
metrics_bugzilla.csv The list of metrics with their values (CSV). |
/projects/technology.apogy/Bugzilla/metrics_bugzilla.csv |
Bugzilla |
metrics_bugzilla.json The list of metrics with their values (JSON). |
/projects/technology.apogy/Bugzilla/metrics_bugzilla.json |
EclipseForums |
eclipse_forums_forum.csv The forum description file as returned by Eclipse servers (CSV). |
/projects/technology.apogy/EclipseForums/eclipse_forums_forum.csv |
EclipseForums |
eclipse_forums_posts.csv The list of posts for the forum as returned by Eclipse servers (CSV). |
/projects/technology.apogy/EclipseForums/eclipse_forums_posts.csv |
EclipseForums |
eclipse_forums_threads.csv The list of threads for the forum as returned by Eclipse servers (CSV). |
/projects/technology.apogy/EclipseForums/eclipse_forums_threads.csv |
EclipseForums |
import_eclipse_forums_forum.json The forum description file as returned by Eclipse servers (JSON). |
/projects/technology.apogy/EclipseForums/import_eclipse_forums_forum.json |
EclipseForums |
import_eclipse_forums_posts.json The list of posts for the forum as returned by Eclipse servers (JSON). |
/projects/technology.apogy/EclipseForums/import_eclipse_forums_posts.json |
EclipseForums |
import_eclipse_forums_threads.json The list of threads for the forum as returned by Eclipse servers (JSON). |
/projects/technology.apogy/EclipseForums/import_eclipse_forums_threads.json |
EclipsePmi |
pmi.json The PMI file as returned by the Eclipse repository (JSON). |
/projects/technology.apogy/EclipsePmi/pmi.json |
EclipsePmi |
pmi_checks.csv The list of PMI checks and their results (CSV). |
/projects/technology.apogy/EclipsePmi/pmi_checks.csv |
EclipsePmi |
pmi_checks.json The list of PMI checks and their results (JSON). |
/projects/technology.apogy/EclipsePmi/pmi_checks.json |
GenericR |
generic_r.pdf The PDF document generated from the R markdown file. |
/projects/technology.apogy/GenericR/generic_r.pdf |
Git |
git_branches.csv List of branches of the Git repository, one by line (CSV). |
/projects/technology.apogy/Git/git_branches.csv |
Git |
git_commits.csv List of all commits, with id, message, time, author, committer, and added, deleted and modifed lines (CSV). |
/projects/technology.apogy/Git/git_commits.csv |
Git |
git_commits_evol.csv Evolution of number of commits and authors by day (CSV). |
/projects/technology.apogy/Git/git_commits_evol.csv |
Git |
import_git.txt The original git log file as retrieved from git (TXT). |
/projects/technology.apogy/Git/import_git.txt |
Git |
info_git.csv All information computed by the Git plugin (CSV). |
/projects/technology.apogy/Git/info_git.csv |
Git |
metrics_git.csv Current metrics for the SCM Git plugin (CSV). |
/projects/technology.apogy/Git/metrics_git.csv |
Git |
metrics_git.json Current metrics for the SCM Git plugin (JSON). |
/projects/technology.apogy/Git/metrics_git.json |
Jenkins |
jenkins_builds.csv The list of CI builds, in CSV format. |
/projects/technology.apogy/Jenkins/jenkins_builds.csv |
Jenkins |
jenkins_jobs.csv The list of CI jobs, in CSV format. |
/projects/technology.apogy/Jenkins/jenkins_jobs.csv |
Scancode |
metrics_scancode.csv The CSV list of metrics computed by the ScanCode plugin. |
/projects/technology.apogy/Scancode/metrics_scancode.csv |
Scancode |
scancode.json The JSON output of the ScanCode execution. |
/projects/technology.apogy/Scancode/scancode.json |
Scancode |
scancode_authors.csv The CSV extract of all holders authors in files. |
/projects/technology.apogy/Scancode/scancode_authors.csv |
Scancode |
scancode_copyrights.csv The CSV extract of all copyrights found in files. |
/projects/technology.apogy/Scancode/scancode_copyrights.csv |
Scancode |
scancode_files.csv The CSV list of all files analysed by Scancode. |
/projects/technology.apogy/Scancode/scancode_files.csv |
Scancode |
scancode_holders.csv The CSV extract of all holders found in files. |
/projects/technology.apogy/Scancode/scancode_holders.csv |
Scancode |
scancode_licences.csv The CSV extract of all license expressions found in files. |
/projects/technology.apogy/Scancode/scancode_licences.csv |
Scancode |
scancode_packages.csv The CSV extract of all packages identified in sources. |
/projects/technology.apogy/Scancode/scancode_packages.csv |
Scancode |
scancode_programming_languages.csv The CSV extract of all programming languages found in files. |
/projects/technology.apogy/Scancode/scancode_programming_languages.csv |
Scancode |
scancode_special_files.csv The CSV list of all special files. See documentation to know what a special file is. |
/projects/technology.apogy/Scancode/scancode_special_files.csv |
Page generated by Alambic 3.3.3-dev on Wed Aug 10 13:25:45 2022.