Re: New wiki article: TPAC 2015 issues list (was RE: wpwg-ACTION-8: Move google docs list of issues to github wiki)

Manu,

In looking at the list on the wiki I don't think these are ready to be
captured as issues yet in the issue tracker.

Rather than fill the issue tracker up prematurely let's discuss an approach
to filtering and refining this list on Thursdays call and then assign some
actions to have them captured as issues.

I also think we will have more luck in dealing with issues once we have the
start of a spec to refer to and the impact of the different ways of
addressing the issue are more clear.

I will put this on Thursday's agenda.

Adrian

On 29 November 2015 at 20:56, Adrian Hope-Bailie <adrian@hopebailie.com>
wrote:

>
> On 28 November 2015 at 22:22, Manu Sporny <msporny@digitalbazaar.com>
> wrote:
>
>> On 11/27/2015 06:00 AM, Adrian Hope-Bailie wrote:
>> > My approach would be, when in doubt create a new issue. i.e. Favour
>> > more issues over many topics in a single conversations
>>
>> +1
>>
>> > I was actually just thinking that the thread about the abstract
>> > architecture should be split into a few issues.
>>
>> +1
>>
>
> Will find some time to do this this week.
>
>
>>
>> There are a number of issues that I've been biting my tongue on for over
>> a year that I feel the group really needs to get their mind wrapped
>> around. These issues will affect the design of the various messages and
>> APIs. The sooner we start talking about these issues, the better. I've
>> been holding off on discussing them until we put them into the issue
>> tracker.
>>
>> Would there be any objection to me championing some of these issues
>> starting on Tuesday?
>>
>
> Not from me
>
>
>>
>> -- manu
>>
>> --
>> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
>> Founder/CEO - Digital Bazaar, Inc.
>> blog: Web Payments: The Architect, the Sage, and the Moral Voice
>> https://manu.sporny.org/2015/payments-collaboration/
>>
>>
>