Feature Wiki

Information about planned and released features

Tabs

Page is read-only.

JourFixe-2022-04-04

Date and place

Monday, 04 April 2022 from 13:00 - 16:50 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).

Participant

Joined VC

Amstutz, Timon [amstutz]

X

Auerswald, Kristina [kauerswald]

Becker, Maximilian [mbecker]

X

Bechtold, Patrick [pbe]

Beym, Marvin [mBeym]

Bromberger, Norbert [bromberger]

Falkenstein, Rob [rob]

X

Famula, Thomas [tfamula]

X

Fuhrer, Thibeau [tfuhrer]

X

Glaubitz, Marko [mglaubitz]

X

Gröbe, Gerald [g_groebe]

Großkopf, Katrin [katrin.grosskopf]

Grotz, Kendra [kgrotz]

X

Haas, Ramona

Heim, Johannes [jheim]

Hilbert, Mirco [mirco.hilbert]

Hesse, Joel [Joel_Hesse]

Jackisch, Ingo [jackisch]

Jacobs, Maximilian [m.jacobs]

Jansen, Michael [mjansen]

X

Kaufmann, Olivia [o.kaufmann]

Kiegel, Colin [kiegel]

Killing, Alexander [alex]

X

Klees, Richard [rklees]

X

Koch, Karola [kkoch]

Kohnle, Uwe [ukohnle]

X

Kröpelin, Philipp [kroepelin]

Kruse, Fabian [Fabian]

X

Kunkel, Matthias [mkunkel] (Minutes)

X

Lorenz, Katharina [klorenz]

X

Meyer, Stefan [smeyer]

Neumann, Fred [fneumann]

Rabah, Rachid [rabah]

X

Reuschenbach, Volker [vreuschen]

Robbenhaar, Clemens

Roeser, Nico [nicoroeser]

X

Samoila, Oliver [oliver.samoila]

X

Scharmer, Lukas [lscharmer]

X

Schenk, Ralf [rschenk]

Schmid, Fabian [fschmid]

X

Seeland, Per Pascal [PerPascalSeeland]

X

Seibt, Alina [alina.seibt]

X

Seiler, Yvonne [yvseiler]

X

Slotosch, Sven [sven.slotosch]

Stepper, Christian [christian.stepper]

Strassner, Denis [dstrassner]

Sesterhenn, Fabian [sesterhenn]

Suittenpointner, Florian [suittenpointner]

Szmais, Ingmar [iszmais]

Tesche, Uwe [utesche]

X

Tödt, Alexandra [atoedt]

X

Vejda, Stefan [stv]

Vollbach, Guido [gvollbach]

Weber, Daniela [dani.weber]

Wessels, Karin [karin.wessels]

Kergomard, Stephan [skergomard]

X

Wischniak, Stanislav [wischniak]

Zehnder, Lukas [lzehnder]

Zenzen, Enrico [ezenzen]

X

1 Appointments

Workshops / Working GroupS

If you want to participate at one of the above mentioned workshops, please register for the related session. This helps to organise the workshop. Thanks!

UPCOMING Jour FixeS

No Jour Fixe at 18 APR 2022 due to Eastern.
  • Monday, May 02, 13:00 - 18:00
  • Monday, May 16, 13:00 - 18:00
  • Monday, June 13, 13:00 - 18:00
No Jour Fixe at 30 MAY 2022 due to Learntec!

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 Pre-Testing ILIAS 8

The Technical Board, the Product Manager, and the Test Coordinator have decided to intoduce a pre-testing phase with very experienced testers testing a few transversal functions of ILIAS to ensure a smooth start of the actual beta-testing phase. This testrun will currently not be tracked in TestRail. For ILIAS 8 it will start on April 7, 2022 and will last until April 15, 2022. We kindly ask developers to reserve some time in the two weeks between April 15, 2022 and April 30, 2022 to fix the issues uncovered by this pre-testing and to give these issues a high priority.

JourFixe, ILIAS [jourfixe]: please clarify how these bugs can be identified easily in Mantis and let us know on the next JF.

Kergomard, Stephan [skergomard], 2022 Mar 10: We would add "Pre8" at the beginning of the summary in mantis. Thus it should be easy to filter correspondingly.

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

2.5 Rescheduling of Jour Fixe

Several community members are complaining that it is difficult to attend the Jour Fixe at the afternoon due to conflicts with family duties. A Jour Fixe in the morning would make it easier to manage work and family commitments. 

