Software

Some of the latest developed software

A software characterisation is provided according to Inria Software Self-Assessment Criteria (https://www.inria.fr/medias/recrutement-metiers/pdf/criteria-for-software-self-assessment).

MUTE: A web-based peer-to-peer real-time collaborative editor

Publicly available at: https://coedit.re

MUTE relies on the CRDT LogootSplit algorithm for the consistency maintenance. The software is distributed under the term of GNU Affero GPLv3 licence and is freely available at: https://github.com/coast-team/mute.

Software Self-Assessment
Software characterisation: A-3 SO-4 SM-3 EM-3 SDL-4
  • Audience: ambitious software, usable by people outside the team
  • Software Originality: original software implementing a fair number of original ideas
  • Software Maturity: well-developed software, good documentation, reasonable software engineering
  • Evolution and Maintenance: good quality middle-term maintenance, with persistent attention to users
  • Software Distribution and Licensing: public source or binary distribution on the web, organized by the development team
Own contribution: DA-3 CD-1 MS-2 TPM-4
  • Design and architecture: a regular contributor
  • Coding and debugging: not involved
  • Maintenance and support: an occasional contributor
  • Team/project management: a main contributor

The influence of trust score on cooperative behavior in trust game

Implementation in zTree of four variations of the trust game: with and without partner identity and with and without explicit computation of user trust values based on the computational trust model proposed. Publication of the datasets collected during an experimental design with 30 people on the variations of the trust game and of the analyses of the collected data. The software is freely available at: https://github.com/coast-team/trust_influence_analysis.

Software Self-Assessment
Software characterisation: A-3 SO-4 SM-2 EM-2 SDL-4
  • Audience: ambitious software, usable by people outside the team
  • Software Originality: original software implementing a fair number of original ideas
  • Software Maturity: basic usage should work, terse but usable documentation, some software engineering, basic bug fixes done from time to time;
  • Evolution and Maintenance: basic maintenance to keep the software alive
  • Software Distribution and Licensing: public source or binary distribution on the web, organized by the development team
Own contribution: DA-3 CD-2 MS-2 TPM-4
  • Design and architecture: a regular contributor
  • Coding and debugging: an occasional contributor
  • Maintenance and support: an occasional contributor
  • Team/project management: a main contributor

Trusternity

Implementation of Trusternity, an auditing scheme for public key transparency mechanisms using Ethereum blockchain. Trusternity is implemented as an extension to CONIKS (http://coniks.org), a key management system that provides transparency and privacy for end-user public keys. The extension to CONIKS is available at : https://github.com/coast-team/coniks-go. Definition of Ethereum contracts that publish the root of the signed Merkle tree (STR) of CONIKS server in Ethereum blockchain is available at: https://github.com/coast-team/trusternity-contract/

Software Self-Assessment
Software characterisation: A-3 SO-4 SM-2 EM-2 SDL-4
  • Audience: ambitious software, usable by people outside the team
  • Software Originality: original software implementing a fair number of original ideas
  • Software Maturity: basic usage should work, terse but usable documentation, some software engineering, basic bug fixes done from time to time;
  • Evolution and Maintenance: basic maintenance to keep the software alive
  • Software Distribution and Licensing: public source or binary distribution on the web, organized by the development team
Own contribution: DA-4 CD-1 MS-1 TPM-4
  • Design and architecture: a main contributor
  • Coding and debugging: not involved
  • Maintenance and support: not involved
  • Team/project management: a main contributor

Prediction of quality classes of Wikipedia articles

Prediction of quality classes of Wikipedia articles using different machine learning techniques including feature engineering (e.g. random forest) and deep learning (e.g. RNN-LSTM). The software is freely available at: https://github.com/vinhqdang/wikipedia_analysis.

Software Self-Assessment
Software characterisation: A-3 SO-4 SM-2 EM-2 SDL-4
  • Audience: ambitious software, usable by people outside the team
  • Software Originality: original software implementing a fair number of original ideas
  • Software Maturity: basic usage should work, terse but usable documentation, some software engineering, basic bug fixes done from time to time;
  • Evolution and Maintenance: basic maintenance to keep the software alive
  • Software Distribution and Licensing: public source or binary distribution on the web, organized by the development team
Own contribution: DA-3 CD-1 MS-1 TPM-4
  • Design and architecture: a regular contributor
  • Coding and debugging: not involved
  • Maintenance and support: not involved
  • Team/project management: a main contributor

Measurement of real-time performance of collaborative editors

Evaluation of delays of several web-based real-time collaborative editing systems: GoogleDocs, Etherpad, Cryptpad, MUTE. The software is freely available at: https://github.com/vinhqdang/collaborative_editing_measurement.

Software Self-Assessment
Software characterisation: A-3 SO-4 SM-2 EM-2 SDL-4
  • Audience: ambitious software, usable by people outside the team
  • Software Originality: original software implementing a fair number of original ideas
  • Software Maturity: basic usage should work, terse but usable documentation, some software engineering, basic bug fixes done from time to time;
  • Evolution and Maintenance: basic maintenance to keep the software alive
  • Software Distribution and Licensing: public source or binary distribution on the web, organized by the development team
Own contribution: DA-3 CD-1 MS-2 TPM-4
  • Design and architecture: a regular contributor
  • Coding and debugging: not involved
  • Maintenance and support: an occasional contributor
  • Team/project management: a main contributor