On 30.11.2023 23:57, Tamas K Lengyel wrote: > I think this form is bad and is not helpful. We ought to be able to > recommend an alternative term beside "broken" and "deprecated". I > would not use the term broken in this context but that also doesn't > mean we shouldn't use it in any context. But also in this context > deprecated is not the right term to use either since deprecated would > require us to actually make the old hypercalls stop working altogether > at some future point, which we won't ever do AFAIU. My vote would be > to use the term superseded in this context, which I can't express > clearly in the form so I'm not going to cast a vote.
+1 This really supports my earlier voiced concern that reducing things too much for "ease" of voting isn't helpful. (That said, I don't share Tamas'es view on the use of "deprecated".) Jan > On Thu, Nov 30, 2023 at 5:28 PM Stefano Stabellini > <sstabell...@kernel.org> wrote: >> >> Hi all, >> >> This vote is in the context of this thread: >> https://marc.info/?l=xen-devel&m=169213351810075 >> >> >> On Thu, 30 Nov 2023, Kelly Choi wrote: >>> Hi all, >>> There have been a few discussions about how we use documentation wording >>> within the community. Whilst there are differences in opinions and >>> perceptions of the definition, it would be helpful to see a wider consensus >>> of how we feel. >>> >>> Discussion: Should we use the term 'broken' in our documentation, or do you >>> think an alternative wording would be better? If you agree or >>> disagree, please vote as this will impact future discussions. >>> >>> I have purposely made the vote between two options to help us move in a >>> forward direction. >>> >>> PLEASE VOTE HERE. Deadline 15th December 2023. >>> Your name will be required but will be private. If you answer anonymously, >>> your vote will not count. This is to ensure it is fair and each >>> person gets one vote. >>> >>> As an open-source project, we need to come to a common ground, which >>> sometimes means we may not personally agree. To make this fair, please >>> note the final results will be used to determine our future actions within >>> the community. >>> >>> If the majority votes for/against, we will respect the majority and >>> implement this accordingly. >>> >>> Many thanks, >>> Kelly Choi >>> >>> Xen Project Community Manager >>> XenServer, Cloud Software Group >>> >>>
