2019-01-11

Summary

Team Meeting

11 JANUARY 2019 / 11:00 AM / #ow2-tc on IRC, freenode

Participants

  • Iyad Alshabani (IAL)
  • Daniele Gagliardi (DGA)
  • Martin Hamant (MHA)
  • Davide Zerbetto (DZE)
  • Assad Montasser (AMO)
  • Benoit Mortier (BMO)

Agenda

Download stats state of the art

  1. Update by MHA: he is finishing the script that take care to launch the matomo log analysis on the right set of logfile, at the right time, avoiding duplicate metrics

New project acceptance process: state of the art

  1. DGA recaps the situation: at https://tc.ow2.org/view/wiki/Project%20lifecycle we have defined the project acceptance process. In the issue https://gitlab.ow2.org/ow2/technology-council/issues/7 there is a proposal to update the process in order to give explicit importance to vetoes. The idea is: even if a project receives just one motivated veto, the acceptance process should be suspended, to solve issues related to vetoes. In last discussions there were two approaches: one define explicitly a set of criteria that must be met in order to avoid the veto; the other approach prefers to have less explicit criteria,but at the same time keep the importance of the vote. Both approaches ask for suspending the acceptance process, in order to fix veto issues
  2. IYA asks whether is there anybody in the TC against the fact that a Veto suspends the process.
  3. DGA says no objections have been raised by TC members, until today
  4. DGA proposes to add to the page https://tc.ow2.org/view/wiki/Project%20lifecycle, in the "Project Acceptance" section the following statement: "A soon a a veto has been given, the vote is stopped up to a week starting from the moment the objection is raised, and the applicant has to answer the objections before the vote is started again. All the objections are raised and sent to the mailing list, the applicant has (how much time? TBD) to answer them. If they are not answered satisfyingly the vote is stopped and the project is rejected." as per the BMO's proposal
  5. YIA agrees, noticing that maybe one week for the applicant is too short
  6. DGA agrees too
  7. DGA will send an email to TC to propose the change

Google Summer of Code 2019

  1. DGA reports about the email sent before Christmas holidays to participate to GSoC 2019: 2 project leaders (Romain Ferrari and BMO) are interested
  2. DZE is interested too on KnowAge side
  3. YIA reports OW2 MO considers GSoC not really relevant
  4. DGA proposes that would 2 or more projects are interested in it, it would be worth to have another chance for the current year
  5. DGA proposes to collect information about MO effort to be a mentoring organization for this year (deadline: next tuesday, January 15 th), send communication to TC ML and collect interested projects: each interested project commits to provide ideas, which will be published on a wiki page (deadline: 24  January), then OW2 submit applications to GSoC 2019. Info and hints at:
    1. https://tc.ow2.org/bin/view/wiki/GSoC+2018+Ideas+List
    2. https://www.owasp.org/index.php/GSOC2018_Ideas
    3. https://developers.google.com/open-source/gsoc/timeline
  6. YIA agrees with it
  7. DGA: the wiki page will be structured per project, each project with a set of ideas
  8. at 12:00 the meeting ends