Show Advanced KnowledgeHide Advanced Knowledge

JourFixe-2017-01-30

Date and place

Monday, January 30, 2017 from 12:30 – 17:40 at ILIAS-Verein office in Köln

Time	Topic	Speaker
12:30 - 13:15	1. Appointments 2. Maintained Versions	Kunkel
13:15 - 14:00	3. Kitchen Sink	Amstutz
14:10 - 15:00	4. Publishing ILIAS 5.2	Kunkel
15:00 - 17:15	5. Developing 5.3
17:15 - 17:30	6. Miscellaneous	Kunkel

Participants

At ILIAS office in Cologne:

• Alexander Killing, Michael Jansen, Stefan Meyer, Colin Kiegel, Matthias Kunkel (Minutes)

Participating via Skype:

• Timon Amstutz, Fabian Schmid, Björn Heyser

If you like to participate at the Jour Fixe via Skype (audio) please contact Amstutz, Timon [amstutz] to get invited to call. His Skype-Username is timon.amstutz!

1 Appointments

• January 31, 2017: Virtual workshop 'Multilinguality for all object types' | more
• February 02, 2017: Face2face workshop 'Page Editor' | more
• February 03, 2017: Virtual workshop 'Introduction of Task Manager' | more
• February 07, 2017: Release date 5.2.0
• February 10, 2017: Virtual workshop 'Reminder Service' | more
• March 09, 2017: 27^th Development Conference, Aachen
• March 31, 2017: Feature Freeze ILIAS 5.3

2 Maintained Versions

2.1 Roadmap

Last releases:

• ILIAS 5.2.0 beta 4 published at November 30, 2016
• ILIAS 5.1.14 published at January 25, 2017
• ILIAS 5.0.18 published at January 25, 2017

Next releases:

• ILIAS 5.2.0 (stable) scheduled for February 07, 2017
• ILIAS 5.1.15 not scheduled yet
• ILIAS 5.0.19 not scheduled yet

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. #20124: Cannot load badges: Please deactivate the backpack service within Badges to avoid additional Mantis bug reports. If a new authentication service is available we would like to discuss a possible solution in the Jour Fixe.
2. #20100: Suchfunktion in Wiki: Zurück-Funktion des Browsers nach Auswahl eines Suchergebnisses nicht möglich: We had a longer discussion of this problem and see a general need to clarify the use of GET and POST parameters in general. But changing the current behaviour needs a clear concept and a certain effort. This cannot be done as a bug fix. The Technical Board will discuss this problem and try to work out a general solution for current versions.
3. #19210: Failed test: Lösungsvergleich 2 - Variant 2 doesn’t work: Please discuss this conceptual problem with the heads of SIG E-Assessment and give us a feedback about the preferred solution.

Postponed

1. #19159: Problems copying file whose description contains "|": We postpone this report to the next JF to give Alex some time for investigation.

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

Responsible Maintainer	Open bugs without feedback	Last JF	Priority bugs and votes *	Last JF
Amstutz, Timon	0	0
Arsenij, Anton	1	1
Becker, Max	7	8
Braun, Jean-Luc	0	0
Heyser, Björn	79 (-14)	93	1x2v, 6x1v	1x2v, 8x1v
Jansen, Michael	0	0
Killing, Alexander	16 (-7)	23		2x1v
Klees, Richard	1	1
Kohnle, Uwe	15 (+15)	0
Kunkel, Matthias	3	0
Langkau, Thomas	1	1
López Reyes, Jesús	1	1
Meyer, Stefan	0	1	9x1v	1x2v, 9x1v
Neumann, Fred	0	0
Schmid, Fabian	0	2
Studer, Martin	0	0
Tödt, Alexandra	1	0
Truffer, Oskar	0	0
Vollbach, Guido	0	0
Winiker, Stephan	0	1

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

1. none

Postponed to next Jour Fixe:

1. none

2.5 Continuous Integration

2.5.1 Overview

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

• automated tests: 1558 (+2!) passing unit tests on PHP 5.5, PHP 5.6, PHP 7.0, PHP 7.1 und hhvm
• dicto architectural tests
• Performance monitoring: see below

