maturity and status and attributes, oh my!
Quoted 11 lines · Robert P. J. Day
at the risk of driving everyone here totally bonkers, i'm going to
take one last shot at explaining what i was thinking of when i first proposed this whole "maturity level" thing. and, just so you know, the major reason i'm so cranked up about this is that i'm feeling just a little territorial -- i was the one who first started nagging people to consider this idea, so i'm a little edgy when i see folks finally giving it some serious thought but appearing to get ready to implement it entirely incorrectly in a way that's going to ruin it irreparably and make it utterly useless.
Quoted 9 lines
this isn't just about defining a single feature called "maturity".
it's about defining a general mechanism so that you can add entirely new (what i call) "attributes" to kernel features. one attribute could be "maturity", which could take one of a number of possible values. another could be "status", with the same restrictions. heck, you could define the attribute "colour", and decide that various kernel features could be labelled as (at most) one of "red", "green" and "chartreuse." that's what i mean by an "attribute", and attributes would have two critical and non-negotiable properties:
<<< snip>>>>
Quoted 8 lines
but i hope i've flogged this thoroughly to the point where people
can see what i'm driving at. once you see (as in simon's patch) how to add the first attribute, it's trivial to simply duplicate that code to add as many more as you want.rday
Quoted 8 lines
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADAhttp://crashcourse.ca
========================================================================
Robert Day,
If I can interpret what you are asking about and changing it abit.
Don't you think that Maturity can be defined ALSO, as the
number of known bugs and their priority / serverity against a architecture dependent or independent item?
Would this suffice and wouldn't it be easier to maintain?
Mitchell Erblich
Quoted 42 lines · Mitchell Erblich
Quoted 11 lines · Robert P. J. Day
at the risk of driving everyone here totally bonkers, i'm going to
take one last shot at explaining what i was thinking of when i first proposed this whole "maturity level" thing. and, just so you know, the major reason i'm so cranked up about this is that i'm feeling just a little territorial -- i was the one who first started nagging people to consider this idea, so i'm a little edgy when i see folks finally giving it some serious thought but appearing to get ready to implement it entirely incorrectly in a way that's going to ruin it irreparably and make it utterly useless.Quoted 9 lines
this isn't just about defining a single feature called "maturity".
it's about defining a general mechanism so that you can add entirely new (what i call) "attributes" to kernel features. one attribute could be "maturity", which could take one of a number of possible values. another could be "status", with the same restrictions. heck, you could define the attribute "colour", and decide that various kernel features could be labelled as (at most) one of "red", "green" and "chartreuse." that's what i mean by an "attribute", and attributes would have two critical and non-negotiable properties:<<< snip>>>>
Quoted 8 lines
but i hope i've flogged this thoroughly to the point where people
can see what i'm driving at. once you see (as in simon's patch) how to add the first attribute, it's trivial to simply duplicate that code to add as many more as you want.rday
Quoted 8 lines
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADAhttp://crashcourse.ca
========================================================================Robert Day,
If I can interpret what you are asking about and changing it abit.
Quoted 7 lines
Don't you think that Maturity can be defined ALSO, as the
number of known bugs and their priority / serverity against a architecture dependent or independent item?Would this suffice and wouldn't it be easier to maintain?
Mitchell Erblich
perhaps. all i'm begging for is that these attributes be defined cleanly and clearly, and following those two conditions i suggested earlier:
1) all attributes are orthogonal to one another, and
2) values within an attribute are mutually exclusive
if you violate either of those conditions, i think you're going to find it very difficult to design sane Kconfig entries around them. if you don't believe me, give it a try.
rday
p.s. rather than saying that maturity can be defined "also" in another way, you should say that it can be defined "instead" in another way. i don't want to think what it might mean to define something like maturity in two different ways simultaneously, if that's what you were suggesting. that just makes my brain hurt.
Signature · 7 lines
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca ========================================================================
Quoted 6 lines · Robert P. J. Day
perhaps. all i'm begging for is that these attributes be defined cleanly and clearly, and following those two conditions i suggested earlier:
1) all attributes are orthogonal to one another, and
This "orthogonal" argument is reserved for the cdrecord maintainer;
I cannot figure out what you mean by orthogonal. If A is orthogonal to B and B is orthogonal to C, then A is parallel to C. If there are more objects than dimensions, at least one pair of them is not orthogonal. That is what orthogonal means to me ;-)
Jan
Quoted 7 lines · Jan Engelhardt
Quoted 5 lines · Robert P. J. Day
perhaps. all i'm begging for is that these attributes be defined cleanly and clearly, and following those two conditions i suggested earlier:
Quoted 8 lines
Quoted 1 line
1) all attributes are orthogonal to one another, and
This "orthogonal" argument is reserved for the cdrecord maintainer;
I cannot figure out what you mean by orthogonal. If A is orthogonal to B and B is orthogonal to C, then A is parallel to C. If there are more objects than dimensions, at least one pair of them is not orthogonal. That is what orthogonal means to me ;-)
you're being too literal in a purely mathematical sense.
"orthogonality" has a much more general definition in the context of computer science -- see here:
http://dict.die.net/orthogonal/
"The term is used loosely to mean mutually independent or well separated. It is used to describe sets of primitives or capabilities that, like linearly independent vectors in geometry, span the entire "capability space" and are in some sense non-overlapping or mutually independent."
and here:
"Computer science
"Orthogonality is a system design property facilitating feasibility and compactness of complex designs. Orthogonality guarantees that modifying the technical effect produced by a component of a system neither creates nor propagates side effects to other components of the system."
in the case of Kconfig "attributes", a set of orthogonal attributes
might be a variable's maturity, its colour and its flavour (i'm just making those last two up, of course). and each of those clearly orthogonal attributes is allowed to have at most one value, and that value is entirely independent of what the value is of any of the *other* attributes for that kernel feature.
i'm harping on this because it seems to me that lumping together
values such as experimental, deprecated, obsolete and broken in a single attribute is creating a dangerously ill-defined attribute that's trying to do two things at once -- identify both a variable's "age", if you will, and its current code quality. and i'm simply arguing that those are two different things and, if you do that, it would prevent you from saying that some kernel feature is both experimental *and* broken.
note: the above is assuming that an attribute is *defined* as being
allowed to have at most one possible value at a time, as in deprecated *or* obsolete, and never deprecated *and* obsolete. if you go down that second road, very bad things await you.
rday
Signature · 7 lines
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca ========================================================================