Define Common Taxonomy

[kvandecr]

Split off from #7

create unambiguous definitions for the different states a product can be in such as "End Of Life", "End Of Development", ...

[tschmidtb51]

There is a comment in OpenEoX/openeox#29 that we should consider:

https://endoflife.date/contribute has taken the lead for a while in helping publish and consolidate end of sale information. The also have public source in https://github.com/endoflife-date

Please ensure coordination between OpenEoX and endoflife.date so that everyone can learn from one another, and benefit from commonalities.

[tschmidtb51]

And from the same issue:

Thanks @playphil for letting us know about the OpenEoX effort.

At endoflife.date, we have been working on a specification effort as well, which was a super-set of the OpenEoX idea: documenting all releases. The current WIP is at endoflife-date/releases.json#1 for context. Our existing API is already how many projects and companies consume EoL information: https://github.com/endoflife-date/endoflife.date/wiki/Known-Users

I looked at joining the TC meeting tomorrow, but it seems the TC membership is already closed (plus, as an open-source project we can't really join as a member easily). Would it be possible to get an invite for the meeting?

Originally posted by @captn3m0 in OpenEoX/openeox#29 (comment)

This might be something for @santosomar to respond to...

[santosomar]

I believe that @captn3m0 is already a TC member.

[santosomar]

We can start a document to start defining some of the following:

• Software End-of-life
• Hardware End-of-life
• Software End-of-sales (in open source, there will not be an end-of-sales)
• Hardware End-of-sales (in open source, there will not be an end-of-sales)
• End-of-software maintenance or vulnerability support
• Last date of support (i.e., End-of-Support)

[santosomar]

I started a rough draft of some of the definitions at: #13

Please edit/add/remove, as needed.