Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Define Common Taxonomy #11

Open
kvandecr opened this issue Jan 24, 2024 · 5 comments · May be fixed by #13
Open

Define Common Taxonomy #11

kvandecr opened this issue Jan 24, 2024 · 5 comments · May be fixed by #13
Labels
help wanted Extra attention is needed tc-discussion Further TC discussion is needed

Comments

@kvandecr
Copy link

Split off from #7

create unambiguous definitions for the different states a product can be in such as "End Of Life", "End Of Development", ...
@kvandecr kvandecr mentioned this issue Jan 24, 2024
Open
@tschmidtb51 tschmidtb51 mentioned this issue Jan 24, 2024
Draft
@kvandecr kvandecr changed the title Common Taxonomy Define Common Taxonomy Jan 24, 2024
@tschmidtb51
Copy link
Contributor

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
Copy link
Contributor

tschmidtb51 commented Jan 24, 2024 •
edited

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
Copy link
Contributor

I believe that @captn3m0 is already a TC member.

@santosomar
Copy link
Contributor

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 added a commit that referenced this issue Jan 24, 2024
@santosomar
Create definitions.md
2cbcea1 
This document **draft** aims to clearly define key terms related to the lifecycle of software and hardware products, providing a reference for understanding various phases from sales or creation to support termination. 

This is just a starting point and the TC will provide additional edits, inputs, etc.

Fixes #11
@santosomar santosomar linked a pull request Jan 24, 2024 that will close this issue
Open
@santosomar
Copy link
Contributor

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

Please edit/add/remove, as needed.

@santosomar santosomar added help wanted Extra attention is needed tc-discussion Further TC discussion is needed labels Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed tc-discussion Further TC discussion is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Create definitions.md oasis-tcs/openeox
3 participants
@santosomar @tschmidtb51 @kvandecr