Summary of developer meeting at 2018-10-26
Contents
Discussions and Outcomes
In advance of the meeting we spoke about the conflicts while merging or rebasing the branch bug-1260 into testserver-stable and release.
We decided to reopen the recently opened bug-1442 and declare it a child of bug-1260
During the meeting we agreed that the migration to a new PHP version should have priority.
Peter Moulding gave a list of what has to be fixed for using PHP 7.2:
- Change from mysql to mysqli
- Replace each() with foreach()
Replace <?= with <?php echo
Replace <? with <?php
- Convert to new error class
- Use autoloader class
A second outcome was to document the status quo:
- we need to do a documentation of the modules/files of the current version for doing some reliable tests
- these documentations could help setup a testing tool for automating the tests
- this documentation could help to do the specifications for a new version of the whole system piece by piece
Jan announced to install a tool for this documentation.
https://jenkins.cacert.org/job/cacert-codedocs/ and https://codedocs.cacert.org/
We agreed to do a bottom-up documentation at first to see what we do have, touching each existing file of the project; whilst doing this we could try to create some tests for the documented module/file.
After we are finished with bottom-up - or may be parallel - we could do a top-down development with looking at the web site and identify modules for which we should write a specification, define testing-rules and then decide to replace or not to replace the code.
- "The bottom-up would describe the actual code, the top down would describe the needs and intents."
For the automated testing PHPUnit was proposed.
Questions
Open Questions
Must we change to a new database-system MySQL -> MariaDB |
|
Are the git-repositories up to date |
|
Implementation of CAA |
not even started |
Get arbitration to help support |
egal and Ted will phone about |
when will theCAcert root certificate signed using the SHA256 algorithm be published? |
egal and Ted will telephone about it |
Answered Questions
What do we have to do to pass the audits, required for browser inclusion? |
As the current PHP-code is audit-fail, we have to wait until the source is documented and possibly redesigned |
Logfile of the meeting
Next Meeting
The next meeting was proposed to be held on Fri 2018-11-09-T20:00 UTC
Done Work
- the connectivity of test.cacert.org and testmgr.cacert.org were fixed