ow2 issueshttps://gitlab.ow2.org/groups/ow2/-/issues2023-12-20T10:40:10Zhttps://gitlab.ow2.org/ow2/servicedesk/-/issues/594Register account waiting2023-12-20T10:40:10ZClément OUDOTRegister account waitingSeems someone is waiting for the register process, see this comment: https://github.com/LemonLDAPNG/lemonldap-ng/issues/3#issuecomment-1863284515
Could you check?Seems someone is waiting for the register process, see this comment: https://github.com/LemonLDAPNG/lemonldap-ng/issues/3#issuecomment-1863284515
Could you check?https://gitlab.ow2.org/ow2/mrl/-/issues/109improving rocketchat's meteor installation2023-07-17T15:50:58ZMartin Hamantimproving rocketchat's meteor installationI'm currently starting from a buster slim image and run the meteor installation script from there (as user `meteor`). After that I'm storing the resulting `.meteor` folder in as cache. It's about 2GB large.
Then the cache is restored in...I'm currently starting from a buster slim image and run the meteor installation script from there (as user `meteor`). After that I'm storing the resulting `.meteor` folder in as cache. It's about 2GB large.
Then the cache is restored in the next job (`test`).
The main issue here is performance: storing and restoring 144K files for a total size of 2GB is I/O intensive.
One possibility I could explore is to store the runtime as part of the mounted docker host storage (`/srv/project-sources`) then run that from the container.Antoine MottierAntoine Mottierhttps://gitlab.ow2.org/ow2/mrl/-/issues/113Add Redmine issue support2023-01-23T19:20:13ZAntoine MottierAdd Redmine issue supportLutece is migrating from Jira to Redmine so we need to add the support for Redmine.Lutece is migrating from Jira to Redmine so we need to add the support for Redmine.https://gitlab.ow2.org/ow2/mrl/-/issues/112Installation and Upgrade instructions seems to be globally missing2022-06-28T07:51:06ZAlban Espié-GuillonInstallation and Upgrade instructions seems to be globally missingREADME seems to be lacking clear installations for new installations, upgrade steps may be missing as well.README seems to be lacking clear installations for new installations, upgrade steps may be missing as well.https://gitlab.ow2.org/ow2/mrl/-/issues/111Evaluate the current approch for unanswered bugs thresholds2022-01-13T12:26:22ZAntoine MottierEvaluate the current approch for unanswered bugs thresholdsAfter getting some questions from XWiki regarding their score in quality metric we did some investigation.
2 queries (see [JiraHandler.java](https://gitlab.ow2.org/ow2/mrl/-/blob/master/data-collection/src/main/java/org/ow2/mrl/data/jira...After getting some questions from XWiki regarding their score in quality metric we did some investigation.
2 queries (see [JiraHandler.java](https://gitlab.ow2.org/ow2/mrl/-/blob/master/data-collection/src/main/java/org/ow2/mrl/data/jira/JiraHandler.java) for the exact query definition) are executed on XWiki issue tracker:
- To get the total number of opened issues: `Type=Bug AND Status=Open AND project = XWIKI` : https://jira.xwiki.org/browse/XWIKI-19127?jql=Type%3DBug%20AND%20Status%3DOpen%20AND%20project%20%3D%20XWIKI%20ORDER%20BY%20created%20DESC
- To get the total number of issues with comments: `Type=Bug AND Status=Open AND comment!~'\"M"' AND Project=XWIKI` https://jira.xwiki.org/browse/XWIKI-19126?jql=Type%3DBug%20AND%20Status%3DOpen%20AND%20comment!~%27%5C%22M%22%27%20AND%20Project%3DXWIKI%20ORDER%20BY%20created%20DESC
In our test today we add 1022 opened issue and 673 of them have comments leading to a remaining of 349 issue without comments so flagged as "unanswered".
Value of the metric is defined by threshold get using REST API call on https://projects.ow2.org/get/ow2/Project_metrics_thresholds
The different thresholds for unanswered bugs are currently defined with absolute numbers of bugs without comments: `UnansweredBugs,15.0,50.0,100.0,150.0,300.0,1`
As we have a value (`349`) higher than the threshold `300.0` the metric value is set to 0.
@gibello I suggest that we discuss together to validate that having absolute values for threshold is the best option we currently have. We might use percentage of opened bugs or maybe use a coefficient depending on project "popularity".Pierre-Yves GibelloPierre-Yves Gibellohttps://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.https://gitlab.ow2.org/ow2/mrl/-/issues/110Zenroom to SonarQube2021-12-17T10:34:32ZMartin HamantZenroom to SonarQubeWe are working on this with Jaromil using https://github.com/SonarOpenCommunity/sonar-cxx (because SonarQube Community Edition doesn't provide a C analyzer.).
/cc @amottierWe are working on this with Jaromil using https://github.com/SonarOpenCommunity/sonar-cxx (because SonarQube Community Edition doesn't provide a C analyzer.).
/cc @amottierAntoine 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/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/107Setup SonarQube for GLPI2021-08-10T14:33:47ZAntoine MottierSetup SonarQube for GLPIWe need to configure the CI to run Sonar Scanner on GLPI.
Some information can be found in [CONTRIBUTING.md](https://github.com/glpi-project/glpi/blob/9.5/bugfixes/CONTRIBUTING.md), [tests README.md](https://github.com/glpi-project/glpi...We need to configure the CI to run Sonar Scanner on GLPI.
Some information can be found in [CONTRIBUTING.md](https://github.com/glpi-project/glpi/blob/9.5/bugfixes/CONTRIBUTING.md), [tests README.md](https://github.com/glpi-project/glpi/blob/9.5/bugfixes/tests/README.md) and in [run_tests.sh](https://github.com/glpi-project/glpi/blob/9.5/bugfixes/tests/run_tests.sh).
Running the tests require to use [atoum](http://atoum.org/) an alternative or addition to PHPUnit. Explanation why GLPI moved from PHPUnit to atoum can be found in a [blog post](https://glpi-project.org/glpi-now-uses-atoum-for-its-unit-tests-2/).
atoum has an [extension](http://extensions.atoum.org/extensions/reports) to produce Sonar coverage reports.https://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/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/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/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/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/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/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/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/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 Lizounat