- From: Phil J. Laszkowicz <phil@fillip.pro>
- Date: Tue, 10 Jun 2014 17:19:23 +0100
- To: Joseph Potvin <jpotvin@opman.ca>
- Cc: Timothy Holborn <timothy.holborn@gmail.com>, Kingsley Idehen <kidehen@openlinksw.com>, Web Payments CG <public-webpayments@w3.org>
Agreed. In that respect, can we just clarify what those terms are? Perhaps it's just me, but I can't find the open source license. > On 10 Jun 2014, at 17:12, Joseph Potvin <jpotvin@opman.ca> wrote: > > Okay. More explicitly then, I'll suggest that your original statement > be adjusted as follows: > > I think the fact the solution is available on free/libre/open terms > significantly influences whether or not it may be suitable as a > reference implementation of an open standard specification. > > Joseph > > On Tue, Jun 10, 2014 at 11:41 AM, Timothy Holborn > <timothy.holborn@gmail.com> wrote: >> Um... Statement made was.. >> >> " >> >> I think the fact the solution is available on Github, significantly >> >> influences the rational surrounding whether or not it’s starting out to be a >> >> workable solution… >> >> " >> Sent from my iPad >> >> On 11 Jun 2014, at 1:21 am, "Phil J. Laszkowicz" <phil@fillip.pro> wrote: >> >> I think the fact the solution is available on Github, significantly >> >> influences the rational surrounding whether or not it’s starting out to be a >> >> workable solution… > > > > -- > Joseph Potvin > Operations Manager | Gestionnaire des opérations > The Opman Company | La compagnie Opman > jpotvin@opman.ca > Mobile: 819-593-5983 >
Received on Tuesday, 10 June 2014 16:19:54 UTC