search

oasis-tcs / openeox

OASIS OpenEoX TC: The purpose of this repository is to support version control for Work Product artifacts developed by members of the OASIS OpenEoX TC, including prose specification editing and secondary artifacts like meeting minutes, productivity code, etc.
Other
13 stars 6 forks source link

Define which EoX states are in and out of scope #7

Open kvandecr opened 11 months ago

kvandecr commented 11 months ago

For different orgs, EoX can mean different things: end of development, end of vulnerability support, end of sales.
We should collect the different states that we would want to cover in this standard and define them unambiguously

Break out into #11 and #12

santosomar commented 9 months ago

Instead of out-of-scope only. We should start deciding on what fields/states should be optional and mandatory. This way we can be more inclusive of some states, but make them optional.

tschmidtb51 commented 9 months ago

I think, we need to define the terms that we want to use...