j---

OK, thanks. Good point we don't need to handle UI questions here. Agree. Is `deprecated = True` useful without a reference to what it is deprecated by? Just putting pressure...

Thanks! > (E.g., all the CVSS vector elements as decision points), and those seem like they are more "proposed" than "supported" I might propose these are "informational". I'm trying to...

> proposing informational as a distinct state from proposed, supported, and deprecated, or I was thinking this first one. Of course we will accept bug fixes and typos to things...

Thanks for expanding this out. Here's my thoughts on the difference (using these labels for now, point taken we may rename them once we decide what the SLEs actually mean)...

> I suppose while we're thinking about this kind of state machine, we should probably be working towards one that works for any of the formally-versioned things (Decision Points, Decision...

Maybe we could simplify with a "supported --> available --> deprecated" workflow. And things that I've been thinking about as "informational" just enter directly into available status. Creation / proposal...

Something like this, yes. In this case, I think we also have the opportunity to chat with the FIRST framework authors and get their feedback after we draft it.

Prefer to introduce this once we have time to make it into a how-to section.

Those PDFs are generated from LaTeX, specifically TikZ diagrams. There is already python that takes a CSV and generates the TikZ/LaTeX. Would it be easier to hook the TikZ into...

How much do we want the "Not Important+Not Urgent" category to translate to our *Defer* outcome? Whatever the term, the Eisenhower matrix terms are more aggressive about removing that category...