Therefore, we would like to open a discussion about an alternative date for the Jour Fixe - either on Tuesday morning, Wednesday morning or Thursday morning. A related survey for a preferred date and for reasons to change (or to keep) the day will be prepared by the product manager. A change of the JF day is planned not before September to give everyone a chance to adapt the new date.

Feedback from the JF participants today:
  • Changing the day and time of the Jour Fixe is considered difficult because …
    • several community members have built their week around the JF
    • believe that the afternoon after a five hour JF in the morning is not an efficient working day
    • a lot of community members have fixed duties in the morning at their universities
  • Survey should offer also option to keep day and time as is (Monday 1 p.m.)
  • Some community members have family duties in the morning which bring them into conflicts with a JF starting at 9 a.m.
  • It is important that as much maintainers as possible can attend the JF to make decisions about features and bugs.

3 Maintained Versions

At the time being, we are maintaining ILIAS version 6 (until mid 2022) and version 7 (until mid 2023). Maintenance of ILIAS 5.4 has ended at 31 DEC 2021.

3.1 Roadmap

LAST RELEASES

  • ILIAS 7.7 published at 09 MAR 2022
  • ILIAS 6.16 published at 16 MAR 2022
  • ILIAS 5.4.26 published at 22 DEC 2021 (last release - end of lifetime)

NEXT RELEASES

  • ILIAS 7.8 scheduled for April 2022
  • ILIAS 6.17 scheduled for April 2022

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:

  1. #32058: Missing support of custom tile image for category link: We accept this as a usability fix for ILIAS 8. 
  2. #32064: Missing support of custom tile image for course link: We accept this as a usability fix for ILIAS 8. 
  3. #32065: Missing support of custom tile image for group link: We accept this as a usability fix for ILIAS 8. 
  4. #32066: No support for tile images in study programme and link to study programme object: We accept this as a usability fix for ILIAS 8. We ask @smeyer to provide a PR for the study programme and link to study programme if possible.
  5. #32255: TA A11y Empty Heading Tag on Info Screen: We highly appreciate the suggested PR. Please merge to release_7 and trunk.
  6. #32259: TA A11y Table Headings in Results Table of Tests Results Tab: We highly appreciate the suggested PR. All table headers should have a headline to make it easier for people using screen readers to use ILIAS. Please merge to release_7 and trunk.
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:

Open Bugs Without Feedback

Last JF

ø Age in Days

Last JF

New Votes*

Old Votes**

Resolved or Closed***

Amstutz, Timon [amstutz]

1x2v

1x3v 2x1v

2

2

47

33

1x2v

Becker, Maximilian [mbecker]

106

110

218

215

1x3v 4x2v 10x1v

1x3v 1x1v

Famula, Thomas [tfamula]

5

3

148

213

1x1v

Fuhrer, Thibeau [tfuhrer]

Großkopf, Katrin [katrin.grosskopf]

0

2

0

110

Haagen, Nils [nlz]

Hecken, Stefan [shecken]

Jansen, Michael [mjansen]

1

1

47

33

Killing, Alexander [alex]

1x2v 4x1v

3x3v 8x2v 64x1v

2x4v 2x3v

Klees, Richard [rklees]

1x3v 2x2v 8x1v

1x4v

Kohnle, Uwe [ukohnle]

9

8

70

64

5x1v

Kunkel, Matthias [mkunkel]

1x2v 1x1v

Ahmad, Nadia [nadia]

2

2

247

233

Meyer, Stefan [smeyer]

188

182

218

220

1x1v

1x5v 1x3v 3x2v 14x1v

1x1v

Neumann, Fred [fneumann]

1x1v

Roeser, Nico [nicoroeser]

1

1

96

82

2x1v

Samoila, Oliver [oliver.samoila]

1x3v

Scharmer, Lukas [lscharmer]

1

1

40

26

Schenk, Ralf [rschenk]

Schmid, Fabian [fschmid]

7

6

78

73

2x2v 7x1v

Schneider, Stefan [sschneider]

Seeland, Per Pascal [PerPascalSeeland]

3

2

44

39

Seiler, Yvonne [yvseiler]

1x1v

Strassner, Denis [dstrassner]

1x1v

41

41

279

266

1x1v

Szmais, Ingmar [iszmais]

1

2

40

28

1x6v

Tödt, Alexandra [atoedt]

3

1

33

27

Vollbach, Guido [gvollbach]

