From hannu.nyman at iki.fi  Mon Jan  2 02:18:57 2017
From: hannu.nyman at iki.fi (Hannu Nyman)
Date: Mon, 2 Jan 2017 12:18:57 +0200
Subject: [LEDE-DEV] Release planning
In-Reply-To: <20ef6da7-8fad-44b6-c6eb-b0d770cfc1f0@ncentric.com>
References: <612e61a0-6664-78a0-b058-58938a31c651@mein.io>
 <20ef6da7-8fad-44b6-c6eb-b0d770cfc1f0@ncentric.com>
Message-ID: <93aa3ca3-ca70-f291-f790-1ccb7dd3cb9b@iki.fi>

On 22.12.2016 14:19, Koen Vandeputte wrote:
> Bump musl to a newer head? (or better to backport some fixes?)
>
> I see a lot of fixes since 1.1.15 on important parts which could influence 
> stability as a lot of packages depend on musl:
>
> http://git.musl-libc.org/cgit/musl/log/ 

musl 1.1.16 has been released on 2017-01-01  ;-)

http://git.musl-libc.org/cgit/musl/commit/?id=8fe1f2d79b275b7f7fb0d41c99e379357df63cd9



From richb.hanover at gmail.com  Mon Jan  2 08:17:18 2017
From: richb.hanover at gmail.com (Rich Brown)
Date: Mon, 2 Jan 2017 11:17:18 -0500
Subject: Release Planning - Current Status?
Message-ID: <B3085C37-04CF-4E7D-943F-1DBAB593AFB5@gmail.com>

If I remember correctly, there was a window for submitting updates for the initial Release Candidate. Where does that process stand?



From jo at mein.io  Tue Jan  3 04:22:54 2017
From: jo at mein.io (Jo-Philipp Wich)
Date: Tue, 3 Jan 2017 13:22:54 +0100
Subject: Fading out PolarSSL
Message-ID: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>

Hi list,

the mbed TLS project (formerly known as PolarSSL) declared the mbedTLS
1.3 branch (packaged as "libpolarssl" by LEDE) to be EOL with the end of
the year 2016. [1]

In order to avoid shipping an outdated and possibly vulnerable SSL
library with the first LEDE release we begun migrating core package
dependencies and default library choices to the "mbedtls" package which
includes the most recent 2.4.0 release of mbedTLS.

There has been an ongoing discussion in IRC on how to handle the
remaining users of the legacy PolarSSL package and whether to ship this
library with the initial release and remove it later or whether to drop
it now in order to catch potential fallout early.

Since we didn't want to single-handedly decide this issue in IRC I took
the topic to the list now to facilitate wider feedback.

Right now there are more or less two approaches proposed:

a) Keep libpolarssl available for the initial 17.01.0 release and drop
   it with the first maintenance release 17.01.1 about 6-8 weeks later

b) Drop libpolarssl now, even before branching and urge the feed package
   maintainers to migrate users of libpolarssl to the libmbedtls variant

Currently known remaining users of polarssl are:

 * bmx7
 * pianod
 * shadowsocks-libev-polarssl
 * shairport-sync-mini
 * shairport-sync-polarssl
 * transmission-cli-polarssl
 * transmission-daemon-polarssl
 * transmission-remote-polarssl
 * umurmur-polarssl


Please provide feedback on which approach you'd prefer and if you'd be
affected by the PolarSSL deprecation or not.

Regards,
Jo


1: https://tls.mbed.org/tech-updates/releases/mbedtls-2.0.0-released


From champetier.etienne at gmail.com  Tue Jan  3 08:01:20 2017
From: champetier.etienne at gmail.com (Etienne Champetier)
Date: Tue, 3 Jan 2017 08:01:20 -0800
Subject: Fading out PolarSSL
In-Reply-To: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>
References: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>
Message-ID: <CAOdf3gqipa-SU80o9pWm8oNBobv15YD0f7r95EjLnaB9uNBpJA@mail.gmail.com>

Hi,

2017-01-03 4:22 GMT-08:00 Jo-Philipp Wich <jo at mein.io>:
> Hi list,
>
> the mbed TLS project (formerly known as PolarSSL) declared the mbedTLS
> 1.3 branch (packaged as "libpolarssl" by LEDE) to be EOL with the end of
> the year 2016. [1]
>
> In order to avoid shipping an outdated and possibly vulnerable SSL
> library with the first LEDE release we begun migrating core package
> dependencies and default library choices to the "mbedtls" package which
> includes the most recent 2.4.0 release of mbedTLS.
>
> There has been an ongoing discussion in IRC on how to handle the
> remaining users of the legacy PolarSSL package and whether to ship this
> library with the initial release and remove it later or whether to drop
> it now in order to catch potential fallout early.
>
> Since we didn't want to single-handedly decide this issue in IRC I took
> the topic to the list now to facilitate wider feedback.
>
> Right now there are more or less two approaches proposed:
>
> a) Keep libpolarssl available for the initial 17.01.0 release and drop
>    it with the first maintenance release 17.01.1 about 6-8 weeks later
>
> b) Drop libpolarssl now, even before branching and urge the feed package
>    maintainers to migrate users of libpolarssl to the libmbedtls variant
>
> Currently known remaining users of polarssl are:
>
>  * bmx7
>  * pianod
>  * shadowsocks-libev-polarssl
>  * shairport-sync-mini
>  * shairport-sync-polarssl
>  * transmission-cli-polarssl
>  * transmission-daemon-polarssl
>  * transmission-remote-polarssl
>  * umurmur-polarssl
>
>
> Please provide feedback on which approach you'd prefer and if you'd be
> affected by the PolarSSL deprecation or not.

