@@ -137,27 +137,27 @@ built.
Whether or not we do this in the first release probably depends on what
framework we decide to build on. If the framework itself requires
JavaScript out of the box, it may make sense to have the first release go
with the flow, then work to add JavaScript-free functionality in a later
release.
In any case, Javascript used will respect software freedom of users and, *if
possible*, will adhere to LibreJS protocols.
## 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"
* Additional exporters:
* Export to SQLedger
* [Certainly many more, feel free to add them here]
* Richer lifecycle management: A leader may need to approve a request before
it's added to the books, like an employee's manager or a program director
* Various currency improvements: