JourFixe-2024-11-11

Date and place

Monday, 11 November 2024 from 13:00 – 17:05 at 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).

1 Appointments

2 Technical Board

This is a new topic on our agenda that should improve the information flow between the Technical Board and the society members and ILIAS users.

• Happy we finished coding completed on time.
• Big Projects JF and Dependency JF.

3 Miscellaneous

3.1 UI Clinic

Our UI/UX/A11y experts Yvonne Seiler, Kristina Auerswald and Kendra Grotz are offering bi-weekly UI clinic consultation hours for UI/UX and accessibility topics. The consultation hours are open for all users that need or are interested in related help for their ILIAS development activities. The UI Clinic consultation take place every Wednesday before the Jour Fixe from 10h30 to 11h30.

If you are interested in discussing an issue, please register here!.

3.2 Privacy Clinic

In the Privacy Clinic, you can get advice on how to protect user privacy and effectively navigate the complexities of data protection in the context of ILIAS. Our privacy experts Seidel, Elyesa [seidel], Gribchenko, Kseniia [ksgrie] and a member of the Technical Board are offerin support in all privacy related issues. The Privacy Clinic has consultation hours every Wednesday after the Jour Fixe from 11h00 to 12h00. Please announce the topic you want to discuss by e-mail: privacy@lists.ilias.de

3.3 Language Issues

• Often in ILIAS, one language variable is triggered by both an a singular and a multiple event - everything from badges being awarded, to members being removed from a group. This seems to generally work ok in German. In English, however, it can lead to solutions that are not exactly ideal. It would be great if developers could actually pay attention to this singular / plural issue and make a difference in the code, so that two separate language variables could be triggered. If in English, using the plural with one item is worse than in German, how bad might it be in other languages? Do we know how ugly this seems in Italian? Bulgarian? Chinese? In some languages it might not make sense at all.

a suggestion for a way to deal with this: Every language language-variable that supports singular/plural is duplicated and extened with a suffix like "_s" and "_p". In the code using this variable, the name of the language-variable then can be constructed by adding the suffix according to the situation required. This should keep code changes rather simple. I found some examples in plugins using a _info- suffix for the combination of the name of an input field and an associated byline-text.

3.4 Authorities

3.4.1 Authorities to be Handed Over

For the following components there are authorities to be handed over: 

• Multilingualism: We are looking for persons who are willing to take over the authorities to sign off on conceptual changes for this component, to sign off on code changes, to curate testcases and to (de-)assign authorities.

Community members who are willing to take over one of the offered authorities are highly appreciated. In case of interest, please contact the Technical Board.

3.4.2 Requests for Modifying Authorities

• none

3.4.3 Changed Authorities

For the following components authorities have been changed: 

• Eventhandling: Klees, Richard [rklees] is willing to take over the authorities to sign off on conceptual changes for this component, to sign off on code changes, to curate testcases and to (de-)assign authorities.
  • TB and PM have accepted the application.

4 Maintained Versions

At the time being, we are maintaining ILIAS version 8 and ILIAS version 9.

4.1 Roadmap

Lifecycles of maintained versions

• ILIAS 8 : end of full maintenance at 31 DEC 2024, security bug fixes (only) until 31 DEC 2025.
• ILIAS 9 : end of full maintenance at 31 DEC 2025, security bug fixes (only) until 30 JUN 2027.

4.2 Mantis Reports

The following Mantis reports have been tagged with 'Needs Jour Fixe Decision' and were therefore be discussed in detail:

1. #37379: Download of all submissions is broken when it contains utf-8 invalid character (Excel export invalid): We would like to have a centralised solution to tackle the problem. If every component implements its own handling of broken UTF8, this will result in duplicate code and different implementations. 
   As a first step the Excel service should reject the input of invalid UTF8 and throw an exception. This could be used by the Exercise component (or another component) to ignore the input of the "infected cell input". The rest of the table could be given to the Excel service.
   In a second step we improve the KS Textarea element to "sanitise" text input by only accepting/using UTF8 compliant content. This will prevent to get invalid UTF8 into the system.
2. #42458: Datepicker cannot be used in Chrome: We prefer solution c and would like to have a solution for the LegacyUI that is similar to the new one in the Kitchen Sink. Matthias will take care of funding to realise this. In addition, we want to get rid of the "no validation" attribute of the KS element. This will solve the problem in FF where no input is accepted when no time is entered manually, see #38267 and #41392. At the time being we are not fully aware of the effect of this decision and might return to the current behaviour if problems arise. All related issues should be addressed to the JourFixe.
3. #42501: Error "Incorrect string value: '\xC3 " when creating new OrgUnit in GUI or running CronJob: We follow Richard's suggestion and accept the PHP multibytestring extension as a required extension of PHP for ILIAS 8 and higher. This allows to fix this issue with `mb_`-functions. The related composer.json have to be updated accordingly.