you can also mark it @BROKEN, so people can still build it manually
without too much effort

My 2 cents
Etienne


>
> Regards,
> Jo
>
>
> 1: https://tls.mbed.org/tech-updates/releases/mbedtls-2.0.0-released
>
> _______________________________________________
> lede-adm mailing list
> lede-adm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm


From steven at midlink.org  Tue Jan  3 08:32:51 2017
From: steven at midlink.org (Steven Barth)
Date: Tue, 03 Jan 2017 17:32:51 +0100
Subject: Fading out PolarSSL
In-Reply-To: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>
References: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>
Message-ID: <d2aeb1bdb7169fdd210ea09ebdbd6378@midlink.org>

Hey everyone,

> Currently known remaining users of polarssl are:
> 
>  * bmx7
>  * pianod
>  * shadowsocks-libev-polarssl
>  * shairport-sync-mini
>  * shairport-sync-polarssl
>  * transmission-cli-polarssl
>  * transmission-daemon-polarssl
>  * transmission-remote-polarssl
>  * umurmur-polarssl
> 
> 
> Please provide feedback on which approach you'd prefer and if you'd be
> affected by the PolarSSL deprecation or not.

I think for all but the first two from this list, there is a 
non-polarssl version already packaged.
Which would mainly leave bmx7 and pianod as main concerns. I think the 
former used to work with cyassl
at some point in time and the latter should work with gnutls. Both of 
which we have, so it might just
be a minor change to the packaging Makefiles.

So from my point of view dropping libpolarssl now (with a bit of upfront 
notice to the maintainers)
makes more sense than trying to drop a package later which is a bit of 
unexpected and am not sure if
it can be effectively announced in a service release and just delays the 
inevitable.


Cheers,

Steven


From nbd at nbd.name  Wed Jan  4 13:10:50 2017
From: nbd at nbd.name (Felix Fietkau)
Date: Wed, 4 Jan 2017 22:10:50 +0100
Subject: lede-dev list not working
Message-ID: <645858e0-293f-f1b7-ff47-1b1a727cf1e2@nbd.name>

Hi David,

Happy new year!

I'm not sure if anybody else reported this already, but apparently the
lede-dev list isn't working anymore.
A lot of mails from yesterday and today didn't make it to the list.

- Felix


From nbd at nbd.name  Thu Jan  5 01:22:43 2017
From: nbd at nbd.name (Felix Fietkau)
Date: Thu, 5 Jan 2017 10:22:43 +0100
Subject: lede-dev list not working
In-Reply-To: <645858e0-293f-f1b7-ff47-1b1a727cf1e2@nbd.name>
References: <645858e0-293f-f1b7-ff47-1b1a727cf1e2@nbd.name>
Message-ID: <36ea2da3-de7d-44bf-011e-2c36b5251c63@nbd.name>

On 2017-01-04 22:10, Felix Fietkau wrote:
> Hi David,
> 
> Happy new year!
> 
> I'm not sure if anybody else reported this already, but apparently the
> lede-dev list isn't working anymore.
> A lot of mails from yesterday and today didn't make it to the list.
Seems to be working again, thanks.

- Felix



From lede at kitschensync.net  Fri Jan  6 10:23:01 2017
From: lede at kitschensync.net (Ted Hess)
Date: Fri, 06 Jan 2017 13:23:01 -0500
Subject: Fading out PolarSSL
In-Reply-To: <d2aeb1bdb7169fdd210ea09ebdbd6378@midlink.org>
References: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>
 <d2aeb1bdb7169fdd210ea09ebdbd6378@midlink.org>
Message-ID: <1483726981.14436.4.camel@kitschensync.net>

On Tue, 2017-01-03 at 17:32 +0100, Steven Barth wrote:
> Hey everyone,
> 
> > 
> > Currently known remaining users of polarssl are:
> > 
> > ?* bmx7
> > ?* pianod
> > ?* shadowsocks-libev-polarssl
> > ?* shairport-sync-mini
> > ?* shairport-sync-polarssl
> > ?* transmission-cli-polarssl
> > ?* transmission-daemon-polarssl
> > ?* transmission-remote-polarssl
> > ?* umurmur-polarssl
> > 
> > 
> > Please provide feedback on which approach you'd prefer and if you'd be
> > affected by the PolarSSL deprecation or not.
> I think for all but the first two from this list, there is a?
> non-polarssl version already packaged.
> Which would mainly leave bmx7 and pianod as main concerns. I think the?
> former used to work with cyassl
> at some point in time and the latter should work with gnutls. Both of?
> which we have, so it might just
> be a minor change to the packaging Makefiles.
> 
> So from my point of view dropping libpolarssl now (with a bit of upfront?
> notice to the maintainers)
> makes more sense than trying to drop a package later which is a bit of?
> unexpected and am not sure if
> it can be effectively announced in a service release and just delays the?
> inevitable.
> 
> 
> Cheers,
> 
> Steven
> 
> _______________________________________________
> lede-adm mailing list
> lede-adm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm

Drop it now.

Speaking for pianod and shairport-sync... I have already updated pianod (which I
still develop) to use mbed TLS and I am currently working with the shairport-
sync developer to replace PolarSSL with mbed TLS this weekend.

/ted


From luka.perkov at sartura.hr  Sun Jan  8 12:34:19 2017
From: luka.perkov at sartura.hr (Luka Perkov)
Date: Sun, 8 Jan 2017 21:34:19 +0100
Subject: request for access to lede tree
Message-ID: <20170108203419.GA18427@localhost.localdomain>

