Feature Wiki

Information about planned and released features

Tabs

Information Message
Page is read-only.

JourFixe-2018-08-27

Page Overview

[Hide]

Date and place

Monday, August 27, 2018 from 13:00 – 18:00 at ILIAS-Verein office in Köln

Time

Topic

13:00 - 14:50

1. Appointments
2. Maintained Versions

15:00 - 17:30

3. Developing 5.4

17:30 - 18:00

4. Miscellaneous

Participants

At ILIAS office:Participated via VC:

If you like to participate at the Jour Fixe via Skype, please join our Skype meeting!

1 Appointments

  • 19 SEP 2018, 09:00 - 16:00: "Workshop Workflow Engine" at University of Cologne | this is a introduction on how to use the Workflow Engine | main target group are developers | maximum number of participants is 8 | Please contact Klees, Richard [rklees] if you want to participate!

2 Maintained Versions

2.1 Roadmap

Last releases:
  • ILIAS 5.3.7 published at July 25, 2018
  • ILIAS 5.2.18 published at August 08, 2018
  • ILIAS 5.1.28 published at August 01, 2018 – this is the last maintained release for 5.1!
Next releases:
  • ILIAS 5.3.8 scheduled for end of August 29, 2018
  • ILIAS 5.2.19 scheduled for September 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:

  1. #20524: No neutral (gender-unspecific) salutation possible : We need at least changing five components to tackle thsi problem. This is far too much for a bug fix. Therefore, we close this report. But we accept this as a feature request for 5.4. Matthias will prepare the feature request and Michael will check the amount of work for this request.
  2. #22572: The same icon is used for Determines Learning Progress and the status Failed of the learning progress. : We prefer not to use the glyicon_ok but the glyphicon-ok-circle to distinguish it from the UI Apply Glyph. We agree that not assigned or not displayed items do no longer show an icon but have an empty cell in the column. We prefer to use the column titles "Is Displayed" and "Is Assigned" instead of "Status" or "Assignments". Matthias will try to create a PR for the new UI element. Report is first assigned to Stefan for LP and session and then to Alexander for component item group.
  3. #23358: Interpretation von URL und Mailadresse in der Visitenkarte : URLs and mail addresses on the Vcard were never rendered as links. Therefore, we do not consider this being a bug. Nevertheless, the request is okay and we recommend to create a related Feature Request. But we need also to consider the handling of other appearances of mail addresses and URLs in the system, e.g. in description texts.
  4. #23364: Custom-Icon unter Chrome (Win) nicht verfügbar : We do not consider this being an ILIAS bug. We cannot add an SVG parser to ILIAS only to prevent that svg images created by programmes that use other mime type descriptions still work in ILIAS. And the way Alexander mentioned above to just change img->image is an easy way to solve this problem (if Oliver does not want to change the programme for svg creation).
  5. #23442: Fehler Disk-Quota-Bericht "Cannot access protected property ilTableGUI::$tpl" und #23449: Fehler Disk-Quota-Bericht block"tbl_header_title_icon' : Both bugs do not need to be fixed. We have to decided to abandon the disk quota in the repository with 5.4 (see JF 11 SEP 2017). Nevertheless, Alexander will have a look which classes he might need for the disk quota implementation in Services /Workspace and move them there. After that, Fabian will remove the rest of the code for the disk quota to abandon this feature with 5.4.
  6. #23464: On mobile screens: Hamburger menu overlaps Profile menu : Hello Jean-Luc, can you please have a look at this problem and give us a feedback if this can be solved somehow? Thanks!
  7. #23465: correction-mode overlaps ilias-page : Assigned to Björn Heyser, but won't be fixed for 5.3.
  8. #23472: swichting to preview mode for questions : We do not consider this being a bug. This is the default behaviour from the very beginning of ILIAS and it works as expected - even if it might not be satisfying. For the future we should tackle this problem for ILIAS in general. But this requires a dedicated feature request and cannot be part of a bug fix for the T&A component.
  9. #23473: No stable link to user agreement : We accept the introduction of a permalink for the user agreement page as bugfix for 5.3 (5.2 not possible due to missing permalink implementation). The link should be shown to logged in and anoymous users in the profile. It always show the current user agreement (not the last accepted one by a user).
Postponed :
  • none

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]

2

32

1x1v

Becker, Maximilian [mbecker]

6

134

1x2v

Braun, Jean-Luc [braun]

3

2

42

35

1x1v

Hecken, Stefan [shecken]

Heyser, Björn [bheyser]

11

6

38

33

2x1v

23x1v

1x1v

Jansen, Michael [mjansen]

Thomas Joussen

1

1

80

66

Killing, Alexander [alex]

37

27

46

41

1x1v

1x2v 3x1v

Klees, Richard [rklees]

1x1v

Kohnle, Uwe [ukohnle]

14

13

100

92

2x1v

Kunkel, Matthias [mkunkel]

6

4

183

248

1x1v

Ahmad, Nadia [nadia]

Meyer, Stefan [smeyer]

9

7

144

163

1x2v 2x1v

1x3v 2x2v 19x1v