4.3 Mantis Statistic

Current information from Mantis:

                        * … Issues with status 'open' and 'fix.acc.prio.' are recorded.

4.4 Development Issues of Maintained Versions

The following development issues concern one or more maintained versions. Issues related to trunk are listed further below.

• No issues to discuss today.

4.5 Pull Requests

4.5.1 Pull Requests for Maintained Versions

Pull requests in the ILIAS repository on GitHub that are related to maintained versions of ILIAS.

1. PR8294 • Auth/OpenIDConnect: Use id_token for claims: We highly appreciate this suggestion and accept the PR for 9 and higher.
2. PR8360 • Legacy Form: fix date range comparison for combination inputs:
3. PR • :
4. PR • :
5. PR • :

4.5.2 Looking for Shepherd

The following PRs are adressing components that are currently under no authority. So nobody has the authority to do the related code change and accept the PR. We are looking for shepherds that check and review the PR and merge it.

1. PR7599 • Add ext-pdo as required extension in composer.json:
2. PR7618 • Prevent deletion of required file uploads:
3. PR7815 • Phpunit code coverage:
4. PR7857 • Block: Preserve block title on slice
5. PR8202 • [FIX] add scripts/PHPUnit/.phpunit.cache/ to .gitignore:
6. PR8229 • Legacy UI: Remove Tooltip (with usages) from code base:
7. NEW: PR8360 • Legacy Form: fix date range comparison for combination inputs:

4.6 Continuous Integration

• Unit Tests:
  • As of today, there are (executed with PHP 8.3) ./scripts/PHPUnit/run_tests.sh --random-order-seed 1720173999
    • 12591 (+9)
    • 30731, assertions (depends on the order of tests being executed / not stably determinable)
  • 1 failure:
    • ILIAS\Cache\CacheTest::testLock Failed asserting that false is true.
      /var/www/ilias/trunk/components/ILIAS/Cache/tests/CacheTest.php:166
  • 36 skipped (-804):
    • See file below
  • 0 errors, 0 PHP deprecations
• Code Style:
  • 379 Violations (-14) ./vendor/composer/vendor/friendsofphp/php-cs-fixer/php-cs-fixer fix --config=./scripts/PHP-CS-Fixer/code-form
