JourFixe-2024-11-25

Date and place

Monday, 25 November 2024 from 13:00 – 17: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 topic on our agenda should improve the information flow between the Technical Board and the society members and ILIAS users.

2.1 Process for the Jour Fixe on dependencies

• Please provide a separate PR for each dependency to be added until 9 days before the Jour Fixe. A template for the text of the PR is available as Github-Template. Please make sure you fill in all required information. You need to make the PRs against `composer_new.json` and `package_new.json` not against the production files.
• Please do not forget to add the Tag "dependencies" to your PRs.
• Please have a look at the proposed dependencies before the Jour Fixe. We will only look at those dependencies more closely about which questions are asked.
• Be sure to be aware of significant changes in the maintenance of the dependencies you propose.
• It is possible to propose dependencies later on, but in order to keep the trunk of ILIAS as functional as possible, we kindly ask you to go through all the dependencies you proposed for ILIAS 10.
• The dependencies will be merged by the Technical Board.

2.2 Shortening discussions on trivial and already discussed feature requests at the Jour Fixe

In order to create a more fluid and effective Jour Fixe, the Product Manager together with the Technical Board decided that the Product Manager when going through the Feature Requests will flag requests that have already been decided for a previous version or that he considers to be trivial. These requests will still be put on the agenda for visibility, but will not be presented again. There will still be the opportunity to ask questions.

3 Miscellaneous

3.1 Feature Wiki

The Feature Wiki currently consists of over 5.400 pages which are mainly linked via metadata. A good 5000 of these pages relate to feature requests.

To ensure that the Feature Wiki remains clearly organised and that the many suggestions and information posted in it can be found quickly, all participants must observe a few points when creating wiki pages in the Feature Wiki:

1. Please edit the metadata after you created a new wiki page for a feature request.
   • Assign your request to at least one component and remove the assignment to "AAA...". Otherwise, it is hard or impossible to find the new page.
   • PM: On my Feature Wiki Cleaning Day I found 60 feature requests that still were assigned to "AAA..." and for most of them the assignment to the respective component was missing (so I had to assign them according to the content of the request).
2. Please do not create just an empty page with no content in the chapters 'Initial Problem' and 'Conceptual Summary'.
   • At least briefly write down why something should be changed in ILIAS and what the change could look like. You don't need a finished concept for the first proposal. But a feature request that only consists of a title doesn't help much.
   • PM: I removed several empty pages from the Feature Wiki, none of them younger than 6 month. I assume that the respective request is currently not being pursued and therefore no texts have been posted.
3. Please try to re-use existing feature wiki pages for the same feature request instead of creating duplicates.
   
   • If your request for a feature or modification of a component already exists in the Feature Wiki, try to modify and update this wiki page instead of creating a new one. If possible, you can contact the author of the original proposal and ask if the page can be revised. And you can move the description of the first attempt to an accordeon for documentation purposes.
   • PM: When browsing the feature wiki, I keep finding wiki pages on features that have been implemented in the meantime. The older proposals continue to haunt the list of ‘Not scheduled yet’ entries, making the pages unnecessarily full.

3.2 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.3 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.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.
  • A community member is interested to take over these authorities. A discussion about the next steps will take place shortly.

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: 

• none

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. #41549: The deletion of required referenced fields prevents creation and editing and related PR8484: we follow the suggestion of Ingmar and accept the mentioned change for all maintained releases (8, 9 and 10). Please add a short notice to the release pages in section "Changed Behaviour" to notify our users.
2. #42223: RBAC/GlobalRoleAdministratio/Performance: Memory issue in role table when selecting autom. created local roles and related PR8442: We follow the suggestion of Stephan and accept the mentioned changes for all maintained versions. PR is accepted as well.
3. #42718: Failed test: Lernfortschritt durch Öffnen/Herunterladen (Wording/WOPI): We follow Fabian's suggestion and accept the mentioned change. The learning progress in files will be triggered by download, by editing the file via WOPI and by reading the file in view mode (WOPI). All three consumations are treated equally. Test case should be adapted accordingly.
4. #42740: Setting Minute Step Size in Datetime and Duration Inputs does not behave like expected: We follow Tim's suggestion and accepted the change to step sizes of one minute. Accepted for 10 and trunk.
5. #42857: No Access to Import for Users with only Create Object Rights: We keep the current behaviour that was introduced with ILIAS 10. An import of objects is only possible when (a) the related create permission is given and (b) EDIT SETTINGS is given for the parent container (to display the 'Import' tab on the 'Manage' screen).

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.

