Dear ILIAS developers,
as already announced at the last DevConf in Duisburg, we are looking for authors to complete our Tutorial for ILIAS Developers. With this tutorial we would like to promote the transfer of know-how among ILIAS developers and, above all, reduce the hurdle for newcomers to ILIAS programming.
Parts of the tutorial are already availble. But we need authors for special topics for which we have no competence in the ILIAS office. This is why we decided to start a Call for Bids which I would like to send to you with this e-mail.
Please have a look in the attached document ‚2025-04_CfB_Tutorials.pdf‘’ and the related ‚2025-04_DevTutorial_Structure.pdf‘ to read more about the objectives of the bid, the topics of the needed content and required deliverables. You can give a bid for a single topic or for multiple texts.
In case of questions, please contact Ann-Christin Gruber for support: acgruber(a)ilias.de <mailto:acgruber@ilias.de>
Deadline for bids is 15 May 2025
We are looking forward to many applications.
Kind regards,
Matthias


* * * * *
Matthias Kunkel
Geschäftsführer ILIAS open source e-Learning e.V.
Vereinsheim & Geschäftsstelle:
Berrenrather Straße 177 • 50937 Köln
Fax: +49 221 5607 8458
Web: www.ilias.de
E-Mail: verein(a)ilias.de
* * * * *
Future Skills mit ILIAS: Lernen, Vernetzen, Gestalten
24. ILIAS-Konferenz am 5. und 6. Juni 2025 in Berlin
Das ILIAS-Event des Jahres!
Mehr unter: www.ilias-conference.org
* * * * *
Diese E-Mail und ihre Anlagen können vertrauliche und / oder rechtlich
geschützte Informationen enthalten. Wenn Sie nicht der richtige Adressat
sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie mich bitte
und löschen diese E-Mail.
Dear developers,
as already announced at the last Development Conference in Duisburg, we abandon the Feature Freeze with ILIAS 11. There will be no more deadline to suggest new features. And accepted features will no longer be scheduled in the Jour Fixe for a specific ILIAS version. Accepted feature requests will be ‚Accepted for Trunk‘. The decision if they make it into ILIAS 11, 12 or 13 is made by responsible authority of the related component(s). Only these persons know if there are resources, funding and time to implement the feature before ‚Coding Completed‘ of the selected version.
What does this change means for you as a developer of ILIAS?
If you do not have an authority for a core component of ILIAS, this change has no impact on your work. You can now stop reading and go on with coding.
If you are an authority of a core component, please consider:
Feature requests are no longer suggested for a specific ILIAS version. They are just a ‚Suggestion‘. A specific list ‚Suggested for ILIAS 11‘ or ‚… 12‘ on the related component page exists just as little as a related tag in the metadata block. To avoid an uncontrolled growing of the list of ‚Already Suggested‘ feature requests for your component, please check the individual requests. Set outdated and redundant requests to the related metadata and features you do not support in your component to ‚Rejected feature‘.
If you have completed a feature request and it contains all information that is needed to discuss it in the Jour Fixe and accept it for ILIAS, please set the status of this request to ‚Jour Fixe Ready‘. You can do this also before you suggest it for the Jour Fixe agenda. This tag notifies interested persons that the feature request is ready to be discussed and that they can contribute to the funding of the feature if needed.
Feature requests as well as abandon requests that are accepted by the Jour Fixe are set to ‚Accepted for Trunk‘ and not for a selected ILIAS version. Acceptance of a feature says nothing about its scheduling. For which version a feature will be implemented is only decided by the responsible component authority. And unlike in the past, features have no longer be rescheduled when they didn’t made it into the version they were originally accepted for.
If you know that you will implement an accepted feature request (‚Accepted for Trunk‘) for an upcoming ILIAS version, please set the metadata of this request to the selected ILIAS version, e.g. ‚ILIAS 11‘. You can do this without consulting the product manager or the Jour Fixe. You know best if you have the time and the funding to develop this feature for ILIAS.
When the underlying conditions of an accepted feature request have changed in the years after it has been accepted (and not yet implemented), the product manager as well as the responsible authority have the right and duty to set the request on the agenda again to update its concept, e.g.: a UI component has been introduced in the meantime that should be used for this implementation and that didn’t existed yet when the original request was accepted. In this case, the Jour Fixe will discuss and - hopefully - accept the updated request again.
The statuses in the metadata have already been updated accordingly by the product manager. Features that were already scheduled for ILIAS 11 and have at least a release status of ’settled’ (meaning a contract to implement the feature has been settled) are still tagged with ILIAS 11. We assume that they will make it into ILIAS 11 anyway. Features that were originally scheduled for ILIAS 11 but have not or not sufficient funding are set to ‚Accepted for Trunk‘. Once it is clear that the feature will become part of ILIAS 11 (even if you haven’t started coding), you can change the status to ‚ILIAS 11‘. As the responsible authority please feel free to update the status to the correct one. Thanks for this in advance.
A side effect of the status changes is that component pages currently have two lists with the similar content: ’Suggested for ILIAS 11’ and ‚Already Suggessted‘. Both lists are created automatically and show the pages tagged with ’Suggestion’. We will remove the duplicate list on the component pages in the next days (‚Already Suggessted‘ will be kept).
The Technical Board and the ILIAS product manager hope that this change of process makes things a bit easier for you and all of us who are involved in the development process of ILIAS. If you have questions or if you need additional information, please do not hesitate to contact me.
Kind regards,
Matthias
* * * * *
Matthias Kunkel
Geschäftsführer ILIAS open source e-Learning e.V.
Vereinsheim & Geschäftsstelle:
Berrenrather Straße 177 • 50937 Köln
Fax: +49 221 5607 8458
Web: www.ilias.de
E-Mail: verein(a)ilias.de
* * * * *
Future Skills mit ILIAS: Lernen, Vernetzen, Gestalten
24. ILIAS-Konferenz am 5. und 6. Juni 2025 in Berlin
Das ILIAS-Event des Jahres!
Mehr unter: www.ilias-conference.org
* * * * *
Diese E-Mail und ihre Anlagen können vertrauliche und / oder rechtlich
geschützte Informationen enthalten. Wenn Sie nicht der richtige Adressat
sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie mich bitte
und löschen diese E-Mail.
