Hello Awasum, Yes, they have an entry, it was requested to Apache Infra team, but I mean to add the configurations required in the .yml and in the build configuration files for reporting the analysis result to SonarCloud for each Fineract-CN repository.
Regards. Victor El mié, 20 oct 2021 a las 10:48, Awasum Yannick (<[email protected]>) escribió: > Hi Victor, > > I searched SonaQube and found that most Apache projects already have > defined keys or ids which we can reuse when referencing Fineract CN repos: > https://sonarcloud.io/organizations/apache/projects?search=fineract > > > On Wed, Oct 20, 2021 at 2:18 PM Awasum Yannick <[email protected]> wrote: > >> >> >> On Wed, Oct 20, 2021 at 12:32 PM James Dailey <[email protected]> >> wrote: >> >>> Yes. Good to have another measure. Thanks Victor! >>> >>> I would not be discouraged and please take the total days w a big grain >>> of salt. These automated tools are kinda mindless (sic). >>> >> >> I was thinking more along the lines of if the estimate is this long, then >> in an open source project where all the contributors are volunteers, it >> will probably take longer than a year to get compliant with SonarQube. >> >> Some of those code smells and bug reports might be false positives. >> >>> >>> Curious if the six blocker issues found are critical and already raised >>> on Jira in some way? (That would be a good data point.) >>> >>> Maybe version 1.6 can reduce this debt estimate by 25% ? Is that a good >>> target? >>> >> >> Depends alot on the volunteers available. Even just a 5% technical debt >> reduction per month is a good goal given the community rate of code >> contributions. >> >> The good thing is that with SonarQube in place, we can check and make >> sure new code doesn't increase the technical debt. >> >> Recently at work, we started using SonarLint (https://www.sonarlint.org/) >> to aid us in writing higher quality code. SonarLint is actually the >> lighter, IDE specific version of SonarQube, It will find faults or errors >> as you code before it even reaches the compile stage or CI tools. It would >> be a good idea to test it on a Fineract repo and follow most of the >> recommendations. >> >> >>> >>> >>> >>> >>> >>> On Tue, Oct 19, 2021, 10:47 PM Awasum Yannick <[email protected]> wrote: >>> >>>> Thanks very much for this valuable work Victor. >>>> >>>> This will help the Fineract code bases to improve in quality over time. >>>> >>>> Woow, we have about 360 days of tech debt... Weeeew... >>>> >>>> This will probably also be added as a point in Fineract 1.x roadmap >>>> been discussed on the other thread. >>>> >>>> On Wed, Oct 20, 2021, 05:58 VICTOR MANUEL ROMERO RODRIGUEZ < >>>> [email protected]> wrote: >>>> >>>>> Hello Fineract Community, >>>>> >>>>> Today the SonarQube at SonarCloud is publishing the results of the >>>>> Fineract's Source Code Analysis. >>>>> >>>>> https://sonarcloud.io/dashboard?id=apache_fineract >>>>> >>>>> The results will give us visibility about the improvements that can be >>>>> done for improving the QA. >>>>> >>>>> Now working also in the Fineract-CN repositories and I will let you >>>>> know the results. >>>>> >>>>> Regards >>>>> >>>>> Victor >>>>> >>>>
