[Ninux-Wireless] Fwd: [OpenWrt-Devel] Introducing the LEDE project
Original Message Subject: [OpenWrt-Devel] Introducing the LEDE project Date: Tue, 3 May 2016 18:59:55 +0100 From: Jo-Philipp Wich To: OpenWrt Development List , OpenWrt User List 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. We are building an embedded Linux distribution that makes it easy for developers, system administrators or other Linux enthusiasts to build and customize software for embedded devices, especially wireless routers. The name 'LEDE' stands for 'Linux Embedded Development Environment'. Members of the project already include a significant share of the most active members of the OpenWrt community. We intend to bring new life to Embedded Linux development by creating a community with a strong focus on transparency, collaboration and decentralisation. LEDE’s stated goals are: - Building a great embedded Linux distribution with focus on stability and functionality. - Having regular, predictable release cycles coupled with community provided device testing feedback. - Establishing transparent decision processes with broad community participation and public meetings. We decided to create this new project because of long standing issues that we were unable to fix from within the OpenWrt project/community: 1. Number of active core developers at an all time low, no process for getting more new people involved. 2. Unreliable infrastructure, fixes prevented by internal disagreements and single points of failure. 3. Lack of communication, transparency and coordination in the OpenWrt project, both inside the core team and between the core team and the rest of the community. 4. Not enough people with commit access to handle the incoming flow of patches, too little attention to testing and regular builds. 5. Lack of focus on stability and documentation. To address these issues we set up the LEDE project in a different way compared to OpenWrt: 1. All our communication channels are public, some read-only to non-members to maintain a good signal-to-noise ratio. 2. Our decision making process is more open, with an approximate 50/50 mix of developers and power users with voting rights. 3. Our infrastructure is simplified a lot, to ensure that it creates less maintenance work for us. 4. We have made our merge policy more liberal, based on our experience with the OpenWrt package github feed. 5. We have a strong focus on automated testing combined with a simplified release process If you're interested in participating or want to learn more about the project, check out https://www.lede-project.org/. Sincerely, Jo-Philipp Wich, John Crispin, Daniel Golle, Felix Fietkau, Hauke Mehrtens John Crispin Matthias Schiffer, Steven Barth ___ openwrt-devel mailing list openwrt-de...@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ Wireless mailing list Wireless@ml.ninux.org http://ml.ninux.org/mailman/listinfo/wireless
Re: [Ninux-Wireless] Fwd: Introducing the LEDE project
L'hanno annunciato qui al battlemesh oggi pomeriggio verso le 4. https://twitter.com/nemesisdesign/status/727519655368265733 In questa iniziativa ci sono i membri più attivi (e più forti a mio avviso) di OpenWRT, se hanno deciso di fare questo passo evidentemente hanno un ottimo motivo per farlo. Uno di questi motivi è che non si riusciva a migliorare la gestione del progetto e della community OpenWRT per problemi interni di alcuni membri che si oppongono ad alcuni cambiamenti. Nemesis On Wed, 4 May 2016 00:20:16 +0200, Ilario Gelmetti wrote: Qualcuno dal Battlemesh può commentarci questa bbomba? Da quel che ho capito: 8 degli sviluppatori principali di OpenWrt hanno deciso di fare un "fork" (cioè copiare lo stato attuale di un progetto ed usarlo come base di partenza per un altro progetto) di OpenWrt, chiamato LEDE "Linux Embedded Development Environment". Era davvero necessaria questa nuova frammentazione? Forwarded Message Subject: [Battlemesh] Introducing the LEDE project Date: Tue, 3 May 2016 20:55:23 +0200 From: John Crispin Reply-To: Battle of the Mesh Mailing List To: Battle of the Mesh Mailing List , cerowrt-de...@lists.bufferbloat.net, ninux-...@ml.ninux.org, guifi-...@llistes.guifi.net, gl...@luebeck.freifunk.net, qmp-...@mail.qmp.cat, wlanw...@freifunk.net The LEDE project is founded as a spin-off of the OpenWrt project and shares many of the same goals. We are building an embedded Linux distribution that makes it easy for developers, system administrators or other Linux enthusiasts to build and customize software for embedded devices, especially wireless routers. The name 'LEDE' stands for 'Linux Embedded Development Environment'. Members of the project already include a significant share of the most active members of the OpenWrt community. We intend to bring new life to Embedded Linux development by creating a community with a strong focus on transparency, collaboration and decentralisation. LEDE’s stated goals are: - Building a great embedded Linux distribution with focus on stability and functionality. - Having regular, predictable release cycles coupled with community provided device testing feedback. - Establishing transparent decision processes with broad community participation and public meetings. We decided to create this new project because of long standing issues that we were unable to fix from within the OpenWrt project/community: 1. Number of active core developers at an all time low, no process for getting more new people involved. 2. Unreliable infrastructure, fixes prevented by internal disagreements and single points of failure. 3. Lack of communication, transparency and coordination in the OpenWrt project, both inside the core team and between the core team and the rest of the community. 4. Not enough people with commit access to handle the incoming flow of patches, too little attention to testing and regular builds. 5. Lack of focus on stability and documentation. To address these issues we set up the LEDE project in a different way compared to OpenWrt: 1. All our communication channels are public, some read-only to non-members to maintain a good signal-to-noise ratio. 2. Our decision making process is more open, with an approximate 50/50 mix of developers and power users with voting rights. 3. Our infrastructure is simplified a lot, to ensure that it creates less maintenance work for us. 4. We have made our merge policy more liberal, based on our experience with the OpenWrt package github feed. 5. We have a strong focus on automated testing combined with a simplified release process. We would like to thank the communities using the codebase and would welcome endorsements. If your community feels that the idea is good and will benefit all our communities as a whole then please post an endorsement on the lede-dev mailing list. Find out more on our project website http://lede-project.org/ Daniel Golle Felix Fietkau Hauke Mehrtens Jo-Philipp Wich John Crispin Matthias Schiffer Steven Barth ___ Battlemesh mailing list battlem...@ml.ninux.org http://ml.ninux.org/mailman/listinfo/battlemesh ___ Wireless mailing list Wireless@ml.ninux.org http://ml.ninux.org/mailman/listinfo/wireless
[Ninux-Wireless] Fwd: Introducing the LEDE project
Qualcuno dal Battlemesh può commentarci questa bbomba? Da quel che ho capito: 8 degli sviluppatori principali di OpenWrt hanno deciso di fare un "fork" (cioè copiare lo stato attuale di un progetto ed usarlo come base di partenza per un altro progetto) di OpenWrt, chiamato LEDE "Linux Embedded Development Environment". Era davvero necessaria questa nuova frammentazione? Forwarded Message Subject: [Battlemesh] Introducing the LEDE project Date: Tue, 3 May 2016 20:55:23 +0200 From: John Crispin Reply-To: Battle of the Mesh Mailing List To: Battle of the Mesh Mailing List , cerowrt-de...@lists.bufferbloat.net, ninux-...@ml.ninux.org, guifi-...@llistes.guifi.net, gl...@luebeck.freifunk.net, qmp-...@mail.qmp.cat, wlanw...@freifunk.net The LEDE project is founded as a spin-off of the OpenWrt project and shares many of the same goals. We are building an embedded Linux distribution that makes it easy for developers, system administrators or other Linux enthusiasts to build and customize software for embedded devices, especially wireless routers. The name 'LEDE' stands for 'Linux Embedded Development Environment'. Members of the project already include a significant share of the most active members of the OpenWrt community. We intend to bring new life to Embedded Linux development by creating a community with a strong focus on transparency, collaboration and decentralisation. LEDE’s stated goals are: - Building a great embedded Linux distribution with focus on stability and functionality. - Having regular, predictable release cycles coupled with community provided device testing feedback. - Establishing transparent decision processes with broad community participation and public meetings. We decided to create this new project because of long standing issues that we were unable to fix from within the OpenWrt project/community: 1. Number of active core developers at an all time low, no process for getting more new people involved. 2. Unreliable infrastructure, fixes prevented by internal disagreements and single points of failure. 3. Lack of communication, transparency and coordination in the OpenWrt project, both inside the core team and between the core team and the rest of the community. 4. Not enough people with commit access to handle the incoming flow of patches, too little attention to testing and regular builds. 5. Lack of focus on stability and documentation. To address these issues we set up the LEDE project in a different way compared to OpenWrt: 1. All our communication channels are public, some read-only to non-members to maintain a good signal-to-noise ratio. 2. Our decision making process is more open, with an approximate 50/50 mix of developers and power users with voting rights. 3. Our infrastructure is simplified a lot, to ensure that it creates less maintenance work for us. 4. We have made our merge policy more liberal, based on our experience with the OpenWrt package github feed. 5. We have a strong focus on automated testing combined with a simplified release process. We would like to thank the communities using the codebase and would welcome endorsements. If your community feels that the idea is good and will benefit all our communities as a whole then please post an endorsement on the lede-dev mailing list. Find out more on our project website http://lede-project.org/ Daniel Golle Felix Fietkau Hauke Mehrtens Jo-Philipp Wich John Crispin Matthias Schiffer Steven Barth ___ Battlemesh mailing list battlem...@ml.ninux.org http://ml.ninux.org/mailman/listinfo/battlemesh signature.asc Description: OpenPGP digital signature ___ Wireless mailing list Wireless@ml.ninux.org http://ml.ninux.org/mailman/listinfo/wireless
Re: [Ninux-Wireless] Bozza decreto attuazione direttiva EU
Il 30/04/2016 14:20, Nemesis ha scritto: > E' disponibile una bozza del decreto per l'attuazione della normativa EU > di cui abbiamo parlato sul blog: > > http://www.sviluppoeconomico.gov.it/images/stories/documenti/schema_di_decreto_di_attuazione_2014_53_UE.pdf Ho aggiornato http://wiki.ninux.org/LeggiWireless con una sezione apposita. Stefanauss. signature.asc Description: OpenPGP digital signature ___ Wireless mailing list Wireless@ml.ninux.org http://ml.ninux.org/mailman/listinfo/wireless
