Changeset - f9cb44d5f49c
[Not reviewed]
0 1 0
Brett Smith (brett) - 5 years ago 2016-08-31 18:04:15
brett@sfconservancy.org
Better explain the functionality line between first and later releases.
1 file changed with 7 insertions and 4 deletions:
0 comments (0 inline, 0 general)
Reimbursements/Requirements.mdwn
Show inline comments
...
 
@@ -137,10 +137,13 @@ built.
 

	
 
## Requirements for later releases
 

	
 
These are features that we would ultimately like the system to have, but we
 
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.
 
These are features that we would ultimately like the system to have.  We
 
would also like to release a first version as early as possible, to start
 
getting feedback from users and generating more development interest.  It's
 
good to keep these in mind when architecting—in particular, we may choose an
 
existing system to use, or framework to build on, based on its ability to
 
support these features.  However, they needn't be a focus of development
 
effort for the first release.
 

	
 
* Allow optional questions: With this, question conditions probably need to
 
be extended to address the case of "other question isn't answered"
0 comments (0 inline, 0 general)