Feature Wiki
Tabs
JourFixe-2021-04-19
Page Overview
[Hide]Date and place
Monday, 19 April 2021 from 13:00 – 18:15 as VC meeting in BBB.
If you like to participate at the Jour Fixe, please join our BigBlueButton-based Jour Fixe VC!
We recommend to use BBB in Chrome (or Firefox).
Joined VC | |
---|---|
X | |
X | |
X | |
X | |
X | |
Ferdinand Engländer | |
X | |
Thibeau Fuhrer | |
X | |
Haas, Ramona | |
X | |
X | |
X | |
X | |
X | |
Kunkel, Matthias [mkunkel] (Minutes) | X |
X | |
Clemens Robbenhaar | |
X | |
X | |
X | |
X | |
X | |
X | |
Ingmar Szmais | X |
X | |
X | |
X | |
X |
1 Appointments
Workshops
- 22 APR 2021, 13:30 - 15:00: Bi-Weekly of WG Page Editor Revision
- 26 APR 2021, 14:00 - 16:00: Bi-Weekly of WG Splitting-up Test&Assessment
- 29 APR 2021, 10:00 - 12:00: Workshop "Legally compliant archiving of ILIAS tests (Plugin)"
- 29 APR 2021, 13:30 - 15:00: Bi-Weekly of WG Page Layout Revision – Part III
If you want to participate at one of the above mentioned workshops, please register for the related session. This helps to organise the workshop. Thanks!
UPCOMING Jour FixeS
- Monday, May 03, 13:00 - 18:00
- Monday, May 17, 13:00 - 18:00
- Monday, May 31, 13:00 - 18:00
Feature Freeze for ILIAS 8 will be at 30 APR 2021!
Hurry-up if you want to suggest features for 8.
2 Miscellaneous
- Required Software ILIAS 8? Especially PHP 7.3 or 7.4 as minimal requirement?
- Website for "Required Software for ILIAS 8" does not yet exists. Information needed by developers
- TB will discuss requirements asap and communicate result.
- Minimal PHP version for ILIAS 8 will be PHP 7.4 probably.
- What is the current status PHP 8 project?
- First session with new PHP8 project manager this Wednesday.
- PHP8 related workshops planned afterwards. Every developer is invited to join.
- TB's aim is to make PHP 8 the PHP version for ILIAS 8.
- Alexander estimates a big effort on developer's side to make his components PHP8 compliant.
- Security Bug 29897, shell command handling / ilUtil / exec
- Found a solution for problem in his component (convert) but sees it as a general issue and asks for abandoning implicit maintainership for shell command handling / ilUtil
- ilUtil is considered as a problem in the ILIAS architecture. This is why TB tries to get rid of this class on the long run, see PR3314 (below).
- TB will apply for bids to analyse ilUtil and how this class can be separated in multiple and better maintainable classes.
- Remove ilBenchmark related code (abandond Database Benchmark in Administation) or move ilBenchmark to Database service
- Alexander would like to stop maintenance of this class (in /Services/Utilities).
- Fabian has no interest in integrating this class in the Database service.
- Timon considers benchmark feature as useful in general (helped him several times to indicate missing indices a.o.).
- In case, no one except Bern would keep the feature, it should be abandoned for 8.
- Handling of require/includes when doing refactorings
- Alex would like to do refactoring of code without considering if consuming components still use require or include.
- Alex don't want to remove requires and includes from code of others or post PRs.
- Problem comes up for classes that do not use auto-loading (which has been introduced years ago).
- Suggestion: giving some weeks to developers to remove requires and includes for 8 and then allow moval of classes.
- TB will pick-up issue and communicate solution.
- implicit maintainership removal / maintenance.md handling
- Alex asks if there is a process for being removed from implicit maintenance?
- Timon: step back is possible wihtout "allowance".
- maintenance.md process and creation is still a problem. TB is still in discussion.
- Alex asks if there is a process for being removed from implicit maintenance?
Maintainerships
- Authentication, incl. LDAP, Radius, CAS, SOAPAuth, AuthApache, OpenIdConnect, Init
- ECS (E-Learning Community Server) service
Anyone who is interested in taking over one of these 1st maintainerships should contact the product manager and justify her/his interest within the next four weeks.
3 Maintained Versions
3.1 Roadmap
LAST RELEASES
- ILIAS 7.0_beta4 published at 16 MAR 2021
- ILIAS 6.8 published at 19 MAR 2021
- ILIAS 5.4.21 published at 26 MAR 2021
NEXT RELEASES
- ILIAS 7.0 scheduled for 23 APR 2021
- ILIAS 6.9 scheduled for 30 APR 2021
- ILIAS 5.4.22 scheduled 14 MAY 2021
Due to the extraordinary workload in all e-learning teams based on the Covid pandemia, the technical board and product manager decided to extend the maintenance of ILIAS version 5.4 until end of 2021. This will give all ILIAS using institutions enough time for the migration from 5.4 to 6 or 7.
3.2 Mantis Bug Reports
All open issues reported or modified since the last Jour Fixe were screened by the product manager before the Jour Fixe and assigned to the responsible developers if necessary. The following issues were discussed in detail:
- #18295: Modal needed after answered last question: We accept the maintainer's suggestion and modify the 2016 decision as follows:
- An interruptive modal to confirm the finishing of the test is always presented when finishing the test (and other related screens like list of questions have already been presented) - no matter if test has one or multiple test runs. Please implement accordingly for trunk (ILIAS 8) and adapt test case(s) accordingly.
- #26388: Buchungspool kann ilias zeitweise unbenutzbar machen: The maintainer gave explanations to the issue and why the current implemantation is so expensive. Issue is still on his agenda but wasn't yet tackled due to only one vote. In case, this fix is very urgent, please contact the maintainer and offer funding for bugfix.
- #29338: Unclear licensing of ILIAS source code: There is no unique concept for the header. And due to several licensing situations in the past, at least four different licence information strings (incl. no information) do exist. The product manager together with the TB will discuss how to deal with this problem, incl. the handling of authors, and make a guideline - or open a call for bids to create one. Our aim is to have a clear guideline for all code pages that are also easy to update.
- #29934: Failed test: Inhalte entzippen: Because SCORM specs only allows ASCII for file names, a check of non-ASCII could already be made during the upload process – and reject upload in case the flle names use non-ASCII. HTML LM should behave similar. IRSS cannot solve problem in its current development status.
- #30294: Failed test: Bei einem Autoplay-Video per Tastatur den Ton ausschalten: Because autoplay is no longer supported by all browsers, we decide to abandon this feature for ILIAS 7 and trunk. Please add a notice to the release report of 7.0 under "Changed Behaviour" to notify users and remove the related checkbox from the UI. Please also update the related testcase.
- #30329: Leere Paragraphen sollen nicht gespeichert werden.: Also empty paragraphs should be saved - and not deleted automatically. This would be unexpected behaviour. Report closed accordingly.
- #30357: Dashboard: Column "Unfinished Passes" (expired Limit Duration of Test): We follow the maintainer's suggestion and accept the following change for all maintained versions:
- When clicking on the button "Finish all Test passes", ILIAS checks if the options "Finishing Time" and/or "Limit Duration of Test" are activated in the test. If yes and the finishing time has not yet been reached or the processing time has not yet expired, the test runs will not be finished and an error message will be displayed.
- However, it should still be possible to terminate individual test runs from participants, even if the above conditions apply (e.g. in the case of cheating). Nevertheless, the warning message should clearly warn that a single test run will be terminated although the end time or the end of the processing time has not yet been reached.
- #30531: Change the order of page view and list view in ILIAS Tests: We follow the maintainer's suggestion and change the order of the sub-tabs for ILIAS 7 and trunk accordingly. This change will not adapted to the survey due to a bit different behaviour there. When a user creates new questions in one the views, she/he always stays in the chosen view and is not redirected to another.
- …
3.3 Bugfixing Statistic
Bug reports[1] set to status 'open' and not been touched by responsible maintainer for more than 21 days (checked this morning) as well as bug reports with priorisation voting:
Open Bugs Without Feedback | Last JF | ø Age in Days | Last JF | New Votes* | Old Votes** | Resolved or Closed*** | |
---|---|---|---|---|---|---|---|
1x1v | |||||||
166 | 177 | 208 | 179 | ||||
8 | 8 | 652 | 624 | 1x2v 1x1v | |||
5 | 6 | 69 | 38 | ||||
[iln user="katrin.grosskopf"] | 0 | 1 | 0 | 69 | |||
0 | 1 | 0 | 312 | 1x1v | |||
Thomas Joussen | 0 | 1 | 0 | 924 | |||
109 | 195 | 55 | 80 | 1x1v | 15x1v | 1x3v | |
1x2v 2x1v | |||||||
27 | 53 | 64 | 122 | 3x1v | |||
1x1v | |||||||
0 | 3 | 0 | 385 | 1x1v | |||
126 | 138 | 137 | 126 | 2x2v 43x1v | |||
0 | 1 | 0 | 24 | ||||
1 | 1 | 426 | 398 | ||||
13 | 15 | 111 | 91 | 1x4v 1x3v 2x2v 9x1v | |||
5 | 5 | 427 | 399 | ||||
15 | 20 | 156 | 139 | 2x1v | |||
1 | 11 | 94 | 78 | ||||
10 | 16 | 176 | 122 | 5x1v | |||
7 | 6 | 89 | 70 | 1x1v | |||
1 | 1 | 38 | 39 | ||||
0 | 1 | 0 | 53 | 1x1v | |||
1 | 31 | ||||||
Zehnder, Lukas | |||||||
* New votes: bugs priorised within the last 14 days ** Old votes: priorised bugs before last JF (older then 14 days) *** Resolved: Resolved or closed bug reports in the last 14 days
Bug reports with status 'Fixing according to priorisation' should be fixed before other bugs are tackled. Priorised bugs very important for one or more institutional members of the ILIAS society. Handling this reports with low priority contradicts the intention of the established bug fixing process.
3.4 Development Issues of Maintained Versions
The following development issues concern one or more maintained versions. Issues related to upcoming versions have to be added in chapter 4.
3.5 Open Pull Requests to Discuss
- PR3190 • Docs: Accessibility Process : We highly appreciate this suggestion and accept the PR for ILIAS 8 / trunk. According to the process documentation we will extend the FW template and add a section for Accessibility. This will also be done for all FW requests for 8 that will be presented for decision for the next JF. This is a first version of the process documentation. Please help us to make it even better by providing related PR.
- PR3278 • UI/CombinedSlate: Add optional entry id for menu sub entries (ILIAS 6) : We highly appreciate this suggestion and accept the PR for ILIAS 6. Implementation for ILIAS 7 and trunk is tackled in PR #3315. Changes to 6 will be adapted similar for 7 due to upcoming release date of 7.0. Changes for trunk can be more extended.
- PR3296 • Switching repository chat message field to textarea and also switched… : We highly appreciate this suggestion and accept the PR as usability fix for all maintained versions.
- PR3312 • UI Components, Avatar Symbol, fix of #29727 : We highly appreciate this suggestion and accept the PR for ILIAS 7 and trunk.
- PR3314 • Marked ilUtil as deprecated : We highly appreciate this suggestion and accept that ilUtil is set to deprecated. Please contact Fabian or Timon in case of problems in your components that rely to this decision.
3.6 Continuous Integration
- We currently have 5655 automated test for the trunk, which is the +2 compared to 2021-03-08.
- Please remind yourself to run the unit tests after commiting or before pushing to our repo. This could be done git hooks like these.
- Please have a look into the results from the PHP-Fixer. We are again accumulating lots of violations. Run `
libs/composer/vendor/bin/php-cs-fixer fix --dry-run --using-cache=no --config=./CI/PHP-CS-Fixer/code-format.php_cs
`to check all files in the repository.
We kindly ask all developers to use git hooks to be notified automatically when committing code styles violations. Installing git hooks is quite easy now, see https://github.com/ILIAS-eLearning/ILIAS/blob/trunk/docs/development/git-hooks.md and run libs/composer/vendor/bin/captainhook install
4 Publishing ILIAS 7
- All features implemented and test cases completed until November 12, 2020
- Release 7.0 beta1 published and release-7 branch crated at November 13, 2020
- Testing phase started at November 16, 2020
- End of testing phase scheduled for February 26, 2021
- First stable 7.0 release planned for April 23, 2021 (changed)
4.1 Status of Testing 7
65 features have been developed for ILIAS 7 and merged until deadline of 'Coding Completed'. 9 features have been abandoned. Testing of ILIAS 7 has started at 16 NOV 2020. All test cases had been executed once until 10 MAR 2021.
Testing Status this morning

