| *** paulsherwood has quit IRC | 08:36 | |
| *** paulsherwood has joined #trustable | 08:37 | |
| *** paulsherwood has quit IRC | 08:40 | |
| *** paulsherwood has joined #trustable | 08:44 | |
| *** paulsherwood has joined #trustable | 08:47 | |
| *** paulsherwood has quit IRC | 08:56 | |
| *** paulsherwood has joined #trustable | 08:59 | |
| *** toscalix has joined #trustable | 09:00 | |
| *** sambishop has joined #trustable | 09:51 | |
| *** sambishop has quit IRC | 09:59 | |
| *** sambishop has joined #trustable | 09:59 | |
| *** sam_ has joined #trustable | 10:00 | |
| *** sambishop has quit IRC | 10:00 | |
| *** sam_ has quit IRC | 10:01 | |
| *** sambishop has joined #trustable | 10:01 | |
| *** sambishop has quit IRC | 13:03 | |
| * paulsherwood didn't quite understand the answer to "are we clear about how best to express 'intents' yet?" | 13:34 | |
| paulsherwood | as a stakeholder for trustable, i'd like to attempt to describe some intents | 13:34 |
|---|---|---|
| persia | Quick summary: "no". | 13:35 |
| paulsherwood | shall i write them as bullet-points, or something else? | 13:35 |
| * paulsherwood assumes that we don't expect stakeholders to create identifiers etc | 13:35 | |
| persia | For now, my recommendation (unvalidated) is to write them in a text file (bullet points is fine, as is list of sentences or whatever), and put them in a repo in which you expect them to be analysed. | 13:36 |
| paulsherwood | right. do i need to order the list, agile style, or not? | 13:36 |
| persia | Since there are N ways to map constraints to intents, it is probably best to leave that mapping to the analysts. | 13:36 |
| persia | I think that depends on your analysts. My presumption is that they will be free to cause your list to be numbered (or whatever) in the course of their analysis. | 13:36 |
| paulsherwood | ok | 13:37 |
| persia | For confirmation of validitiy, I think best practice is to submit a candidate change with your intents, have the analysis done as an update to that change pre-merge, after which the merge can include an atomic revision to intents and constraints in the repo. | 13:38 |
| persia | But I'm not sure if trustable.gitlab.com supports allowing analysts to modify a pull request from a stakeholder prior to merge. | 13:39 |
| *** sambishop has joined #trustable | 14:15 | |
| *** sambishop has quit IRC | 14:22 | |
| *** sambishop has joined #trustable | 14:41 | |
| *** sambishop has quit IRC | 14:55 | |
| *** sambishop has joined #trustable | 15:28 | |
| *** sambishop has quit IRC | 15:30 | |
| *** toscalix has quit IRC | 17:02 | |
| *** sambishop has joined #trustable | 17:02 | |
| *** sambishop has quit IRC | 17:16 | |
| *** milloni has quit IRC | 17:35 | |
| *** milloni has joined #trustable | 17:35 | |
| *** milloni has quit IRC | 17:37 | |
| *** milloni has joined #trustable | 17:37 | |
| *** sambishop has joined #trustable | 17:52 | |
| *** milloni has quit IRC | 18:11 | |
| *** milloni has joined #trustable | 18:11 | |
| *** sambishop has quit IRC | 18:20 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!