hat
>> level of detail.
>>
>> Now, for addressing the comments, I think we should just split them up by
>> topic into issues for the repository, and then address them one by one.
>>
>> Thanks again!
>>
>> Cheers,
>> Michael
>>
6, 2020, at 9:30 PM, Martin Duke wrote:
>
> Here is my promised "no prior knowledge" review of taps-interface. I
> haven't filed issues for these yet, as I suspect some of these have already
> been well-litigated there.
>
> The only other draft I've read is taps-arch.
>
into issues for the repository, and then address them one by one.
Thanks again!
Cheers,
Michael
> On Aug 6, 2020, at 9:30 PM, Martin Duke wrote:
>
> Here is my promised "no prior knowledge" review of taps-interface. I haven't
> filed issues for these yet, as I suspect some
Here is my promised "no prior knowledge" review of taps-interface. I
haven't filed issues for these yet, as I suspect some of these have already
been well-litigated there.
The only other draft I've read is taps-arch.
*High level comments*:
(1) I think this conceptually headed in
