Feature Wiki

Information about planned and released features

Tabs

Page is read-only.

JourFixe-2019-09-09

Date and place

Monday, September 09, 2019 from 13:0015:00 at ILIAS-Verein office

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

  • none

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.5 published at August 29, 2019
  • ILIAS 5.3.17 published at August 15, 2019
Next releases:
  • ILIAS 6.0_beta1 scheduled for October 31, 2019
  • ILIAS 5.4.6 scheduled for October 2019
  • ILIAS 5.3.18 scheduled for October 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. #24272: Portfolio List: Property Name/Values suffer from lots of space: We accept Timon's latest solution and ask him to implement this modification of the UI element accordingly.
  2. #25903: Displaying the properties of an object causes the tile view to look broken.: PM will check possible options to reduce or to get rid of some properites shown below the tile. Will be presented at next JF.
  3. #25919: Order number in the settings tab of a competence is difficult to understand without context : We follow the suggestion to remove the order input on the settings screen to get this screen compliant with other similar screens and to support sorting only on dedicated sorting screens.
Postponed due to absence of maintainer:

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:

User

Open Bugs Without Feedback

Last JF

ø Age in Days

Last JF

New Votes*

Old Votes**

Resolved or Closed***

Amstutz, Timon [amstutz]

Becker, Maximilian [mbecker]

6

6

370

356

1x2v 2x1v

Braun, Jean-Luc [braun]

4

5

116

108

1x2v 1x1v

Hecken, Stefan [shecken]

Heyser, Björn [bheyser]

70

66

133

125

3x1v

1x2v 38x1v

1x1v

Jansen, Michael [mjansen]

2

2

140

126

Thomas Joussen

2

2

335

321

Killing, Alexander [alex]

13

9

41

34

12x1v

Klees, Richard [rklees]

2x1v

Kohnle, Uwe [ukohnle]

1

45

2x1v

1x1v

Kunkel, Matthias [mkunkel]

Langkau, Thomas [langkau]

3

3

309

295

3

2

205

279

1x1v

lz@studer-raimann.ch

1x1v

Ahmad, Nadia [nadia]

1

62

Meyer, Stefan [smeyer]

5

14

449

190

2x3v 3x2v 34x1v

1x1v

Neumann, Fred [fneumann]

Schmid, Fabian [fschmid]

15

11

62

61

1x5v 2x1v

Schneider, Stefan [sschneider]

Studer, Martin [mstuder]

6

6

53

39

2

2

166

152

Tödt, Alexandra [atoedt]

13

12

228

231

1x1v

4

4

55

48

Vollbach, Guido [gvollbach]

1

1

61

47

1x1v

Weise, Daniel [daniwe4]

Kergomard, Stephan [skergomard]

Wolf, Fabian [fwolf]

* 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. PR1969 • Documentation for “Secure ILIAS” : We highly appreciate this PR and accept the document for trunk. Please merge accordingly.
  2. PR2110 • Changed version number pattern for ILIAS 6 and ff. : We highly appreciate this PR and accept it for trunk. Please merge accordingly.
  3. PR2145 • Introduce PSR-4 namespace for Tests : We highly appreciate this PR and accept it for trunk. Please merge accordingly.
Postponed to next Jour Fixe:

2.5 Guidelines

The following guideline has implecitely been accepted with 5.1 when the related feature requested Uninstall Plugins has been scheduled. Unfortunately, no guideline page has been created for it. This has happened in the meantime:

  • Deletion of plugins and related data : Guideline is to enter into force retroactively.
    • Jour Fixe: Deinstallation of plugins has been introduced with ILIAS 5.1. But the according guideline has never been accepted. This has been done today. Guideline is effective from ILIAS 6.

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

2.7 Performance monitoring:

  • There is currently no performance data available due to the trunk branch being broken. Performance monitoring will resume as soon as the trunk is fixed.

3 Developing ILIAS 6

