JourFixe-2020-02-03

Date and place

Monday, February 03, 2020 from 13:00 – 17:20 at the office of ILIAS-Verein and as VC meeting

If you like to participate at the Jour Fixe, please join our DFN VC meeting! Due to technical problems, Skype is no longer used for our VC!

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

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:

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:

* 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

2.5 Continuous Integration

2.6 Performance monitoring:

3 Publishing ILIAS 6

3.1 Status of Testing

The official test installation for ILIAS version 6 is at https://test6.ilias.de.
 
All test suites to test ILIAS 6 are available in our Testrail installation. Please contact our test manager Kruse, Fabian [Fabian] if you want to join our testing team.
 
Testing of ILIAS 6 has started at 09 DEC 2019. All test cases have to be executed once until 28 FEB 2020. Retesting and bugfixing has to be completed at 08 APR 2020 at the latest.

3.2 Development Issues

Development issues and topics related to ILIAS versions 6

1. none

   JourFixe, ILIAS [jourfixe]:

4 Developing ILIAS 7

4.1 Presenting Large Developments for 7

Initiated by the SIG Client, the Technical Board decided to organise a yearly development planning meeting for the ILIAS version to be developed in the future months. For ILIAS 7, this meeting will take place at the Jour Fixe at February 17, 2020. In the future, these meetings will take place straight after the start of the beta phase of the former version (usually in November).

You will find more information about the intention and rules for this meeting in the Community FAQ, chap 4.10. All presented projects shall be shortly described in advance in the following data collection 'Large Developments for ILIAS'.

4.2 Development Issues

Development issues and topics related to ILIAS versions 7

1. none

   JourFixe, ILIAS [jourfixe]:

4.3 Suggested Features

1. Editable page area for competence profiles : We highly appreciate this suggestion and accept the feature request for 7. Please use the label "Preview" instead of "Content" in the administration view. Support of different content styles is very good to distinguish these pages from those in other parts of ILIAS.

2. Storing Specific Values for Competence Levels : We still like this suggestion and re-schedule this feature for 7. This feature has no impact on the user interface. ILIAS only stores the results and make them available for external re-use. In addition, we ask for a streamlining of the threshold handling (currently different in survey and test). It does not make sense to have a percentage threshold that goes over 100 (see also Mantis 22458).

3. Competences and competence profiles get tab «Assigned Objects» : We still like this suggestion and re-schedule this feature for 7 (incl. requested changes by last JF comment).

4. Local Competence Profiles for Courses and Groups : We still like this suggestion and re-schedule this feature for 7. Feature should support courses as well as groups (as groups are already tackled by the competence management).

5. Assign Competence Profiles to Courses and Groups : We still like this suggestion and re-schedule this feature for 7. Feature should support courses as well as groups (as groups are already tackled by the competence management).

6. New tab ‘Media‘ and revised tab ‘Questions‘ : Thanks for updating the mockups according to the last JF comments. We still like this suggestion and reschedule the feature for 7. Please consider if the presentation table could be a better way to visualise this information and make them available for mobile divices.

7. Sumscores per Participant : We prefer to move the setting for Sum Score from the question to the survey as it is always related to a specific survey and not a question in general. The presentation of sum scores should be sortable by sum scores as well. Please present request again after having considered the above mentioned suggestion.

8. Custom (User Defined) Booking Data : We highly appreciate this suggestion and schedule the feature for 7. Offering only one metadata set for reservations would need a bigger change in the custom metatdata service and introduce a single exeption. Therefore we reject this suggestion by Matthias. Changing the confirmation screen to modals needs also a lot of additional work due to the complexity of these screens. So modals are rejected as well. Creating and editing the metadata for reservation should be moved to the Metadata tab.

9. Add New Item to Item Group from Action Menu : We had a longer discussion about the different options and preferred workflows of adding / creating / embedding objects and ask for an extra round to clarify the problems and find solutions before scheduling this feature. Timon is interested to support this refinement.

10. Allow to create introductory text in Item Group : We highly appreciate this suggestion and schedule the feature for 7. Ressource lists / item lists should not be added to the new content block of an item list (to prevent another level of cascading). We recommend to wait with the implementation of this feature some weeks until have a clearer view of what similar processes might be tackled by the planned page editor revision.

11. Add New Item Group in ILIAS Page Editor : We highly appreciate this suggestion and schedule the feature for 7. We would like to follow Matthias' suggestion and make "Existing Item Group" as default option (placed on top) and use "Create New Item Group" as alternative default in case no item group exists in the container. Option "All Items of Type" would become last of the list.

Postponed to next Jour Fixe

5 Miscellaneous

Next Jour Fixe dates