+1 Great idea. Go forth!
On Thu, Sep 4, 2025 at 11:29 PM lewis john mcgibbney <lewi...@apache.org> wrote: > Hi dev@, > > It recently came to my attention that accurate $title information would be > useful for our community. > > Tika (EOL) data could be useful and important for several reasons: > > - Security Management: EOL software no longer receives security updates or > patches, making it vulnerable to exploits and cyberattacks. Knowing EOL > dates could help the Tika community and users plan upgrades to maintain a > secure environment. > - Compliance and Risk Mitigation: Many industries have regulations > requiring up-to-date software to ensure data protection. EOL data helps > organizations avoid non-compliance and reduce risks associated with > unsupported software. With Tika being such a popular toolkit, it is > important to give consideration to the downstream consumer supply chain. > - Cost Planning: Understanding EOL timelines allows our user community to > budget for upgrades, replacements, or migrations, avoiding unexpected costs > from emergency updates or system failures. > - Operational Continuity: Unsupported/older versions of Tika may not > function properly with newer systems or applications, leading to > compatibility issues. EOL data will better equip our user community to plan > operations. > - Vendor Support: After EOL, vendor support (e.g., technical assistance, > bug fixes) typically ends. Knowing these dates ensures organizations can > seek alternative support or solutions in advance. > > I'm sure that several additional compelling reasons exist for why we should > consider publishing $titel information. > > In my research so far I have discovered two platforms which seem to play a > similar role in the niche business of collecting and publishing software > EOL and support information, these are > > 1. https://endoflife.date/, and > 2. https://www.eol.support/ > > Both seem fairly similar in functionality. The former is open source (MIT > License) as is the dataset (https://github.com/endoflife-date). UI have no > preference at this stage. > Not surprisingly many vendors exist in this EOL and support area. I have > intentionally not included them above because they offer paid services > which I think introduces unnecessary complexity for the Tika project. > > Publishing this information is not going to be a one-and-done deal. The > information is dynamic in nature and needs to be curated, likely alongside > every Tika release and maybe more frequently depending on what decisions > are being made in the Tika community regarding project direction, etc. > > Generally speaking I am for publishing EOL and support information. Maybe > one of the above platforms is the right way to go about doing that... maybe > not. I hope this thread will spur some input. > > Thank you > lewismc > > > -- > http://people.apache.org/keys/committer/lewismc >