- At least 98% of all test cases (~ 4490 test cases) have to be passed succesfully.
- No critical bug should still exist in the release.
Test Case Status | Test Cases Today | Last JF | Change |
---|---|---|---|
Passed | 4376 | 4099 | + 277 |
Blocked | 32 | 105 | - 73 |
Retest | 57 | 100 | - 43 |
Failed | 115 | 281 | - 166 |
Untested | 0 | 0 | 0 |
We are about 100 test cases away from 98% coverage of passed test cases, incl. over 50 retests. There is a slight chance to reach this quorum this week. Therefore, we keep the stable release date of April 23. We please all developers and testers to focus on bugfixing and testing in the next days so we will be able to reach the quorum within schedule. Thanks a lot!
4.2 Development Issues
Development issues and topics related to ILIAS versions 7
Samoila, Oliver [oliver.samoila] March 26, 2021: As part of the Page Editor Revision, compatibility with the existing MarkDown concept has been restricted.
This concerns in particular the marking of headings by means of equal signs. "=Headline1=
"
In the Working Group Page Editor Revision we have agreed on this.JourFixe, ILIAS [jourfixe]: We accept this decision and looking forward for an improved markdown concept in ILIAS 9 hopefully.
Samoila, Oliver [oliver.samoila] 14 APR 2021: In our Page Editor Revision Working Group we identified the problem, that when uploading larger media files (audio, video, pictures, ...) the user does not realise that the system is busy with a longer process.
For ILIAS 7, we would therefore like to give a visual indication of this process. See MockUps.
(On the longer run / ILIAS 8: we would also like to have a loading bar that shows the actual progress of the upload.)MockUp Dev IssueJourFixe, ILIAS [jourfixe]: We highly appreciate this change and accept it for ILIAS 7.
Killing, Alexander [alex], 19 Apr 2021: Abandon Disk-Quota I am not sure, if this was clearly communicated. But the removal will include the personal webspace quota as well.
JourFixe, ILIAS [jourfixe]: PM will add a short notice to the FW page that this request covers the disk quota in repository and personal workspace.
5 Developing ILIAS 8
5.1 Development Issues
Development issues and topics related to ILIAS versions 8
: none
5.2 Suggested Features for 8
Abandon Link Checker : We highly appreciate this suggestion and abandon the cronjob with ILIAS 8.
Output Formats of Submissions : We highly appreciate this suggestion and accept the feature for ILIAS 8. We would like to have "HTML Export" activated by default and "PDF Export" as additional option that can be activated, too. The byline for PDF Export should mention that this export format might not include all content elements of the portfolio, esp. videos and other media objects.
Create Portfolio from Template and for Global Roles : We highly appreciate this suggestion and re-schedule the feature for ILIAS 8.
Protected Sections in Portfolios from Portfolio Templates : We highly appreciate this suggestion and schedule the feature for ILIAS 8. The mentioned feature requests for read-only sections differs slightly because of the different context (here: portfolio, there: wiki). But the basic concept of implementation and permission handling is the same.
Limited View of postings : We highly appreciate this suggestion and schedule the feature for ILIAS 8. As glyph we prefer the "target" glyph (needs to go through KS).
Repository Chat: Add option to hide automatically created status : We highly appreciate this suggestion and schedule the feature for ILIAS 8. Please implement the two suggested checkboxes as toggles in one row. Looks nicer.
Improve Statistics : We highly appreciate this suggestion and schedule the feature for ILIAS 8. Ref.ID-column is still welcome.
Create ECS user accounts as non-local users (Shibboleth, LDAP, ...) via ECS : We highly appreciate this suggestion and accept the feature for ILIAS 8. We keep the list of authentications as dropdown because it could be a long list if a lot of installations each with its own LDAP are listed.
Ask for user consent before data is transferred to remote ECS platform : We highly appreciate this suggestion and schedule the feature for ILIAS 8. The confirmation for the transfer of user data should be made once per participant. Please complete the chapters for security and privacy with the related information.
- [[]] :
- Feature request presented by
- Length of slot: '
Last edited: 17. Apr 2025, 14:33, Kunkel, Matthias [mkunkel]