• 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. 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. NEW: PR8288 • [FIX] remove @uppy/core and @uppy/tus npm packages:
6. PR8360 • Legacy Form: fix date range comparison for combination inputs:
7. NEW: PR8403 • Table/Overlays/Templates: Remove legacy overlays (and with this: table templates):
8. NEW: PR8481 • LegacyUI/Modals: Remove legacy modals:
9. NEW: PR8496 • App: Support PHP 8.4:

4.6 Continuous Integration

• Unit Tests (trunk):
  • As of today, there are (executed with PHP 8.3) ./scripts/PHPUnit/run_tests.sh --random-order-seed 1720173999
    • 12580 (-11)
    • 30757, 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
  • 35 skipped (-1):
    • See file below
  • 0 errors, 0 PHP deprecations
  • PHP 8.4
    • @ all devs.: Please check the issues listed in the failed PHP 8.4 run https://github.com/ILIAS-eLearning/ILIAS/actions/runs/11953437130/job/33321297683?pr=8496
• Code Style:
  • 368 Violations (-11) ./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
  • 26 findings (-3)
    • 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 Status Community Test

• Productivity week 1 (KW 46): 8,5%
• Productivity week 2 (KW 47): 6,4%

• Please test early!
  • Tests are being reassigned faster if other testers report free capacity.
• Blockers remain in Search, Rating, SCORM, cmi5/xAPI; the latter also block parts of Learning Progress 
• Great UI call with Yvonne

5.2.2 WebDAV Tester wanted

Several new testers joined the team in the last few weeks. This allows us to assign almost all test cases. We are still looking for a WebDAV tester. Please get in touch with Kruse, Fabian [Fabian]Fabian Kruse.

5.2.3 Live Testing

Last week’s live testing in our Test-BBB was a great success. We will keep going! Next calls:

• Wednesday, November 27, 14:00 - 15:00 
• Tuesday, December 3, 11:00 - 12:00

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. Kergomard, Stephan [skergomard]: After discussing the issue with the SIG E-Assessment, we would like to simplify the page showing the results:

   • Even if multiple participants are selected, only one is directly shown on the page.
   • Other participants can be selected in the dropdown on the top of the page (as currently).
   • The button "Print" will print a page showing all participants with all the entries in the presentation table expanded. The option to show the best solution will be used as set on the results page.

   JourFixe, ILIAS [jourfixe], 25 NOV 2024: we accept Stephan's suggestion and accept the mentioned change for ILIAS 10 and trunk. A final discussion about the label of the button currently named "Print" can be done until testing completed.

5.6 Dependencies

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

• 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. For ILIAS 11 we are looking to make an own implementation so we do not need to re-accept this dependency anymore.
  • Used by: ILIAS/UI
  • Decision: Dependency is accepted 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. PR8359 • [FIX] Add Buttons and Modals separately to Footer: Pull Request accepted for 10 and trunk. PR will be merged by UI coordinators.
2. PR • :
3. PR • :

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

• Next Bi-Weekly-Meetings:
  • Monday, 02 December 2024, 14:30 - 16:00 
  • no meeting on Monday, 16 December 2024
  • Monday, 13 January 2025, 14:30 - 16:00 
• Further progress on UI components (exemplary): 
  • Integration of Filters in UI Data Table
  • Field\TreeSelect and Field\TreeMultiSelect for the compensation of ilExplorer and related. 
  • Confirmation Modals for the compensation of ilConfirmationGUI & ilConfirmationTableGUI
