You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@milagro.apache.org by Kealan Mccusker <ke...@miracl.com> on 2017/02/24 15:26:37 UTC
milagro-crypto-c
Hi All
We have a repo (below) that is currently on the Miracl GitHub account and
it is part of the Apache Milagro project. For operational reasons we would
like to maintain this repo on the Miracl GitHub account and make it public.
Would this be be OK with the dev community? May I propose a vote?
The milagro-crypto-c should remain on Miracl GitHub: me +1
https://github.com/miracl/milagro-crypto-c
Regards
Kealan
RE: milagro-crypto-c
Posted by Simeon Aladjem <si...@miracl.com>.
+1
Mony
-----Original Message-----
From: Patrick Hilt [mailto:patrick.hilt@miracl.com]
Sent: Friday, February 24, 2017 18:47
To: dev@milagro.incubator.apache.org
Subject: Re: milagro-crypto-c
+1
Alternatively, would it be ok for the community if a GitHub account is
opened for Milagro and the milagro-crypto-c repo is moved there? I believe
that hosting Milagro repos on GitHub would help this community to make more
progress.
Cheers,
Patrick
On Fri, Feb 24, 2017 at 4:26 PM, Kealan Mccusker <kealan.mccusker@miracl.com
> wrote:
> Hi All
>
> We have a repo (below) that is currently on the Miracl GitHub account
> and it is part of the Apache Milagro project. For operational reasons
> we would like to maintain this repo on the Miracl GitHub account and make
> it public.
> Would this be be OK with the dev community? May I propose a vote?
>
> The milagro-crypto-c should remain on Miracl GitHub: me +1
>
> https://github.com/miracl/milagro-crypto-c
>
> Regards
>
> Kealan
>
Re: milagro-crypto-c
Posted by Alessandro Budroni <bu...@gmail.com>.
+1, I agree too!
On Feb 24, 2017 7:06 PM, "Nicola Asuni" <ni...@miracl.com> wrote:
> +1 for me.
>
> On 24 Feb 2017 16:47, "Patrick Hilt" <pa...@miracl.com> wrote:
>
> > +1
> >
> > Alternatively, would it be ok for the community if a GitHub account is
> > opened for Milagro and the milagro-crypto-c repo is moved there? I
> believe
> > that hosting Milagro repos on GitHub would help this community to make
> more
> > progress.
> >
> > Cheers,
> > Patrick
> >
> > On Fri, Feb 24, 2017 at 4:26 PM, Kealan Mccusker <
> > kealan.mccusker@miracl.com
> > > wrote:
> >
> > > Hi All
> > >
> > > We have a repo (below) that is currently on the Miracl GitHub account
> and
> > > it is part of the Apache Milagro project. For operational reasons we
> > would
> > > like to maintain this repo on the Miracl GitHub account and make it
> > public.
> > > Would this be be OK with the dev community? May I propose a vote?
> > >
> > > The milagro-crypto-c should remain on Miracl GitHub: me +1
> > >
> > > https://github.com/miracl/milagro-crypto-c
> > >
> > > Regards
> > >
> > > Kealan
> > >
> >
>
Re: milagro-crypto-c
Posted by Nicola Asuni <ni...@miracl.com>.
+1 for me.
On 24 Feb 2017 16:47, "Patrick Hilt" <pa...@miracl.com> wrote:
> +1
>
> Alternatively, would it be ok for the community if a GitHub account is
> opened for Milagro and the milagro-crypto-c repo is moved there? I believe
> that hosting Milagro repos on GitHub would help this community to make more
> progress.
>
> Cheers,
> Patrick
>
> On Fri, Feb 24, 2017 at 4:26 PM, Kealan Mccusker <
> kealan.mccusker@miracl.com
> > wrote:
>
> > Hi All
> >
> > We have a repo (below) that is currently on the Miracl GitHub account and
> > it is part of the Apache Milagro project. For operational reasons we
> would
> > like to maintain this repo on the Miracl GitHub account and make it
> public.
> > Would this be be OK with the dev community? May I propose a vote?
> >
> > The milagro-crypto-c should remain on Miracl GitHub: me +1
> >
> > https://github.com/miracl/milagro-crypto-c
> >
> > Regards
> >
> > Kealan
> >
>
Re: milagro-crypto-c
Posted by Tomasz Matecki <to...@miracl.com>.
+1
Original Message
From: patrick.hilt@miracl.com
Sent: 24 February 2017 4:47 p.m.
To: dev@milagro.incubator.apache.org
Reply to: dev@milagro.incubator.apache.org
Subject: Re: milagro-crypto-c
+1
Alternatively, would it be ok for the community if a GitHub account is
opened for Milagro and the milagro-crypto-c repo is moved there? I believe
that hosting Milagro repos on GitHub would help this community to make more
progress.
Cheers,
Patrick
On Fri, Feb 24, 2017 at 4:26 PM, Kealan Mccusker <kealan.mccusker@miracl.com
> wrote:
> Hi All
>
> We have a repo (below) that is currently on the Miracl GitHub account and
> it is part of the Apache Milagro project. For operational reasons we would
> like to maintain this repo on the Miracl GitHub account and make it public.
> Would this be be OK with the dev community? May I propose a vote?
>
> The milagro-crypto-c should remain on Miracl GitHub: me +1
>
> https://github.com/miracl/milagro-crypto-c
>
> Regards
>
> Kealan
>
Re: milagro-crypto-c
Posted by Patrick Hilt <pa...@miracl.com>.
+1
Alternatively, would it be ok for the community if a GitHub account is
opened for Milagro and the milagro-crypto-c repo is moved there? I believe
that hosting Milagro repos on GitHub would help this community to make more
progress.
Cheers,
Patrick
On Fri, Feb 24, 2017 at 4:26 PM, Kealan Mccusker <kealan.mccusker@miracl.com
> wrote:
> Hi All
>
> We have a repo (below) that is currently on the Miracl GitHub account and
> it is part of the Apache Milagro project. For operational reasons we would
> like to maintain this repo on the Miracl GitHub account and make it public.
> Would this be be OK with the dev community? May I propose a vote?
>
> The milagro-crypto-c should remain on Miracl GitHub: me +1
>
> https://github.com/miracl/milagro-crypto-c
>
> Regards
>
> Kealan
>
Re: milagro-crypto-c
Posted by Brian Spector <br...@miracl.com>.
That's great. We should take advantage of this and push the code into the
apache repo as soon as possible.
Thanks for your help, Nick.
+1
On 9 March 2017 at 18:13, Nick Kew <ni...@apache.org> wrote:
> On Fri, 2017-02-24 at 15:26 +0000, Kealan Mccusker wrote:
> > Hi All
> >
> > We have a repo (below) that is currently on the Miracl GitHub account and
> > it is part of the Apache Milagro project. For operational reasons we
> would
> > like to maintain this repo on the Miracl GitHub account and make it
> public.
>
> We now have a new repo at apache. The process for creating it
> has changed: infra don't want to be responsible for IP clearance,
> so the project takes responsibility. That means we have an
> empty repo: someone will have to push the contents.
>
> Basic github mirroring is enabled by default. Additional integration
> should be requested through a jira servicedesk ticket: see
> https://reference.apache.org/pmc/github
>
> --
> Nick Kew
>
>
--
Brian Spector
CEO
MIRACL
T: +44 (0) 20 3389 8190
https://www.miracl.com
81 Rivington Street
London UK, EC2A 3AY
Registered in England and Wales 7017635
Re: milagro-crypto-c
Posted by Nick Kew <ni...@apache.org>.
On Fri, 2017-02-24 at 15:26 +0000, Kealan Mccusker wrote:
> Hi All
>
> We have a repo (below) that is currently on the Miracl GitHub account and
> it is part of the Apache Milagro project. For operational reasons we would
> like to maintain this repo on the Miracl GitHub account and make it public.
We now have a new repo at apache. The process for creating it
has changed: infra don't want to be responsible for IP clearance,
so the project takes responsibility. That means we have an
empty repo: someone will have to push the contents.
Basic github mirroring is enabled by default. Additional integration
should be requested through a jira servicedesk ticket: see
https://reference.apache.org/pmc/github
--
Nick Kew
Re: milagro-crypto-c
Posted by Kealan Mccusker <ke...@miracl.com>.
Hi Nick
This does supersede the existing repo. This is a C repo with language
wrappers for golang and Python.
Regards
Kealan
On Fri, Feb 24, 2017 at 10:00 PM, Nick Kew <ni...@apache.org> wrote:
> On Fri, 24 Feb 2017 15:26:37 +0000
> Kealan Mccusker <ke...@miracl.com> wrote:
>
> > Hi All
> >
> > We have a repo (below) that is currently on the Miracl GitHub account
> > and it is part of the Apache Milagro project. For operational reasons
> > we would like to maintain this repo on the Miracl GitHub account and
> > make it public. Would this be be OK with the dev community? May I
> > propose a vote?
> >
> > The milagro-crypto-c should remain on Miracl GitHub: me +1
> >
> > https://github.com/miracl/milagro-crypto-c
> >
>
> Does this replace/supersede anything in the existing
> milagro-crypto repo?
>
> I've just asked informally about the status of full two-way
> github integration, and I understand it's now being made
> available more widely. I'm not sure where we stand as an
> incubating project, but it's probably worth looking in
> to putting in a request for it.
>
> I have a horribly busy weekend, but will take a look next
> week if noone else gets there first.
>
> --
> Nick Kew
>
Re: milagro-crypto-c
Posted by Genoveffa Pagano <ge...@miracl.com>.
+1
(FWIW)
Genoveffa Pagano
VP of Product
MIRACL
T: +44 (0) 20 3389 08190
M: +44 (0) 7749 159 824
Skype: genoveffa.pagano
https://www.miracl.com
81 Rivington Street
London UK, EC2A 3AY
Registered in England and Wales 7017635
On 3 March 2017 at 13:28, Kealan Mccusker <ke...@miracl.com>
wrote:
> Hi All
>
> The results are below. As a week has passed can we take it that this motion
> as carried? Is this result recorded somewhere?
>
> For 7
> Against 0
>
> Regards
>
> Kealan
>
> On Mon, Feb 27, 2017 at 9:19 AM, Vladislav Mitov <
> vladislav.mitov@miracl.com
> > wrote:
>
> > +1
> >
> > Vladi
> >
> > On Mon, Feb 27, 2017 at 11:12 AM Kealan Mccusker <
> > kealan.mccusker@miracl.com>
> > wrote:
> >
> > > Hi Nick
> > >
> > > This does supersede the existing repo. It is a C repo with language
> > > wrappers for golang and Python.
> > >
> > > Regards
> > >
> > > Kealan
> > >
> > > On Fri, Feb 24, 2017 at 10:00 PM, Nick Kew <ni...@apache.org> wrote:
> > >
> > > > On Fri, 24 Feb 2017 15:26:37 +0000
> > > > Kealan Mccusker <ke...@miracl.com> wrote:
> > > >
> > > > > Hi All
> > > > >
> > > > > We have a repo (below) that is currently on the Miracl GitHub
> account
> > > > > and it is part of the Apache Milagro project. For operational
> reasons
> > > > > we would like to maintain this repo on the Miracl GitHub account
> and
> > > > > make it public. Would this be be OK with the dev community? May I
> > > > > propose a vote?
> > > > >
> > > > > The milagro-crypto-c should remain on Miracl GitHub: me +1
> > > > >
> > > > > https://github.com/miracl/milagro-crypto-c
> > > > >
> > > >
> > > > Does this replace/supersede anything in the existing
> > > > milagro-crypto repo?
> > > >
> > > > I've just asked informally about the status of full two-way
> > > > github integration, and I understand it's now being made
> > > > available more widely. I'm not sure where we stand as an
> > > > incubating project, but it's probably worth looking in
> > > > to putting in a request for it.
> > > >
> > > > I have a horribly busy weekend, but will take a look next
> > > > week if noone else gets there first.
> > > >
> > > > --
> > > > Nick Kew
> > > >
> > >
> >
>
Re: milagro-crypto-c
Posted by Kealan Mccusker <ke...@miracl.com>.
Hi All
The results are below. As a week has passed can we take it that this motion
as carried? Is this result recorded somewhere?
For 7
Against 0
Regards
Kealan
On Mon, Feb 27, 2017 at 9:19 AM, Vladislav Mitov <vladislav.mitov@miracl.com
> wrote:
> +1
>
> Vladi
>
> On Mon, Feb 27, 2017 at 11:12 AM Kealan Mccusker <
> kealan.mccusker@miracl.com>
> wrote:
>
> > Hi Nick
> >
> > This does supersede the existing repo. It is a C repo with language
> > wrappers for golang and Python.
> >
> > Regards
> >
> > Kealan
> >
> > On Fri, Feb 24, 2017 at 10:00 PM, Nick Kew <ni...@apache.org> wrote:
> >
> > > On Fri, 24 Feb 2017 15:26:37 +0000
> > > Kealan Mccusker <ke...@miracl.com> wrote:
> > >
> > > > Hi All
> > > >
> > > > We have a repo (below) that is currently on the Miracl GitHub account
> > > > and it is part of the Apache Milagro project. For operational reasons
> > > > we would like to maintain this repo on the Miracl GitHub account and
> > > > make it public. Would this be be OK with the dev community? May I
> > > > propose a vote?
> > > >
> > > > The milagro-crypto-c should remain on Miracl GitHub: me +1
> > > >
> > > > https://github.com/miracl/milagro-crypto-c
> > > >
> > >
> > > Does this replace/supersede anything in the existing
> > > milagro-crypto repo?
> > >
> > > I've just asked informally about the status of full two-way
> > > github integration, and I understand it's now being made
> > > available more widely. I'm not sure where we stand as an
> > > incubating project, but it's probably worth looking in
> > > to putting in a request for it.
> > >
> > > I have a horribly busy weekend, but will take a look next
> > > week if noone else gets there first.
> > >
> > > --
> > > Nick Kew
> > >
> >
>
Re: milagro-crypto-c
Posted by Vladislav Mitov <vl...@miracl.com>.
+1
Vladi
On Mon, Feb 27, 2017 at 11:12 AM Kealan Mccusker <ke...@miracl.com>
wrote:
> Hi Nick
>
> This does supersede the existing repo. It is a C repo with language
> wrappers for golang and Python.
>
> Regards
>
> Kealan
>
> On Fri, Feb 24, 2017 at 10:00 PM, Nick Kew <ni...@apache.org> wrote:
>
> > On Fri, 24 Feb 2017 15:26:37 +0000
> > Kealan Mccusker <ke...@miracl.com> wrote:
> >
> > > Hi All
> > >
> > > We have a repo (below) that is currently on the Miracl GitHub account
> > > and it is part of the Apache Milagro project. For operational reasons
> > > we would like to maintain this repo on the Miracl GitHub account and
> > > make it public. Would this be be OK with the dev community? May I
> > > propose a vote?
> > >
> > > The milagro-crypto-c should remain on Miracl GitHub: me +1
> > >
> > > https://github.com/miracl/milagro-crypto-c
> > >
> >
> > Does this replace/supersede anything in the existing
> > milagro-crypto repo?
> >
> > I've just asked informally about the status of full two-way
> > github integration, and I understand it's now being made
> > available more widely. I'm not sure where we stand as an
> > incubating project, but it's probably worth looking in
> > to putting in a request for it.
> >
> > I have a horribly busy weekend, but will take a look next
> > week if noone else gets there first.
> >
> > --
> > Nick Kew
> >
>
Re: milagro-crypto-c
Posted by Kealan Mccusker <ke...@miracl.com>.
Hi Nick
This does supersede the existing repo. It is a C repo with language
wrappers for golang and Python.
Regards
Kealan
On Fri, Feb 24, 2017 at 10:00 PM, Nick Kew <ni...@apache.org> wrote:
> On Fri, 24 Feb 2017 15:26:37 +0000
> Kealan Mccusker <ke...@miracl.com> wrote:
>
> > Hi All
> >
> > We have a repo (below) that is currently on the Miracl GitHub account
> > and it is part of the Apache Milagro project. For operational reasons
> > we would like to maintain this repo on the Miracl GitHub account and
> > make it public. Would this be be OK with the dev community? May I
> > propose a vote?
> >
> > The milagro-crypto-c should remain on Miracl GitHub: me +1
> >
> > https://github.com/miracl/milagro-crypto-c
> >
>
> Does this replace/supersede anything in the existing
> milagro-crypto repo?
>
> I've just asked informally about the status of full two-way
> github integration, and I understand it's now being made
> available more widely. I'm not sure where we stand as an
> incubating project, but it's probably worth looking in
> to putting in a request for it.
>
> I have a horribly busy weekend, but will take a look next
> week if noone else gets there first.
>
> --
> Nick Kew
>
Re: milagro-crypto-c
Posted by Nick Kew <ni...@apache.org>.
On Fri, 24 Feb 2017 15:26:37 +0000
Kealan Mccusker <ke...@miracl.com> wrote:
> Hi All
>
> We have a repo (below) that is currently on the Miracl GitHub account
> and it is part of the Apache Milagro project. For operational reasons
> we would like to maintain this repo on the Miracl GitHub account and
> make it public. Would this be be OK with the dev community? May I
> propose a vote?
>
> The milagro-crypto-c should remain on Miracl GitHub: me +1
>
> https://github.com/miracl/milagro-crypto-c
>
Does this replace/supersede anything in the existing
milagro-crypto repo?
I've just asked informally about the status of full two-way
github integration, and I understand it's now being made
available more widely. I'm not sure where we stand as an
incubating project, but it's probably worth looking in
to putting in a request for it.
I have a horribly busy weekend, but will take a look next
week if noone else gets there first.
--
Nick Kew