Feature Wiki

Information about planned and released features

Tabs

Page is read-only.

JourFixe-2019-03-11

Date and place

Monday, March 11, 2019 from 13:0018:00 at ILIAS-Verein office in Köln

Time

Topic

13:00 - 14:20

1. Appointments
2. Maintained Versions

14:30 - 15:00

3. Publishing 5.4

15:00 - 17:45

4. Developing 6.0

17:45 - 18:00

5. Miscellaneous

Participants

At ILIAS office:

Participated via VC:

If you like to participate at the Jour Fixe via Skype, please join our Skype meeting! (Achtung: geändert URL)

1 Appointments

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!

2 Maintained Versions

2.1 Roadmap

Last releases:

  • ILIAS 5.4.0_beta1 published at October 31, 2018
  • ILIAS 5.3.13 published at February 14, 2019
  • ILIAS 5.2.22 published at February 14, 2019
Next releases:
  • ILIAS 5.4.0 scheduled for March 20, 2019
  • ILIAS 5.3.14 scheduled for March 2019
  • ILIAS 5.2.23 scheduled for April 2019

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:

  1. #21675: The tabs are missing if you acces the information of the SCORM module : There is no guideline yet that tackles this problem. The ILIAS LM and the glossary have two different views (presentation vs. authoring). This is why you see different tabs when clicking on Info or Settings. But as the current behaviour is according to the maintainer's vision of user behaviour we accept it. Bug can be closed.
  2. #24069: Failed test: Probleme bei Bewertung, Medienobjekt, Textfeld m. Variante; : We consider the display problem of the rating stars as a problem but do not request to fix this for 5.4. The rating in general should be changed to the KS Pop Over to prevent such problems. This could be done as part of a refactoring for 6.0. Bug can be closed if all other issues above have been solved.
  3. #24748: Column "Organisational Units": In 5.4 we do not have a setting that enables or activates Org Units. Such a setting would be necessary to check if this column should be offered or not. Therefore, we cannot offer a fix for 5.4. But we would highly appreciate if a new setting would be added to the OrgUnit Administration. If this setting enables org unit support a column like this would be displayed. Please add a new FR for this. Thanks!
  4. #24967: Captcha für Registrierung funktioniert die Audioausgabe nicht: The implementation of the feature is based on Flash. We keep the feature as it is - esp. because a feasible alternative is not known yet. Please create a Feature Wiki request for a non-flash-based implementation for 6.0. Any good technological base that also correspond with our data protection requirements is highly appreciated.
  5. #25030: Failed test: Link-Haupteintrag in Sprachen übersetzen : Alexander will have a look how this issue can be solved in the user service. For us it is required that the language-sensitivity for the Public Area works for the main menu like for category titles or page content.
  6. #23993: Position des Hauptmenüeintrages "Achievements"We agree with Fabian's suggestion to remove separators for installations updated from 5.3 or below. For new installations the suggested entries above incl. separators are taken.
  7. #24616: Failed test: Mehrere Medienobjekte gleichzeitig hochladen (ilFileStandardDropzoneInputGUI not usable for multiple files?) : We prefer to stay on the page (for the moment). An automatic redirect would be highly appreciated. If this cannot be done for 5.4.0 we accept it for 5.4.1 as well.
Postponed :

2.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:

Responsible Maintainer

Open bugs without feedback

Last JF

ø Age in days

Last JF

New Votes*

Old Votes**

Resolved***

Amstutz, Timon [amstutz]

Becker, Maximilian [mbecker]

5

5

240

226

1x2v 2x1v

Braun, Jean-Luc [braun]

5

85

1x2v 1x1v

Hecken, Stefan [shecken]

Heyser, Björn [bheyser]

31

30

56

45

4x2v 32x1v

1x2v

Jansen, Michael [mjansen]

1

111

2x2v

Thomas Joussen

2

2

153

139

Killing, Alexander [alex]

4x1v

1x5v 5x1v

Klees, Richard [rklees]

1x1v

Kohnle, Uwe [ukohnle]

6

19

87

90

3x1v

Kunkel, Matthias [mkunkel]

Langkau, Thomas [langkau]

2

2

193

179

4

4

205

191

1x1v

lz@studer-raimann.ch

Matuschek, Nadia [nadia]

1

32

Meyer, Stefan [smeyer]

7

3

199

414

3x1v

1x3v 3x2v 32x1v

3x1v

Neumann, Fred [fneumann]

Schmid, Fabian [fschmid]

1x2v

Schneider, Stefan [sschneider]

Benjamin Seglias

Studer, Martin [mstuder]

1

26

Niels Theen

1

1

41

27

Tödt, Alexandra [atoedt]

12

11

148

179

1x1v

Vollbach, Guido [gvollbach]

2

1

73

102

1x1v

Weise, Daniel [daniwe4]

Kergomard, Stephan [skergomard]

3

2

79

89

1x1v

