[OpenWrt-Devel] Introducing the LEDE project

[David Lang]

It's not unusual for developers who disagree with project management issues to 
fork a project.

I am also interested in who is left in OpenWRT and what their viewpoint is.

Have the developers who are founding LEDE given up their commit privileges in 
OpenWRT? or are they going to be workting a bit in both for a while?

It will take time to see what effect this is really going to end up having. It 
could be a permanent fork, it could be a replacement for OpenWRT, it could be a 
dead end, and it could be something that ends up merging back in later.

It's clear that the issues are management, not technical.

David Lang

On Wed, 4 May 2016, Luiz Angelo Daros de Luca wrote:

> It is really strange that the decision to create a new project was so
> opaque when it was motivated to be a more "transparent project".
> They could've started to be more transparent already with the decision to
> create a new project.
>
> Maybe the answer for the need of an external reboot might be not in the
> names that jumped into but on those left behind.
> Maybe it was easier to create a new project than to boot out the problems.
>
> My 2 cents,
>
> Em qua, 4 de mai de 2016 às 14:50, Roman Yeryomin <leroi.lists at gmail.com>
> escreveu:
>
>> On 4 May 2016 at 19:25, Kathy Giori <kathy.giori at gmail.com> wrote:
>>> On Tue, May 3, 2016 at 10:59 AM, Jo-Philipp Wich <jow at openwrt.org>
>> wrote:
>>>> Hi,
>>>>
>>>> we'd like to introduce LEDE, a reboot of the OpenWrt community
>>>> .
>>>>
>>>> The project is founded as a spin-off of the OpenWrt project and shares
>>>> many of the same goals.
>>>
>>> While I appreciate the enthusiasm, I do not see why you cannot apply
>>> these same "principles" of openness and transparency to the OpenWrt
>>> project. Makes no sense to me to branch the project. That simply
>>> divides the resources in the community into fewer numbers working on
>>> each fork.
>>
>> Exactly, tearing down the project and community without any real
>> explanations (and plans to solve the stated issues) is just wrong.
>>
>>> Also wearing my hat within the prpl Foundation, which is funded by
>>> industry sponsorships that in turn provides financial support for
>>> OpenWrt, no one I have spoken to in prpl understands the reason for
>>> this spin-off either. It'll cause more confusion and inefficiency in
>>> industry. prpl will stick with OpenWrt, and I expect most companies
>>> who follow and/or contribute to OpenWrt will stick with it too.
>>>
>>> kathy
>>> _______________________________________________
>>> openwrt-devel mailing list
>>> openwrt-devel at lists.openwrt.org
>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>> _______________________________________________
>> openwrt-devel mailing list
>> openwrt-devel at lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>
>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel