Feature Wiki
Tabs
JourFixe-2018-07-02
Date and place
Monday, July 02, 2018 from 13:00 – 18:00 at ILIAS-Verein office in Köln
Time | Topic |
|---|---|
13:00 - 14:30 | 1. Appointments |
14:40 - 17:30 | 3. Developing 5.4 |
17:30 - 18:00 | 4. Miscellaneous |
Participants
At ILIAS office:
- Killing, Alexander [alex], Kunkel, Matthias [mkunkel] (Minutes), Vollbach, Guido [gvollbach], Seeland, Per Pascal [PerPascalSeeland], Meyer, Stefan [smeyer], Klees, Richard [rklees], Famula, Thomas [tfamula], , Jansen, Michael [mjansen]
- Schmid, Fabian [fschmid], Samoila, Oliver [oliver.samoila], Heyser, Björn [bheyser], , Amstutz, Timon [amstutz]
If you like to participate at the Jour Fixe via Skype, please join our Skype meeting!
1 Appointments
- July 04, 2018, 10:00 - 16:00: Workshop 'Introduction of Service Discovery for Workflow Engine' at Databay AG AG, Würselen
- July 13, 2018, 10:00 - 12:00: Workshop 'Setup Revision and support of clients', VC in Skype (see info in group)
2 Maintained Versions
2.1 Roadmap
Last releases:
- ILIAS 5.3.6 published at June 20, 2018
- ILIAS 5.2.17 published at June 28, 2018
- ILIAS 5.1.27 published at May 11, 2018
- ILIAS 5.3.7 scheduled for July 2018
- ILIAS 5.2.18 scheduled for August 2018
- ILIAS 5.1.28 scheduled for July 2018
2.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:
- Mantis #22248: Taxonomy tree filter in question pool cannot be reset : Question pool should show same behaviour as glossary: clicking on the taxonomy title shows all questions. Notice: current icon of taxonomy is wrong - should be tree, not leaf -> Matthias will open a separate bug report for this.
- Mantis #23160: ilMimeMail shows erratic behaviour for consumer code : Michael will have a look at this issue and discuss a possible solution with Alex.
- Mantis #23169: Media objects in html have some implications : The Technical Board decided that features that improve security can also be suggested after feature freeze. But the current suggestion is not accepted as a sound solution for the problem of uploading HTML content. A workshop about HTML content handling would be highly appreciated.
- Mantis #23208: The second LDAP-Server is not used, when the first fails : We follow the recommendation of the maintainer and abandon the support of multiple LDAP server support in the current implementation with ILIAS 5.4. Nevertheless, a sound implementation of such a feature would be highly appreciated but needs a separate feature request. @ Stefan: please create a feature wiki request to abandon this feature and add it to one of the next JF agendas.
- Mantis #23238: Individual Assessment does not respect the 'Initial Permissions Guideline' : Object types created after the guideline has been accepted will introduce permissions for new objects as a bug fix. Permissions cannot be changed for other global roles like USER (id=4). If the original USER role has been deleted, no global role will be changed. "Change existing objects" cannot be executed due to missing API and because we do not want to overwrite permissions already set by users through a db update step.
- …
2.3 General Development Issues
The IMS-Global-Library for LTI seems to be abandonned. The original maintainer supposedly left IMS-Global, PRs and issues weren't processed since end of 2016. How do we deal with that situation? (Richard [rklees], 2018-06-27)
- A fork of the original library has already been added to the ILIAS e.V. repo. We try to find more supporters in other software projects that help us to maintain the library for the future. In general we should be careful in adding additional libraries. Otherwise we get more and more dependencies and related problems.
- Stefan will fix the known problem of the library in our fork.
2.4 Bugfixing Statistic
Bug reports[1] set to status 'open' and not been touched by responsible maintainer for more than 21 days (checked this morning):
Responsible Maintainer | Open bugs without feedback | Last JF | ø Age in days | Last JF | Priority bugs and votes * | Last JF |
|---|---|---|---|---|---|---|
1x1v | 1x1v | |||||
5 | 5 | 106 | 92 | 1x2v, 2x1v | 1x2v, 2x1v | |
2x1v | 1x1v | |||||
1x3v, 1x2v, 28x1v | 1x3v, 1x2v, 29x1v | |||||
Thomas Joussen | 2 | 1 | 151 | 265 | 1x1v | 1x1v |
40 | 47 | 59 | 60 | 1x2v, 4x1v | 3x1v | |
1x1v | 1x1v | |||||
7 | 7 | 94 | 80 | 4x1v | 4x1v | |
6 | 6 | 153 | 139 | 2x1v | 2x1v | |
13 | 13 | 118 | 107 | 1x3v, 3x2v, 29x1v | 1x3v, 3x2v, 40x1v | |
1x1v | 1x1v | |||||
Benjamin Seglias | 1x3v | 1x3v | ||||
1 | 38 | |||||
1x1v | 1x1v |
* Reports set to 'funding needed' are not listed.
Bug reports with status 'Fixing according to priorisation' should be fixed before other bugs are tackled. Priorised bugs 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.
2.5 Open Pull Requests to Discuss
The following pull requests in the ILIAS GitHub repository were marked with 'Jour Fixe' this morning:
- DIC Additions : Additional guideline is highly appreciated. Please merge to trunk.
- UI Workflow : We highly appreciate this suggestion and accept it for the trunk. Please change the status of the label "not yet available" to "not available" to cover also status that are independent from any timing.
- KS: Toggle Button : We highly appreciate this suggestion and accept for trunk. Activation / deactivation of the toggle should be called 'on' / 'off'. Please add the on-off-state to the constructor.
2.6 Continuous Integration
Overview on current status and reports from CI-server at http://ci.ilias.de:
- automated tests: 2769 (+176) passing unit tests on PHP PHP 7.0, PHP 7.1..
- We lost tests. Why?
- We did not. Some tests are conditional (i.e. they only run if another test passed) and TeamCity does not count them.
- We lost tests. Why?
- results of dicto architectural tests
- 3659 violations (net) resolved since last JF
- only ~4100 to go... (was ~7800 on last JF!!)
- Please run unit tests locally before committing.
- Performance monitoring:
- CI-Server (Login as Guest)
- No info available at the moment.
2.7 Status of Documentation of 5.3
Finally, all new 5.3 features have now sufficient information about its implementation on the related feature page and chapter. Thanks to all maintainer for providing this information.
3 Developing 5.4
3.1 Release Cycle for Version 5.4
Feature freeze | 30 APR 2018 |
Coding completed | 29 OCT 2018 |
Test cases completed | 29 OCT 2018 |
Documentation of implementation completed | 29 OCT 2018 |
Beta1 release and start of testing 5.4 | 31 OCT 2018 |
Testing completed | 31 JAN 2019 |
End of bug fixing | 08 MAR 2019 |
Stable version 5.4.0 | 13 MAR 2019 |
In accordance with the Technical Board the product manager decided to set the documentation of implementation of a feature as another requirement to get an implemented feature into trunk. This information helps testers to understand the feature they have to test and improves the understanding of the feature for users. This requirement is effective from ILIAS version 5.4. Similar to test cases and approval, the documentation of implementation on the feature wiki page needs to be completed until October 29, 2018 for version 5.4.
3.2 Status of Development
Number of features scheduled for Release 5.4 and their status this morning:
Status | Today | Last JF | Diff |
|---|---|---|---|
A - in trunk | 3 | 3 | 0 |
B - approved / committed soon | 1 | 1 | 0 |
C - waiting for approval | 10 | 6 | +4 |
D - in development | 5 | 7 | -2 |
E - contract settled | 11 | 11 | 0 |
F - option or agreement for funding | 39 | 40 | -1 |
G - partly funded | 0 | 0 | 0 |
H - funding needed | 14 | 13 | +1 |
Candidates for abandoned features | 2 | 2 | 0 |
Total | 85 | 83 | +2 |
Notice: Features currently assigned to categories B to H have to be in the trunk until October 29, 2018 to become part of the official 5.4 release.
3.3 Development Issues in 5.4
- …
3.4 Feature Requests to be Discussed
The following features suggested for 5.4 were added to the data collection 'Suggestions for Jour Fixe Agenda' to be discussed today (see procedure documented in ILIAS community FAQ):
Filter-Configuration in Categories : We highly appreciate this suggestion and schedule it for 5.4 with the following changes / extensions:
- We would like to have a general setting in Administration » Repository to enable / disable the category filters for a whole installation.
- Implementation of this feature must respect the decisions of the general UI Responsive Table Filters discussion, see Responsive Table Filters.
- We would like to have one button to add a filter that contains standard metadata fields and custom metadata fields.
- We prefer to use checkboxes for selecting the fields to filter.
Show-More Behavior : We highly appreciate this suggestion and schedule it for 5.4 with the following change:
- We would like to have a new KS element "Show More Button" that can be addressed separately and that comes with a spinner wheel for showing the loading of new items when clicked. The button should use the entire space under each block (when needed) and be centralised. The existing list implementation can be re-used.
Optionally hide title of learning module : We highly appreciate this suggestion and schedule the feature for 5.4. The menu in ILIAS learning modules should be presented as tabs in general.
- Feature suggestion presented by Glaubitz, Marko [mglaubitz]
- Slot length: 15'
Make Chapter / Page Tree Collapsible in Learning Module Page Layout : We highly appreciate this suggestion and schedule it for 5.4. We use the already introduced pattern of the explorer toggle for this implementation because there won't be an alternative from the General Layout Revision for 5.4.
Improved Question Preview in Pool : We highly appreciate this suggestion and schedule it for 5.4. Please follow Matthias' suggestion and modify the paragraph style for "Feedback" accordingly.
Relative Deadlines for Assignments : We highly appreciate this suggestion and schedule it for 5.4. Please change the label for "Tage" in "Bearbeitungszeitraum in Tagen" to clarify the meaning of the UI.
SOAP: include online/offline status of learning modules in object xml / Centralizing online/offline status - step 1: We highly appreciate this suggestion and schedule it for 5.4. Please provide some more information about the technical concept to give a better impression of possible dependencies, esp. for objects that do not support online/offline yet.
- Feature suggestion presented by Meyer, Stefan [smeyer]
- Slot length: 30'
Postponed to next Jour Fixe due to missing time
Plugin Slot for user profile data (UDF) :
- Feature suggestion presented by Meyer, Stefan [smeyer]
- Slot length: 15'
User: Criteria-based »User Agreement« documents :
- Feature suggestion presented by Jansen, Michael [mjansen]
- Slot length: 30'
Improve Usability of Export of and Access to Personal Data :
- Feature suggestion presented by Tödt, Alexandra [atoedt]
- Slot length: 30'
Export of huge amount of data categories :
- Feature suggestion presented by Tödt, Alexandra [atoedt]
- Slot length: 30'
4 Miscellaneous
Clean-up and Concept about improving Test & Assessment
Based on the recommendations made by the maintainer to improve the quality of the T&A component, a coordinated review of reported bugs in the T&A has been made by members of the SIG Test & Assessment and other community members in the last weeks.
- 14 participants have checked 25 bugs (total 350 bugs), tried to reproduce them, closed them in case of non-reproducability or added additional information incl. click-ways to ease bugfixing.
- 156 Bugs could be closed due to non-reproducability.
- Description of a lot of bug reports were improved.
The Technical Board has analysed the document 'Investigation on Large Components : Test & Assessment', written and committed by Björn Heyser and given the following feedback / statement:
Das TB bedankt sich bei Björn Heyser und seinen Co-Autoren für die detaillierte Ausarbeitung der Vorschläge zur Verbesserung der Zuverlässigkeit des Moduls "Test und Assessment". Das TB hofft auf eine breite Kenntnisnahme der dargestellten Probleme, Lösungsvorschläge und weiteren Erwägungen und stellt das Paper allen interessierten Personen zur Verfügung.
Wie der Maintainer selbst, empfiehlt auch das TB dringend, die vorgeschlagene Option 1 bald möglichst umzusetzen. Bis zur Implementierung der Option sieht das TB die weitere Umsetzung von Features für das T&A kritisch, besonders wenn diese nicht zur Realisierung der Option 1 beitragen oder die Komplexität des T&A erhöhen. Für die Umsetzung der Option empfiehlt das TB ein kleinschrittiges Vorgehen und damit zunächst die Erstellung eines technischen Konzepts für die Schnittstellen eines Fragenservices und die Abstimmung dessen in der Community. Das TB bittet Björn Heyser um die Erstellung einer Offerte für eine entsprechende Erarbeitung der Schnittstellenspezifikation. Das TB wird die gesamten Umsetzung der Option begleiten, sich mit Rat und Tat beteiligen und wenn nötig bei der Suche nach Budgets unterstützen.
Die im Paper unter 8.3. aufgezählten Maßnahmen hält das TB ebenfalls für sinnvoll und bedankt sich für die bereits angelaufene Umsetzung derer. Der vorgeschlagene Rückbau der Features wird vom TB für sehr sinnvoll erachtet. Dieser sollte schnell begonnen werden, um die Komplexität der Komponente für ein Refactoring zu verringern. Das TB bittet außerdem darum, auch der Überarbeitung der Testfälle des T&As ein besonderes Augenmerk zukommen zu lassen, da diese benötigt werden, um einen Umbau abzustützen.
Das TB hält weiter die in Abschnitt 3.3 vorgeschlagene Option zur organisatorischen Aufteilung des TA Moduls durch den Einsatz einer Konzepterin oder eines Konzepters umzusetzen für schlüssig. Je nach Komplexität eines Vorhabens hält das TB es auch für sinnvoll eine Projektmanagerin oder einen Projektmanager hinzuzuziehen. Das TB empfiehlt deshalb, diese Option weiter zu verfolgen. Das TB sieht den Maintainer des T&A aber auch in Zukunft als ersten Ansprechpartner für die Komponente.
--- In English ---
The TB thanks Björn Heyser and his co-authors for their detailed elaboration of proposals for improving the reliability of the "Test and Assessment" module. The TB is hoping for a broad acknowledgement of the problems described, proposals for solutions and further considerations and provides the paper to interested people.
As the maintainer, the TB strongly recommends the proposed option 1 to be implemented as soon as possible. Until the implementation of option 1, the TB believes the further implementation of features to be risky for T&A, especially if they are not used for realizing option 1 or if they additionally increase the complexity of the T&A. For the implementation of option 1, the TB recommends an iterative procedure in small steps and thus recommends first of all the creation of a technical concept for the interfaces of a question service in coordination with the community. The TB asks Björn Heyser for an offer for a corresponding development of the interface specification. The TB will accompany the entire implementation of the option, participate in word and deed and, if necessary, support the process of the fundraising.
The TB also considers the measures listed in the paper under 8.3. to be reasonable and thanks for the implementation, which has already begun. The proposed dismantling of features is considered to be important by the TB. This should be started quickly in order to reduce the complexity of the component for refactoring. The TB also asks for the revision of the T&As test cases as these are required for supporting the refactoring.
The TB further considers the option proposed in Section 3.3 for the organizational distribution of the TA module by introducing a conceptual designer as conclusive. Depending on complexity of a project, the TB also believes that it makes sense to to call in a project manager. The TB therefore recommends this option to be pursued further. However, the TB still considers the Maintainer of the T&A as the first contact for the component in future.
---
Next Jour Fixe dates
- Monday, July 16, 2018, 13:00 - 18:00
- Monday, July 30, 2018, 13:00 - 18:00
- Monday, August 13, 2018, 13:00 - 18:00
Last edited: 19. Apr 2023, 12:28, Kunkel, Matthias [mkunkel]