5

5

116

102

1x2v

Weise, Daniel [daniwe4]

1

1

388

374

Kergomard, Stephan [skergomard]

0

1

0

48

Wolf, Fabian [fwolf]

Zehnder, Lukas

Zenzen, Enrico [ezenzen]

* 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:
  1. PR3848 • UI: Implementation of HasDynamicInputs file-input : We highly appreciate this PR and accept it for trunk. Please merge.
  2. PR4137 • Make Chaining of Renderers possible : We highly appreciate this suggestion and accept the PR for all maintained versions and trunk.
  3. PR • :
Postponed to next JF:

3.6 Continuous Integration

  • We currently have 8209 working unit tests for PHP 7.4, 8.0 and even 8.1.
  • Michael Jansen will take over reporting of CI in the future from Richard (after having taken care about it for several years).
  • Thanks a lot to Richard for reporting about CI status!

A screencast (by Jansen, Michael [mjansen]) how to use local qualiy tools to prevent pushing failing unit tests or invalid code style can be found here: https://www.youtube.com/watch?v=yzflNsRpRig

4 Developing ILIAS 8

4.1 Timeline for ILIAS 8

Due to necessary time for reviewing the entire ILIAS code that has been refactored for PHP8 support, it is necessary to add additional time for the reviews and thus change the timeline for ILIAS 8.

  • Reviews completed until April 14, 2022 (newly listed)
  • Reviews integrated and coding completed for refactored components: April 28, 2022
  • Final check of components by their maintainers on April 28 & 29, 2022 (new)
  • Pre-Testing from May 02, 2022 until May 06, 2022 (former April 7, 2022 until April 15, 2022 | new)
  • Integration of the Pre-Test results from May 09, 2022 until May 20, 2022 (former April 15, 2022 until April 30, 2022 | new)
  • Release 8.0 beta1 and release-8 branch planned for May 20, 2022 (former April 29, 2022)
  • Begin of testing phase scheduled for May 23, 2022 (former May 02, 2022)
  • End of testing phase planned for July 29, 2022
  • First stable 8.0 release planned for August 29, 2022
  • Full maintenance for version 8: until December 31, 2023
  • Security bugfixes only: until December 31,2024

4.2 Software Requirements for ILIAS 8

Required and supported software for ILIAS 8 is as follows:
  • ILIAS 8 will support PHP 7.4 and 8.0.
  • ILIAS 8 will not support PHP 8.1. Reasons are:
    • It is not possible to support the range of PHP 7.4 - 8.1 in a single release without suppressing E_DEPRECATED errors for 8.1, and we don't want to soften our error reporting policy for future releases of ILIAS.
    • We can't guarantee all our dependencies are compatible with PHP 8.1 until the beta release.
    • Nevertheless, all component maintainers and contributors MUST provide commits with passing unit tests for the PHP 8.1 build.
    • If you have any questions, do not hesitate to contact the Technical Board.
  • Support for PHP 7.3 will be dropped!
  • PostgreSQL support is abandoned.
  • OpenJDK 11 shall be supported for ilServer.

4.3 Development Issues

Development issues and topics related to ILIAS versions 8

  1. Learning Sequence: Replace TinyMCE with Page Editor : Glaubitz, Marko [mglaubitz]: In the development of the above feature, we encountered some probelmatic aspects which, in our opition, need a short discussion in the JF.

    JourFixe, ILIAS [jourfixe]: We discussed the development issues presented by Marko Glaubitz and decided:
    • "Edit Start Page" and "Edit Exit Page" should be subtabs of tab "Content". Former "Content" sub-tab will be re-labeled to "View" (as known from other components).
    • We would like to have two buttons "View Former Start Page" (fka Abstract) and "View Former Exit Page" on the Settings screen as shown on the mock-up 1 as well as "View Former Start Page" in the tool bar of the new "Edit Start Page" and "View Former Exit Page" on the "Edit Exit Page"
    • If clicking on one of the buttons, a modal with the former start or exit page is presented and content can be copied or downloaded to be re-used in new start or exit page.
    • The representations of the page elements to customise the Start and Exit page of the Learning Sequence ("Start Button" and "Curriculum") should be streamlined to the existing elements. Oliver from PageEditorRevision will get into contact with Richard.
  2. Abandon Link Checker : Tödt, Alexandra [atoedt] The request should inlcude not only the link checker cron job, but the actual link checker in its entirety as well as its implementation in the weblink. The request is to be renamed to "Abandon Link Checker".

    JourFixe, ILIAS [jourfixe]: We accept the requested changes of the article and rename the page to "Abandon Link Checker". The request includes also the removal of the link checker from the Weblink object.