Hi everybody,

I'd like to get access to LEDE tree. I'll be working on integrating some
of the OpenWrt patches and adding few other ones as well. Can we make
this happen?

Thanks,
Luka


From john at phrozen.org  Sun Jan  8 13:25:51 2017
From: john at phrozen.org (John Crispin)
Date: Sun, 8 Jan 2017 22:25:51 +0100
Subject: request for access to lede tree
In-Reply-To: <20170108203419.GA18427@localhost.localdomain>
References: <20170108203419.GA18427@localhost.localdomain>
Message-ID: <e0ffac2a-0bc8-533e-a8c3-65b7f4495e09@phrozen.org>



On 08/01/2017 21:34, Luka Perkov wrote:
> Hi everybody,
> 
> I'd like to get access to LEDE tree. I'll be working on integrating some
> of the OpenWrt patches and adding few other ones as well. Can we make
> this happen?
> 
> Thanks,
> Luka

Hi Luka,

it was already agreed that this is not a problem. please send your ssh
key to jow and ted. once its added, you need to add yourself to the
keyring.git (https://git.lede-project.org/?p=web.git;a=blob;f=keygen.txt)

	John


From jo at mein.io  Tue Jan 10 02:16:37 2017
From: jo at mein.io (Jo-Philipp Wich)
Date: Tue, 10 Jan 2017 11:16:37 +0100
Subject: Sponsor request
In-Reply-To: <CAHEvHNooMckYaSAutkd5Adgj0fgoZn=NkurpvX01VU5UeiH9+A@mail.gmail.com>
References: <CAHEvHNooMckYaSAutkd5Adgj0fgoZn=NkurpvX01VU5UeiH9+A@mail.gmail.com>
Message-ID: <c853eab9-67e6-fcac-3fdb-03fa281567ec@mein.io>

Dear Arve,

thank you very much for your sponsorship offer.

> We're a (small) fiber based ISP located in Norway with ongoing plans to
> release a new Wi-Fi platform (waves.io <http://waves.io>) based on
> OpenWRT/LEDE during summer 2017. I've noticed that LEDE needs a sponsor
> to help with the hosting bill, and perhaps other expenses, and this is
> where we might be able to contribute back.

The most pressing need I can think of right now is further compute nodes
to extend the buildbot cluster. There is some need for build machines
having having 2TB+ disk space in order to be able to incrementally build
releases. Is this something you would be able to offer?

> I've also registered that there are talks between OpenWRT and LEDE to
> reunite, and in that case, what will happen with the infrastructure? Is
> this a common need for both project so that the infrastructure would be
> re-used?

Yes, I expect the compute infrastructure to get re-used as the build
cluster is a common need of both projects.

> Could someone please elaborate a bit on what the sponsoring needs for
> LEDE is in 2017 and further?

With decreasing order of importance, the following items are needed:

 - Build cluster machines
 - CDN resources for distributing binaries

I think some of the developers would also appreciate a waves.io sample
unit :)

Since LEDE is no legal entity at the moment we'd rather not accept
monetary donations as we currently lack the infrastructure to properly
handle those.

@others: please chime in if you can think of anything more.

Kind regards,
Jo


From thess at kitschensync.net  Fri Jan 13 09:59:23 2017
From: thess at kitschensync.net (Ted Hess)
Date: Fri, 13 Jan 2017 12:59:23 -0500
Subject: Flyspray updates
In-Reply-To: <19ff6353-9c7f-063a-c8c3-150bc440fe7a@kresin.me>
References: <FS287@bugs.lede-project.org>
 <09871b4f7b9a35551bc1eb50aa506821@bugs.lede-project.org>
 <CABwW5nn7dUg_rYg6x6ZJE+m-mSO22oVy0g0+O+vu6YAxoSO_7g@mail.gmail.com>
 <6C678B2042B145B4B8D69A6BABFCB2B4@fortmeadow.com>
 <19ff6353-9c7f-063a-c8c3-150bc440fe7a@kresin.me>
Message-ID: <C67ECBFC295049DFA37BC03DC2AEC36B@fortmeadow.com>

Mathias -

I see no reason why Developers should not have project manager status in Flyspray. To that end, I've added "Manage Project" and 
"View Event Log" privs to all Developers. If this is undesirable, I can add a new group for those privs (who want them) instead.

To get project notifications, you need to subscribe to lede-bugs at lists.infraded.org.

/ted

-----Original Message----- 
From: Mathias Kresin
Sent: Friday, January 13, 2017 3:08 AM
To: Ted Hess
Subject: Re: [FS#287] Missing crosscompiler in imagebuilder? (ramips - A5-V11 platform)

Hey Ted,

never noticed the history tab...

Would it be possible to setup an e-mail notification in case one
requests a ticket to be reopen or closed? At the moment it don't get
noticed of such requests.

Is it intentional that members of the Developers group can not denial a
reopen request?

Mathias 



From john at phrozen.org  Thu Jan 19 00:41:41 2017
From: john at phrozen.org (John Crispin)
Date: Thu, 19 Jan 2017 09:41:41 +0100
Subject: commit access for Yousong Zhou
Message-ID: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>

Hi,

i would like to propose that we give full commit/voting rights to
Yousong Zhou. He has been contributing for what feels like a decade. the
patches he sends are as good/bad as what we produce ourselves.

	John


From dedeckeh at gmail.com  Thu Jan 19 00:59:54 2017
From: dedeckeh at gmail.com (Hans Dedecker)
Date: Thu, 19 Jan 2017 09:59:54 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <CAJLcKsErshZcHs3PeO8Qs2iHmd5yURuwDv8p5nCZ3qtaYR-x4A@mail.gmail.com>

On Thu, Jan 19, 2017 at 9:41 AM, John Crispin <john at phrozen.org> wrote:
> Hi,
>
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
+1

Hans
>
>         John
>
> _______________________________________________
> lede-adm mailing list
> lede-adm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm


From nbd at nbd.name  Thu Jan 19 01:00:58 2017
From: nbd at nbd.name (Felix Fietkau)
Date: Thu, 19 Jan 2017 10:00:58 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <553a2019-3dc9-ad3c-74bd-03363f5238bc@nbd.name>

On 2017-01-19 09:41, John Crispin wrote:
> Hi,
> 
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
ACK, good idea!

- Felix


From luka.perkov at sartura.hr  Thu Jan 19 01:11:02 2017
From: luka.perkov at sartura.hr (Luka Perkov)
Date: Thu, 19 Jan 2017 10:11:02 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <CAJLcKsErshZcHs3PeO8Qs2iHmd5yURuwDv8p5nCZ3qtaYR-x4A@mail.gmail.com>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
 <CAJLcKsErshZcHs3PeO8Qs2iHmd5yURuwDv8p5nCZ3qtaYR-x4A@mail.gmail.com>
Message-ID: <20170119091102.GA22061@localhost.localdomain>

On Thu, Jan 19, 2017 at 09:59:54AM +0100, Hans Dedecker wrote:
> On Thu, Jan 19, 2017 at 9:41 AM, John Crispin <john at phrozen.org> wrote:
> > Hi,
> >
> > i would like to propose that we give full commit/voting rights to
> > Yousong Zhou. He has been contributing for what feels like a decade. the
> > patches he sends are as good/bad as what we produce ourselves.
> +1
> 
> Hans

+1

Luka


From daniel at makrotopia.org  Thu Jan 19 03:16:21 2017
From: daniel at makrotopia.org (Daniel Golle)
Date: Thu, 19 Jan 2017 12:16:21 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <20170119111619.GD1798@makrotopia.org>

+1

On Thu, Jan 19, 2017 at 09:41:41AM +0100, John Crispin wrote:
> Hi,
> 
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
> 
> 	John
> 
> _______________________________________________
> lede-adm mailing list
> lede-adm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm


From jo at mein.io  Thu Jan 19 04:22:18 2017
From: jo at mein.io (Jo-Philipp Wich)
Date: Thu, 19 Jan 2017 13:22:18 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <d6ad4c74-e330-641a-e7ed-20477bc16d04@mein.io>

Hi,

+1

~ Jo


From mschiffer at universe-factory.net  Thu Jan 19 05:07:10 2017
From: mschiffer at universe-factory.net (Matthias Schiffer)
Date: Thu, 19 Jan 2017 14:07:10 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <24a504c6-77dc-9f8b-b75d-fca9fb985471@universe-factory.net>

On 01/19/2017 09:41 AM, John Crispin wrote:
> Hi,
> 
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
> 
> 	John

+1


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/lede-adm/attachments/20170119/a51dc19a/attachment.sig>

From f.fainelli at gmail.com  Thu Jan 19 11:14:11 2017
From: f.fainelli at gmail.com (Florian Fainelli)
Date: Thu, 19 Jan 2017 11:14:11 -0800
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <cb462006-7b55-c5d4-6b51-272163c1ba8b@gmail.com>

On 01/19/2017 12:41 AM, John Crispin wrote:
> Hi,
> 
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.

Ack
-- 
Florian


From stijn at linux-ipv6.be  Thu Jan 19 13:13:52 2017
From: stijn at linux-ipv6.be (Stijn Tintel)
Date: Thu, 19 Jan 2017 22:13:52 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <3f91469e-2439-2bef-bb5b-b033cd989ca6@linux-ipv6.be>

On 19-01-17 09:41, John Crispin wrote:
> Hi,
>
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
>
ACK


From thess at kitschensync.net  Fri Jan 20 07:31:23 2017
From: thess at kitschensync.net (Ted Hess)
Date: Fri, 20 Jan 2017 10:31:23 -0500
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <1484926283.4403.7.camel@kitschensync.net>

On Thu, 2017-01-19 at 09:41 +0100, John Crispin wrote:
> Hi,
> 
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
> 
> 	John
> 
> _______________________________________________
> lede-adm mailing list
> lede-adm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm
Late to the party - ACK from me.


From yszhou4tech at gmail.com  Sun Jan 22 06:36:58 2017
From: yszhou4tech at gmail.com (Yousong Zhou)
Date: Sun, 22 Jan 2017 22:36:58 +0800
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <CAECwjAiCC5_TeNby0ZzUf+w62y4x5AWvtPisVA+r669S3tWz5w@mail.gmail.com>

On 19 January 2017 at 16:41, John Crispin <john at phrozen.org> wrote:
> Hi,
>
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
>
>         John

Thanks, guys.  It's always a pleasure of me to be part of the project
since the very first time I came across it years ago.  This proposal
and the acknowledgements are really good surprise to me and I am very
grateful.

Thanks and Happy New Year from China ;)

                yousong


From hannu.nyman at iki.fi  Mon Jan  2 05:18:57 2017
From: hannu.nyman at iki.fi (Hannu Nyman)
Date: Mon, 2 Jan 2017 12:18:57 +0200
Subject: [LEDE-DEV] Release planning
In-Reply-To: <20ef6da7-8fad-44b6-c6eb-b0d770cfc1f0@ncentric.com>
References: <612e61a0-6664-78a0-b058-58938a31c651@mein.io>
 <20ef6da7-8fad-44b6-c6eb-b0d770cfc1f0@ncentric.com>
Message-ID: <93aa3ca3-ca70-f291-f790-1ccb7dd3cb9b@iki.fi>

On 22.12.2016 14:19, Koen Vandeputte wrote:
> Bump musl to a newer head? (or better to backport some fixes?)
>
> I see a lot of fixes since 1.1.15 on important parts which could influence 
> stability as a lot of packages depend on musl:
>
> http://git.musl-libc.org/cgit/musl/log/ 

musl 1.1.16 has been released on 2017-01-01  ;-)