2.5.2 Performance Monitoring Report

Performance Monitoring at ci.ilias.de (Login: Guest) shows two artefacts in roughly the last quarter (2016-10-24..2017-01-16). It would be interesting to know whether this is related to a code change or something spurious changed the state of the test setup. You can click on the commit ranges to inspect all relevant commits at github.

First Artefact
2016-11-20..2016-11-22, commit range: 318ab35f980709fa07bc..aa12133fdd621d3ddcc8

• Get Repository: 10% drop from 615 ±8 to 555 ±15 ms
• Manage Repository: 13% drop from 6649 ±121 to 5789 ±84 ms
• Get Selected Items: temporary 12% drop from 391 ±11 to 342 ±10

Second Artefact
2016-12-08..2016-12-10, commit range: 13959e1692bff890d6a0..6dfd5e4aa08bb01c611c

• Login: 23% drop from 904 ±19 to 699 ±16 ms
• Get Selected Items: 342 ±10 regression back to 394 ±15 ms

Note:

• It is a lot of manual work to create these kind of summaries. So I will not be able to do that regularly. However, I may give some hand-wavy qualitative summaries more often.
• Each data point is an average value of 15 individual measurements after 10 warm-up testruns to minimize effects of invalidated bytecode caches after code changes, etc.
• These are the measurements from the PHP testsuite, since it is more popular than HHVM.

3 Kitchen Sink

• none

Postponed:

1. none

4 Publishing ILIAS 5.2

4.1 Status of 5.2 Development

The following 94 features are part of 5.2:

4.2 Updating Policy

• We decided that updating to ILIAS 5.2 requires an installation based on ILIAS 4.4 or higher. Straight update from 4.3 to 5.2 will not be supported. For installations using 4.3 or lower it is necessary to update first to 4.4, 5.0 or 5.1 before finally updating to 5.2.
• When updating from 4.4 or 5.0 to 5.2, this has to be done on a PHP 5.5 system first before updating the server to PHP 7.

4.3 Development Issues 5.2

Notice for developers: please add all suggestions for changed defaults to page Default Database Template Settings for 5.2 !

Development issues to be discussed / to be decided upon:

Identifying unused language variables for 5.2.0 (stable)

• We won't remove unused lang vars for 5.2.0 but make it easier to identify them.
• All maintainer had the chance to check the English lang file until January 30, 2017 and to remove the deprecated info from the lang var in ilias_en.lang in case of a false positive.
• A new script will add the deprecated info to other language files per script. This information will avoid that language maintainer translate unused lang vars.
• All deprecated marked lang vars will be removed in the trunk after building the 5.2 branch and opening of trunk for development. Accidently removed lang vars will be collected and added later by script again. A final removal of these deprecated lang vars will be done with 5.3.

4.4 Testing 5.2

• The test52 installation using PHP 7 is available at: www.ilias.de/test52. This installation does not contain any plugins.
• A test installation with the same database and content running under PHP 5.5 is available at http://php5.ilias.de/test52.
• A test installation for plugins is offered at http://www.ilias.de/test52/goto.php?target=root_1&client_id=plugins52

4.5 Information about implementation in Feature Wiki

Among the new features for ILIAS 5.2, the following 2 feature pages still have no information about how the feature is implemented. Please add / complete the missing information to avoid misunderstandings on the feature's new or changed functionality:

• Features under maintenance of Heyser, Björn [bheyser]
  1. http://www.ilias.de/docu/goto.php?target=wiki_1357_Create_New%C2%A0Pools_from_Random_Tests_having_Lost_Pools#ilPageTocA18
  2. http://www.ilias.de/docu/goto.php?target=wiki_1357_Export_and_Import_Questions_with_Competencies#ilPageTocA116

4.6 Release Date

Even if more than 96% of test cases are already set to passed, we are still a step away from a 98% passed quote. Especially the failed test cases above should be fixed first before a stable release can be published. According to the maintainer of the T&A additional time is necessary to fix theses bugs. The release date January 18, 2017 cannot be hold. New release date is now February 07, 2017. We apologize for any inconvenience.

