<commit_before>If you want to contribute to the development of Jorani, here is a list of things to be implemented.
I tried to sort them out by priority and to explicitly explain what is out of scope.

## v0.5.0 or later

- [X] Copy contract/calendar (definition of non-working days for a yearly period).
- [X] A manager can create a leave request in behalf of a collaborator.
- [ ] Better entitled days editor (contract / employee).
- [ ] Report carried-over leaves (Semi-auto / wizard), employee by employee (or mass ?).
- [ ] Notification by e-mail : Request deleted / modified.
- [ ] Delete a past leave request (Request + Wkf ?), or...
- [ ] ... send an e-mail (send to line manager, option to CC the HR officers). Contextual to a leave/overtime request.
- [ ] Provide an example of a REST client (seniority leaves, carry over...) in PHP (cron) or go (service).

## Not a priority

- [ ] Better LDAP integration.
- [ ] Implement a kind of heritage in HR/organization for supervisors (child entities).
- [ ] Inactive employees (today we can put them into an archive entity in HR/organization so as to exclude them from reports).
- [ ] HR officers of a part of the organization (defined in HR/organization), for future functions when they'll be CCed.
- [ ] Add a field explaining why a request is rejected. Validation E-mail will redirect to a form is this option is activated ?
- [ ] Anticipated leaves (entitled days of next yearly period). Today we can deal with it manually because LMS doesn't forbid to 
request a leave even if your credit is negative and because leave balance reports can be executed with a past/future date.
- [ ] Setup assistant.
- [ ] Mass importer of users (from CSV, LDAP ?).
- [ ] Multitenancy (add global filter / Additionnal field on all tables). Allow access to the same instance for multiple tenants.

## Post v1.0

- [ ] Simplified time tracking.

## Will not be implemented

- [ ] Requests are validated by two users (opens the door to a wkf engine, too complicated for targeted users).
- [ ] PDF Export (no serious OSS PDF lib dealing correctly with Unicode / Modern browsers can print as PDF).
- [ ] Migration to CI 3.0.0 (we don't rely too much on the library, so it has no interrest and it is slower than v2).<commit_msg>ER:Update of TODO list<commit_after>If you want to contribute to the development of Jorani, here is a list of things to be implemented.
I tried to sort them out by priority and to explicitly explain what is out of scope.

## v0.5.0 or later

- [X] Copy contract/calendar (definition of non-working days for a yearly period).
- [X] A manager can create a leave request in behalf of a collaborator.
- [X] Check Ajax return (e.g. calendar views) to redirect to login in case of disconnection.
- [ ] Better entitled days editor (contract / employee).
- [ ] Report carried-over leaves (Semi-auto / wizard), employee by employee (or mass ?).
- [ ] Notification by e-mail : Request deleted / modified.
- [ ] Delete/Edit a rejected leave request (option).
- [ ] Provide an example of a REST client (seniority leaves, carry over, LDAP sync...) in PHP (cron) or go (service).
- [ ] Fix Deprecation warning: moment.lang is deprecated. Use moment.locale instead.

## Not a priority

- [ ] Better LDAP integration.
- [ ] Implement a kind of heritage in HR/organization for supervisors (child entities).
- [X] Inactive employees (put them into an archive entity in HR/organization so as to exclude them from reports).
- [ ] HR officers of a part of the organization (defined in HR/organization), for future functions when they'll be CCed.
- [ ] Add a field explaining why a request is rejected. Validation E-mail will redirect to a form is this option is activated ?
- [ ] Anticipated leaves (entitled days of next yearly period). Today we can deal with it manually because LMS doesn't forbid to 
request a leave even if your credit is negative and because leave balance reports can be executed with a past/future date.
- [ ] Setup assistant (with links to requirements, testldap and testmail scripts).
- [ ] Mass importer of users (from CSV, LDAP ?). From GUI or a side tool using the REST API ?
- [ ] Multitenancy (add global filter / Additionnal field on all tables). Allow access to the same instance for multiple tenants.
- [ ] Alternative overtime module. It will be separated from the LMS, accepted extra time will not be added as a compensate entitled days but compensation will have its own wkf.

## Post v1.0

- [ ] Simplified time tracking. Not sure because Jorani is specialized in LMS. Maybe a side project ?

## Will not be implemented

- [ ] Requests are validated by two users (opens the door to a wkf engine, too complicated for targeted users).
- [ ] PDF Export (no serious OSS PDF lib dealing correctly with Unicode / Modern browsers can print as PDF).
- [ ] Migration to CI 3.0.0 (we don't rely too much on the library, so it has no interrest and it is slower than v2).
{'fraction_non_alphanumeric': 0.07717237188576058, 'fraction_numerical': 0.0036459388292485314, 'mean_word_length': 3.614953271028037, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5223800', 'n_tokens_mistral': 1332, 'n_tokens_neox': 1274, 'n_words': 743}