http://git.musl-libc.org/cgit/musl/commit/?id=8fe1f2d79b275b7f7fb0d41c99e379357df63cd9




From richb.hanover at gmail.com  Mon Jan  2 11:17:18 2017
From: richb.hanover at gmail.com (Rich Brown)
Date: Mon, 2 Jan 2017 11:17:18 -0500
Subject: Release Planning - Current Status?
Message-ID: <B3085C37-04CF-4E7D-943F-1DBAB593AFB5@gmail.com>

If I remember correctly, there was a window for submitting updates for the initial Release Candidate. Where does that process stand?




From jo at mein.io  Tue Jan  3 07:22:54 2017
From: jo at mein.io (Jo-Philipp Wich)
Date: Tue, 3 Jan 2017 13:22:54 +0100
Subject: Fading out PolarSSL
Message-ID: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>

Hi list,

the mbed TLS project (formerly known as PolarSSL) declared the mbedTLS
1.3 branch (packaged as "libpolarssl" by LEDE) to be EOL with the end of
the year 2016. [1]

In order to avoid shipping an outdated and possibly vulnerable SSL
library with the first LEDE release we begun migrating core package
dependencies and default library choices to the "mbedtls" package which
includes the most recent 2.4.0 release of mbedTLS.

There has been an ongoing discussion in IRC on how to handle the
remaining users of the legacy PolarSSL package and whether to ship this
library with the initial release and remove it later or whether to drop
it now in order to catch potential fallout early.

