2020-04-29

Summary

Team Meeting

29 April 2020 / 10:00 AM

Attendees

  • Antoine Mottier (AMO)
  • Benoit Mortier (BMO)
  • Clément Oudot (CLO)
  • Daniel Le Berre (DLB)
  • Daniele Gagliardi (DGA)
  • Martin Hamant (MHA)

Agenda

Jitsi

https://gitlab.ow2.org/ow2/technology-council/issues/28

According to DLB, it seems that the issue related to a limited support of Jitsi by Firefox will be fixed soon (version 76 should bring a fix). There is an ongoing collaboration between Jitsi and Firefox (see: https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=substring&status_whiteboard=jitsi-meet - additional link added by AMO after the meeting).
Also, based on DLB experience, a server with 16Gb of RAM and 2Mb of bandwidth managed to deal with a group of 20 users listening to one speaker with screen sharing. No CPU issue, good quality.
DLB and BMO recommend to setup OW2 own Jitsi server.
MHA report high CPU usage when using Chrome. Also confirmed by AMO. Does not seems to prevent a successful usage of the solution.
Everyone agrees to use Jitsi. Next meetings will use Jitsi using public servers until more investigation can be done about the setup of an OW2 Jitsi instance.

Pretalx

https://gitlab.ow2.org/ow2/technology-council/issues/27

AMO indicates that tests are on going for OW2online event. So far the solution look promising and only minor bug / enhancement requests have been identified. See GitLab issue for details.
BMO recommend OW2 contribution to user documentation in order to compensate the current lack of user documentation for Pretalx.
CLO also reports having already used the solution and being satisfied with it.

Next step will be to make a real life test with OW2online event and gather feedback.

WordPress

https://gitlab.ow2.org/ow2/technology-council/issues/29

BMO suggest the usage of WordPress as an alternative to XWiki for some of OW2 websites, more precisely for www.ow2.org and www.ow2con.org and provide some details about the motivation for such change:

  • Making a website with XWiki is rather difficult for a non technical user
  • WordPress provide a solution to easily translate a website
  • WordPress support delegation
  • WordPress only require low maintenance effort when used with a limited sets of plugins. It's also easy to backup and clone (to get a test instance)
  • The need of having a "marketing" with attractive look and feel, translated, content aiming at visitors discovering OW2
  • XWiki will still be used for projects websites. It is about using right tool for the right job.

AMO express his concern regarding the message send to OW2 project if we stop the usage of XWiki.

??? share the concern about the message send to XWiki

DGA reminds that OW2's job is to promote the OW2 projects and identifies two issues: relation with XWiki, and the message to other projects about how strongly OW2 supports them. Also DGA notes that OW2 MO didn't raise any issue regarding usage of XWiki (they are the main users).
DLB shares the moto: "eat your own dog food" and suggests to report usability issues to XWiki team. DGA suggests that TC can provide usability requirement to XWiki team.
MHA reports that the webmaster gets frequent requests for help when a page needs to be created/edited.

Matomo

https://gitlab.ow2.org/ow2/technology-council/issues/5

DLB reports that he needs from time to time to be able to provide download statistics for sat4j. Such information does not seems to be really useful for the project but are required by funding agencies. They can also help you to get an idea of how widely a project is used. Also some limitations exist (e.g. download on Maven repository are not counted).
DGA reports that Knowage project leader asked for it. Also that number of download is easy to understand compare for example to a number of commits. It's not the perfect metric to measure the usage of a software. Maybe guidelines with projects regarding how to measure usage can be shared.
BMO suggests to add number of downloads on the project dashboard.
DLB mentions that sometimes download numbers can influence decision when downloading for example a plugin.
CLO agrees that it can be a useful indicator, but recommends not to recreate the top 10 download page.

Project binaries - OW2 forge

The sentence "The project binaries must be synced to the OW2 forge, at least once per release" (https://tc.ow2.org/view/wiki/Mature%20level) is no longer relevant.

MHA suggests to rephrase it to something like "The project must provide a link to download the binary on the project page"

Not on the agenda

CLO asked about the situation of LDAP Tool Box project.
The issue (https://gitlab.ow2.org/ow2/technology-council/issues/21) was accidentally closed with still some tasks to be done and has been reopened.

Next Meeting Agenda

Some topics have not been covered during this meeting and are moved to the next meeting agenda: