JourFixe-2024-11-11

Date and place

Monday, 11 November 2024 from 13:00 – … 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 Authorities

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

• PR • :

3.3.3 Changed Authorities

For the following components authorities have been changed: 

• …
  

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:

• none

4.3 Mantis Statistic

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.

• No PRs to discuss today.

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. PR6538 • Fix value presentation and allow combination input types:
2. PR7599 • Add ext-pdo as required extension in composer.json:
3. PR7618 • Prevent deletion of required file uploads:
4. PR7815 • Phpunit code coverage:
5. PR7857 • Block: Preserve block title on slice
6. NEW: PR8202 • [FIX] add scripts/PHPUnit/.phpunit.cache/ to .gitignore:
7. NEW: PR8229 • Legacy UI: Remove Tooltip (with usages) from code base:

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
    • 12582 (+663)
    • 29930, 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
  • 5 PHPUnit deprecations
    • 5 non-static data providers in "components/ILIAS/MetaData" (see file below)
  • 840 skipped (+800):
    • See file below
  • 0 errors, 0 PHP deprecations
• Code Style:
  • 393 Violations (-83) ./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
  • 31 findings (-24)
    • 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 Release Branch

A new branch 'release_10' will be created today. Once this branch is opened, the 'trunk' is available for development activities for ILIAS 11.

5.3 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.3.1 Pretest 10

We kick off the pretest of ILIAS 10.0_beta1 on 29 October 2024 at test10.ilias.de. The experienced team from last year will compete again - thanks to all supporting companies and universities.

We ask all maintainers to reserve time until 13 November to fix blocker bugs quickly. Our princicple is: You fix, we test: We are happy to ping-pong issues, retest them directly for you and report any follow-up problems.

5.3.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. Parts of the Administration
2. Parts of Category & Repository
3. Certificate
4. Contacts
5. Copy Process (new test run in ILIAS 10)
6. Parts of Learning Progress
7. Parts of LTI
8. Media Pools & Media Objects
9. Personal and Shared Resources
   
10. Poll
11. Parts of Test & Assessment
12. Statistics
13. Study Programme
14. Who-is-online?

5.4 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 Implementation Info

Some wiki pages of merged features are missing information about the feature's implementation (chap. 10). If nothing has changed compared to chapter 2 and 3 of the feature request, it is sufficient to write "Implemented as described above". And if screenshots of the implementation are available they are highly appreciated.

• Further revamping of Repository Chat
• Removing Legacy-UI » Toolbar » ‘Label‘ + ‘Legacy Dropdown‘ + ‘Submit‘ (in ILIAS 10)
• Revamping Footer with Link-Groups
• Test: Revision of the Participant Tab using the new data table

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. Please provide links to your test cases as soon as possible! If you need assistance, please contact our test manager  Fabian Kruse!

• Further revamping of Repository Chat
• Learning Modules: Migrate Page/Chapter Overview to Data Table - Test case info missing (maybe nothing to change)
• Manage Attachments
• Removing Legacy-UI » Toolbar » ‘Label‘ + ‘Legacy Dropdown‘ + ‘Submit‘ (in ILIAS 10)
• Replace TinyMCE by Markdown Editor in Data Collection
• Revamping Footer with Link-Groups
• Session Reminder and Configuration as a User Default Settings

5.5 Software Requirements for ILIAS 10

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

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

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

   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

5.7 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
  • Status of maintenance: …
  • Used by: …
  • Decision: Dependency is accepted/rejected for ILIAS 10.
• PR •
  • Status of maintenance: …
  • Used by: …
  • Decision: Dependency is accepted/rejected for ILIAS 10.

5.8 Pull Requests for ILIAS 10

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

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

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

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

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.

6.4 Deprecated for ILIAS 11

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

• Services/UIComponent
  • ilConfirmationGUI & ilConfirmationTableGUI
  • ilExplorer
  • ilSyntaxHighlighter
  • ilTextHighlighterGUI
  • ilToolbarGUI
  • ilTabsGUI
  • ilNestedList
• Services/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: 
• PR • : 
• PR • : 
• PR • : 
• PR • : 

6.6 Suggested Features for 11

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