5 Developing 5.3

5.1 Feature Requests Scheduled for Former Version

The following feature requests have already been discussed in the past and scheduled for a former ILIAS major release:

• none

5.2 New Feature Requests to be Discussed

Suggestions for Jour Fixe Agenda : The following features suggested for 5.3 have been applied for being discussed at the Jour Fixe (see procedure documented in ILIAS community FAQ).

Slot 1 : 30'

Feature presented by Jansen, Michael [mjansen]

• Second email address for user accounts: We appreciate the feature request and schedule it for 5.3. We prefer the label 'Second E-Mail Address' and we would like to have a modified settings screen where the dropdown 'Incoming Mail' is changed to a radio group with sub-options for 'local and forwarding' and 'to external mail...'. This sub-option allows to specify to which mail address a mail is sent.

Slot 2 : 15'

Presented by Klees, Richard [rklees]

• Fileupload in participant record: Feature is highly appreciated and scheduled for 5.3. We would like to have the setting 'File is accessible for participant' on the IA's setting screen as a general setting for each IA (and not for each participant). Same with 'Notify...' on the same screen.

Slot 3 : 15'

Presented by Klees, Richard [rklees]

• Place and time when IA was held: Highly appreciated and scheduled for 5.3.

Slot 4 : 15'

Presented by Klees, Richard [rklees]

• Allow superiors of participants to enter and view results: We have a similar requirement for courses and other object types and need a general roadmap how to integrate org units as an additional dimension in the access control of user groups in objects. If we have a common approach for this scenario we can implement this for all related object types and decide again about this suggestion.

Slot 5 : 15'

Feature request presented by Klees, Richard [rklees]

• New Permission: Amend Finalized Records: We appreciate this feature request and schedule it for 5.3. We would like to call this permission "Amend grading". It should not be given to owner of the object. An additional column in 'Participants' screen should offer name and date in case a record has been changed after finalisation.

Slot 6 : 15'

Feature request presented by Tödt, Alexandra [atoedt]

• Printable Member List for Members : We highly appreciate this suggestion and schedule it for 5.3.

Slot 7 : 30'

Feature request presented by Tödt, Alexandra [atoedt]

• Explaining the Purpose of the Personal Profile : Highly appreciated and scheduled for 5.3. We would like to show the explanation text as info message (blue background) without formatting. We don't want the Tiny but re-use the existing form for multilingual category titles (according to Alexander's suggestion above).

Slot 8 : 15'

Feature request presented by Amstutz, Timon [amstutz]

• Custom Metadata: Field Type Link : We highly appreciate the feature request and schedule it for 5.3. Search engine will only search the description of objects linked with internal links.

5.2.1 Additional suggestions

The following suggestions have already been added to the 'Suggestions for Jour Fixe Agenda' data collection. But the maintainer has to checked the suggestion before agenda deadline. If the maintainer agrees with the suggestion and is present in Jour Fixe, the request can be discussed and scheduled.

• none
  
  

5.3 Status of ILIAS 5.3 development and open suggestions

6 Miscellaneous

6.1 Feedback on Meeting Today

• Michael: We had some problems with our countdown...
• Alexandra: We discussed two important cross-sectional features: (1) grading and (2) handling of org units and objects permissions within objects. We need to push both topics to get sound solutions for both features. Alexandra will go on with the grading feature ...
• Matthias: I take over the initiative to work out a concept for org units and RBAC for 5.3.
• Timon: Thanks for the flexible time management so we had enough time to discuss these topics.
• Fabian: Would like to contribute to the org unit discussion and push decisions.
• Colin: Discussion of feature 'Allow superiors of participants to enter and view results' was controversial in Jour Fixe but without prior comments in the wiki. We should all take the time to comment in advance to give the presenter a chance for being prepared in the JF.

6.2 Next Jour Fixe

Monday, February 13, 2017, from 12h30 until 17:30 at the office of ILIAS-Verein in Cologne.

---