Since we didn't want to single-handedly decide this issue in IRC I took
the topic to the list now to facilitate wider feedback.

Right now there are more or less two approaches proposed:

a) Keep libpolarssl available for the initial 17.01.0 release and drop
   it with the first maintenance release 17.01.1 about 6-8 weeks later

b) Drop libpolarssl now, even before branching and urge the feed package
   maintainers to migrate users of libpolarssl to the libmbedtls variant

Currently known remaining users of polarssl are:

 * bmx7
 * pianod
 * shadowsocks-libev-polarssl
 * shairport-sync-mini
 * shairport-sync-polarssl
 * transmission-cli-polarssl
 * transmission-daemon-polarssl
 * transmission-remote-polarssl
 * umurmur-polarssl


Please provide feedback on which approach you'd prefer and if you'd be
affected by the PolarSSL deprecation or not.

Regards,
Jo


1: https://tls.mbed.org/tech-updates/releases/mbedtls-2.0.0-released



From champetier.etienne at gmail.com  Tue Jan  3 11:01:20 2017
From: champetier.etienne at gmail.com (Etienne Champetier)
Date: Tue, 3 Jan 2017 08:01:20 -0800
Subject: Fading out PolarSSL
In-Reply-To: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>
References: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>
Message-ID: <CAOdf3gqipa-SU80o9pWm8oNBobv15YD0f7r95EjLnaB9uNBpJA@mail.gmail.com>

Hi,

2017-01-03 4:22 GMT-08:00 Jo-Philipp Wich <jo at mein.io>:
> Hi list,
>
> the mbed TLS project (formerly known as PolarSSL) declared the mbedTLS
> 1.3 branch (packaged as "libpolarssl" by LEDE) to be EOL with the end of
> the year 2016. [1]
>
> In order to avoid shipping an outdated and possibly vulnerable SSL
> library with the first LEDE release we begun migrating core package
> dependencies and default library choices to the "mbedtls" package which
> includes the most recent 2.4.0 release of mbedTLS.
>
> There has been an ongoing discussion in IRC on how to handle the
> remaining users of the legacy PolarSSL package and whether to ship this
> library with the initial release and remove it later or whether to drop
> it now in order to catch potential fallout early.
>
> Since we didn't want to single-handedly decide this issue in IRC I took
> the topic to the list now to facilitate wider feedback.
>
> Right now there are more or less two approaches proposed:
>
> a) Keep libpolarssl available for the initial 17.01.0 release and drop
>    it with the first maintenance release 17.01.1 about 6-8 weeks later
>
> b) Drop libpolarssl now, even before branching and urge the feed package
>    maintainers to migrate users of libpolarssl to the libmbedtls variant
>
> Currently known remaining users of polarssl are:
>
>  * bmx7
>  * pianod
>  * shadowsocks-libev-polarssl
>  * shairport-sync-mini
>  * shairport-sync-polarssl
>  * transmission-cli-polarssl
>  * transmission-daemon-polarssl
>  * transmission-remote-polarssl
>  * umurmur-polarssl
>
>
> Please provide feedback on which approach you'd prefer and if you'd be
> affected by the PolarSSL deprecation or not.

you can also mark it @BROKEN, so people can still build it manually
without too much effort

My 2 cents
Etienne


