Updated on 1 April 2026
NB: Only the French version of this charter is authentic.
The current DG developer is : Sylvain Gay, Clément Allard, Louis Houlès and Pierre Bodet.
DG developers are in charge of the proper functioning of the information systems for which the DG is responsible, including in particular, but not exclusively, Degette and webmoderation. These operators ensure in particular, but not exclusively, the proper functioning of Degette. Proper operation includes the maintenance, repair and updating of said information systems. DG developers are independent of the sysadmins and the DGNum. However, multiple positions remain possible.
DG developers must be students, within the meaning of Article 3 of the Internal Rules, or former students. No former student can be a developer if they finished their education at ENS more than five years previously.
The DG organises the recruitment of developers. This recruitment must be public and be done via an email sent to all students in school. The DG then selects the developers at its discretion, after having obtained the advisory opinion of the developers in place. Their name is published at the top of this Appendix. The mandate of the developers is limited, except in the event of revocation, only by the conditions of article 2.
There cannot be more than three developers in office at the same time, except during handover periods. If the DG is technically capable of ensuring the IT development of its information systems itself, it may not appoint any developers.
The DG may revoke, at any time, without notice, the mandate of the developers. Likewise, any student can request from the DG, upon presentation of a petition with at least 33.3 signatures, the revocation of one or more developers. The DG is then obliged to convene an GA, which can only revoke the developer with an absolute majority in favor of the revocation.
The DG may give developers in office, excluding periods of suspension as provided for in Article 7, all administrator and super-user rights on all information systems which depend on her, at the request of the developers and according to the needs of the DG. The developers undertake to respect the confidentiality of the data to which they will thus have access. This commitment is made in writing, on a form provided by the DG to new developers.
In the event of non-compliance with article 6 by one of the developers, the DG is forced to terminate its mandate and immediately removes all its access and administration rights to the information systems which fall within its competence.
If one or more developers report abusive or counterproductive behavior on the part of another developer to the DG, the DG may suspend the latter by temporarily revoking their access and administrator rights and decides within two weeks on its maintenance or revocation.
Any revocation or suspension must be the subject of a notification email sent by the DG to the developer concerned. In this email, the DG justifies its decision to revoke. The decision of revocation or suspension is communicated by the DG on its website.
The DG gives developers information regarding large-scale updates, i.e. those affecting the functionalities, of the information systems that depend on it. Developers cannot implement such updates without a request from the DG, or explicit agreement from it. Security updates can be undertaken by developers alone, who must first indicate what they intend to do on a chat channel including all developers and to which the DG will have access at any time . They do not have to obtain authorisation from the DG to implement such updates. In the event of a breakdown, the DG reports the problem to the developers, who deal with the problem as quickly as possible.
The DG organises a meeting with developers at least once per academic year.
Every January, starting in January 2025, the developers send the DG a brief activity report including in particular the list of interventions carried out. The DG includes this report as an appendix to its own annual activity report, which it sends to the School Management and publishes on its website.