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

My approach would be, when in doubt create a new issue.
i.e. Favour more issues over many topics in a single conversations

I agree that a threaded conversation per issue is the ideal way to track,
work on and ultimately close out topics that the group must reach consensus
on.

I was actually just thinking that the thread about the abstract
architecture should be split into a few issues.



On 26 November 2015 at 15:47, Telford-Reed, Nick <
Nick.Telford-Reed@worldpay.com> wrote:

> Manu
>
> I was thinking about doing something similar (hence the "todo" - I know
> some of the issues are being actively discussed as github issues.)
>
> Folks on the mailing list - preferences for how we work on this? Decompose
> list to individual issues pre-emptively? Or do dynamically as someone
> choose to lead off a debate? The latter has a neat sense of progress - we
> will know that we have actually looked at all the issues on the list when
> someone has created an issue because someone has something to say about it.
>
> Nick
>
> --
> Nick Telford-Reed
> e: nick.telford-reed@worldpay.com | m: +447799473854 | t: +44 203 664 5069
>
> > -----Original Message-----
> > From: Manu Sporny [mailto:msporny@digitalbazaar.com]
> > Sent: 26 November 2015 12:55
> > To: public-payments-wg@w3.org
> > Subject: Re: New wiki article: TPAC 2015 issues list (was RE:
> wpwg-ACTION-8:
> > Move google docs list of issues to github wiki)
> >
> > On 11/25/2015 10:24 AM, Telford-Reed, Nick wrote:
> > > You can find the new page here:
> > > https://github.com/w3c/webpayments/wiki/TPAC-2015-issues-list
> >
> > Thanks for doing that Nick. :)
> >
> > I think we should put each of those questions in the WPWG issue tracker
> > because:
> >
> > * it will help us have a nice threaded conversation on each of the
> >   issues (that is also reflected to the mailing list)
> > * it'll help us track how the conversation on each point is progressing
> >   (where it started, where it is today)
> > * it'll help us tag and track each issue independently of the specs
> >   themselves (which many of these issues are spec-independent)
> >
> > https://github.com/w3c/webpayments/issues
> >
> > I'm happy to convert all of them to Github issues, if there isn't strong
> push-
> > back on this approach.
> >
> > -- 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/
> >
>
> This e-mail and any attachments are confidential, intended only for the
> addressee and may be privileged. If you have received this e-mail in error,
> please notify the sender immediately and delete it. Any content that does
> not relate to the business of Worldpay is personal to the sender and not
> authorised or endorsed by Worldpay. Worldpay does not accept responsibility
> for viruses or any loss or damage arising from transmission or access.
>
> Worldpay (UK) Limited (Company No: 07316500/ Financial Conduct Authority
> No: 530923), Worldpay Limited (Company No:03424752 / Financial Conduct
> Authority No: 504504), Worldpay AP Limited (Company No: 05593466 /
> Financial Conduct Authority No: 502597). Registered Office: The Walbrook
> Building, 25 Walbrook, London EC4N 8AF and authorised by the Financial
> Conduct Authority under the Payment Service Regulations 2009 for the
> provision of payment services. Worldpay (UK) Limited is authorised and
> regulated by the Financial Conduct Authority for consumer credit
> activities. Worldpay B.V. (WPBV) has its registered office in Amsterdam,
> the Netherlands (Handelsregister KvK no. 60494344). WPBV holds a licence
> from and is included in the register kept by De Nederlandsche Bank, which
> registration can be consulted through www.dnb.nl. Worldpay, the logo and
> any associated brand names are trade marks of the Worldpay group.
>