e-lo
commented
9 years ago @fscottfoti - it seems a little strange to put a bunch of user stories into a singular issue and have it stay open for eternity.
After the tests are suggested and decided upon in this issue, do you think we can create a .md document within the codebase that documents the "how to" for each of these stories? If the "how to" is cumbersome for any of these stories, then that would be an indication that maybe this isn't the best way of doing things (or that there needs to be a significant upside in some other category).
An alternative would be to just list them in a wiki and come back to them every once and a while. The downside here is that it isn't linked as elegantly to the code version.
jiffyclub
fscottfoti
A suggestion was made on Friday to start making a list of "user stories," or perhaps more specifically, those things that users of the modeling system might want to change for different implementations or different scenarios. These are things that we want to be able to change easily, version control those changes, and not have to change any core parts of the model system in order to do so. Perhaps this issue can be the place to collect those stories?