4.4 PHP 8 Support for ILIAS 8

Allowing to run ILIAS 8 with the latest PHP version 8 is the big project for developing ILIAS 8 as it requires a major overhaul of the entire ILIAS source code.

Current Status

176 components in ILIAS have to be refactored. (last JF: 176) (last JF-information 2022-03-21)
  • components to be abandon: services_LinkChecke, services_Radius and Cloud Object
 

Not started yet:

   0

Not started on last JF:

0

 

Components in progress:

 10

Components in progress on last JF:

11

 

Components completed:

 166

Components completed on last JF:

165

 
Components still to be completed:
  • services_Notifications » depending on PRs (until 07th April)
  • services_Migration » depending on PR #3925
  • Workflow Engine (until 07th April)
  • Organisational Units
  • Staff and services_MyStaff
  • Data Collection
  • services_LinkChecker (to be abandon)
  • services_Radius (to be abandon)
  • Cloud Object (to be abandon)

Reviews and Timeline

 

Not finished yet:

 85

Not started on last JF:

 154

 

Reviews completed:

 91

Reviews completed on last JF:

   22

 

Components completed

Review was delivered.
The results have been integrated by the maintainer.

 

Components completed:

 54

Components completed on last JF:

   3

Currently, about 45 hours are still missing for code reviews.
The essential part is allocated to Data Collection, Organisational Units, Staff and Workflow Engine

Next Steps

  • Code refactoring at all service providers with maintenances of outstanding components
  • Code reviews at some service providers
  • Fundraising
 
In the case that dependencies to other components occur that do not allow a maintainer to take any next steps, a corresponding issue in Mantis is requested. The issue should be marked with a [php8] tag. 
 
For ongoing meetings, see: Working Group PHP 8

 
For current funding status please have a look at the crowdfunding page.
 

4.5 Suggested Features for 8

  1. Revision of Private Notes Overview : Thanks for revising the feature request. We highly appreciate the suggestion and accept the feature for ILIAS 8. 

  2. Revision of Public Comments Overview : Thanks for revising the feature request. We highly appreciate the suggestion and accept the feature for ILIAS 8. Filter should be deactivated by default to show all comments.

  3. Streamlining standard and outline icon set : We highly appreciate the new iconset and accept it for ILIAS 8. This iconset does not tackle the glyphs used in the MetaBar. This will be another project - probably for ILIAS 9.

  4. Alphabetical Sorting for Favorites and My Courses & Groups : We highly appreciate this suggestion and schedule the feature for ILIAS 8.

  5. Type ahead for User Notification : We highly appreciate this suggestion and schedule the feature for ILIAS 8.

  6. Member Assignments for Import Type Campus Management : We highly appreciate this suggestion and schedule the feature for ILIAS 8.

5 Developing ILIAS 9

5.1 Timeline for ILIAS 9

  • Feature freeze at May 31, 2022 (changed): deadline to suggest new features for this version
  • Coding completed: all features implemented and test cases finished until October 28, 2022
  • Release 9.0 beta1 and release-9 branch planned for October 30, 2022
  • Beginn of testing phase scheduled for October 30, 2022
  • End of testing phase planned for Februar 02, 2023
  • First stable 9.0 release planned for March 15, 2023
  • Full maintenance support for version 9: until December 31, 2024
  • Security bug fixes only: until December 31, 2025

5.2 Big Projects for 9

The following suggestions have been made for Large Developments for ILIAS 9.

