JourFixe-2025-08-04

1 Appointments

2 Technical Board

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

Abandoned Components (see: https://github.com/ILIAS-eLearning/ILIAS/pull/9177)

Security-Updates:

3 Miscellaneous

3.1 UI Clinic

Our UI/UX/A11y experts Yvonne Seiler 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 13h30 to 14h00. Please announce the topic you want to discuss by e-mail: privacy@lists.ilias.de

Elyesa prepared a checklist to make it easier to check for privacy issues in new feature requests, see PR9932. Everybody is invited to add comments and questions to the PR. They will be tackled on the JF at 01 SEP.

3.3 Authorities

The process for changing authorities is described here.

3.3.1 Authorities to be Handed Over

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

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.3.2 Requests for Modifying Authorities

Requests to modifiy authorities exist for the following components [1]: 

3.3.3 Changed Authorities

Authorities have been changed for the following components: 

3.4 Feature Wiki

Due to reported problems of users who have not understand where to add a new feature request on the category page of a component, Matthias has created a new block for directing users to this list of new requests (see here for example). We will update all category pages in the next weeks.

4 Maintained Versions

At the time being, we are maintaining ILIAS version 8 (security bug fixes only), version 9 and version 10.

4.1 Roadmap

Lifecycles of maintained versions

4.2 Mantis Reports

Needs Jour Fixe Decision

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

Postponed to next Jour Fixe

4.3 Changed Behaviour in Maintained Versions

Below we list all changed behaviour in the full maintained ILIAS versions. This information is managed in a dedicated media pool to which all developers should have access. If not, please contact Kunkel, Matthias [mkunkel].

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.

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.

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.

4.6 Continuous Integration

Topic skipped due to vacation of Michael.

5 Developing ILIAS 11

5.1 Timeline for ILIAS 11

5.2 Software Requirements for ILIAS 11

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

5.3 Development Issues

1. Schmitz, Tim [tschmitz]: During the implementation of Recurrence Form to Kitchensink we realized that there is a better way to present the 'Recurrence End' inputs: one could move them into all of the 'Recurrence' radios, except for 'No Recurrence', such that it is only offered to the user if relevant.

   The KS rules state that radio inputs should not be nested, but allows for JF approved exceptions when the second radios only contain simple numeric or date inputs (as is the case here). We believe this change to be a big enough improvement to warrant such an exception.

   

   JourFixe, ILIAS [jourfixe]: We accept the suggested exception for nesting two radio inputs for this feature request.

5.4 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.

The following pull requests have been set on the agenda to be discussed:

5.5 Deprecated for ILIAS 11

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

5.6 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.

Postponed to Next Jour Fixe

5.7 Preparing the Testing of ILIAS 11

5.7.1 Test Installation

New installation test11.ilias.de is now prepared for update to 11 (cleaning of outdated content and lost objects). We keep major parts of the existing content from test10. As already annonced on test10 we have deleted the old sandbox and also pruned parts of the existing objects in our test category.

If anyone needs an empty test environment for specific purposes, please contact Kruse, Fabian [Fabian] to discuss on how to proceed. Additonal existing (or possibly also new) test installations could be used for retests if required. Test cases could be amended accordingly.

5.7.2 Test Case Lab will return

After the culmination of the test phase for ILIAS 10, our Test Case Lab will return to improve existing test cases. Meetings of Test Case Lab: every Tuesday from 11:00 to 11:45.

Please contact Kruse, Fabian [Fabian] if you would like to participate.

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

No news due to absence on holiday.

5.9 Suggested Features for 11

1. New tab ‘Media‘ and revised tab ‘Questions‘: We still would like to have this improvement of question and media handling in ILIAS and accept the FR for trunk. Please consider the requested order of tabs as decided above in the JF decision from 2023.

2. Add New Object Action for Item Groups: We highly appreciate this suggestion and accept the feature request for trunk. Please remove all language entries that are no longer needed due to the streamlining of labels.

3. Distinct Administration Nodes for Maps and WOPI: We highly appreciate this suggestion and accept the feature request for trunk.

4. Unbundling of Admin Permissions: We highly appreciate this suggestion and would like to solve the mentioned problems above. We all have a preference for the described option 2. But we had a longer discussion in the JF about the impact of the suggested changes and would like to continue this discussion in a dedicated feature workshop. This will give us more time for discussing and modelling this feature.

   Open questions to discuss are:

   • how we handle the above mentioned workarounds?
   • do we still need the VISIBLE permission for single administration nodes (as well as for the parent administration node)?
   • who will check the permissions for a selected administration node?

   We schedule a workshop for Thursday, 07 August, 16:00: Link to workshop

5. Content Tab for Poll: We highly appreciate this suggestion and accept the feature for trunk. We prefer a left-aligned presentation of questions and results, incl. a headline for the results. The width of the presented bar chart should be limited to avoid its presentation on the full screen width.

6. Show Poll in Object Lists: We highly appreciate this suggestion and schedule the feature for trunk. We also need a VISIBLE permission for polls if we present the in the object lists. The migration should give all roles with READ permission VISIBLE permission, too.

7. Let Anonymous Users Vote in Poll: We highly appreciate this suggestion and schedule the feature for trunk. We start with a cookie lifetime of 24 hours and see if this is a feasible value. And no additional info text about the impact of allowing Anonymous to vote is added.

8. QR Code for Poll: We highly appreciate this suggestion and accept the feature request for trunk. Please create a PR for the needed dependency and a PR for the new KS element ‘QR code‘. It would be great if this KS element supports and additional presentation of the QR code in a modal to support use cases when the QR code is presented in lecture halls and on similar big screens.

6 Participants