Notices where this attachment appears
-
> We decided to create this new project because of long standing issues that we were unable to fix from within the OpenWrt project/community:
> Number of active core developers at an all time low, no process for getting more new people involved.
> Unreliable infrastructure, fixes prevented by internal disagreements and single points of failure.
> 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.
> Not enough people with commit access to handle the incoming flow of patches, too little attention to testing and regular builds.
> Lack of focus on stability and documentation.
> To address these issues we set up the LEDE project in a different way compared to OpenWrt:
> All our communication channels are public, some read-only to non-members to maintain a good signal-to-noise ratio.
> Our decision making process is more open, with an approximate 50/50 mix of developers and power users with voting rights.
> Our infrastructure is simplified a lot, to ensure that it creates less maintenance work for us.
> We have made our merge policy more liberal, based on our experience with the OpenWrt package github feed.
> We have a strong focus on automated testing combined with a simplified release process.
Sounds *very* similar to the egcs events. Seems the increased transparency paid off. Cool!
https://lede-project.org/about
Link to http://hintjens.com/blog:93 obligatory.