Please find a statement from the Technical Board for each of the projects below. The Technical Board has also added the statements of the UX/UI/A11y-Experts for the projects they deemed most important. You can also find the statements below directly on the Wiki-pages of the projects.

  1. Establish Referential Integrity
    • Relevance for strategic ILIAS development: Data integrity important for further development and security of ILIAS.
    • Plan for ILIAS 9: more workshops; development of tools for migration, utility functions, ilDB...; creation of guideline; reference implementation in mail component.
    • Chance of realisation: partly financed - good (but still needs to be estimated); personnel: depends on distribution of tasks
    • Dependencies: No dependencies on other developments 
    • Impact on other development activities: not known, if at most positive

    Statement Technical Board: 
    Thank you very much for relentlessly pushing this effort for the last few years. Database integrity is definitely a valid target for improvement. The outlined plan to provide tools to maintainers to actually move their component to a better integrity sounds plausible. If these tools are applied, they will definitely make the system more reliable. Still, we worry that this effort will bind resources urgently needed for other efforts with similar goals that are already ongoing. Especially the IRSS seems to be problematic, since Fabian Schmid (as a maintainer of database and IRSS) will be heavily involved in both efforts. In general, we cannot push too many improvements at the same time, as this would overwhelm maintainers. We thus suggest keeping this effort low profile for ILIAS 9 and prepare the according code and documentation. If prepared properly, we can see this becoming a large topic with ILIAS 10. Please coordinate closely with Fabian to enable him to distribute his resources judiciously. In addition, please see, if maybe other people can tackle tasks for him. We will be happy to support this effort with advice for a proper preparation and project management. We are looking forward to making this a larger topic with ILIAS 10.

  2. Page Editor Revision – Step 3
    • Relevance for strategic ILIAS development: Content creation within the system important for ILIAS; continuation of developments started since 7
    • Plan for ILIAS 9: see project page
    • Chance of realisation: financially good; personnel: depends on workload Alexander Killing. Is important for maintainer and he gives project therefore high priority!
    • Dependencies: no dependencies on other developments, but needs further KS elements
    • Impact on other development activities: No impact on other developments

    Statement Technical Board:
    With this proposal, the Page Editor revision enters its third iteration since the initial push with ILIAS 6. The project will certainly involve many people, but only a few of them maintainers. We would be very happy if very concrete goals are formulated and implemented here for ILIAS 9 and if after the completion of this iteration the "revision" is finished or the work is continued in a taskforce. From a product-strategic point of view, the editor is of course a critical tool for content creation and therefore deserves a lot of attention. We thank you very much for this contribution.

    Statement UX/UI/A11y-Experts:
    The editor is not accessible yet and from a user perspective quite a few issues are still open so that the general appearance is inconsistent for them. This leads to some confusion. This important next step will allow us to considerably streamline the experience. We already see the need to further pursue this project with ILIAS 10.

  3. Splitting up Tools
    • presented by Yvonne Seiler
    • project page: [[[Project] Splitting Up Tools]]
    • Relevance for strategic ILIAS development: Important for better and more user-friendly use of tools. Current concept irritates users. Confusing workflows need to be reduced → better usability!
    • Plan for ILIAS 9: see project page
    • Chance of realisation: Project can be realised in small steps / incriminating approach
    • Dependencies: Partly dependent on development of page editor and accessibility improvements.
    • Impact on other development activities: None

    Statement Technical Board:
    We see how this significant project impacts the strategic aims to make ILIAS a more adaptable learning environment as well as usable for everyone. We thus consider this development very beneficial for the project. Still, we do not see that the coaching of the TB would have a considerable impact on the further progress of the projects, as most answers regarding technical implications related to this endeavor are already considered and published.

    Statement UX/UI/A11y-Experts:
    The tools as they are today leave the users with quite a few questions. The conceptual work done during the last few years has created strong indications that splitting the tools up into different groups of tools with different strategies for the UX/UI should improve the situation considerably. It is a very important project, but the working group that already works on these issues will continue working, and thus the project can be advanced outside of the frame of the Big Projects.

    • Relevance for strategic ILIAS development: Unification of the UI addresses all targets of Technical Board to improve ILIAS.
    • Plan for ILIAS 9: See PR4013 and PR4014 
    • Chance of realisation: Staggering to two versions increases chance of realisation; funding necessary
    • Dependencies: requires cooperation of all maintainers
    • Impact on other development activities: Further developments must use KS UI elements and can no longer fall back on legacy components.

    Statement Technical Board:
    This project was proposed by the Technical Board and is to be understood as a strategic project. It is very important to save resources in the future and to get more consistency in the UX/UI. In connection with the abolition of bootstrap 3, the project is also important for the security, consistency and usability of ILIAS.
    This project will, in a first step, require a lot of conceptual work and the Technical Board sees itself in an important role. Thus, a strong focus will be put on it and it will be accompanied closely. After the conception of individual components, they must be implemented in the entire code base through a lot of diligent work.

    Statement UX/UI/A11y-Experts:
    This project as well as Project E and F will be important to improve consistency of the UI. They are important steps to continue the change started with the UI-Kitchensink and the Global Screen Service.

  4. Abandon Bootstrap 3
    • presented by Timon Amstutz
    • Relevance for strategic ILIAS development: get rid of dependency on Bootstrap 3 and LESS (middle prio)
    • Plan for ILIAS 9: Get rid of Bootstrap CSS/Less
    • Chance of realisation: good financial chance of realisation; sticking point rather human resources
    • Dependencies: great dependence on project D
    • Impact on other development activities: influence on all developments that work with DOM structure

    Statement Technical Board:
    The proposed project is strongly related to "Remove Services/UIComponent and Services/Table", as there are numerous DOM elements that still rely on Bootstrap. Bootstrap 3 has dependencies on JS and DOM nesting that need to be removed as part of this project, and therefore many places will be touched. There will be many people involved, and it will tie up considerable resources. Since Bootstrap 3 is no longer supported, we definitely need to tackle this project asap.

    Statement UX/UI/A11y-Experts:
    This project as well as Project D and F will be important to improve consistency of the UI. They are important steps to continue the change started with the UI-Kitchensink and the Global Screen Service.

  5. Views / InnerContent
    • presented by Fabian Schmid
    • project page: [[[Project] Views / InnerContent]]
    • Relevance for strategic ILIAS development: High priority! Many bugs come from complexity of page structure. It would be simpler and safer in future through predefined structures; also creates more consistency on UI side, also more security.
    • Plan for ILIAS 9: development, elaboration and discussion of the concept; proof of concept of a simple component (probably file object), including new UI components (e.g. assynchronous tabs), screen IDs
    • Chance of realisation: can only be said after concept development; screen IDs financed and thus safe for I9
    • Dependencies: dependent on UI components, on ilCtrl, on GlobalScreen
    • Impact on other development activities: impact on other components only in the context of the respective adaptation

    Statement Technical Board:
    The Technical Board believes that this project has a big technical relevance and will have deep architectural impacts to allow ILIAS to be a more "Adaptable Learning Environment". However, we think that the already outlined technical approaches (e.g. integration into the Global Screen Service) should not need too much involvement of the Technical Board. Still, we agree to support „on demand“ when deemed necessary for this medium-to-high priority project.

    Statement UX/UI/A11y-Experts:
    This project as well as Project D and E will be important to improve consistency of the UI. They are important steps to continue the change started with the UI-Kitchensink and the Global Screen Service.

    • Relevance for strategic ILIAS development: Important continuation of the conversion to IRSS in many other components.
    • Plan for ILIAS 9: Convert other components to IRSS
    • Chance of realisation: Conversion in components can also be done by the respective maintainers themselves
    • Dependencies: Cooperation of other maintainers
    • Impact on other development activities: No impact

    Statement Technical Board:
    The TB believes this effort to be on a good track. First components are already migrated, and the infrastructure is ready. The remaining effort mostly lies in migrating the various components using file storage functionality. To complete this project soon, we assign a high priority to it. We ask every collaborator to focus on this effort or include according changes into other efforts. If we all pull together, we can move our system to the IRSS soon. To achieve this, we feel that Fabian will mostly need to do some further marketing and dissemination, and we will happily support him as Technical Board to convince everyone to finally use the IRSS.

  6. ILIAS Refinement
    • presented by Oliver Samoila & Denis Strassner
    • project page: [[[Project] ILIAS Refinement]]
    • Relevance for strategic ILIAS development: Promotes acceptance in everyday life when even the small bugs are fixed; confirms bug reporters when their bug reports are also addressed.
    • Plan for ILIAS 9: Prioritise the bugs and work through them.
    • Chance of realisation: Project can be done in small steps, possible co-financing by advisory board; time for bug fixing must be available with maintainer.
    • Dependencies: none
    • Impact on other development activities: none

    Statement Technical Board:
    We strongly endorse the goal to reduce the number of issues and improve the workflow around tackling them. However, we believe this to be an effort to be worked on continuously. Since we believe this to be a necessary task for all future versions of ILIAS, we do not give this special priority for the next ILIAS version. However, we fully support and endorse activities around it for ALL upcoming ILIAS versions. Since we believe “ILIAS Refinement” to be a continuous project, we should take care to only support measures that we have the capacity to sustain for all releases in years to come.

  7. Continuous Refactoring Initiative
    • presented by: Oliver Samoila
    • project page: [[[Project] Continuous Refactoring Initiative]]
    • Relevance for strategic ILIAS development: very high for sustainability of ILIAS
    • Plan for ILIAS 9: See project page
    • Chance of realisation: use of quality assurance funds of ILIAS association; personell: depending on free capacities until October
    • Dependencies: to be clarified for each component
    • Impact on other development activities: to be clarified for each refactoring

    Statement Technical Board:
    The Technical Board agrees that continuous refactoring is a key aspect in ILIAS. We believe that we need strategies to ensure, that this refactoring activity will continuously accompany the work on ILIAS OSS. Since we believe this to be a necessary task for all future ILIAS versions, we do not give this special priority for the next ILIAS versions. However, we fully support and endorse activities around it for ALL upcoming ILIAS versions. Since we believe ILIAS Refinement to be a continuous project, we should take care to only support measures that we have the capacity to sustain for all releases in years to come.

  8. Component Revision
    • Relevance for strategic ILIAS development: Considerable strategic relevance, especially with regard to plug-ins (will make it easier to adopt plug-ins in core in future); also improves maintainability and expandability of ILIAS.
    • Plan for ILIAS 9: Implementation of a parallel implementation
    • Chance of realisation: Time for workshops of maintainers, financing for ILIAS 10 hopefully via advisory board
    • Dependencies: Coordination with Views
    • Impact on other development activities: Impact on all developments (when implemented)

    Statement Technical Board:
    The Technical Board believes that this project has a big technical relevance and will have deep architectural impacts to allow ILIAS to be a more "Adaptable Learning Environment". The Technical Board assigns a high priority to this development, and we’re looking forward to further collaborate on this matter. The project also requires the focus of the component maintainers.

  9. Booking Tool Revision
    • Relevance for strategic ILIAS development: Important administrative tool that can only survive if it can cope with intensive use.
    • Plan for ILIAS 9: see project page
    • Chance of realisation: step-by-step implementation; funding interest justified; maintainer willing to allow time for 9
    • Dependencies: no dependencies on other developments
    • Impact on other development activities: none

    Statement Technical Board:
    We believe this project to involve a limited number of stakeholders. We see that there are related feature requests, however we are also not sure how large the impact on other services or modules will be. There is definitely a lot of room for improvement, and we hope the projects will achieve the outlined goals. The Technical Board will assign no special priority to this project.

  10. Search Revision
    • presented by: Stefan Meyer
    • project page: [[[Project] Search Revision]]
    • Relevance for strategic ILIAS development: Improvement of a central service that rarely receives funding but is of hugh importance for using the system.
    • Plan for ILIAS 9: Workshops, first feature development (especially presentation)
    • Chance of realisation: Funding still unclear / dependent on workshop results
    • Dependencies: Dependence on KS / UI elements
    • Impact on other development activities: None

    Statement Technical Board:
    We believe this project to involve a limited number of stakeholders. We see that the related feature requests mainly concern the search maintainer. Therefore, we are not certain how large the impact on other services or modules will be. There is definitely a lot of room for improvement, and we hope the project will achieve its goals. The Technical Board will assign no special priority to this project.

    Statement UX/UI/A11y-Experts:
    A good search-functionality is vital for the accessibility of ILIAS. It needs to be made sure while improving the search-functionality that the search forms and results pages themselves are accessible.

  11. Export Revision
    • Relevance for strategic ILIAS development: Import validation in particular is important to prevent broken database structures in the future. Also relevant for security to reduce attack vectors.
    • Plan for ILIAS 9: Above all
    • Chance of realisation: Funding available, human resources available
    • Dependencies: Intersection with Resource Storage Service
    • Impact on other development activities: In principle, influence on all objects that support export/import.

    Statement Technical Board:
    The export and import of ILIAS-Content can clearly be improved, and we thank Stefan Meyer to tackle this task. We see the importance specially concerning the validation of imports. We don't see special priorities regarding the resources of the Technical Board, but please make sure to involve the other maintainers impacted by any changes as early as possible.

5.3 Suggested Features for 9

  1. [[]] :
    • Feature request presented by
    • Length of slot: '
  2. [[]] :
    • Feature request presented by
    • Length of slot: '
  3. [[]] :
    • Feature request presented by
    • Length of slot: '
  4. [[]] :
    • Feature request presented by
    • Length of slot: '

[1] Bug reports counted only for core project, not for plugins

Last edited: 18. Oct 2024, 16:07, Kunkel, Matthias [mkunkel]