Date: 3.12.2018 9.30-12.00 at CSC.
Present: Mietta, Jussi, Jyrki (some comments below), Sam, Tero, João (from 10:25), Martin (notes).
Let us look at a few examples of the 12 repos more or less in use.
The following 2 repos are obsolete:
Our Korp development happens here:
The forks have master and dev branches that supercede the now obsolete ”Kielipankki-korp”-versions.
The sb/dev, sb/master branches follow the original Språkbanken’s branches. Jyrki plans to port our changes to these branches so that pull requests are possible. [Jyrki: Or, to be exact, I intend to port our changes to separate topic branches based on
The repo is for internal use only and contains a few things that do not belong there. These directories will be removed (the praat scripts, commandline scripts). The relevant directories are:
The public ”Kielipankki-palvelut” contains two main parts:
We discussed parts of ”Kielipankki-konversio”, the main decisions below:
We agreed that we need a minimum of documentation. Therefore most repo-directories should have a README.md describing what is in them. It might even be possible that the README.md:s can be generated in some cases.
The public repositories should have Github topics in Finnish and English so that they can be found easier. [Jyrki: I think that the private ones could also have topics. Who decides what topics to use and who adds them?]
We also agreed that reliable documentation will require effort on our part, like documentation reviews, it otherwise gets too often neglected. We made no formal decision on how to proceed.
We use GitHub, should we start using Gitlab?
GitHub and Gitlab do similar things, both are well suited for version control and Continuous Integration (CI). GitHub uses travis-ci.org for CI, Gitlab has it built in.
The Language Bank does not yet use Gitlab and we discussed serveral options why we should start using it, since we have access to a Neic-hosted instance at https://source.coderefinery.org/.
The main point for starting to use Gitlab is the easier CI framework and very good support for Continuous Delivery (”CD”, i.e. automatic deployment). The points against:
Decision: We focus on GitHub and Travis CI. João will follow Gitlab-developments as part of his involvement with Neic CodeRefinery and will create some test instances, but we will not use Gitlab for the Language Bank for the time being.
Nothing at the moment, since we do not actively use Gitlab.
We had to skip this part.
We will look into Github and travis-ci.org. A very good simple example: https://github.com/CSCfi/ansible-workshops/blob/master/.travis.yml (The script performs a syntax check on an Ansible script).