>
> Regards,
> Jo
>
>
> 1: https://tls.mbed.org/tech-updates/releases/mbedtls-2.0.0-released
>
> _______________________________________________
> lede-adm mailing list
> lede-adm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm



From steven at midlink.org  Tue Jan  3 11:32:51 2017
From: steven at midlink.org (Steven Barth)
Date: Tue, 03 Jan 2017 17:32:51 +0100
Subject: Fading out PolarSSL
In-Reply-To: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>
References: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>
Message-ID: <d2aeb1bdb7169fdd210ea09ebdbd6378@midlink.org>

Hey everyone,

> Currently known remaining users of polarssl are:
> 
>  * bmx7
>  * pianod
>  * shadowsocks-libev-polarssl
>  * shairport-sync-mini
>  * shairport-sync-polarssl
>  * transmission-cli-polarssl
>  * transmission-daemon-polarssl
>  * transmission-remote-polarssl
>  * umurmur-polarssl
> 
> 
> Please provide feedback on which approach you'd prefer and if you'd be
> affected by the PolarSSL deprecation or not.

I think for all but the first two from this list, there is a 
non-polarssl version already packaged.
Which would mainly leave bmx7 and pianod as main concerns. I think the 
former used to work with cyassl
at some point in time and the latter should work with gnutls. Both of 
which we have, so it might just
be a minor change to the packaging Makefiles.

So from my point of view dropping libpolarssl now (with a bit of upfront 
notice to the maintainers)
makes more sense than trying to drop a package later which is a bit of 
unexpected and am not sure if
it can be effectively announced in a service release and just delays the 
inevitable.


Cheers,

Steven



From nbd at nbd.name  Wed Jan  4 16:10:50 2017
From: nbd at nbd.name (Felix Fietkau)
Date: Wed, 4 Jan 2017 22:10:50 +0100
Subject: lede-dev list not working
Message-ID: <645858e0-293f-f1b7-ff47-1b1a727cf1e2@nbd.name>

Hi David,

Happy new year!

I'm not sure if anybody else reported this already, but apparently the
lede-dev list isn't working anymore.
A lot of mails from yesterday and today didn't make it to the list.

- Felix



From nbd at nbd.name  Thu Jan  5 04:22:43 2017
From: nbd at nbd.name (Felix Fietkau)
Date: Thu, 5 Jan 2017 10:22:43 +0100
Subject: lede-dev list not working
In-Reply-To: <645858e0-293f-f1b7-ff47-1b1a727cf1e2@nbd.name>
References: <645858e0-293f-f1b7-ff47-1b1a727cf1e2@nbd.name>
Message-ID: <36ea2da3-de7d-44bf-011e-2c36b5251c63@nbd.name>

On 2017-01-04 22:10, Felix Fietkau wrote:
> Hi David,
> 
> Happy new year!
> 
> I'm not sure if anybody else reported this already, but apparently the
> lede-dev list isn't working anymore.
> A lot of mails from yesterday and today didn't make it to the list.
Seems to be working again, thanks.

- Felix




From lede at kitschensync.net  Fri Jan  6 13:23:01 2017
From: lede at kitschensync.net (Ted Hess)
Date: Fri, 06 Jan 2017 13:23:01 -0500
Subject: Fading out PolarSSL
In-Reply-To: <d2aeb1bdb7169fdd210ea09ebdbd6378@midlink.org>
References: <2e242fd7-aa1f-7ebf-2aad-f139771548f1@mein.io>
 <d2aeb1bdb7169fdd210ea09ebdbd6378@midlink.org>
Message-ID: <1483726981.14436.4.camel@kitschensync.net>

On Tue, 2017-01-03 at 17:32 +0100, Steven Barth wrote:
> Hey everyone,
> 
> > 
> > Currently known remaining users of polarssl are:
> > 
> > ?* bmx7
> > ?* pianod
> > ?* shadowsocks-libev-polarssl
> > ?* shairport-sync-mini
> > ?* shairport-sync-polarssl
> > ?* transmission-cli-polarssl
> > ?* transmission-daemon-polarssl
> > ?* transmission-remote-polarssl
> > ?* umurmur-polarssl
> > 
> > 
> > Please provide feedback on which approach you'd prefer and if you'd be
> > affected by the PolarSSL deprecation or not.
> I think for all but the first two from this list, there is a?
> non-polarssl version already packaged.
> Which would mainly leave bmx7 and pianod as main concerns. I think the?
> former used to work with cyassl
> at some point in time and the latter should work with gnutls. Both of?
> which we have, so it might just
> be a minor change to the packaging Makefiles.
> 
> So from my point of view dropping libpolarssl now (with a bit of upfront?
> notice to the maintainers)
> makes more sense than trying to drop a package later which is a bit of?
> unexpected and am not sure if
> it can be effectively announced in a service release and just delays the?
> inevitable.
> 
> 
> Cheers,
> 
> Steven
> 
> _______________________________________________
> lede-adm mailing list
> lede-adm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm

Drop it now.

Speaking for pianod and shairport-sync... I have already updated pianod (which I
still develop) to use mbed TLS and I am currently working with the shairport-
sync developer to replace PolarSSL with mbed TLS this weekend.

/ted



From luka.perkov at sartura.hr  Sun Jan  8 15:34:19 2017
From: luka.perkov at sartura.hr (Luka Perkov)
Date: Sun, 8 Jan 2017 21:34:19 +0100
Subject: request for access to lede tree
Message-ID: <20170108203419.GA18427@localhost.localdomain>

Hi everybody,

