[Gnu-arch-users] GNU arch design process

[Tom Lord]

I replied to jblack with the enclosed list of questions.

If we can't cool off and return to productivity the mailing list
discussions, perhaps we should add a little bit of structure to help
them out.  E.g., a list of such questions that new proposals ought to
(not required to --- just informally ought to) explicitly address.

(Some of my questions to jblack are specific to his specific proposal
but some apply to all proposals.)

-t


    > Date: Sat, 28 Aug 2004 12:48:50 -0700 (PDT)
    > From: Tom Lord <address@hidden>
    > CC: address@hidden
    > 
    > 
    >     > From: address@hidden (James Blackwell)
    > 
    >     > ddaa and I put our heads together not long ago, and we came up with 
a new
    >     > feature that would probably help programs like pyarch and aba. This 
new
    >     > command, called "tla features" would list features and feature 
version
    >     > numbers. One could also query either for a specific feature, or a 
specific
    >     > version of a feature. Please see the example output at the end of 
this
    >     > email.
    > 
    > How would user's benefit from such a feature?  How would it make arch
    > better?  Why is it important to work on now?  What is the definition
    > of "a feature"?  How do implementors know whether or not they should
    > say that such-and-such a feature is present?  Who shall be the
    > arbitrator of "feature names"?   How does this relate to the idea of
    > standardizing arch with formal standards docs?
    > 
    > -t
    > 
    > 
    >