TC Meeting - 2017-01-13


Participants

  • Daniele Gagliardi DGA
  • Martin Hamant MHA
  • Stéphane Laurière SLA
  • Daniel Le Berre DLB
  • Marius Matei MMA
  • Benoit Mortier BMO
  • Clément Oudot CLO

Minutes

User management service

  • The login procedure has changed on all OW2 sites, mirgation to FusionDirectory done, one single auth for all wikis
  • Logging in requires that you ask for a password reset first
  • DGA, KPTN, BMO can log in successfully on www.ow2.org and on JIRA
  • MHA: Pending : reconfigure all groups and access rights
  • MHA managed to make JIRA use paginated results (it holds a local cache of all users and groups from the LDAP)
  • MHA:: The status and ongoing tasks related to the finalization of the migration are available on the OW2 infrastructure status page
  • Several options for managing issues: use a dedicated component in SERVICEDESK, or turn UM into public, or use an issue collector or use GitLab once it's up – to be discussed. We don't want to maintain UM issues in multiple areas. We should make sure to add a link to the issue tracker in the login panel.
  • DGA: Bulk fonctions can be used in JIRA.

Forge v2

GitLab

  • MHA We'll be ready to fire up the VM next week or soon after
  • DGA asks if is it usable also with Maven site generator goal. DLB is not sure yet,but in principle, it can be anything.
  • BMO: we use Proxmox and its RPC API to boostrap vm emoticon_smile
  • DGA: new to Proxmox, will check it. DGA mentions the GitLab Docker support
  • BMO: no use of Docker at the moment but will look into the feature.
  • DLB is ready to give insights and help regarding the setup / usage of GitLab and SonarQube.
  • BMO is also looking to GitLab to mirror the Git repo on OW2 infrastructure
  • DLB: GitLab now supports pages: https://about.gitlab.com/2016/12/24/were-bringing-gitlab-pages-to-community-edition/
  • DLB is looking forward to moving to GitLab + GitLab pages for Sat4j
  • MHA is not in favor to bring project websites on GitLab pages OR xwiki: we have to consolidate, here again
  • BMO agrees
  • SLA: the less tools the better probably, as long as it fits the needs
  • DBL: ok, GitLab pages is not my priority emoticon_smile
  • BMO: GitLab pages could be a nice way to do a simpler site for us we have already a big site in production

Statistics

  • MHA open questions: how to handle release management, and how to use a CDN, how to get statistics? How to have a smooth transition from GForge to GitLab on this topic?
  • MHA: statistics depend entirely on how we will host the files
  • SLA:  an option for getting detailed statistics would be to use a tool like JFrog Artifactory
  • As for Web site statistics, BMO suggests the use of Piwik
  • MHA: we have to consolidate the old downloads with the newer from GitLab
  • MHA: we currently use http://download.forge.ow2.org/ - a mirror of GForge download volume - and https://stats.ow2.org (login required). The current system gather stats from the log of the website above ie http://download.forge.ow2.org/
  • MHA: an important task will be to match old download to GitLab instance to make proper releases
  • MHA: my take is that for statistic we should use a tool designed for that
  • DGA agrees on this: serveral ETL were developed with Spago4Q in 2015-2016. See also QDash.
  • BGO: could the old release mechanism automatically moved to the new GitLab?inside the new gitlab could be automatized ??

Releases

  • BMO: Gitlab like GitHub has a release system. Example: https://github.com/otrosien/sonar-perl/releases/download/0.2.10/sonar-perl-plugin-0.2.10.jar
  • DLB: GitLab relase feature: https://about.gitlab.com/2015/11/22/gitlab-8-2-released/
  • MHA: if iam right, download.ow2.org will be historical and the release will be inside GitLab or still be hosted on download.ow2.org
  • DLB: releases in GitLab are just git tags, right?
  • MHA: all releases will be hosted on a single place download.ow2.org. We have to consolidate the path/version/name thing. Old is /project/projectname-version-packagename new is ... GitLab own scheme
    MHA: on the  download topic, the initial work is to consolidate the download access scheme
  • SLA: the OW2 Management Office is in touch with the JFrog team, considering the use of JFrog Artifactory for managing binaries with integrated statistics

Continuous integration

  • SLA: We got very positive feedback from AlterWay who migrated entirely from Jenkins to GitLab-CI and they're very happy with the move
  • DGA mentions that'd be good to know more about their detailed experience.
  • SLA: one of the reasons for the move was that were very happy with the way GitLab-CI manages Docker containers for CI
  • BMO: we are heavy user of Jenkins but welcoming other experience
  • SLA: GitLab-CI is integrated in the community edition (to be checked)
  • DGA: yes and gitlab also manage a docker images repository integrated in in the community edition

OSCAR

Metrics / Quality Model / AppHub

  • GrimoireCon: http://grimoirelab.github.io/con/ it will take place Feb 3. afternoon in Brussels, just before the FOSDEM
  • SLA has registered and will attend the con, it's about metrics. SLA invites everyone to join: Bitergia is doing a great job around metrics gathering and display.
  • Another quality model found, within the Eclipse community, at PolarSys / Alambic project: http://eclipse.castalia.camp/documentation/quality_model.html Cédric and SLA are in touch with the author, Boris Baldassari, participant in the CROSSMINER project, on behalf of Eclipse Europe R&D. See also: http://castalia.camp/alambic/
  • DGA likes it's based on GQM and finds it interesting.
  • SLA: we have no news since months from the Antelink team, Not sure what's going on, but we may need to search for alternate software for checking vulnerabilities and source code originality. Any idea welcome.
  • SLA: a new "Deployment" tab was added to some of the OW2 projects dashboards, giving access to Cloud images generated by AppHub.

SonarQube plugins

  • BMO mentions that the FusionDirectory project is using SonarQube for Perl and PHP with great success, so we can ask for help or tips on this matter
  • SonarQube in action at FusionDirectory: https://sonar.fusiondirectory.org/
  • Plugin used: https://github.com/otrosien/sonar-perl
  • BMO: our Jenkins is used to do the parsing with perlcrtic, then sent to sonar
  • BMO: we use SonarQube to scan and evalutate the code of our argonaut project, i'am a contributor/tester to the sonarperl plugin
  • BMO: we have our own instance, i'am a big fan of everything under our control emoticon_smile
  • SLA mentions https://www.sourcemeter.com/ as a potentially useful plugin for SonarQube (it adds 70+ new measurements), developped by FrontEndART, a company participating with OW2 in the CROSSMINER H2020 project. Not open-source yet but they're working on it. Does not work with PHP or Perl.

Google Summer of Code

  • Organization registration starts 19 January. SLA to look into the exact process.
  • BMO/SL: OW2 will be the mentoring organization, then, if accepted, each project can propose topics under the OW2 umbrella

FOSDEM 2017

  • SLA: the more project leaders the better for running the booth
  • BMO, CLO will take part in it

STAMP

  • DGA, SLA, MHA will have a discussion about the STAMP platform.
  • DLB is ready to consider participating in STAMP

OpenPaas

  • SLA: since we got no reaction from Linagora on the licensing issue despite several e-mails, we've mode OpenPaas to the archive eventually. That's a pitty but we need to make sure that all the projects hosted by OW2 comply with an OSI-approved license. It is not the case for OpenPaas.

Next meeting

  • DLB mentions he will be teaching on Friday morning starting Jan 27, hence won't be available to participate in the TC meetings until end of March
  • Next meeting: Fri. 27 January 11:00 12:00 am CET