Hi. Le jeu. 17 oct. 2024 à 11:38, Piotr P. Karwasz <piotr.karw...@gmail.com> a écrit : > [...] make the public aware that if > they don't start contributing to a "dormant/at risk" sub-project (e.g. > Flume), the sub-project will reach EOL.
+1 "Commons" has been unable to achieve this "awareness".[1] Most components are "alive" by virtue of a single active maintainer. Part of the problem is that new people won't be interested in contributing to an "old" library. LTS makes the "burden" heavier, and participation even less attractive. JDK has LTS but, as a counterpoint, it actively promotes/offers new features (and, as Gary pointed out, makes companies pay if they prefer to stay in the past). If "Commons" stays too long in the past (wrt the evolution of the language it purports to use), it will die. Regards, Gilles [1] Despite disproportionate efforts like e.g. participation to GSoC (not a single candidate stayed around).] --------------------------------------------------------------------- To unsubscribe, e-mail: security-discuss-unsubscr...@community.apache.org For additional commands, e-mail: security-discuss-h...@community.apache.org