3.1 Developing Issues in 6

  1. Tödt, Alexandra [atoedt] 2019-08-30: Description for Competences and Competence Categories did not deal with Competence Templates. Competence Templates can be referenced. Referenced Competence stay perfectly the same as the Comeptence Template besides their very title. 
    Now we introduced the description it is disputed whether the description ought to be fixed or editable. 

    JourFixe, ILIAS [jourfixe]: In addition to the accepted feature request we have decided that description texts of competence templates cannot be changed. This should guarantee consistency of description texts. If similar competencies should have different description texts, copies of compentencies should be made.

  2. CSS Maintainership and Processes: the current model for the CSS maintainership is not working well for the maintainer Jean-Luc Braun and therefore needs some modifications to keep Jean-Luc as team member. The following suggestions have been discussed between maintainer, UI KS coordinators and product manager. They suggest to …:

    1. give up the Mantis category "CSS / Templates" : Jean-Luc gets a lot of reports for bugs he cannot fix as they are related to the implementation itself and need changes made by the responsible component maintainer. In the future, only developers should assign reports to Jean-Luc to ask him for fixing CSS or HTML issues or to ask him for advice. The chosen category is the one for the component in which the issue has happened.
    2. check all CSS taged reports in Mantis and to assign them to the right maintainer or close them : At the time being, there are almost 100 reports (from 'open' to 'fixing …') assigned to Jean-Luc. The vast majority of them has been assigned to JL due to the chosen category 'CSS / Templates'. Some of them cannot be reproduced any more or belong to no longer maintained versions, and can therefore be closed. Others can easily be assigned to the responsible component maintainer.
    3. to give up delos.css and delos.less on the long run and to block commits to delos.less with 6.0 and to allow only imports : …
    4. to add two new metrics to the CI 'Lines of LESS outside KS' and 'Lines of templates outside KS' and to monitor them on the Jour Fixe : …
    Additionally, Richard and Timon will work out a project plan for a 'Transition of CSS to UI Framework' for ILIAS 7.

    JourFixe, ILIAS [jourfixe] : We highly appreciate this suggestion and implement the proposed changes as described above.

3.2 Feature Requests for ILIAS 6

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

  • None

POSTPONED TO NEXT JOUR FIXE

4 Miscellaneous

ILIAS Development Conference

Like in spring we are offering again a data collection to collect suggestions for the programme of the next ILIAS Development Conference in Dresden (September 2019). At this DevConf we will address topics for the development of the next ILIAS 7 (2021). Please add your suggestions for presentations, workshops or hands-on-tutorials here!

Maintenance.md

  • Entries in the current version of the maintenance.md are always listing a second maintainership which in most cases has the value "MISSING". I would like to suggest to use "MISSING" only in case a person is really needed for a position, e.g. as tester. It is not required that components have a second maintainership. There should not be made an entry for second maintainership in case it is vacant.
  • There are some services listed at the bottom of the maintenance.md that have no maintainer. I guess this list is not correct:
    • Services/AssessmentQuestion
    • Services/DiskQuota
    • Services/Like
    • Services/Membership
    • Services/OpenIdConnect
    • Services/PHPUnit
    • Services/QTI
    • Services/Randomization

Jour Fixe: To update maintenance.md it is necessary that maintainer do not only changes in the related maintenance.json but also to run the related script in the ILIAS maintenance tools. Otherwise, the maintenance.md won't be changed. We ask all maintainer to act accordingly. In case of  questions, please contact Jansen, Michael [mjansen]

Mantis

Schmid, Fabian [fschmid]: Status of "Reproduction steps" in Mantis a mandatory field:
https://docu.ilias.de/goto.php?target=wiki_1357_JourFixe-2019-03-25#ilPageTocA1211

Kunkel, Matthias [mkunkel] : Fabian Wolf will modify Mantis to make "Required Steps" a mandatory field and to allow adding this information already in Testrail.

Jansen, Michael [mjansen] : Mantis will be extended by two new fields for the CVE number and the severity quota.

PSR2 in UI Framework

We will shift to PSR2 in the UI Framework by Sept. 9. Make sure that any branches are merged untill this date. We try our best to feedback and merge any open PR untill this date as well. If any Dev. needs more time, let us know as soon as possible.

JourFixe, ILIAS [jourfixe] : There are no objections to introduce PSR-2 in UI framework. Merge can be done this week.

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.

Next Jour Fixe dates

  • Monday, September 23, 13:00 - 18:00
  • Monday, October 07, 13:00 - 18:00
  • Monday, October 21, 13:00 - 18:00
  • Monday, November 04, 13:00 - 18:00
  • Monday, November 18, 13:00 - 18:00
  • Monday, December 02, 13:00 - 18:00
  • Monday, December 16, 13:00 - 18:00


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

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