Every vote counts! On 27/08/2019, 12:44, "Howard Kitto" <[email protected]> wrote:
I guess I’m too late but it gets +1 from me
Howard Kitto
Qredo
Chief Technology Officer
[email protected]
> On 27 Aug 2019, at 11:24, Brian Spector <[email protected]> wrote:
>
> I vote +1.
>
> Folks, I'm taking the unusual step of now closing the vote. We have
discussed contributing the new D-TA over the dev channel for the last couple of
months and there has been no disagreement as to our need to go forward with
this.
>
> I will now:
>
> a) send a [RESULT] email into the channel
> b) create and update the IP clearance forms in subversion on
incubator/public/trunk/content/ip-clearance/
> c) send an email into general@incubator to ask for lazy consensus which
should last 72 hours
>
> Thanks
> Brian
>
> On 27/08/2019, 11:23, "Stanislav Mihaylov" <[email protected]> wrote:
>
> I vote +1
>
> [x ] +1 Accept this donation.
>
> On Tue, Aug 27, 2019 at 11:56 AM Brian Spector
<[email protected]>
> wrote:
>
>> Hi All,
>>
>> A few days ago we received a code donation from Howard [1] that falls
>> under his ICLA and the CCLA from Qredo.
>> This donation contains the 'in development' alpha version of the new
>> Decentralized Trust Authority software client which we would like to
>> release broadly in a series of staged releases until a final GA version
in
>> Q4. We would like to get the alpha release out asap, followed by a beta,
>> then an RC1 and finally a GA version.
>>
>> The vision is that the D-TA will be the server process that functions as
>> the master key generation server for a) issuing Type-3 pairing/identity
>> based secrets for M-Pin clients and servers (the original D-TA version)
and
>> b) safeguard shares of secrets like Bitcoin private keys.
>>
>> The problem with the initial version of the M-Pin client/server code into
>> Milagro was that there was no standardized REST API method to issue
>> identity based secrets for M-Pin clients and servers, and the Trust
>> Authority was conflated with the authentication server. This new donation
>> fixes that design limitation and enables a broader set of functional use
>> cases to be addressed, particular for protecting cryptocurrency private
>> keys.
>>
>> Because this D-TA is developed outside of the ASF version control and
>> mailing list, this donation will need to be formally accepted and follow
>> the IP clearance procedure [2].
>>
>> I would like to start a formal vote on accepting this code. If the vote
is
>> successful I will start with the IP clearance.
>>
>> Please vote:
>>
>> [ ] +1 Accept this donation.
>> [ ] 0 Don't care
>> [ ] -1 Don't accept this donation (please motivate your vote).
>>
>> Greetings,
>> Brian
>>
>> [1]:
>>
https://github.com/apache/incubator-milagro-dta/commit/e1067aef61dc0b2a523348dc9b71eb578983c9ee
>> [2]: http://incubator.apache.org/ip-clearance/
>>
>
smime.p7s
Description: S/MIME cryptographic signature