• some new funding parties – Many thanks to all contributors !
• Estimated funding needed to realise project in 2025: 339.000€ (like 238 Person Days) – currently further 25.000€ are announced

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

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

• Legacy Modal
  • UIComponent » PR #8481 – Looking for shepherd
• Legacy Overlay
  • Table » PR #8403 – Looking for shepherd

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

6.2.1 Status Definitions

Each project in ILIAS has to have one of the following status:

• 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.2.2 Suggested Projects

The following 'Big Projects for ILIAS 11' have been announced in the related data collection and will be presented today:

1. Removing of Legacy-UIComponents-Service and Table

   • Related page in Feature Wiki: (Project) Removing of Legacy-UIComponents-Service and Table
   • Presented by: Samoila, Oliver [oliver.samoila]

   JourFixe, ILIAS [jourfixe]: Oliver gave a short overview of the plans of the ongoing project 'Removing LUI' for 11. Thanks a lot for managing this projects over the years.

   Statement UX/UI/A11y-Experts, 05 DEC 2024: We still welcome this project and consider it very central to the development of ILIAS for the following reasons: As it leads to code reduction, standardisation and a much needed movement forward in bug fixing e.g. of accessibility bugs, the project is able to improve usability and accessibility.

2. Revision of Test Question Creation

   • Related page in Feature Wiki: (Project) Revision of Test Question Creation
   • Presented by: Strassner, Denis [dstrassner]

   JourFixe, ILIAS [jourfixe]: Denis gave an overview of the plans for implementing a new creation of test questions with ILIAS 11.

   Statement UX/UI/A11y-Experts, 05 DEC 2024: We appreciate the aims of this project towards a broad usage of Kitchensink UI elements (like Markdown) and a standardisation in general, thereby helping usability. A reduced volume of support requests could be one result in the long term. Especially the listed improvements of accessibility issues are appreciated so that various usergroups can actually benefit from this project.

3. OER Connect for ILIAS 11

   • Related page in Feature Wiki: (Project) OER Connect for ILIAS 11
   • Presented by: Schmitz, Tim [tschmitz]

   JourFixe, ILIAS [jourfixe]: Tim explained what is planned within this project for ILIAS 11. The project is mainly supported by bwOER Connect (universities from Baden-Württemberg). Several usability tests are planned and findings might result in usability fixes for 10 and new features in 11. More ideas to improve the support for OER support are highly appreciated.

   Statement UX/UI/A11y-Experts, 05 DEC 2024: It is difficult for us to estimate how large the group of users who will benefit from this project will be - however, the easier it becomes, the more likely it should be that OERs will be used and offered. We believe that improving interoperability and compatibility with Moodle is important for the (public) perception of ILIAS. We are very pleased about the planned usability tests and would be happy for the results to be shared; perhaps they can be of use across the board.

4. Calendar Improvement

   • Related page in Feature Wiki: (Project) Calendar Improvement
   • Presented by: Tödt, Alexandra [atoedt]

   JourFixe, ILIAS [jourfixe]: Alexandra reported on what has already been done to improve the calendar in ILIAS 10 and what is now to be tackled with 11. This also includes the implementation of CalDav for ILIAS in order to permanently get rid of current usage problems with the calendar.

   UI/UX/Ally-Experts, 05 DEC 2024: Cleaning up the calendar, getting rid of outdated code and the consistent use of UI components and standards such as CalDAV are steps that we generally consider to be positive and worthy of support. The broad impact of these measures appears to be rather limited and restricted to consultation hours. We consider the mentioned usability tests to be a useful approach and we would like the results to be made visible. We welcome it if the user testing provides findings that are also useful in other areas where the same problems occur (e.g. challenges with UI components).

