JourFixe-2022-06-13

Date and place

Monday, 13 June 2022 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 Miscellaneous

2.1 Tool for an Open ILIAS Workspace

Discord has been selected as tool for an Open ILIAS Workspace. The ILIAS channel of Discord is here: https://discord.gg/H9v2v2Ar2T. Feel free to join.

2.2 UI Clinic

Our UI/UX/A11y experts Yvonne Seiler and Kristina Auerswald 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 hours take place every Tuesday before Jour Fixe from 14h30 to 15h00. If you are interested in discussing an issue, please register here!

2.3 Maintainerships

The following maintainerships will change or are offered for takeover by another developer:

1. User Service: Stefan Meyer would like to hand over maintainership of the component Services/User to an interested developer in the nearer future.

   • Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.
2. Object Service: Alexander Killing has removed his implicit maintainership for  Services/Object.

   • Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.
3. Administration: Alexander Killing and Stefan Meyer (2nd maintainer) would like to hand over maintainership of Services/Administration to an interested developer. Code is in good state and the service ready to be used with PHP 8.

   • Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.
4. RBAC: Stefan Meyer would like to hand over the maintainership for /Services/AccessControl to an interested developer in the nearer future.

   • Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.
5. Tree: Stefan Meyer would like to hand over the maintainership for /Services/Tree to an interested developer in the nearer future.

   • Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.
6. SOAP & Web Services: Stefan Meyer would like to hand over the maintainership for /Services/WebServices to an interested developer in the nearer future.

   • Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.

3 Maintained Versions

At the time being, we are maintaining ILIAS version 6 (until mid 2022) and version 7 (until mid 2023).

3.1 Roadmap

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:

Postponed to next Jour Fixe:

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:

* 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 are 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.

1. JourFixe, ILIAS [jourfixe]:

3.5 Open Pull Requests to Discuss

The following pull requests in the ILIAS GitHub repository were marked with 'Jour Fixe' this morning:

Postponed to next JF:

3.6 Continuous Integration

4 Developing ILIAS 8

4.1 Software Requirements for ILIAS 8

4.2 Development Issues

1. Seeland, Per Pascal [PerPascalSeeland]: The codebase of ILIAS contains an undocumented login mechanism ScriptAuth, see here. Since it cannot be modified or enabled via the UI it should be removed entirely

   JourFixe, ILIAS [jourfixe]: Please remove ScriptAuth from the code base of ILIAS 8 as this login mechanism is not used and needed.

2. Killing, Alexander [alex]: While implementing Revision of Public Comments Overview and changed the UI components to Kitchen Sink elements, Alex noticed a problem with the required modal dialogues. Using modals would significantly increase the number of requests and complexity of the implementation. See also the related FR.

   JourFixe, ILIAS [jourfixe]: We accept the current implementation. For the future, we will consider this problem when discussing the modal KS element again.

4.3 PHP 8 Support for ILIAS 8

4.4 Status of Implementation

 
Crowdfunding for Project "PHP 8 for ILIAS 8" is closed. Many many thanks for all contributions. See crowdfunding page.

Information about Implementation and Test Cases

4.5 Pre-Testing ILIAS 8

A first Pre-Pre-Tests showed that the current ILIAS alpha is still quite buggy (5 issues in 5 minutes). We ask all component maintainers to check their components and fix them if necessary within the next two days. This is necessary to run the pre-tests somewhat successfully from Thursday on.

4.6 Timeline for ILIAS 8

TB and PM will discuss the timeline on their meeting tomorrow to decide if we can start the pre-testing on 16 June.

5 Developing ILIAS 9

5.1 Timeline for ILIAS 9

5.2 Suggested Features for 9

1. Page Editor » Presentation of Item Groups in Page Editor: We still would like to have this feature and re-schedule it for ILIAS 9. Concerning Stephan' question: all type of blocks that are available in the container should be presented. Technical preconditions for this will be discussed on the next Page Editor Revision meeting.

2. Abandon Multiple Definitions per Term in Glossary : We follow the suggestion of the maintainer and abandon the feature to have multiple definitions per term in the glossary with ILIAS 9.

3. Abandon Virtual Modes of Glossaries: We support the maintainer's wish to reduce the complexity of the glossary feature and agree to remove the option in ILIAS to have glossaries that have own terms and definitions and collect glossary terms from other glossaries (of the same node or also of sub-nodes).

   Concerning the idea of removing the "collection" behaviour of the glossary in total, we would like to know from more universities if they use this feature and need it for their scenarios. If you are using these virtual glossaries, please let us know here!

   Nevertheless, if we keep this "collecting" behaviour, it will be only offered as an unchangeable mode. So a glossary can have either own terms and definitions _or_ collect them from other glossaries.

   Final decision of this request to abandon is scheduled for 08 August 2022. In case this behaviour is removed in total, a plugin could be implemented to collect glossary terms.

4. New Glossary Presentation for «Flashcards» : We highly appreciate this suggestion and schedule the feature for ILIAS 9. We keep the discussion open about the position and presentation of the "Reset all Boxes" button on the screen. Also other suggestions for presenting the feature are welcome. Please provide mockups here / to Alex. We also suggest to mention the current box (e.g. Box 1) as description text under the glossary title to show the user from which box cards are currently presented.

5. Notification mail to submitter of portfolio after allocation of evaluation status : We highly appreciate this suggestion and schedule the feature for ILIAS 9. We prefer not to send grades per e-mail but just to notify the participants of an exercise that their portfolio, wiki or file upload has been rated. We prefer also to mention the type of assignment in the notification.

   Concerning Yvonne's suggestion: the question of adding additional information about the parent container to such system notifications should be discussed in general on a dedidated workshop as it affects the related guideline for all object types.

6. Add Mailto Feature in list of Portfolio of Other Users : We highly appreciate this suggestion and schedule the feature for ILIAS 9. According to Yvonne's suggestion we prefer to label the action "Send Mail". And we have to make it an action within a dropdown for all resource types (as files have the option "Copy"). Instead of using mail placeholders we prefer to add a short information to the mail text like known from group or course mails where the title and the permanent link of the resource is presented. The subject should not contain "Re:" as it is not a reply but the first message sent.

7. • Feature request presented by
   • Length of slot: '