at.php_cs --using-cache=no -vvv --dry-run components/ILIAS/* :
    • See file below
• ilCtrl "// @todo: removed deprecated ilCtrl methods, this needs inspection by a maintainer."
  • PR: https://github.com/ILIAS-eLearning/ILIAS/pull/6628 / https://github.com/ILIAS-eLearning/ILIAS/pull/5100
  • 29 findings (-2)
    • See file below

5 Preparing ILIAS 10

5.1 Timeline for ILIAS 10

• Big Projects Jour Fixe on 27 November 2023 ✓
  
• Feature freeze on 30 April 2024 ✓
• Coding completed on 25 October 2024 ✓
  • New features are implemented and related test cases completed
  • Existing test cases are updated/revised
• Release 10.0_beta1 published and release-10 branch created on 28 October 2024 ✓
• Beginn of testing phase on 30 October 2024 ✓
  
  • Pretest: 30 October – 12 November 2024
  • Community testing: 13 November 2024 – 05 February 2025
• End of testing phase planned for 05 Februar 2025
• First stable 10.0 release planned for 13 March 2025
• Full maintenance support for version 10: until 31 December 2026
• Security bug fixes only: until 31 December 2027

5.2 Testing ILIAS 10

The official test installation for ILIAS 10 is available at: https://test10.ilias.de. It will be used for the pretest and the community testing. Accounts from test9 should work if not created after 11 July 2024.

5.2.1 Pretest 10

Some numbers:

• 4961 test cases
• 6% tested, 5% passed
• 4670/4961 untested
• 148/376 Mantis issues remain open

Some further observations:

• Blockers remain in Bibliographic List Item, Search, SCORM, xAPI
• We encountered several UI issues that I would like to present to the UI Clinic in order to prevent unnessessary (duplicate) bug reports.

5.2.2 Testers Wanted!

We need additional tester for the community testing! Due to ending projects and changes of job we lost several good testers and weren't yet able to substitute all of them. To avoid a burnout of our current testers we are urgently looking for testers for the following components:

1. Copy Process
2. LTI 1.3
3. Mail
4. Media Pools and Media Objects
5. Personal and Shared Resources
6. Statistics
7. System Check
8. T&A Zugriff auf Tests über Organisationseinheiten
9. Virus Scanner
10. WebDAV

5.2.3 Community Test Kick Off

Kick offs have been scheduled: 

• Wednesday November 13, 11:00 am - 12:30 p.m.
• Thursday November 14, 9:30 - 11:00 am.

Testers have already been informed by mail.

5.2.4 Please Remember: Set Status "Retest" on TestRail

Any bugs pushed from TestRail include a link to the respective test case.

After a fix, please set status "Retest" on TestRail!

5.3 Status of Development

This is the final status of the development of ILIAS Release 10 – based on the metadata of all scheduled feature requests.

Status of Test Case Information

For some feature pages information about test cases (new ones, changed ones, removed ones) is missing. These new and updated test cases are important to test these features sufficiently.

All cases should have been added by now, as the test runs for release 10 will be set up early this week.

• Removing Legacy-UI » Toolbar » ‘Label‘ + ‘Legacy Dropdown‘ + ‘Submit‘ (in ILIAS 10) – Test cases cannot be finalised before decision about labels.

5.4 Software Requirements for ILIAS 10

The required and supported software for ILIAS 10 is as follows:

5.5 Development Issues

1. View-Actions in WOPI for File-Objects

   At the WOPI workshop in Graz and through other channels, it has already been communicated that the click behavior in ILIAS 9 is unclear or cannot be expected. One would expect that if you have the appropriate permissions and the file also has an external editor via WOPI, the editor will start directly. Currently, the file is simply downloaded. The additional setting, as suggested in this feature, would further complicate the behavior. Therefore, the following behavior is currently implemented, which could also be partially implemented in ILIAS 9:

   The file object now works internally with so-called “capabilities” for all central functions. In many cases, these simply involve a permission check; in the case of WOPI, it also involves checking whether either an editor or a viewer is available for the current file. When you click on a file title in the magazine, the capabilities are checked in the following order and forwarded to the first one that is available:

   • View External: User has the permission to view the file in an external editor and the current file is supported by a WOPI viewer (open the current feature here)
   • Edit External: Dame but with a WOPI Editor
   • Download or View: The user has the permission to read the file, depending on the already available setting, the klicks leads to a download or to the info-page
   • Manage Versions: The user has write permission
   • Edit Settings: The user has write permission
   • Info Page: The user has only visible permission
   • None: The user doen't have any permission on the file

   The same behavior (without the "View External" could be implemented in ILIAS 9 as well. 

   JourFixe, ILIAS [jourfixe], 11 NOV 2024: We highly appreciate the change of behaviour when clicking on the file title. The order of checks and the related action should be as follows:

   1. Is setting "Open Info Page" active? → Open Info page.
   2. User has the permission "VIEW CONTENT" and the current file is supported by a WOPI viewer (open the current feature here) → File is opened in WOPI viewer.
   3. User has permission "EDIT FILE" and WOPI is active → File is opened in WOPI editing mode.
   4. User has permission "EDIT SETTINGS" but no view permissions in WOPI → "Manage Versions" tab is opened
   5. User has only permissions "VISIBLE" → Info page is shown.
   6. No permission given → No title of the file object is shown in parent container.

   We also accept to port this change back to ILIAS 9 (except step 2 which is not supported yet in ILIAS 9).

   Customizable Link-Groups in Footer - First

   One option has not yet been fully implemented because the feature request for it was not precise enough: the translation of items. Translations are implemented everywhere in ILIAS as legacy tables and legacy forms, and these views usually look the same. However, we cannot use legacy UI components for this new feature. Therefore, I propose several options how to process (see "Implementaion" in Feature Request).

   JourFixe, ILIAS [jourfixe]: We discussed the different options of Dev Issue 1 (see below in chap. 10). We prefer option C (no language selection possible). It makes only sense to translate labels for languages that are activated as possible user languages in an ILIAS installation. Labels in Swahili will never be presented as Swahili is not supported by ILIAS yet.

   • In addition, all labels for core functions that come from the language files should not be possible to translate. That means, only custom groups and custom links can be translated.
   • The label in the default language that is entered when creating the link or group should already be presented in the translation input form. It is still to decide if the labels of other languages than the default one are already added to the form or if the form is empty. Decision will be prepared in UI Clinic.

   Customizable Link-Groups in Footer - Second

   It is currently not possible for the existing core entries “Terms of Service” and “Data Protection” to be moved to the “Legal Information” link group. Although the UI component Footer allows buttons with modals to be added, these are always rendered in a separate section per se.
   We therefore propose an adjustment to the footer interface (UI component) that allows buttons with modals to be added as part of a link group as well

   JourFixe, ILIAS [jourfixe]: Suggestion accepted.

5.6 Dependencies

The following pull requests in the ILIAS repository on GitHub are related to ILIAS 10 and labeled with 'dependencies'.

• PR8373 • Dependencies: Add jumbojett/openid-connect-php v. 1.0.2
  • Suggested by: Jansen, Michael [mjansen]
  • Status of maintenance: There are 83 contributors. The library is actively maintained, there are recent commits and releases.
  • Used by: components/ILIAS/OpenIDConnect
  • Decision: Dependency is accepted for ILIAS 10.

Postponed to next Jour Fixe

• PR8377 • Deps: add webui-popover (npm)
  • Suggested by: Klees, Richard [rklees]
  • Status of maintenance: There are 26 contributors to the library. The last commit to the library is 8 years old, as well as the last released version. Last opem issue is from Oct '21, as well as the last closed issue. Last closed PR is from 2023. The open issues seem to be either feature requests or rather specific bugs. It seems as if the development of the library has stopped, be it because its feature complete, be it because interest vanished.
  • Used by: ILIAS/UI
  • Decision: Dependency is accepted/rejected for ILIAS 10.

5.7 Pull Requests for ILIAS 10

Pull requests in the ILIAS repository on GitHub that are related to version ILIAS 10.

1. PR8310 • KS: 41633: Video Player not working: We discussed the PR and appreciate the change to the native video players of YouTube or Vimeo. A final decision about the PR can be made after the revision of the PR by the UI coordinators. In addition, our privacy experts will have a look at the suggestion to check if it makes privacy worse compared to the former implementation.

Postponed to next Jour Fixe

1. PR8359 • [FIX] Add Buttons and Modals separately to Footer:
2. PR • :

5.8 Project 'Removing of Legacy-UIComponents-Service and Table'

Component	Usages of Legacy UI-Components deprecated with ILIAS 10
	Legacy Modal	Legacy Overlay	Legacy Progress Bar	Legacy Tooltip	Total
Glossary			2		2
ILIASObject			1 (2)		1 (2)
Search		0 (2)			0 (2)
Survey			1		1
Table		2		1	3
Test	3				3
UIComponent	1			3	4
Wiki			1		1
Total	4	2 (4)	5 (6)	4	15 (18)

• Legacy Modal
  • Test » PR #8211
  • UIComponent » PR follows – Looking for shepherd
• Legacy Overlay
  • Table » PR follows – Looking for shepherd (Usage: Save and Delete of 'Current View‘)
• Legacy Tooltip
  • Table » PR #8229 – Looking for shepherd
  • UIComponent » PR #8229 – Looking for shepherd

Component	Usages of Legacy UI-Components deprecated with ILIAS 10
	Legacy Modal	Legacy Overlay	Legacy Tooltip	Total
Table		2	1	3
Test	3			3
UIComponent	1		3	4
Total	4	2	4	10

Remaining LegacyUI-Usages in Trunk for ILIAS 11 based on Exceptions of  Deprecation for ILIAS 9 and 10

• Legacy Advanced Selection List
  • Form » Style Menu in ILIAS Page Editor » work in progress
• Legacy Button
  • Container
  • Scorm » Mantis #41141
  • Search
  • UIComponent » Required in other legacy UI components. Dependencies will be reduced step by step.
• Legacy Progress Bar
  • Glossary
  • Survey
  • Wiki 

6 Developing ILIAS 11

6.1 Timeline for ILIAS 11

• Big Projects Jour Fixe on 25 November 2024
  
• Dependency Jour Fixe on 09 December 2024
• Feature freeze on 30 April 2025
• Coding completed: all features implemented and test cases finished until 28October 2025
• Release 11.0 beta1 and release-10 branch planned for 28October 2025
• Beginn of testing phase scheduled for 31 October 2025
• End of testing phase planned for  06 Februar 2026
• First stable 11.0 release planned for 17 March 2026
• Full maintenance support for version 11: until 31December 2027
• Security bug fixes only: until 31 December 2028

6.2 Big Project Jour Fixe

Planned projects for ILIAS 11 will be discussed at the Jour Fixe on 25 November 2024.

• If you want to present a project, please create an entry in the related data collection 'Big Projects for 11'!
• If you have promoted a project in the past, please check on the Projects page if its status is still correct – or if needs to be modified!
  • New projects: these are projects that are suggested for the first time and might be realised with ILIAS 11.
  • Ongoing projects: these projects have already been suggested and discussed in the past. They might be realised for ILIAS 11 and parts of them even in later versions on ILIAS.
  • Projects on hold: projects that already have been discussed but are currently not tackled with ILIAS 11. They might be picked up in a later ILIAS version.
  • Completed projects: these projects have been realised and (some of the) related features were already implemented for ILIAS. No additional plans for implementations do currently exist.
  • Retired projects: these are projects that never were tackled and no plans exist to bring them back on the agenda.

6.3 Dependencies in 11

The policy of dependency handling has been changed with ILIAS 10. Please have a look at this README to know how we handle dependencies like third-party libraries and frameworks in ILIAS from now on.

We will have a 'Dependency Jour Fixe' at 09 December 2024 when we discuss and decide upon all needed dependencies for ILIAS 11. Please prepare related PRs for your dependencies in time.

No dependencies to discuss today.

Postponed to Dependency Jour Fixe

• PR8262 • NPM: Add MathJax
  • Suggested by: Neumann, Fred [fneumann]
  • Status of maintenance: MathJax is the de-facto standard for rendering LaTeX on web pages. It is supported by strong partners (IEEE, Elsevier). It is actively developed. In the last month, six pull requests have been merged.
  • Used by:
    
    • Page editor: text content
    • Forum: thread, post, reply
    • Survey: introductory message, final statement
    • Test Questions: question text, feedback, hints
    • Cloze Question: cloze text
    • Kprim Question: answers
    • Matching Question: terms, definitions
    • SC Question: answers
    • MC Question: answers
    • Ordering Question: answers
  • Decision: Dependency is accepted/rejected for ILIAS 11.

6.4 Deprecated for ILIAS 11

The following services, methods and UI elements are deprecated for ILIAS 11:

• ILIAS/components/ILIAS/UIComponent
  • ilConfirmationGUI & ilConfirmationTableGUI
  • ilCheckboxListOverlayGUI
  • ilExplorer
  • ilSyntaxHighlighter
  • ilTextHighlighterGUI
  • ilToolbarGUI
  • ilTabsGUI
  • ilNestedList
• ILIAS/components/ILIAS/Table

6.5 Pull Requests for Current Development / Trunk

The following pull requests in the ILIAS repository on GitHub are related to the current development activities in trunk.

• PR7969 • [FEATURE] UI: Implement initialisation using new component mechanism: Thibeau Fuhrer asks all developers to have a final look on this PR as it should be merged next week. Please notify Thibeau if you object against the current suggestion.
• PR • : 

6.6 Suggested Features for 11

Postponed

We hadn't the time to discuss these features. They will be discussed on one of the next Jour Fixes – depending of the time we need at the Big Projects JF at 25 November or/and at the Dependency JF at 09 December.

1. Removing Legacy-UI » Toolbar » ‘Label‘ + ‘Input‘ + ‘Legacy Dropdown‘ + ‘Submit‘:

   • Suggestion presented by Samoila, Oliver [oliver.samoila]
   • Length of slot: 15'

2. Data Collection : Revision of the Placeholder Usage:

   • Suggestion presented by Samoila, Oliver [oliver.samoila]
   • Length of slot: 15'

3. Streamline LaTeX usage:

   • Suggestion presented by Neumann, Fred [fneumann]
   • Length of slot: 30'

4. Move Personal Learning Progress-tab in Main Bar to KS:

   • Suggestion presented by Schmitz, Tim [tschmitz]
   • Length of slot: 15'

5. Present Users Learning Progress as Secondary Panel in Course/Group/Folder:

   • Suggestion presented by Schmitz, Tim [tschmitz]
   • Length of slot: 15'

6. Split-Up Standard Fields Table and Move to DataTable:

   • Suggestion presented by Kergomard, Stephan [skergomard]
   • Length of slot: 15'

7. Move Custom Fields Table to DataTable:

   • Suggestion presented by Kergomard, Stephan [skergomard]
   • Length of slot: 15'

8. Move Translations Table to DataTable:

   • Suggestion presented by Kergomard, Stephan [skergomard]
   • Length of slot: 15'

9. Move Role-Permissions-Table to DataTable:

   • Suggestion presented by Kergomard, Stephan [skergomard]
   • Length of slot: 15'

7 Participants