* 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 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.4 Open Pull Requests to Discuss

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

  1. PR1614 • Documentation for Repository Pattern: Thank you very much for this proposal. We keep the discussion open on this page and add this topic to the next JF agenda again for final decision.
  2. PR1618 • Proposal/6 0/maintenance srag 2019: Thank you very much for updating the maintenance.md. Can be merged.
  3. PR1619 • GS refactoring: We accept this suggestion and a commit for 5.4.
Postponed:
  • none

2.5 Continuous Integration

Overview on current status and reports from CI-server at http://ci.ilias.de and https://travis-ci.com/ILIAS-eLearning/ILIAS/builds:

  • automated tests: 3625 (+2 passing unit tests on PHP 7.0, PHP 7.1, PHP 7.2 since JF 2019-02-25
    • PHP 7.2 is now added as testing environment for trunk and release_5-4
    •  Please have a look into the skipped and incomplete tests in: Workflow Engine, Test and Assessment
    • Feel free to contact Klees, Richard [rklees] for support!
  • results of dicto architectural tests
    • 6 (net) solved violations since JF 2019-02-25 - Thx folks!
  • Please run unit tests locally before committing.

Travis CI for ILIAS:

  • https://travis-ci.com/ILIAS-eLearning/ILIAS/builds
  • more to come...

Performance monitoring:

  • Pascal updated his test installation to PHP 7.2. Performance tests of trunk are currently not running, esp. the repository. PHP 7.2-related bugs need to be fixed first before continuing performance testing.

3 Publishing 5.4

106 features have been implemented for ILIAS release 5.4, see Release 5.4. They now will be tested together with the existing features of ILIAS 5.4.

A 5.4 release branch has been created at November 19, 2018. Trunk is now set to 6.0 alpha.

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 Development Issues in 5.4

  1. Uploading Images for Presenting Objects in Deck of Cards (Tile View): new suggestion for default backgrounds

    JourFixe, ILIAS [jourfixe]: We highly appreciate the latest suggestion for defining and modifying the background of tiles. Entering a colour code is fine for us. No need for pngs.

  2. Supporting PHP 7.3

    JourFixe, ILIAS [jourfixe]: We highly appreciate this suggestion and decide to support PHP 7.3 with ILIAS 5.4.

3.3 Status of Testing

  • Test installation for ILIAS 5.4 is available at test54.ilias.de.
  • Testing has started at November 02, 2018 and ended officially at  January 31, 2019.
  • Bugfixing should be finished at March 11, 2019
  • Status of test cases compared to last Jour Fixe:
    • Passed: 3717 (94%) → 3807 (97%) ⇒ +90
    • Blocked: 27 (1%) 10 (0%) ⇒ -17
    • Retest: 35 (1%) 29 (1%) ⇒ -6
    • Failed:163 (4%) 95 (2%) ⇒ -68

Components passed with 100%

  1. Badges
  2. Bibliographic List Item
  3. Blog
  4. Booking Tool
  5. Bookmarks
  6. Category and Repository
  7. Certificate
  8. Chat
  9. Cloud Object
  10. Competence Management
  11. Contacts
  12. Content Page
  13. Exercise
  14. File
  15. Forum
  16. Glossary
  17. ILIAS Page Editor
  18. Info Page
  19. Item Groups
  20. Language Handling
  21. Learning History
  22. Learning Module HTML
  23. Learning Module ILIAS - Presentation (1 retest)
  24. Learning Module SCORM 1.2
  25. Maps
  26. MathJax
  27. Mediacast
  28. My Workspace
  29. News
  30. Notes and Comments
  31. Online Help
  32. PDF
  33. Personal Desktop
  34. Personal Profile
  35. Plugin Slots
  36. Poll
  37. Portfolio Template
  38. Rating
  39. SCORM Offline Player
  40. SCORM Online Editor
  41. Study Programme
  42. Survey
  43. Tagging
  44. Terms of Service
  45. Test & Assessment
  46. User Service
  47. Web Access Checker
  48. Web Feeds & RSS
  49. Weblink
  50. Who is online?
  51. Wiki
  52. Workflow Engine

Components with failed and blocked TCs

  1. Administration: 4 failed (-5)
  2. Calendar: 5 failed (-1)
  3. Course Management: 15 failed (-3), 4 blocked, 6 retest
  4. Cron Service: 2 failed (-2)
  5. CSS/Templates: 1 failed (-4)
  6. Data Collection: 1 failed (-1), 1 retest
  7. Export: 14 failed (-4), 4 blocked, 4 retest
  8. Group: 2 failed (-3)
  9. Individual Assessment: 3 failed (+3)
  10. Learning Module ILIAS - Editor: 1 failed | no change since last Jour Fixe
  11. Learning Module SCORM 2004: 2 failed (-12) 
  12. Learning Sequence: 4 failed (-6)
  13. Login, Auth & Registration: 1 failed | no change since last Jour Fixe
  14. LTI: 2 failed (-1), 12 retest
  15. Mail: 1 failed | no change since last Jour Fixe
  16. Media Pools: 2 failed | no change since last Jour Fixe
  17. Metadata: 2 failed (-1)
  18. Organisational Units: 2 failed (-4), 3 retest
  19. Portfolio: 1 failed | no change since last Jour Fixe
  20. Precondition Handling: 6 failed | no change since last Jour Fixe
  21. RBAC: 8 failed | no change since last Jour Fixe
  22. Search: 1 failed | no change since last Jour Fixe
  23. Session: 6 failed (-1)
  24. Setup: 1 failed (-2)
  25. Staff: 1 failed, 1 blocked (-1)
  26. Statistics and LP: 4 failed | no change since last Jour Fixe
  27. WebDAV: 2 failed, 1 blocked | no change since last Jour Fixe

4 Developing ILIAS 6.0

4.1 Developing Issues in 6.0

  1. Required and Supported Software ILIAS 6

    JourFixe, ILIAS [jourfixe]: We highly appreciate this suggestion for the required and supported software for ILIAS 6.0. We invite all developers to discuss these suggestions on the page (see above) until next Jour Fixe. We would like to make a final decision at march 25 and communicate it at the upcoming Jour Fixe.

4.2 Feature Requests for ILIAS 6.0

The following suggestions were made for ILIAS version 6.0 which should be published in March 2020.

  1. Session Registration Notifications : We highly appreciate this suggestion and schedule it for 6.0. We prefer option 2 for the screen "Notification settings in user administration" (change to ID-based input and left empty). In addition to the suggestion above we would like to have a check when saving the form if the entered user name exists and if this user has access (manage members permission) to the related object. If not, an Info message about missing permissions is presented but saving the form is still possible.

  2. Migrate News on Communication » News to Timeline : We highly appreciate this suggestion and schedule the feature for 6.0. Using the new UI Filter would be great if possible.

  3. Navigational Slates «Favourites» and «Tags» : We highly appreciate this suggestion and schedule it for 6.0. At the time being we cannot say how the slates look like and behave. So it might be that there are still changes in the presentation of Favourites or Bookmarks once the slades are available. But for now, the heritage presentation of Bookmarks and Tags can be re-used. Nevertheless, renaming and replacing can be done anyway.

  4. Course and Group Information « Target Group » : We highly appreciate this suggestion and schedule it for 6.0. Please extend this feature to groups, too.

  5. Competence profiles can be assigned to Roles : We highly appreciate this suggestion and schedule it for 6.0. We would like to re-use the known pattern from adding members to a course or role like drawn by Matthias above (incl. search field). This screen is triggered by a button "Add Assignment" on Administration » Competence Management : Profiles. After listing the roles that match to the search term a multi-action "Assign" is displayed and used to finish the assignment of a competence to a role.

  6. Competence profiles can be assigned to OrgUnits : We highly appreciate this suggestion and schedule it for 6.0. Please re-use the pattern to select of roles and org-units that we suggested in Competence profiles can be assigned to Roles. In case a org unit is selected, all sub-nodes of this org unit are included as well. The screen to select positions show all existing positions of all sub-nodes. The list of assigned org units should show the title of the org unit as title and the included positions in Details to ease the management of assignments.

  7. Customisable Main Bar - Icon Upload : We highly appreciate this suggestion and schedule it for 6.0. We prefer option 2 for uploading the image. Please clarify in the Implementation part how the inverted version of the uploaded icon is created / how it could be influenced.

  8. Recommended Content : We highly appreciate this suggestion and schedule it for 6.0. 

  9. Streamlining Blocks as Panels : We highly appreciate this suggestion and schedule the restructuration as described in chap. 2 for ILIAS 6.0. Details about the visual implementation will be discussed with the new UI elements that still need to be finalised and commited.

  10. [[]] :

    • Feature request presented by
    • Length of slot: '

5 Miscellaneous

Mantis 

Schmid, Fabian [fschmid] Proposal to make the field "Reproduction steps" in Mantis a mandatory field. Often we first have to ask for these steps in order to be able to find a mistake at all. We realize that there are also many bugs where this is not necessary, you could simply enter "none" or a comment.

JourFixe, ILIAS [jourfixe]: Postponed to next JF when Fabian is attending the meeting.

Maintainer / Developer

Schmid, Fabian [fschmid] Withdrawal of Benjamin Seglias: Benjamin has left studer + raimann ag. Tickets and responsibilities assigned to him will be distributed to other employees of studer + raimann ag.

Next Jour Fixe dates

  • Monday, March 25, 13:00 - 18:00
  • Monday, April 08, 13:00 - 18:00
  • Wednesday, April 24, 13:00 - 18:00 (changed date due to Eastern)
  • Tuesday, May 07, 13:00 - 18:00
  • Monday, May 20, 13:00 - 18:00

Layout Revision 6.0 working group

Virtual Meeting every Friday, 11:00 - 12:00

  • Weekly Meeting that deals with the project management of the General Layout and Menu Revision. Due to the complexity of the project, we coordinate the next steps and define responsibilities. If you want to stay in contact and get information about the project, feel free to join the Working Group and attend our VC.


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

Last edited: 19. Apr 2023, 12:29, Kunkel, Matthias [mkunkel]