Feature Wiki
Onglets
JourFixe-2022-05-02
Aperçu de Page
[Masquer]Date and place
Monday, 02 May 2022 from 13:00 - 17:05 at VC meeting in BBB.
If you like to participate at the Jour Fixe, please join our BigBlueButton-based Jour Fixe VC!
We recommend to use BBB in Chrome (or Firefox).
Participant | Joined VC |
---|---|
X | |
X | |
X | |
X | |
X | |
X | |
X | |
X | |
Haas, Ramona | |
X | |
X | |
X | |
X | |
X | |
Kunkel, Matthias [mkunkel] (Minutes) | X |
X | |
X | |
X | |
Robbenhaar, Clemens | |
X | |
X | |
X | |
X | |
X | |
X | |
X | |
X | |
X | |
X | |
X | |
1 Appointments
Workshops / Working GroupS
- 05 MAY 2022, 10:00 - 12:00: Workshop 'Clipping LOM Metadata to fit Forms'
- 11 MAY 2022, 13:00 - 14:00: Bi-Weekly of WG PHP 8
- 19 MAY 2022, 14:00 - 15:00: Workshop 'Didactic Templates'
- 20 MAY 2022, 10:15 - 12:00: Workshop 'Suppressing Chapters if Functionality is deactivated'
- 06 JUN 2022, 10:15 - 12:15: Workshop 'Improve Search in Help'
- 20 JUN 2022, 14:00 - 15:30: Workshop 'CalDav for Calendar'
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!
UPCOMING Jour FixeS
- Monday, May 16, 13:00 - 18:00
- No Jour Fixe at 30 MAY 2022 due to Learntec!
- Monday, June 13, 13:00 - 18:00
- Monday, June 27, 13:00 - 18:00
Call for Papers ILIAS Conference 2022
Call for Papers is open until 15 MAY 2022. Please submit your suggestions for a presentation or workshop in the related data collections on the conference page.
2 Miscellaneous
2.1 Tool for an Open ILIAS Workspace
Discord has been selected as tool for an Open ILIAS Workspace. The ILIAS channel of Discord is here: https://discord.gg/H9v2v2Ar2T. Feel free to join.
2.2 UI Clinic
Our UI/UX/A11y experts Yvonne Seiler and Kristina Auerswald are offering bi-weekly UI clinic consultation hours for UI/UX and accessibility topics. The consultation hours are open for all users that need or are interested in related help for their ILIAS development activities. The UI Clinic consultation hours take place every Tuesday before Jour Fixe from 14h30 to 15h00. If you are interested in discussing an issue, please register here!
2.3 Maintainerships
The following maintainerships will change or are offered for takeover by another developer:
- User Service: Stefan Meyer would like to hand over maintainership of the component
Services/User
to an interested developer in the nearer future.- Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.
- Object Service: Alexander Killing has removed his implicit maintainership for
Services/Object
.- Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.
- Administration: Alexander Killing and Stefan Meyer (2nd maintainer) would like to hand over maintainership of
Services/Administration
to an interested developer. Code is in good state and the service ready to be used with PHP 8.- Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.
- RBAC: Stefan Meyer would like to hand over the maintainership for
/Services/AccessControl
to an interested developer in the nearer future.- Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.
- Tree: Stefan Meyer would like to hand over the maintainership for
/Services/Tree
to an interested developer in the nearer future.- Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.
- SOAP & Web Services: Stefan Meyer would like to hand over the maintainership for
/Services/WebServices
to an interested developer in the nearer future.- Developers willing to take over this maintainership are highly appreciated. Please contact the ILIAS product manager (Kunkel, Matthias [mkunkel]) if you are interested in taking over the maintainership.
3 Maintained Versions
At the time being, we are maintaining ILIAS version 6 (until mid 2022) and version 7 (until mid 2023). Maintenance of ILIAS 5.4 has ended at 31 DEC 2021.
3.1 Roadmap
LAST RELEASES
- ILIAS 7.10 published at 28 APR 2022
- ILIAS 6.16 published at 16 MAR 2022
NEXT RELEASES
- ILIAS 7.11 scheduled for June 2022
- ILIAS 6.17 scheduled for 04 May 2022
3.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:
- #32227: LTI Consumer object does not respect the Tab Guideline for embedded content: In case the LTI object is displayed as embedded content in ILIAS (iFrame), the tab "Content" should be displayed first. This would be expected behaviour according to the tab guideline. For the future, please consider the approach of presenting a "Start" button on a "Content" tab as already implemented for survey (and planned for T&A).
- #32439: Essay Question: 'Save' (Symbol) in TinyMCE does not work: We would like to have back the former behaviour (opt.1 - create an authorised answer when clicking on "Save" button ) and pick-up the issue again when discussing the general concept of auto-save in T&A in the pretty near future.
- #32531: Adding New Forum, Type is actually Didactic Template: As there are several complaints about the re-labeling of the current "Type" to "Didactic Templates" we ask the maintainer of the language service to organise a 1h workshop to discuss and find a better wording that reflects both aspects - a clear distinction between those "types" that are didactic templates and those that have different functions - e.g. 360° survey vs. usual survey.
3.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:
Open Bugs Without Feedback | Last JF | ø Age in Days | Last JF | New Votes* | Old Votes** | Resolved or Closed*** | |
---|---|---|---|---|---|---|---|
1x2v | |||||||
3 | 2 | 65 | 47 | 1x2v | |||
104 | 106 | 230 | 218 | 1x3v 3x2v 8x1v | 1x1v | ||
4 | 5 | 100 | 148 | 2x1v | 1x1v | ||
1 | 0 | 46 | 0 | ||||
0 | 1 | 0 | 47 | ||||
1x1v | 10x2v 71x1v | 1x3v 1x2v | |||||
1x3v 1x2v 7x1v | 1x1v | ||||||
12 | 9 | 82 | 70 | 5x1v | |||
1x2v 1x1v | |||||||
2 | 2 | 275 | 247 | ||||
236 | 188 | 197 | 218 | 1x6v 1x5v 1x3v 3x2v 15x1v | |||
1x1v | |||||||
1 | 1 | 124 | 96 | 2x1v | |||
1 | 0 | 46 | 0 | 1x3v | |||
1 | 1 | 68 | 40 | ||||
20 | 7 | 61 | 78 | 1x2v 6x1v | 1x2v 1x1v | ||
21 | 3 | 31 | 44 | 1x3v 1x2v 4x1v | |||
1x1v | |||||||
1x1v | |||||||
43 | 41 | 287 | 279 | 1x1v | |||
6 | 1 | 39 | 40 | ||||
3 | 3 | 53 | 33 | ||||
8 | 5 | 103 | 116 | 1x2v | |||
1 | 1 | 416 | 388 | ||||
1 | 0 | 32 | 0 | ||||
Zehnder, Lukas | |||||||
* 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 are 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.
3.4 Development Issues of Maintained Versions
The following development issues concern one or more maintained versions. Issues related to upcoming versions have to be added in chapter 4.
3.5 Open Pull Requests to Discuss
- PR2943 • BUGFIX[29052] : We discussed the PR and its functional and visual impact. We would like to keep the subheadlines (for place / type of the favourites) and have to get rid of the empty headline tag due to accessibility. Timon will create a new PR and discuss it with the product manager. On the long run, we should improve the UI component (combined slate) and display a kind of 'settings icon' for Favourites (and have one line less in the slate).
- PR2944 • BUGFIX[29053] : Timon will create a new PR and discuss it with the product manager, see PR #2943
- PR4125 • Authentication: Use
SameSite
cookie attribute : We highly appreciate this suggestion and accept the PR for 7 and trunk. This change might have an impact on displaying ILIAS in an iFrame. - PR4189 • Add a PluginRenderer to unify and simplify plugin chaining : We like the approach and waiting for a review by @klees and related improvements until we accept the PR for ILIAS.
- PR4389 • UI Components, Global Screen: Fix favicon.ico not shown, see #29414 : We highly appreciate this PR and accept it for trunk.
- PR4458 • Object: Change label of didactic template element (Mantis 32531) : As there are several complaints about the re-labeling of the current "Type" to "Didactic Templates" we postpone a decision about this PR and ask the maintainer of the language service to organise a 1h workshop to discuss and find a better wording that reflects both aspects - a clear distinction between those "types" that are didactic templates and those that have different functions - e.g. 360° survey vs. usual survey.
- PR4460 • Security: introduces a configurable delay for login and registration attempts : We highly appreciate this suggestion to improve the security of ILIAS. It would be good not to rely on a session-based solution only. Considering the remote-IP or fingerprinting the browser could be options. And concerning presenting the function: please present it in "System Settings and Maintenance » Authentication and Registration : Authentication : Authentication Settings" and present the feature also in "Privacy and Security: Security" with a link to the authentication administration.
- …
3.6 Continuous Integration
- Michael Jansen has taken over reporting of CI from Richard Klees.
- As of today, there are
- 8356 unit tests (+147)
- 20407 assertions
- 12 skipped unit tests
- 1 incomplete unit test
4 Developing ILIAS 8
4.1 Timeline for ILIAS 8
Due to necessary time for reviewing the entire ILIAS code that has been refactored for PHP8 support, it is necessary to add additional time for the reviews and thus change the timeline for ILIAS 8.
- Feature freeze at 30 APR 2021 (deadline to suggest new features for this version)
- PHP-8-Reviews completed until 28 APR 2022 (changed)
- Coding completed for refactored components: 28 APR 2022
- Incorporating results of reviews: 29 APR 2022 to 11 MAY 2022
- Final check of components by their maintainers on 12 and 13 MAY 2022 (changed)
- Pre-Testing from 16 May 2022 until 20 MAY 2022 (changed)
- Incorporating of Pre-Test results: 22 MAY 2022 until 02 JUN 2022 (changed)
- Release 8.0 beta1 and release-8 branch planned for 03 JUN 2022 (changed)
- Begin of testing phase scheduled for 07 JUN 2022 (changed)
- End of testing phase planned for 12 AUG 2022 (changed)
- First stable 8.0 release planned for 29 AUG 2022
- Full maintenance for version 8: until 31 DEC 2023
- Security bugfixes only: until 31 DEC 2024
4.2 Software Requirements for ILIAS 8
- ILIAS 8 will support PHP 7.4 and 8.0.
- ILIAS 8 will not support PHP 8.1. Reasons are:
- It is not possible to support the range of PHP 7.4 - 8.1 in a single release without suppressing E_DEPRECATED errors for 8.1, and we don't want to soften our error reporting policy for future releases of ILIAS.
- We can't guarantee all our dependencies are compatible with PHP 8.1 until the beta release.
- Nevertheless, all component maintainers and contributors MUST provide commits with passing unit tests for the PHP 8.1 build.
- If you have any questions, do not hesitate to contact the Technical Board.
- Support for PHP 7.3 will be dropped!
- PostgreSQL support is abandoned.
- OpenJDK 11 shall be supported for ilServer.
4.3 Development Issues
While trying to fix the failing unit-tests we were once more forced to acknowledge the fundamental fragility of the current unittest-infrastructure. There are tests relying on a certain state of the system as a whole. To mitigate these risks the TB decided to change the execution order of the tests to random and to backup and restore globals for each test.
Thus we:- Added backupGlobals='true'
- Moved executionOrder='random' from command-line to config. See: PR#4438
JourFixe, ILIAS [jourfixe]: We already discussed this topic within the CI presentation (see 3.6)
4.4 PHP 8 Support for ILIAS 8
Allowing to run ILIAS 8 with the latest PHP version 8 is the big project for developing ILIAS 8 as it requires a major overhaul of the entire ILIAS source code.
Current Status
- Cloud Object is abandoned
- Components to be abandoned: services_LinkChecker, services_Radius and src_FileUpload
Not started yet: | 0 |
Not started on last JF: | 0 |
Components in progress: | 4 |
Components in progress on last JF: | 10 |
In additional, components to be abandoned.
Components completed: | 168 |
Components completed on last JF: | 166 |
Components still to be completed:
- Organisational Units
- Staff and services_MyStaff
- Data Collection
Reviews and Timeline
Not finished yet: | 9 |
Not finished on last JF: | 85 |
Reviews completed: | 164 |
Reviews completed on last JF: | 91 |
- services_Notifications
- Session
- services_Migration
- Workflow Engine
- services_Object
completed Components
Review was delivered.
The results have been integrated by the maintainer.
Components completed: | 142 |
Components completed on last JF: | 54 |
- Competence Management
- Study Programme, services_Migration
- LTI, LTI Consumer, Learning Module SCORM
- Language Handling
- SOAP, Logging, services_Registration, Metadata, Didactic Templates
- MathJax
- Test & Assessment , services_QTI
- Login, Auth & Registration, services_CAS, services_OpenIdConnect, services_SOAPAuth, services_AuthApache, ECS Interface, services_LDAP
Next Steps
- Last Code Refactorings
- Code reviews and Integration of Results
- Fundraising for further Code Refactorings
Samoila, Oliver [oliver.samoila]: To support the release periods from now until 02.June, 2022, the update cycle of test8.ilias.de is to be increased. This is intended to enable rapid re-testing after commits.
In specific terms, there should be update cycles of two-hour intervals (00:00 | 02:00 | 04:00 | ...).
Afterwards, the frequency is to be reduced to either daily or twice daily.
Wolf, Fabian [fwolf]: The control structure reload should not be carried out during the updates.
If this is seen as necessary by the developers, then he should be informed about it.
Question to the maintainers: Is it necessary that it is automatically recognised that a ctrl-reload is necessary?
If an individual notification is sufficient, the adjustment of the update cycle to 04 May, 2022 could be made possible.
JourFixe, ILIAS [jourfixe]: We prefer to reload the control structure with every update of test8.
For current funding status please have a look at the crowdfunding page.
New contributions:
- Studierendenschaft der Universität Freiburg
- Heinrich-Heine-Universität Düsseldorf
4.5 Status of Implementation
- Until announced date of coding completed at 28 APR 2022, 58 features have been committed to trunk
- As of 29 APR 2022, there are …
- 4 features waiting to be committed to trunk
- 1 feature waiting for approval
- 3 features still in development
Information about Implementation and Test Cases
- In case a feature does not need new test cases but extends / modifies only existing ones, please mention the modified test cases anyway.
- In case a feature does neither need new test cases nor modifies existing ones, please write "No test cases needed" in the section TEST CASES.
- In case the implementation is made as already described in the chap. 2 and 3 of the request and no changes were needed, please write at least "Implemented as suggested in chap. 2 / 3)" in the section IMPLEMENTATION.
5 Developing ILIAS 9
5.1 Timeline for ILIAS 9
- Feature freeze at May 31, 2022 (changed): deadline to suggest new features for this version
- Coding completed: all features implemented and test cases finished until October 28, 2022
- Release 9.0 beta1 and release-9 branch planned for October 30, 2022
- Beginn of testing phase scheduled for October 30, 2022
- End of testing phase planned for Februar 02, 2023
- First stable 9.0 release planned for March 15, 2023
- Full maintenance support for version 9: until December 31, 2024
- Security bug fixes only: until December 31, 2025
5.2 Big Projects for 9
The following suggestions have been made for Large Developments for ILIAS 9.
Please find a statement from the Technical Board for each of the projects below. The Technical Board has also added the statements of the UX/UI/A11y-Experts for the projects they deemed most important. You can also find the statements below directly on the Wiki-pages of the projects.
- Establish Referential Integrity
- presented by Uwe Tesche & Michael Jansen
- project page: Project: Establish Referential Integrity
- Relevance for strategic ILIAS development: Data integrity important for further development and security of ILIAS.
- Plan for ILIAS 9: more workshops; development of tools for migration, utility functions, ilDB...; creation of guideline; reference implementation in mail component.
- Chance of realisation: partly financed - good (but still needs to be estimated); personnel: depends on distribution of tasks
- Dependencies: No dependencies on other developments
- Impact on other development activities: not known, if at most positive
Statement Technical Board:
Thank you very much for relentlessly pushing this effort for the last few years. Database integrity is definitely a valid target for improvement. The outlined plan to provide tools to maintainers to actually move their component to a better integrity sounds plausible. If these tools are applied, they will definitely make the system more reliable. Still, we worry that this effort will bind resources urgently needed for other efforts with similar goals that are already ongoing. Especially the IRSS seems to be problematic, since Fabian Schmid (as a maintainer of database and IRSS) will be heavily involved in both efforts. In general, we cannot push too many improvements at the same time, as this would overwhelm maintainers. We thus suggest keeping this effort low profile for ILIAS 9 and prepare the according code and documentation. If prepared properly, we can see this becoming a large topic with ILIAS 10. Please coordinate closely with Fabian to enable him to distribute his resources judiciously. In addition, please see, if maybe other people can tackle tasks for him. We will be happy to support this effort with advice for a proper preparation and project management. We are looking forward to making this a larger topic with ILIAS 10. - Page Editor Revision – Step 3
- presented by Oliver Samoila
- project page: New ILIAS Page Editor
- Relevance for strategic ILIAS development: Content creation within the system important for ILIAS; continuation of developments started since 7
- Plan for ILIAS 9: see project page
- Chance of realisation: financially good; personnel: depends on workload Alexander Killing. Is important for maintainer and he gives project therefore high priority!
- Dependencies: no dependencies on other developments, but needs further KS elements
- Impact on other development activities: No impact on other developments
Statement Technical Board:
With this proposal, the Page Editor revision enters its third iteration since the initial push with ILIAS 6. The project will certainly involve many people, but only a few of them maintainers. We would be very happy if very concrete goals are formulated and implemented here for ILIAS 9 and if after the completion of this iteration the "revision" is finished or the work is continued in a taskforce. From a product-strategic point of view, the editor is of course a critical tool for content creation and therefore deserves a lot of attention. We thank you very much for this contribution.Statement UX/UI/A11y-Experts:
The editor is not accessible yet and from a user perspective quite a few issues are still open so that the general appearance is inconsistent for them. This leads to some confusion. This important next step will allow us to considerably streamline the experience. We already see the need to further pursue this project with ILIAS 10. - Splitting up Tools
- presented by Yvonne Seiler
- project page: [[[Project] Splitting Up Tools]]
- Relevance for strategic ILIAS development: Important for better and more user-friendly use of tools. Current concept irritates users. Confusing workflows need to be reduced → better usability!
- Plan for ILIAS 9: see project page
- Chance of realisation: Project can be realised in small steps / incriminating approach
- Dependencies: Partly dependent on development of page editor and accessibility improvements.
- Impact on other development activities: None
Statement Technical Board:
We see how this significant project impacts the strategic aims to make ILIAS a more adaptable learning environment as well as usable for everyone. We thus consider this development very beneficial for the project. Still, we do not see that the coaching of the TB would have a considerable impact on the further progress of the projects, as most answers regarding technical implications related to this endeavor are already considered and published.Statement UX/UI/A11y-Experts:
The tools as they are today leave the users with quite a few questions. The conceptual work done during the last few years has created strong indications that splitting the tools up into different groups of tools with different strategies for the UX/UI should improve the situation considerably. It is a very important project, but the working group that already works on these issues will continue working, and thus the project can be advanced outside of the frame of the Big Projects. - Remove Services/UIComponent and Services/Table
- presented by Technical Board
- Relevance for strategic ILIAS development: Unification of the UI addresses all targets of Technical Board to improve ILIAS.
- Plan for ILIAS 9: See PR4013 and PR4014
- Chance of realisation: Staggering to two versions increases chance of realisation; funding necessary
- Dependencies: requires cooperation of all maintainers
- Impact on other development activities: Further developments must use KS UI elements and can no longer fall back on legacy components.
Statement Technical Board:
This project was proposed by the Technical Board and is to be understood as a strategic project. It is very important to save resources in the future and to get more consistency in the UX/UI. In connection with the abolition of bootstrap 3, the project is also important for the security, consistency and usability of ILIAS.
This project will, in a first step, require a lot of conceptual work and the Technical Board sees itself in an important role. Thus, a strong focus will be put on it and it will be accompanied closely. After the conception of individual components, they must be implemented in the entire code base through a lot of diligent work.Statement UX/UI/A11y-Experts:
This project as well as Project E and F will be important to improve consistency of the UI. They are important steps to continue the change started with the UI-Kitchensink and the Global Screen Service. - Abandon Bootstrap 3
- presented by Timon Amstutz
- Relevance for strategic ILIAS development: get rid of dependency on Bootstrap 3 and LESS (middle prio)
- Plan for ILIAS 9: Get rid of Bootstrap CSS/Less
- Chance of realisation: good financial chance of realisation; sticking point rather human resources
- Dependencies: great dependence on project D
- Impact on other development activities: influence on all developments that work with DOM structure
Statement Technical Board:
The proposed project is strongly related to "Remove Services/UIComponent and Services/Table", as there are numerous DOM elements that still rely on Bootstrap. Bootstrap 3 has dependencies on JS and DOM nesting that need to be removed as part of this project, and therefore many places will be touched. There will be many people involved, and it will tie up considerable resources. Since Bootstrap 3 is no longer supported, we definitely need to tackle this project asap.Statement UX/UI/A11y-Experts:
This project as well as Project D and F will be important to improve consistency of the UI. They are important steps to continue the change started with the UI-Kitchensink and the Global Screen Service. - Views / InnerContent
- presented by Fabian Schmid
- project page: [[[Project] Views / InnerContent]]
- Relevance for strategic ILIAS development: High priority! Many bugs come from complexity of page structure. It would be simpler and safer in future through predefined structures; also creates more consistency on UI side, also more security.
- Plan for ILIAS 9: development, elaboration and discussion of the concept; proof of concept of a simple component (probably file object), including new UI components (e.g. assynchronous tabs), screen IDs
- Chance of realisation: can only be said after concept development; screen IDs financed and thus safe for I9
- Dependencies: dependent on UI components, on ilCtrl, on GlobalScreen
- Impact on other development activities: impact on other components only in the context of the respective adaptation
Statement Technical Board:
The Technical Board believes that this project has a big technical relevance and will have deep architectural impacts to allow ILIAS to be a more "Adaptable Learning Environment". However, we think that the already outlined technical approaches (e.g. integration into the Global Screen Service) should not need too much involvement of the Technical Board. Still, we agree to support „on demand“ when deemed necessary for this medium-to-high priority project.Statement UX/UI/A11y-Experts:
This project as well as Project D and E will be important to improve consistency of the UI. They are important steps to continue the change started with the UI-Kitchensink and the Global Screen Service. - ILIAS Resource Storage Service
- presented by Fabian Schmid
- project page: Project: ILIAS Resource Storage Service (IRSS)
- Relevance for strategic ILIAS development: Important continuation of the conversion to IRSS in many other components.
- Plan for ILIAS 9: Convert other components to IRSS
- Chance of realisation: Conversion in components can also be done by the respective maintainers themselves
- Dependencies: Cooperation of other maintainers
- Impact on other development activities: No impact
Statement Technical Board:
The TB believes this effort to be on a good track. First components are already migrated, and the infrastructure is ready. The remaining effort mostly lies in migrating the various components using file storage functionality. To complete this project soon, we assign a high priority to it. We ask every collaborator to focus on this effort or include according changes into other efforts. If we all pull together, we can move our system to the IRSS soon. To achieve this, we feel that Fabian will mostly need to do some further marketing and dissemination, and we will happily support him as Technical Board to convince everyone to finally use the IRSS. - ILIAS Refinement
- presented by Oliver Samoila & Denis Strassner
- project page: [[[Project] ILIAS Refinement]]
- Relevance for strategic ILIAS development: Promotes acceptance in everyday life when even the small bugs are fixed; confirms bug reporters when their bug reports are also addressed.
- Plan for ILIAS 9: Prioritise the bugs and work through them.
- Chance of realisation: Project can be done in small steps, possible co-financing by advisory board; time for bug fixing must be available with maintainer.
- Dependencies: none
- Impact on other development activities: none
Statement Technical Board:
We strongly endorse the goal to reduce the number of issues and improve the workflow around tackling them. However, we believe this to be an effort to be worked on continuously. Since we believe this to be a necessary task for all future versions of ILIAS, we do not give this special priority for the next ILIAS version. However, we fully support and endorse activities around it for ALL upcoming ILIAS versions. Since we believe “ILIAS Refinement” to be a continuous project, we should take care to only support measures that we have the capacity to sustain for all releases in years to come. - Continuous Refactoring Initiative
- presented by: Oliver Samoila
- project page: [[[Project] Continuous Refactoring Initiative]]
- Relevance for strategic ILIAS development: very high for sustainability of ILIAS
- Plan for ILIAS 9: See project page
- Chance of realisation: use of quality assurance funds of ILIAS association; personell: depending on free capacities until October
- Dependencies: to be clarified for each component
- Impact on other development activities: to be clarified for each refactoring
Statement Technical Board:
The Technical Board agrees that continuous refactoring is a key aspect in ILIAS. We believe that we need strategies to ensure, that this refactoring activity will continuously accompany the work on ILIAS OSS. Since we believe this to be a necessary task for all future ILIAS versions, we do not give this special priority for the next ILIAS versions. However, we fully support and endorse activities around it for ALL upcoming ILIAS versions. Since we believe ILIAS Refinement to be a continuous project, we should take care to only support measures that we have the capacity to sustain for all releases in years to come. - Component Revision
- presented by: Richard Klees
- project page: (Project) Component Revision
- Relevance for strategic ILIAS development: Considerable strategic relevance, especially with regard to plug-ins (will make it easier to adopt plug-ins in core in future); also improves maintainability and expandability of ILIAS.
- Plan for ILIAS 9: Implementation of a parallel implementation
- Chance of realisation: Time for workshops of maintainers, financing for ILIAS 10 hopefully via advisory board
- Dependencies: Coordination with Views
- Impact on other development activities: Impact on all developments (when implemented)
Statement Technical Board:
The Technical Board believes that this project has a big technical relevance and will have deep architectural impacts to allow ILIAS to be a more "Adaptable Learning Environment". The Technical Board assigns a high priority to this development, and we’re looking forward to further collaborate on this matter. The project also requires the focus of the component maintainers. - Booking Tool Revision
- presented by: Alexander Killing
- project page: Booking Tool Revision
- Relevance for strategic ILIAS development: Important administrative tool that can only survive if it can cope with intensive use.
- Plan for ILIAS 9: see project page
- Chance of realisation: step-by-step implementation; funding interest justified; maintainer willing to allow time for 9
- Dependencies: no dependencies on other developments
- Impact on other development activities: none
Statement Technical Board:
We believe this project to involve a limited number of stakeholders. We see that there are related feature requests, however we are also not sure how large the impact on other services or modules will be. There is definitely a lot of room for improvement, and we hope the projects will achieve the outlined goals. The Technical Board will assign no special priority to this project. - Search Revision
- presented by: Stefan Meyer
- project page: [[[Project] Search Revision]]
- Relevance for strategic ILIAS development: Improvement of a central service that rarely receives funding but is of hugh importance for using the system.
- Plan for ILIAS 9: Workshops, first feature development (especially presentation)
- Chance of realisation: Funding still unclear / dependent on workshop results
- Dependencies: Dependence on KS / UI elements
- Impact on other development activities: None
Statement Technical Board:
We believe this project to involve a limited number of stakeholders. We see that the related feature requests mainly concern the search maintainer. Therefore, we are not certain how large the impact on other services or modules will be. There is definitely a lot of room for improvement, and we hope the project will achieve its goals. The Technical Board will assign no special priority to this project.Statement UX/UI/A11y-Experts:
A good search-functionality is vital for the accessibility of ILIAS. It needs to be made sure while improving the search-functionality that the search forms and results pages themselves are accessible. - Export Revision
- presented by: Stefan Meyer
- project page: (Project) Export Revision
- Relevance for strategic ILIAS development: Import validation in particular is important to prevent broken database structures in the future. Also relevant for security to reduce attack vectors.
- Plan for ILIAS 9: Above all
- Chance of realisation: Funding available, human resources available
- Dependencies: Intersection with Resource Storage Service
- Impact on other development activities: In principle, influence on all objects that support export/import.
Statement Technical Board:
The export and import of ILIAS-Content can clearly be improved, and we thank Stefan Meyer to tackle this task. We see the importance specially concerning the validation of imports. We don't see special priorities regarding the resources of the Technical Board, but please make sure to involve the other maintainers impacted by any changes as early as possible.
5.3 Suggested Features for 9
Clickable Links in Personal Profile : We highly appreciate this suggestion and re-schedule the feature for ILIAS 9. We accept this implementation without migrating UDF to Custom Metadata due to the status of the maintainership of the user service. And please complete the sections for Accessibility and Security.
Replace Current Search with Dependency to Query directly from PHP : Stefan Meyer gave a short overview of the current status and concept for an improved search for ILIAS 9. Final FR will be presented in one of the next JF.
Clean up the Badges area in Achievements : We highly appreciate this suggestion and schedule the feature for ILIAS 9. We prefer the label "Table View" instead of "List View" and the suggested "Awarded by" instead of "Object" in the tile and as column header. And we don't want to introduce a special case for a AJAX call for the adding/removing action.
- [[]] :
- Feature request presented by
- Length of slot: '
Dernière édition: 18. oct. 2024, 16:07, Kunkel, Matthias [mkunkel]