Meeting minutes
notes on meeting:
* not a formal meeting, but Ege and I reviewed PR2053 in the TD repo and discussed the user story approach.
* agreed to follow up in tomorrow's TD call.
main points:
* there can be multiple stakeholders, but the "Who" in the user story is the one who "wants" the feature for the stated purpose ("why") - there can, however, be other stakeholders who might be negatively impacted, too (even if just to do the work of implementation or spec writing).
* also, we every user story needs to link from "Why" to at least one use case or use case category - one needs to be created iff there is not already one on file.
* the "what" part can link to MD files in github for "work in progress" but when the work is done can be replaced by links to assertions. Still to be decided is whether we maintain links to the details in MD files.
* as for technical details, we agreed that detailed technical motivations and design principles can go into the spec documents themselves - the user story would just be a high-level summary of the intent and motivation.