1fanwang opened a new issue, #46158:
URL: https://github.com/apache/airflow/issues/46158

   ### What do you see as an issue?
   
   ## Description:
   The croniter package, which Airflow uses for parsing cron expressions 
(particularly extended syntax like `0 0 * * MON#1`), has been officially 
declared unmaintained as of December 10, 2024. The maintainer announced 
potential removal of all resources by March 15, 2025 due to EU Cyber Resilience 
Act regulations.
   
   (Was helping an internal Airflow user on their cron expressions today and 
found out this news through browsing the Airflow User doc links)
   
   Airflow Doc:
   
https://airflow.apache.org/docs/apache-airflow/stable/authoring-and-scheduling/cron.html#cron-presets
   
   ## Impact:
   - Extended cron syntax functionality in Airflow depends on this package
   - No future security patches or updates will be provided
   - Package could be removed from PyPI in March 2025
   
   
   ## Details
   From https://github.com/corpusops/croniter
   ```
   While this repository has been inactive for some time, this formal notice, 
issued on December 10, 2024, serves as the official declaration to clarify the 
situation. Consequently, this repository and all associated resources 
(including related projects, code, documentation, and distributed packages such 
as Docker images, PyPI packages, etc.) are now explicitly declared unmaintained 
and abandoned.
   
   I would like to remind everyone that this project’s free license has always 
been based on the principle that the software is provided "AS-IS", without any 
warranty or expectation of liability or maintenance from the maintainer. As 
such, it is used solely at the user's own risk, with no warranty or liability 
from the maintainer, including but not limited to any damages arising from its 
use.
   
   Due to the enactment of the Cyber Resilience Act (EU Regulation 2024/2847), 
which significantly alters the regulatory framework, including penalties of up 
to €15M, combined with its demands for unpaid and indefinite liability, it has 
become untenable for me to continue maintaining all my Open Source Projects as 
a natural person. The new regulations impose personal liability risks and 
create an unacceptable burden, regardless of my personal situation now or in 
the future, particularly when the work is done voluntarily and without 
compensation.
   
   No further technical support, updates (including security patches), or 
maintenance, of any kind, will be provided.
   
   These resources may remain online, but solely for public archiving, 
documentation, and educational purposes.
   
   Users are strongly advised not to use these resources in any active or 
production-related projects, and to seek alternative solutions that comply with 
the new legal requirements (EU CRA).
   
   Using these resources outside of these contexts is strictly prohibited and 
is done at your own risk.
   
   Regarding the potential transfer of the project to another entity, 
discussions are ongoing, but no final decision has been made yet. As a last 
resort, if the project and its associated resources are not transferred, I may 
begin removing any published resources related to this project (e.g., from 
PyPI, Docker Hub, GitHub, etc.) starting March 15, 2025, especially if the 
CRA’s risks remain disproportionate.
   ```
   
   ### Solving the problem
   
   ## Potential Solutions:
   1. Evaluate alternative cron parsing libraries
   2. Consider forking and maintaining croniter within Apache Airflow
   3. Implement native support for extended cron syntax
   
   ### Open questions
   - It is likely that it's not just this one OSS tool that Airflow depends on 
is reacting to EU CRA, might need a scalable solution to handle this
   - Would be helpful to get broader community input on preferred approach 
before the March 2025 deadline.
   
   ### FYI: Links a few things I read about ASF's reaction (TG)
   
https://news.apache.org/foundation/entry/update-on-eu-software-regulation-lots-of-improvements-good-news
   
https://news.apache.org/foundation/entry/open-source-community-unites-to-build-cra-compliant-cybersecurity-processes
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to