TC Meeting - 2016-05-13

Participants

  • Marc Dutoo (MDU)
  • Daniele Gagliardi (DGA)
  • Yosu Gorroñogoitia (YOG)
  • Martin Hamant (MHA)
  • Daniel Le Berre (DLB)
  • Stéphane Laurière (SLA)
  • Jean Parpaillon (JPA)
  • Clément Oudot (CLO)

Minutes

Contents

Contest

Discussion

  • YOG: some reward is required, no student will work for free
  • JPA: one GSoC student an and Inria intern are working on erocci
  • MDU: in case "bounties" are proposed to the students, we may consider opening up the contributions to individual members. We'd have then a "market of contest topics".
  • JPA is in favour that OW2 becomes a "mentor organization" for other contests, with the following line of reasoning:
    • Apache or other OSS organizations do not have their own contest, they participate in the Google Summer of Code (and possibly other similar programs)
    • Inria has alrady its own contest sponsored by IRILL, it cannot sponsor many other contests
    • Getting OW2 listed on the GSoC page of participating organizations is a must
    • Consolidating other contests would have the advantage of focusing on the OW2 projects and their developers and not trying to compete with better funded or more famous contest
    • The participation of OW2 would then consist in:  
      • 1) reminding project leaders of the deadlines for such contest
      • 2) helping them submit either formally when mentoring organization have a status (like GSoC) or informally when it is not the case (IRILL/Inria contest for instance)
    • That way we will delegate 1) the funding question 2) the organization and some other work benefit from these contests visibility and focus on developing our projects
  • CLO is not participating in the GSoC due to lack of time, not of interest
  • DGA: we should make a selection/a list of available contests...
  • General consensus from the participants that the approach proposed by JPA is meaningful.

The Google Summer of Code process

JPA gave have overview of the GSoC process:

  • Key actors: mentors, mentor organizations, students and Google
  • Google organizes and funds
  • Mentors submit topics
  • Mentor organizations groups topics
  • Not sure if mentors can submit alone, it seems it was the case before but not this year
  • JPA got contacted by 'beam' organization which groups erlang topics, then submitted 3 topics for the project 'erlang DBus' and students have picked this topics and made a proposal based on that topics
  • Then the mentor organization told Google 1/ who was the mentors 2/ which student got chosen and their proposal
  • Given that there were more proposals / students than slots allocated by Google, a selection was made internally in the beam group, trying to have at least one topic by project (2 proposals were received for DBus, ejabberd had 3...)
  • Google rule is 1 mentor = 1 student

See also Google Summer of Code.

Actions

  • Discuss these ideas within the TC, the MO, then the board
  • If approved, be ready for GSoC 2017
  • Know more about the Inria contest in order to see how we can get our projects involved
  • Look for other programs the OW2 projects could get involved into
  • Keep the current OW2 Contest running and see how it can evolve with our partners in China in terms of funding / internationalization
  • Check the existence of possible other OSS-oriented contests in China / possible additional partners in that area (academic, industry, ...)

New forge and infra

  • DGA: Engineering is currently installing GitLab
  • MHA + SLA: the current plan is to finalize the new LDAP + FusionDirectory integration, then to streamline the OW2 virtualization infrastructure, then to progress with the set up of GitLab
  • SLA via DLB: GitLab got a badge from the CII Linux Foundation quality program
  • DLB: the GitLab team is really serious about security

Projects review

Eligibility for maturity

  • Lutece has almost reached maturity, it is about to be ok
  • Imixs-Workflow
  • Prelude
  • Nanocloud
  • Trustie
  • ... list to be completed and discussed within the TC
  • NB: MDU: we have to check with Gurkan the status of Jonas

Eligibility for archiving

To be discussed with the TC:

  • Choreos IDRE
  • OpenPaas (licensing issue: not OSI-compliant license)
  • Nursery
  • NB: DLB emphasizes that we need to check the download figures before archiving any project

Individual members community

Olivier B.  started writing a template for interviewing members

Conferencing system

List of tools at Conferencing. Tox group chat is progressing but not ready yet.

Next meeting

Next meeting date: Fri 27/05 11:00 am - 12:00 am CET