2018-10-05

Summary

Agenda
Download stats state-of-the-art
Other business - Spectre project & Project acceptance process/projects lifecycle
IRC logs
Next meeting

Team Meeting

05 OCTOBER 2018 / 11:00 AM / #ow2-tc on IRC, freenode

Agenda

OW2 download statistics solution: state-of-the-art, part 2;
Any other business

Participants

Daniele Gagliardi DGA
Martin Hamant MHA
Olivier Lizounat OLI
Assad Montasser AMO
Benoit Mortier BMO
Davide Zerbetto DZE
Jean Parpaillon (JPO)

Minutes

Download stats state-of-the-art

MHA: any comments on https://tc.ow2.org/view/wiki/Download-Statistics and https://tc.ow2.org/view/wiki/Download-Statistics-Part2?
DZE: 1. possibility to have download information as CSV file is a must (raw CSV data)
DGA provides a url exporting CSV data ( curl 'https://ow2-utils.ow2.org/matomo/?module=API&method=Actions.getDownloads&idSite=5&period=month&date=2018-05-01&format=csv&token_auth=anonymous&expanded=1' --output asm.csv)
MHA: not the same data/method/metrics than the one showed in the wiki
DZE: but let's try to start from some basic information
MHA: geoloc need has been mentioned before, but indeed "Of course one could also use a combination of Actions.getDownloads and Live.getLastVisitsDetails depending on taste/performance results." Live module provide you with everything in one request
MHA: unsure then how to make a relation / combination with the result from both methods, using both methods, maybe we could process both json files based on a pivot attribute (being download url)
BMO: i have a script somewhere that does that, i will try to find a better one after the meeting
DZE: having data in CSV format is a must, but we can discuss about information CSV file should contain
MHA: that was unclear to me that's why I have asked about it, anyway a script as bilbo-the-hobbit provided can be an inspiration for what we need to implement in xwiki
OLI: ok
MHA: other question I have, is about the time period: wouldn't it be better to have "the last X months" ?
OLI: save each month and at the end of year get a summary for the year ?
BMO: yes thats my idea
DZE: regarding CSV file in part 2: in 1 row I'd like to see: file, number of donwloads, year, month, country. I'd prefer to have a separate row for each country, and I'd like to have data for all countries, if possible
MHA: got it.
DZE: regarding YTD, the requirement is: I'd like to see how donwloads are going this year and compare with previous years, having details at month level (because I want to see what happended when releasing a new version of the product). If user can have values for last X month is fine
MHA: anyway let's start easy. We could provide a single CSV per month
DZE: I'd prefer to have a separate row for each country, and I'd like to have data for all countries, if possible
MHA: In my original suggestion, I was suggestion a country % distribution per file
DZE: we can have values for top 10 countries and other countries aggregated, top 10 or top 20 ...
DZE: to clarify requirement about comparing values for current year with previous years: I don't expect the system to do it by itself. We can get numbers every year, and then compare them with Knowage. For us it is quite easy...
MHA: OLI are you all right with above?
OLI: globally yes, need to test
MHA: OK, and I will help OLI with XWiki/Java app
DGA: Nicola Bertazzo could help but in this period he's very busy
MHA: a last thing, to me the hot topic in xwiki dev about stats is storing/cache the data locally
DGA: we can develop a database for XWiki where to store stats. I will ask Nicola when he'll be available. We can also ask VIncent Massol (better)
MHA: ok to ask Vincent Massol

Other business - Spectre project & Project acceptance process/projects lifecycle

DGA: Spectre project was accepted in the code base, but need to take into account BMO's concerns
MHA: can you recall how the decision is made regarding the vote results
BMO: I think if someone veto it should not be overidden because then veto is useless
DGA: I agreer, but according to https://tc.ow2.org/view/wiki/Project%20lifecycle, "An option that obtains the majority+1 of casted votes will be chosen."
MHA: this assert doesn't take veto into account, isn't ?
DGA: it is, that's why I declared accepted: we had the majority +1 of positive votes
MHA: so what's the function of the veto then ?
DGA: I think we should define better the importance of vetos
BMO: a veto is a veto
DGA: we should say something like "a project to be accepted needs to have no veto at all" in the acceptance process criteria
DGA: we can't go back, but we need to make SPECTRE project leaders aware that they should provide the missing info
BMO: so we must put them on some kind of trial and ask them to fix the issues no ?
MHA: anyway SPECTRE is in incubation
DGA: ok, incubation status fits well for SPECTRE project, the question is: how long a project can stay at incubation level?
DGA: more generally I think we should refine the project lifecycle. 1. imporance of vetos, 2. incubation period duration
OLI: not sure there is a delay, it's more "is this project is mature?"
MHA: explicitely define a delay means someone should care about it
DGA: should project leaders ask for it? should TC periodically examine incubation projects? can a project remain indefinitely at incubation level?
MHA: OW2 can ask, because it's all in our interest to have mature projects. Anyway all good questions. Currently, events are : the projects ask for it OR the CTO takes care of projects lifecycle. But it's very rare that project ask from themselves
MHA: we should show and promote what are the interests, then we'd able to link this to Market Readyness Levels we envision