On Wed, Aug 31, 2016 at 12:08:54PM -0400, Stephen Michel wrote:
> On August 31, 2016 6:38:46 AM EDT, Bryan Richter wrote:
> >On Sat, Aug 20, 2016 at 10:03:38AM -0400, Stephen Michel wrote:
> >> On August 20, 2016 8:27:09 AM EDT, mray wrote:
> >> >On 16.08.2016 00:03, Aaron Wolf wrote:
> >> >> On 08/10/2016 01:27 AM, mray wrote:
> >> >>>
> >> >>> We should be able to promise: "Fees are never over 10%.
> >> >>> Ever." That will always make sense and does not seem
> >> >>> arbitrary.
> >> >>
> >> >> Where are we tracking design decisions like this so that we
> >> >> know what the plan is once we get to implementing or even just
> >> >> mocking things up?
> >> >
> >> >I don't know we are doing this at all. But you're right, we
> >> >probably should do.
> >>
> >> Imo we should do this in the wiki. Using any other location adds
> >> the additional work of making sure that the wiki is up to date
> >> with the other location.
> >
> >Actually, I've been using Issues to capture decisions. See e.g.
> >"Communicate that fees will never be more than 10% of a total
> >charge":
> >
> >https://tree.taiga.io/project/snowdrift/issue/461
> >
> >I believe that capturing requirements out of discussions should be
> >an accountability of the project and/or product managers. I've been
> >doing it, however imperfectly.
> 
> I think we're on the same page here. I was talking about capturing
> requirements, not the discussions themselves (which I agree should
> be in issues).

Are we? :) The discussion is happening on the mailing list, that's
fine. It can happen on issues, too. It will also happen in meetings,
in person, and (eventually) on Discourse. I don't want to limit where
discussions can happen; I want a habit of capturing their outcomes.
Issues is often the correct place for that. Often, part of "resolving"
the Issue will be to document the decision in the wiki. But that is a
whole task unto itself, and doesn't qualify as "capture".

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Discuss mailing list
Discuss@lists.snowdrift.coop
https://lists.snowdrift.coop/mailman/listinfo/discuss

Reply via email to