Neumann, Fred [fneumann]

1

1

53

39

1x1v

Schmid, Fabian [fschmid]

1x2v

Schneider, Stefan [sschneider]

Benjamin Seglias

1x2v 1x1v

Vollbach, Guido [gvollbach]

Weise, Daniel [daniwe4]

Kergomard, Stephan [skergomard]

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. PR1109 •  UI: better encapsulation, tests and some cleanup for Triggerer-trait : Richard notified the JF about a change in the public interface.
  2. PR1133 • UI, Radio Input : We highly appreciate this PR and accept it for 5.4.
  3. PR1136 • UI - MultiSelect Input : We highly appreciate this PR and accept it for 5.4.
  4. PR1146 • Feature/5 4/main menu services interface : We highly appreciate the PR and accept it for 5.4 with the following exchanges:
    • The service should be named "GlobalScreen" instead of "UX".
    • We prefer an alternative label to "Widget" and suggest to extend the "entry" term to different types, e.g. "link entry", "complex entry" (for the "Widget") a.s.o.
    • The GlobalScreen should handle the separators and avoid that a separator follows a former one and that there are no leading and closing separators.
  5. PR1152 • UI Dropdown: Added description and rule for empty dropdowns : Timon changed the rules according to the JF decision for PR1078.
Postponed
  • none

2.5 Continuous Integration

Overview on current status and reports from CI-server at http://ci.ilias.de:

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 ILIAS 5.4 and their status this morning:

Status

Today

Last JF

Diff

A - in trunk

8

8

0

B - approved / committed soon

0

0

0

C - waiting for approval

10

9

+1

D - in development

7

7

0

E - contract settled

20

18

+2

F - option or agreement for funding

52

47

+5

G - partly funded

0

0

0

H - funding needed

14

16

-2

Candidates for abandoned features

3

3

0

Abandoned features

1

1

0

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

  • Responsive Table Filters (Proposal from leifos, 2018-08-27): We discussed Thomas' suggestions and made the following decisions:
    1. First appearance of the Filter : we prefer option 2. Each component should decide about default filters
    2. Role of Reset Glyph : we only want one Glyph to return to initial state (description in FR should adapted accordingdly to clarify that this reset does not go back to the last personal filter setting but to the initial state of the component. Additionally, we should try to find another glyph that shows an arrow counter-clockwise. And if technically possible and implementable with reasonable resources, we would like to have a reset glyph greyed-out when no personal changes compared to the initial state has been made (but this should not be a show-stopper).
    3. Glyph + Text : We prefer bulky buttons with a leading glyph followed by text. There is no majority for abandoning the text labels and just to rely on glyphs.
    4. Width of Filter Item Labels : We prefer solution 1.
    5. Improved Workflow for adding Filter Items : We accept Thomas' suggestion of a reduced workflow (one step less).

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):

  1. Customisable Main Menu :
    We discussed Fabian's questions:
    • Shall Entries be able to be deleted or not? Main menu entries provided by the system (like 'Overview' or 'Repository') should only be deactivated but not deleted. This means that each on these entries can only appear once (but nevertheless a second entry to such a target can be made by adding a link).
    • We discussed if the administration interface should use technical terms (like "slate") or common terms (like "main menu entry" and "main menu sub-entry") but postponed this discussion to the feature page.

    postponed to next jour fixe due to missing time

  2. Page Layout Revision (Desktop) : …
  3. Page Layout Revision (Mobile) : …
  4. Display Repository Root and Categories in Usage Intensity : …
  5. Calendar Selection - Make link target clear : …

4 Miscellaneous

Support of Feature Workshops
  • A new group Feature Workshops has been created at https://www.ilias.de/docu/goto_docu_grp_6768.html.
  • Group is accessible for everybody with an account at ilias.de.
  • Every workshop is represented by a session and can have an Etherpad or any other ILIAS tool to support the workshop.
  • Group members get a calendar entry for all workshop dates.
  • Development projects with a lot of workshops (like Page Layout Revision) can have separate groups.
  • Entries in 'Appointments' list of JF agenda should link to session (a no longer to DC entry).

BrowserStack (Schmid, Fabian [fschmid]): Should we register with BrowserStack as an open source project? With BrowserStack, websites can be viewed in hundreds of browser versions to identify browser-specific differences, which can often simplify the work with UI-related bugs. BrowserStack requires OpenSource projects to link their logo on the Github page (I would ask them if ilias.de would suffice, similar to TestRail etc.).

We would like to thank Fabian for this suggestion and support a related request. BrowserStack could be used by developers to check the ILIAS presentation bugs on operation systems or browser that are not available for the developer. But this tool should not force us to fix every browser bug in the future. Fabian will contact the providing company for the next steps.

Next Jour Fixe dates

  • Monday, September 10, 2018, 13:00 - 18:00
  • Monday, September 24, 2018, 13:00 - 18:00
  • Monday, October 08, 2018, 13:00 - 18:00
[1] Bug reports counted only for core project, not for plugins

Last edited: 17. Apr 2025, 14:39, Kunkel, Matthias [mkunkel]