5. Enforcing the guideline for top actions

   • Related page in Feature Wiki: (Project) Enforcing Guideline for Top Actions
   • Presented by: Kunkel, Matthias [mkunkel]

   JourFixe, ILIAS [jourfixe]: Matthias presented a new project to enforce the Top Actions Guideline. Stephan Kergomard points out that the top actions urgently need to be refactored before new actions are added or removed. Timon points out that the UI/UX experts are already thinking along similar lines. All of these suggestions should be taken up in a planned workshop.

   UI/UX/Ally-Experts, 05 DEC 2024: Guidelines help to standardize and unify the user interface (UI). We support the efforts to implement the guidelines in ILIAS so that users can find what they expect in the same place. In this context, it may also be of interest to define a meaningful sequence of actions to ensure better user guidance. There also appear to be cross-connections with other efforts from the CSS Authorities group, which intends to deal with the content header area (icon, title, tab) next year - the top actions mentioned here are currently placed in this area. We very much welcome the efforts to improve accessibility formulated in the objectives.

6. Individual Assessment: Use in High Volume Scenarios

   • Related page in Feature Wiki: (Project) Individual Assessment: Use in High Volume Scenarios
   • Presented by: Klees, Richard [rklees]

   JourFixe, ILIAS [jourfixe]: Richard explained the background of this project and the related feature requests. Trigger is a specific use case of a big corporate user of ILIAS. Extending the Individual Assessment looks as the best option to realise this use case. But this needs the mentioned extensions of the IA in order to strengthen the tool for the use with bigger groups of participants. Project should be implemented with ILIAS 11 completely.

   UI/UX/Ally-Experts, 05 DEC 2024: In ILIAS, we generally do not yet have so many places where mass processing is possible in a meaningful way, although there is a need for it. It would be great if results/knowledge on how to deal with high volume scenarios could be shared with the community. This could then be helpful for the further development of other objects.

7. Introduce Activities

   • Related page in Feature Wiki: (Project) Introduce Activities
   • Presented by: Klees, Richard [rklees]

   JourFixe, ILIAS [jourfixe]: Richard had already presented this project for ILIAS 10. The aim is to introduce a layer in ILIAS that supports a user's activities. Many of these activities are implemented directly in the GUI classes and are not accessible for web services, for example. This is set to change. Next step will be the publication of related proposal. A prototype implementation in 10 is planned for the study programme.

   UI/UX/Ally-Experts, 05 DEC 2024: It seems to us that this project contributes to code quality and therefore indirectly and in the future helps to improve the accessibility, UI and UX of ILIAS.

8. Component Revision

   • Related page in Feature Wiki: (Project) Component Revision
   • Presented by: Klees, Richard [rklees]

   JourFixe, ILIAS [jourfixe]: Richard will continue the component revision started with ILIAS 9 in ILIAS 11. The sub-project 'Modernize Services/Component' could not yet be fully implemented with ILIAS 10 and will be finalised in 11. A major challenge for ILIAS 11 will be to implement interfaces that are currently used by plugins in the new framework. Aim is to move the existing plugin infrastructure to the new mechanism and to abandon the actual legacy interface. This does not mean that plugins have to be rewritten from scratch. Most of the code could be re-used. If possible, getting a kind of a prototype of a component-revision-compliant plugin would be highly appreciated.

   UI/UX/Ally-Experts, 05 DEC 2024: A modern and stable code architecture is necessary to enable and tackle improvements in UI/UX/accessibility. The project has already brought significant improvements in the past. We look forward to further improvements.

6.3 Software Requirements for ILIAS 11

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

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

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

• none

6.7 Suggested Features for 11

1. Removing Legacy-UI » Toolbar » ‘Label‘ + ‘Input‘ + ‘Legacy Dropdown‘ + ‘Submit‘: We highly appreciate this suggestion and re-schedule the feature for ILIAS 11.

2. Data Collection : Revision of the Placeholder Usage: We highly appreciate this suggestion and re-schedule the feature for ILIAS 11.

3. Move Personal Learning Progress-tab in Main Bar to KS: We highly appreciate this suggestion and re-schedule the feature for ILIAS 11. Please clarify in which view control setting courses without defined period of event are presented (only in "All" or also in "Current").

4. Present Users Learning Progress as Secondary Panel in Course/Group/Folder: We highly appreciate this suggestion and re-schedule the feature for ILIAS 11.

   Postponed to next Jour Fixe

5. Streamline LaTeX usage:

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

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