Conversation

Notices

1. Hallå Kitteh (clacke@social.heldscal.la)'s status on Thursday, 04-Jan-2018 11:43:48 UTC Hallå Kitteh
   > The new, unified OpenWrt project will be governed under the rules established by the LEDE project.
   
   > The merged project will use the code base of the former LEDE project. OpenWrt specific patches not present in the LEDE repository but meeting LEDEs code quality requirements got integrated into the new tree.
   
   Wow. Sounds like a reverse merger like what happened to egcs and gcc back in the day. And I've never even heard of #LEDE! Well, sounds like this is a good thing for #OpenWRT and everyone else. Somebody challenged their way of doing things and apparently won out.
   
   https://lede-project.org/#announcing_the_openwrtlede_merge
   
   /via https://identi.ca/avadiax/note/ZMRteuJiQvGEY6zUK6ZJ2Q
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Thursday, 04-Jan-2018 11:47:19 UTC Hallå Kitteh

     in reply to
     > 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.
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Thursday, 04-Jan-2018 11:48:37 UTC Hallå Kitteh

     • Ekaitz Zárraga 👹
     @ekaitzzarraga Cool, thanks for the background.
   • Antanicus (antanicus@social.coop)'s status on Thursday, 04-Jan-2018 12:53:21 UTC Antanicus

     in reply to

     @clacke the 50/50 voting model is a good start. Ironically, democracy is often lacking in open source communities (mainly due to lack of democracy-enabling structures) and developers end up becoming "benevolent dictators". Embracing the #cooperative model would further improve the situation, in my opinion

     Hallå Kitteh repeated this.