...
The newcomer experience, the effort and time it takes to get into the project, was pretty non existent before. There was little documentation, a lot of it that was there was outdated and scattered, installation of the system was hard to get working, lot's of weird bugs and nearly nothing like a landing page that we have now. In addition to the landing page, effort has been put into streamlining joining of the project with the use of a form, some slack bots/tricks and personal attention to everyone that showed interest in the project in order to get them started. The installation procedure has been greatly simplified and stabilized and a set of tutorials has been made to quickly get you somewhat started with the system. Development processes and guidelines/tips have been defined, including usage of tools.
...
Having a better newcomer experience, focus was once again put into getting people's attention and awareness of the project. An open online meeting was held for everyone interested within AEGEE in addition to an email sent out to all members a banner at the top of intranet, Agora presence and promoting and personal promoting by the people involved already. People were told to visit the Landing page and fill in the form which resulted in quite a useful list of people interested to help. Having filled in the form people received a slack invitation and personal attention as described above. In the end awareness was raised, awareness to involvement conversion was, however, lacking.
...
The effort it takes to install the system has been greatly improved. Upgrading the docker files and setup of the several microservices with the system with the added help of some helper scripts installing and running the system is now as easy as entering 3 commands into a terminal. Additionally the `dev` branch of oms-docker has been stabilized and automated deployment has been put in place on oms.aegee.org. Dependency handling is improved and the log is once again clean, without any major error spam. All of this can be clearly shown on Travis, where automated testing was put in place, showing a full, clean, install. Additionally a reverse-proxy load-balancer and health check service called Taefik has been added to the system which will prove to be especially useful in the future.
...
While I, Derk Snijders, will leave Brussels in a few days time and as a result likely have less time to spend on the project, my greatest effort has been made in achieving continuity with regards to the development of the OMS system. The project plan is the main resource for this, in combination with raising awareness, detailed stakeholder reports, an HR analysis and a proper knowledge transfer to Fabrizio Bellicano (who will be CD IT responsible, having already been involved in the OMS project). Finally a strong focus on documentation, including future tasks
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Resolved issues
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Merged pull requests
New issues
Jira Legacy server JIRA (oms-project.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery resolution = Unresolved AND created >= 2017-03-01 AND created <= 2017-08-03 ORDER BY priority DESC, updated DESC serverId edf3f91b-210c-3cfc-933c-f8d8084c5f2c