They aren't possible, but maybe are necessary.
I agree that all the items listed in here aren't possible given the time allotted for development, and I haven't tried to integrate any of them into the main feature set to avoid feature creep. However, some of them are going to be necessary, and early users may need to realize that some out-of-band workarounds will be necessary in the first version, because the features listed here were, well, necessary. :)
This commit is contained in:
parent
5d36d905e5
commit
d921c03d6f
1 changed files with 3 additions and 3 deletions
|
@ -146,9 +146,9 @@ built.
|
|||
## Requirements for later releases
|
||||
|
||||
These are features that we would ultimately like the system to have, but we
|
||||
know aren't necessary for the first version. It's good to keep them in mind
|
||||
when architecting, but also to know that they've been considered and aren't
|
||||
immediately necessary.
|
||||
know aren't possible for the first version given time allotted for its
|
||||
development. It's good to keep them in mind when architecting, but also to
|
||||
know that they've been considered and aren't immediately possible.
|
||||
|
||||
* Allow optional questions: With this, question conditions probably need to
|
||||
be extended to address the case of "other question isn't answered"
|
||||
|
|
Loading…
Reference in a new issue