ow2 issueshttps://gitlab.ow2.org/groups/ow2/-/issues2021-04-22T10:26:28Zhttps://gitlab.ow2.org/ow2/mrl/-/issues/7Remove legacy user interface related to: Quality Assessment, Tools Quality Dr...2021-04-22T10:26:28ZAntoine MottierRemove legacy user interface related to: Quality Assessment, Tools Quality Drivers and Market ReadinessWhen the new version of MRL will be deployed in production we need to make sure to remove all pages, classes, sheets, etc related to the legacy solution.
For the user interface it includes:
* SHEET https://projects.ow2.org/edit/ow2/Proj...When the new version of MRL will be deployed in production we need to make sure to remove all pages, classes, sheets, etc related to the legacy solution.
For the user interface it includes:
* SHEET https://projects.ow2.org/edit/ow2/ProjectSheetOlivier LizounatOlivier Lizounathttps://gitlab.ow2.org/ow2/mrl/-/issues/8Remove elements related to OMM legacy solution superseded by OMM32021-04-22T10:24:47ZAntoine MottierRemove elements related to OMM legacy solution superseded by OMM3When OMM3 and associated MRL components will all be available in production we will need to remove current project rendering see #7 and the OMM legacy solution.
This include:
* Delete pages with URL `https://projects.ow2.org/view/<proje...When OMM3 and associated MRL components will all be available in production we will need to remove current project rendering see #7 and the OMM legacy solution.
This include:
* Delete pages with URL `https://projects.ow2.org/view/<project-name>/omm`
* CLASS https://projects.ow2.org/edit/ow2/Omm?editor=class
* SHEET https://projects.ow2.org/edit/ow2/OmmSheetOlivier LizounatOlivier Lizounathttps://gitlab.ow2.org/ow2/mrl/-/issues/13Remove outliers when computing average values2021-04-26T13:59:20ZPierre-Yves GibelloRemove outliers when computing average valuesSome computed values are averages: for example, BugOpenTime is the average issue open time.
In this case, a few values may be far above or below the standard deviation: they should be removed, considering them as outliers.Some computed values are averages: for example, BugOpenTime is the average issue open time.
In this case, a few values may be far above or below the standard deviation: they should be removed, considering them as outliers.Pierre-Yves GibelloPierre-Yves Gibellohttps://gitlab.ow2.org/ow2/mrl/-/issues/17Specify and implement factoid2020-12-14T14:42:44ZAntoine MottierSpecify and implement factoidFirst a quick note: I'm not sure factoid is the correct term to use (see: https://en.wikipedia.org/wiki/Factoid).
Idea is to generate sentence that give a meaningful description of the project maturity depending on the MRL score value.
...First a quick note: I'm not sure factoid is the correct term to use (see: https://en.wikipedia.org/wiki/Factoid).
Idea is to generate sentence that give a meaningful description of the project maturity depending on the MRL score value.
@cedric in order to implement this we need to have the structure of the sentence with placeholders for words that will depends on MRL score identified.
We also need to have the words to use depending on MRL score.
Can you provide use with such specification?
We will then implement it.
We need to decide if the implementation is inside MRL web app or in XWiki page. I would personnaly prefer to have a logic related to MRL packaged in the web app and limit XWiki to pure display (i.e. HTML+CSS without any code).
/cc @ol @gibellohttps://gitlab.ow2.org/ow2/mrl/-/issues/30Document MRL REST API endpoints2020-12-31T16:31:15ZAntoine MottierDocument MRL REST API endpointsI need to document the available endpoints, HTTP verb available and response structure.I need to document the available endpoints, HTTP verb available and response structure.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/mrl/-/issues/45Need to review projects OMM form content2020-12-30T13:33:51ZAntoine MottierNeed to review projects OMM form contentWe need to plan to do some verification of projects OMM form information in order to make sure they accurately represent the status of the project.
We should probably start with project in mature state and then move to project that are ...We need to plan to do some verification of projects OMM form information in order to make sure they accurately represent the status of the project.
We should probably start with project in mature state and then move to project that are in incubation and candidates to move to mature.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/mrl/-/issues/56Define folder to ignore for ScanCode for each projects2021-05-04T07:53:12ZAntoine MottierDefine folder to ignore for ScanCode for each projectsWe don't want ScanCode to run on project build results, it should only run on sources.
We need to define the list of folders to exclude for each projects.
Here is a generic start:
- For Maven projects: ignore `target` folder
- For Gradl...We don't want ScanCode to run on project build results, it should only run on sources.
We need to define the list of folders to exclude for each projects.
Here is a generic start:
- For Maven projects: ignore `target` folder
- For Gradle projects: ignore `build` folder
We need to double check that projects sources does not include a folder with same name as one we ignore.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/mrl/-/issues/58Allow to use human readable label instead of technical id label in dendrogram...2021-02-09T14:33:42ZAntoine MottierAllow to use human readable label instead of technical id label in dendrogram displayCurrently the dendrogram display technical id as node label (e.g. `OMM_DOC`).
The need is to have a more "human readable" label (e.g. `Project documentation`).
To do so we need:
- [ ] a list of human readable labels for all dendrogram...Currently the dendrogram display technical id as node label (e.g. `OMM_DOC`).
The need is to have a more "human readable" label (e.g. `Project documentation`).
To do so we need:
- [ ] a list of human readable labels for all dendrogram nodes
- [ ] define technical id for MKT form with out blanks (e.g. `MKT-1`, `MKT-2`, etc.)
- [ ] update the web application to use new technical ids
- [ ] update the XWiki front end to convert technical id to human readable labelsAntoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/mrl/-/issues/62Fix coverage == 0 for Knowage2021-05-31T09:17:37ZAntoine MottierFix coverage == 0 for KnowageOn [Knowage SnoarQube](https://sonarcloud.io/dashboard?id=it.eng.knowage%3Aknowage-core) (actually a SonarCloud) code coverage is at 0.
The [CI](https://github.com/KnowageLabs/Knowage-Server/blob/master/.travis.yml) (Travis) run Maven p...On [Knowage SnoarQube](https://sonarcloud.io/dashboard?id=it.eng.knowage%3Aknowage-core) (actually a SonarCloud) code coverage is at 0.
The [CI](https://github.com/KnowageLabs/Knowage-Server/blob/master/.travis.yml) (Travis) run Maven phases: `clean`, `compile` and Maven goal `sonar` but not phase `test`. Probably a good lead.
Need to check core pom.xml: https://github.com/KnowageLabs/Knowage-Server/blob/master/knowage-core/pom.xml
and also parent pom.xml: https://github.com/KnowageLabs/Knowage-Server/blob/master/knowage-ce-parent/pom.xml
Probably need to:
- Add missing JaCoCo plugin.
- Push change on a fork.
- Update GitLab Oscar CI for Knowage.
- Test with OW2 SonarQube instance.
- Open a pull request at Knowage.
Extra references:
- https://community.sonarsource.com/t/coverage-missing-on-sonarqube-coverage-is-not-showing-multimodule-maven-project/23169
- https://stackoverflow.com/questions/13031219/how-to-configure-multi-module-maven-sonar-jacoco-to-give-merged-coverage-repAntoine MottierAntoine Mottier2021-06-30https://gitlab.ow2.org/ow2/mrl/-/issues/68Random best practices verification2021-06-09T16:16:14ZCedric ThomasRandom best practices verificationRandom best practices form stage 1 verification for projects with highest scores. Check the best you can accuracy of replies.
- [x] [spoon](https://projects.ow2.org/view/spoon/omm3)
- [x] [proactive](https://projects.ow2.org/view/proac...Random best practices form stage 1 verification for projects with highest scores. Check the best you can accuracy of replies.
- [x] [spoon](https://projects.ow2.org/view/spoon/omm3)
- [x] [proactive](https://projects.ow2.org/view/proactive/omm3)
- [ ] [imixs-workflow](https://projects.ow2.org/view/imixs-workflow/omm3)
@amottier @gibello or @mhhttps://gitlab.ow2.org/ow2/mrl/-/issues/71Update OMM3 form tooltip for SEC-12021-03-01T14:12:10ZAntoine MottierUpdate OMM3 form tooltip for SEC-1We need to provide guidance regarding possible solution to answer yes to this question.We need to provide guidance regarding possible solution to answer yes to this question.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/mrl/-/issues/78No license ratio calculation2021-05-03T07:55:55ZAntoine MottierNo license ratio calculation- [ ] We need to confirm if Scancode read and use information regarding license that might be available in a SPDX file in the project repository.
- [ ] We need to define the exhaustive list of file mime type that we found in our project...- [ ] We need to confirm if Scancode read and use information regarding license that might be available in a SPDX file in the project repository.
- [ ] We need to define the exhaustive list of file mime type that we found in our projects.
- [ ] For each mime type we need to define if they need to be included or not in no license ratio.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/mrl/-/issues/81Create a project logo and label image for evaluated projects2021-09-06T12:23:23ZAntoine MottierCreate a project logo and label image for evaluated projectsWe need 2 distinct images:
- [ ] a logo for the project
- [x] an image to be added as label to projects evaluated with MRLWe need 2 distinct images:
- [ ] a logo for the project
- [x] an image to be added as label to projects evaluated with MRLhttps://gitlab.ow2.org/ow2/mrl/-/issues/83Manual launch of `collectdata.sh`2021-05-03T12:30:33ZCedric ThomasManual launch of `collectdata.sh`Create an interface to launch `collectdata.sh` manually on demand without having to wait for the daily cron.Create an interface to launch `collectdata.sh` manually on demand without having to wait for the daily cron.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/mrl/-/issues/89Improve Knowage ScanCode job execution2021-04-06T08:35:24ZAntoine MottierImprove Knowage ScanCode job executionCurrently job takes few hours (between 3 and 4) to complete.
Need to improve that.Currently job takes few hours (between 3 and 4) to complete.
Need to improve that.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/mrl/-/issues/93Marketing MRL2021-04-26T17:21:43ZCedric ThomasMarketing MRLNow MRL is technically developed it is time to promote it. This issue is to list promotion ideas and to follow-up progress.
- [ ] MRL slide deck
- [ ] MRL video primer
- [ ] MRL endorsement, testimonials
- [ ] MRL press release
Partici...Now MRL is technically developed it is time to promote it. This issue is to list promotion ideas and to follow-up progress.
- [ ] MRL slide deck
- [ ] MRL video primer
- [ ] MRL endorsement, testimonials
- [ ] MRL press release
Participants: @allhttps://gitlab.ow2.org/ow2/mrl/-/issues/96Add a "Credits" file2021-08-12T14:26:23ZAntoine MottierAdd a "Credits" fileTo credit contributors, libraries and tools used to build the project, etc.To credit contributors, libraries and tools used to build the project, etc.https://gitlab.ow2.org/ow2/mrl/-/issues/97description for of key/label name2021-05-17T13:33:14ZMartin Hamantdescription for of key/label nameIn the screenshot below the label `act_bugs` seems to come from the database (table `Aggregate`, field `AggregateName`).
In this example, `act_bugs` is the label for the human-readable `Bug Handling` aggregate as documented in [MRL's Sta...In the screenshot below the label `act_bugs` seems to come from the database (table `Aggregate`, field `AggregateName`).
In this example, `act_bugs` is the label for the human-readable `Bug Handling` aggregate as documented in [MRL's Stage 2](https://www.ow2.org/view/MRL/Stage2-ProjectAttributes#HComputation).
At some point we might want to be able to display a human readable "full name" to the end user rather than a system-like key/label
![image](/uploads/2af2bd27f597990c083589ac8d0a16dd/image.png)
![image](/uploads/fb2f81808cc78d6852472752d618cc6f/image.png)
When could leverage the `Description` field for this, and get it exposed by the API then get it displayed somehow in the dendrogramhttps://gitlab.ow2.org/ow2/mrl/-/issues/101Analysis of project with multiple programming languages and/or projects with ...2021-12-20T14:44:05ZAntoine MottierAnalysis of project with multiple programming languages and/or projects with multiple Git repositories and/or multiple componentsOur current implementation mostly assume that a "project" is a single Git repository with a software build using a single type of package manager or equivalent (e.g. Maven, Gradle, NPM, Pip, Make, etc.), this software being considered as...Our current implementation mostly assume that a "project" is a single Git repository with a software build using a single type of package manager or equivalent (e.g. Maven, Gradle, NPM, Pip, Make, etc.), this software being considered as a single component and usually a single programming language used.
This is actually not inline with several OW2 projects. E.g.:
- XWiki includes at least 2 distinct Git repositories ([xwiki-platform](https://github.com/xwiki/xwiki-platform) and [xwiki-commons](https://github.com/xwiki/xwiki-commons)) that include source code required to build the final binary version
- Knowage has a single Git repository ((Knowage-Server)[https://github.com/KnowageLabs/Knowage-Server]) that includes component coded in Java ((knowage-core)[https://github.com/KnowageLabs/Knowage-Server/tree/master/knowage-core]) and other coded in JavaScript ((knowage-vue)[https://github.com/KnowageLabs/Knowage-Server/tree/master/knowage-vue]). `knowage-vue` is actually a Java web application built using Maven but Maven will actually trigger execution of NPM to build the JavaScript code that use the Vue.js framework.
- ASM is a project build from several components/subprojects (core, tree, util, etc), but we provide only a global result and didn't isolate each individual component (see https://gitlab.ow2.org/ow2/servicedesk/-/issues/517#note_42028);
I think the first step to solve this complex problem is to define a list of "elements" types (e.g. OW2 project, Git repository, SonarQube project, project module, etc.) and clarify how they relate together (relation 1..1, 1..*, *..*).
I guess that our goal should be that MRL give a vision of the whole OW2 project no matter the underlying organization of the code. Probably some aggregation would be needed to group data coming from different sources (of different types: GitHub repository, Scancode results, etc.) for a single MRL project and maybe also some aggregation need to be done in SonarQube.https://gitlab.ow2.org/ow2/mrl/-/issues/102display date of the latest analysis/freshness in MRL tab2021-12-20T14:44:05ZMartin Hamantdisplay date of the latest analysis/freshness in MRL tabI remember having raised this some months ago in a MRL call but forgot about it since then.
It got reminded by the comment from Eric in https://gitlab.ow2.org/ow2/servicedesk/-/issues/517#note_42862. Implementing this would solve two of...I remember having raised this some months ago in a MRL call but forgot about it since then.
It got reminded by the comment from Eric in https://gitlab.ow2.org/ow2/servicedesk/-/issues/517#note_42862. Implementing this would solve two of the three items mentioned in this issue.