I'd like to get access to LEDE tree. I'll be working on integrating some
of the OpenWrt patches and adding few other ones as well. Can we make
this happen?

Thanks,
Luka



From john at phrozen.org  Sun Jan  8 16:25:51 2017
From: john at phrozen.org (John Crispin)
Date: Sun, 8 Jan 2017 22:25:51 +0100
Subject: request for access to lede tree
In-Reply-To: <20170108203419.GA18427@localhost.localdomain>
References: <20170108203419.GA18427@localhost.localdomain>
Message-ID: <e0ffac2a-0bc8-533e-a8c3-65b7f4495e09@phrozen.org>



On 08/01/2017 21:34, Luka Perkov wrote:
> Hi everybody,
> 
> I'd like to get access to LEDE tree. I'll be working on integrating some
> of the OpenWrt patches and adding few other ones as well. Can we make
> this happen?
> 
> Thanks,
> Luka

Hi Luka,

it was already agreed that this is not a problem. please send your ssh
key to jow and ted. once its added, you need to add yourself to the
keyring.git (https://git.lede-project.org/?p=web.git;a=blob;f=keygen.txt)

	John



From jo at mein.io  Tue Jan 10 05:16:37 2017
From: jo at mein.io (Jo-Philipp Wich)
Date: Tue, 10 Jan 2017 11:16:37 +0100
Subject: Sponsor request
In-Reply-To: <CAHEvHNooMckYaSAutkd5Adgj0fgoZn=NkurpvX01VU5UeiH9+A@mail.gmail.com>
References: <CAHEvHNooMckYaSAutkd5Adgj0fgoZn=NkurpvX01VU5UeiH9+A@mail.gmail.com>
Message-ID: <c853eab9-67e6-fcac-3fdb-03fa281567ec@mein.io>

Dear Arve,

thank you very much for your sponsorship offer.

> We're a (small) fiber based ISP located in Norway with ongoing plans to
> release a new Wi-Fi platform (waves.io <http://waves.io>) based on
> OpenWRT/LEDE during summer 2017. I've noticed that LEDE needs a sponsor
> to help with the hosting bill, and perhaps other expenses, and this is
> where we might be able to contribute back.

The most pressing need I can think of right now is further compute nodes
to extend the buildbot cluster. There is some need for build machines
having having 2TB+ disk space in order to be able to incrementally build
releases. Is this something you would be able to offer?

> I've also registered that there are talks between OpenWRT and LEDE to
> reunite, and in that case, what will happen with the infrastructure? Is
> this a common need for both project so that the infrastructure would be
> re-used?

Yes, I expect the compute infrastructure to get re-used as the build
cluster is a common need of both projects.

> Could someone please elaborate a bit on what the sponsoring needs for
> LEDE is in 2017 and further?

With decreasing order of importance, the following items are needed:

 - Build cluster machines
 - CDN resources for distributing binaries

I think some of the developers would also appreciate a waves.io sample
unit :)

Since LEDE is no legal entity at the moment we'd rather not accept
monetary donations as we currently lack the infrastructure to properly
handle those.

@others: please chime in if you can think of anything more.

Kind regards,
Jo



From thess at kitschensync.net  Fri Jan 13 12:59:23 2017
From: thess at kitschensync.net (Ted Hess)
Date: Fri, 13 Jan 2017 12:59:23 -0500
Subject: Flyspray updates
In-Reply-To: <19ff6353-9c7f-063a-c8c3-150bc440fe7a@kresin.me>
References: <FS287@bugs.lede-project.org>
 <09871b4f7b9a35551bc1eb50aa506821@bugs.lede-project.org>
 <CABwW5nn7dUg_rYg6x6ZJE+m-mSO22oVy0g0+O+vu6YAxoSO_7g@mail.gmail.com>
 <6C678B2042B145B4B8D69A6BABFCB2B4@fortmeadow.com>
 <19ff6353-9c7f-063a-c8c3-150bc440fe7a@kresin.me>
Message-ID: <C67ECBFC295049DFA37BC03DC2AEC36B@fortmeadow.com>

Mathias -

I see no reason why Developers should not have project manager status in Flyspray. To that end, I've added "Manage Project" and 
"View Event Log" privs to all Developers. If this is undesirable, I can add a new group for those privs (who want them) instead.

To get project notifications, you need to subscribe to lede-bugs at lists.infraded.org.

/ted

-----Original Message----- 
From: Mathias Kresin
Sent: Friday, January 13, 2017 3:08 AM
To: Ted Hess
Subject: Re: [FS#287] Missing crosscompiler in imagebuilder? (ramips - A5-V11 platform)

Hey Ted,

never noticed the history tab...

Would it be possible to setup an e-mail notification in case one
requests a ticket to be reopen or closed? At the moment it don't get
noticed of such requests.

Is it intentional that members of the Developers group can not denial a
reopen request?

Mathias 




From john at phrozen.org  Thu Jan 19 03:41:41 2017
From: john at phrozen.org (John Crispin)
Date: Thu, 19 Jan 2017 09:41:41 +0100
Subject: commit access for Yousong Zhou
Message-ID: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>

Hi,

i would like to propose that we give full commit/voting rights to
Yousong Zhou. He has been contributing for what feels like a decade. the
patches he sends are as good/bad as what we produce ourselves.

	John



From dedeckeh at gmail.com  Thu Jan 19 03:59:54 2017
From: dedeckeh at gmail.com (Hans Dedecker)
Date: Thu, 19 Jan 2017 09:59:54 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <CAJLcKsErshZcHs3PeO8Qs2iHmd5yURuwDv8p5nCZ3qtaYR-x4A@mail.gmail.com>

On Thu, Jan 19, 2017 at 9:41 AM, John Crispin <john at phrozen.org> wrote:
> Hi,
>
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
+1

Hans
>
>         John
>
> _______________________________________________
> lede-adm mailing list
> lede-adm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm



From nbd at nbd.name  Thu Jan 19 04:00:58 2017
From: nbd at nbd.name (Felix Fietkau)
Date: Thu, 19 Jan 2017 10:00:58 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <553a2019-3dc9-ad3c-74bd-03363f5238bc@nbd.name>

On 2017-01-19 09:41, John Crispin wrote:
> Hi,
> 
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
ACK, good idea!

- Felix



From luka.perkov at sartura.hr  Thu Jan 19 04:11:02 2017
From: luka.perkov at sartura.hr (Luka Perkov)
Date: Thu, 19 Jan 2017 10:11:02 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <CAJLcKsErshZcHs3PeO8Qs2iHmd5yURuwDv8p5nCZ3qtaYR-x4A@mail.gmail.com>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
 <CAJLcKsErshZcHs3PeO8Qs2iHmd5yURuwDv8p5nCZ3qtaYR-x4A@mail.gmail.com>
Message-ID: <20170119091102.GA22061@localhost.localdomain>

On Thu, Jan 19, 2017 at 09:59:54AM +0100, Hans Dedecker wrote:
> On Thu, Jan 19, 2017 at 9:41 AM, John Crispin <john at phrozen.org> wrote:
> > Hi,
> >
> > i would like to propose that we give full commit/voting rights to
> > Yousong Zhou. He has been contributing for what feels like a decade. the
> > patches he sends are as good/bad as what we produce ourselves.
> +1
> 
> Hans

+1

Luka



From daniel at makrotopia.org  Thu Jan 19 06:16:21 2017
From: daniel at makrotopia.org (Daniel Golle)
Date: Thu, 19 Jan 2017 12:16:21 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <20170119111619.GD1798@makrotopia.org>

+1

On Thu, Jan 19, 2017 at 09:41:41AM +0100, John Crispin wrote:
> Hi,
> 
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
> 
> 	John
> 
> _______________________________________________
> lede-adm mailing list
> lede-adm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm



From jo at mein.io  Thu Jan 19 07:22:18 2017
From: jo at mein.io (Jo-Philipp Wich)
Date: Thu, 19 Jan 2017 13:22:18 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <d6ad4c74-e330-641a-e7ed-20477bc16d04@mein.io>

Hi,

+1

~ Jo



From mschiffer at universe-factory.net  Thu Jan 19 08:07:10 2017
From: mschiffer at universe-factory.net (Matthias Schiffer)
Date: Thu, 19 Jan 2017 14:07:10 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <24a504c6-77dc-9f8b-b75d-fca9fb985471@universe-factory.net>

On 01/19/2017 09:41 AM, John Crispin wrote:
> Hi,
> 
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
> 
> 	John

+1


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/openwrt-adm/attachments/20170119/a51dc19a/attachment-0001.sig>

From f.fainelli at gmail.com  Thu Jan 19 14:14:11 2017
From: f.fainelli at gmail.com (Florian Fainelli)
Date: Thu, 19 Jan 2017 11:14:11 -0800
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <cb462006-7b55-c5d4-6b51-272163c1ba8b@gmail.com>

On 01/19/2017 12:41 AM, John Crispin wrote:
> Hi,
> 
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.

Ack
-- 
Florian



From stijn at linux-ipv6.be  Thu Jan 19 16:13:52 2017
From: stijn at linux-ipv6.be (Stijn Tintel)
Date: Thu, 19 Jan 2017 22:13:52 +0100
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <3f91469e-2439-2bef-bb5b-b033cd989ca6@linux-ipv6.be>

On 19-01-17 09:41, John Crispin wrote:
> Hi,
>
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
>
ACK



From thess at kitschensync.net  Fri Jan 20 10:31:23 2017
From: thess at kitschensync.net (Ted Hess)
Date: Fri, 20 Jan 2017 10:31:23 -0500
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <1484926283.4403.7.camel@kitschensync.net>

On Thu, 2017-01-19 at 09:41 +0100, John Crispin wrote:
> Hi,
> 
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
> 
> 	John
> 
> _______________________________________________
> lede-adm mailing list
> lede-adm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm
Late to the party - ACK from me.



From yszhou4tech at gmail.com  Sun Jan 22 09:36:58 2017
From: yszhou4tech at gmail.com (Yousong Zhou)
Date: Sun, 22 Jan 2017 22:36:58 +0800
Subject: commit access for Yousong Zhou
In-Reply-To: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
References: <c6ea845f-cd91-2075-e33f-7c5e92de096f@phrozen.org>
Message-ID: <CAECwjAiCC5_TeNby0ZzUf+w62y4x5AWvtPisVA+r669S3tWz5w@mail.gmail.com>

On 19 January 2017 at 16:41, John Crispin <john at phrozen.org> wrote:
> Hi,
>
> i would like to propose that we give full commit/voting rights to
> Yousong Zhou. He has been contributing for what feels like a decade. the
> patches he sends are as good/bad as what we produce ourselves.
>
>         John

Thanks, guys.  It's always a pleasure of me to be part of the project
since the very first time I came across it years ago.  This proposal
and the acknowledgements are really good surprise to me and I am very
grateful.

Thanks and Happy New Year from China ;)

                yousong



