7 ms·
OpenWrt and LEDE to re-merge
- davejamesmiller 10y agoThe submission title "OpenWrt and LEDE to re-merge" doesn't match the post which is titled "Talks between OpenWrt and LEDE" and specifically says: > It is still not decided that both project will finally merge
- kybernetikos 10y agoIt's the record of more than one meeting. Check out the part under 'OpenWrt / LEDE follow up meeting'.
- draugadrotten 10y ago> 1. Results from meeting at prpl OpenWrt summit Agreed upon: - merging back together - using OpenWrt as the merged back project name
- davejamesmiller 10y agoMy bad, I thought the first section was a summary and skipped the rest.
- muppetman 10y agoI did exactly the same thing.
- deleted 10y ago[deleted]
- hoechst 10y agoThe forked from OpenWRT in May 2016 and are now already going back. I guess there's not much to gain from the code merge for end users except for a few bug fixes (https://lede-project.org/faq#were_there_any_technical_reasons_to_split_from_openwrt https://lede-project.org/faq#were_there_any_technical_reason...).
- deleted 10y ago[deleted]
- gadotamexi 10y agoMy Uncle Brayden just got a new cream Chevrolet Camaro Convertible by working part time off of a macbook air... HERE ►ＷＷＷ.ebiz3.ＣＯＭ
- bipson 10y agoWell, technically you might be right, but I would like to point out that two groups joining their efforts, while picking the best of both (organizational) worlds (processes, infrastructure, etc.) is always a good thing in the open-source world and means progress could be accelerated for the new, unified project. Politically this could mean that either OpenWRT has moved and intends to improve regarding the issues that lead to the fork, or that the fork wants to return home either way. I suppose at least both groups think their time is better spent together instead of separate, and I personally like these news way more than those of yet another fork...
- hoechst 10y agoSure, don't get me wrong, I think it's great that they put aside their differences and decided to work together again. I agree that focusing of one project is better. Just wanted to put it more into context.
- cookiecaper 10y agoYes. It's so rare to find people willing to cooperate and make some compromises for much larger overarching productivity. The BFG and Pylons merged to become Pyramid after recognizing that they were working toward a very similar vision and that it was just wasted effort to be getting there separately. It's always great to hear of this kind of thing, and I have huge respect for the people behind the few projects that are willing to do it.
- ak217 10y agoFrom what I've gathered so far, LEDE is where the vast majority of activity and development moved after OpenWRT alienated most of the participants with friction in their workflow. OpenWRT had just a shell of 3 project members left, but continued to have substantial name recognition.
- deleted 10y ago[deleted]
- deleted 10y ago[deleted]
- deleted 10y ago[deleted]
- ktta 10y agoThis is awesome! So this is some of the important stuff: 1. Use the LEDE codebase, rather than OpenWrt's (undecided but likely). They'll first push any new changes in OpenWrt since the fork into LEDE, and then rebrand move completely to LEDE's codebase. 2.Will be using OpenWrt's name, not the name 'LEDE' anymore. 3. The workflow is still being discussed. The workflow of both LEDE and Openwrt will be learnt from to come up with the new one. Github will be used for issues, not PRs.
- Jaepa 10y agoAre you sure about #3? I read it issues are not to be used but PR are.
- ktta 10y agoYou're right #3 is not right, but its not completely wrong either. Looks like issues on github won't be used, but PRs won't really be used since there isn't going to be any merging done using PRs. Maybe it'll be a bit more clear as to what they'll do. I wonder what's left for them to host on github if people can't open issues or merge their code. >- workflow between LEDE and OpenWrt? Using Github to gather pull requests, but not use the merge pull request feature of Github, have staging trees for queuing changes, and then merge into the main tree
- TwoNineFive 10y agoI follow OpenWRT/LEDE fairly closely and I agree that these bullet points are most likely the outcomes. Basically, in a sentence, LEDE may be allowed to take over management of the OpenWRT assets. It's not done yet though. I would not be surprised if six months from now they was still petty haggling going on.
- blumentopf 10y agoLEDE folks have started to dump their patches on kernel mailing lists, but they don't seem to be mainline-able as is and the submitter is loathe to rework them: http://marc.info/?l=linux-kernel&m=148230680302480&w=2 http://marc.info/?l=linux-kernel&m=148230680302480&w=2
- dohqu8Zi 10y agoThe majority of OpenWRT/LEDE patches are gross hacks that need a major rework or a completely different approach. This is not the first patch of that kind.
- RunningDroid 10y agoDo you have a source for that? Iirc openwrt refused to include a kernel patch to make hardware NAT work because it was too much of a hack.
- dv_dt 10y agoPerhaps there is more context, but from a narrow read: the linked email states a need, contains a patch that solves the problem, and offers to solve it another way if needed... that seems pretty mature? The text literally says: > I am not sure if this is the best way to remove the quirks from the build. Let me know if you prefer a different way of solving this.
- blumentopf 10y agoYou need to read the whole thread: http://marc.info/?l=linux-pci&m=148238610022972&w=2 http://marc.info/?l=linux-pci&m=148238610022972&w=2 "obviously i am interested to get this upstream with the least amount of effort. I am quite aware though that some patches will need an overhaul to be applicable for upstream. its not really my call if it is enough to make this an enable patch and review the quirks enabled by it or if the code needs to be moved." Upstreaming patches into the kernel requires that you're willing to spend time to rework them so that the result is maintainable. Saying from the start that you only want to do the least amount of work possible isn't helpful.
- ausjke 10y agobest news for Christmas!
- nwmcsween 10y agoI really wish the openwrt software ecosystem wasn't in its own little world, things like ubus + augeus would be nice.
- junaidajmal 10y agoStay at home mom Kelly Richards from New York after resigning from her full time job managed to average from $6000-$8000 a month from freelancing at home… This is how she done ,,,,,,,,,,,,,,,HERE ►WWW.bizcash3.COM
- junaidajmal 10y agoStay at home mom Kelly Richards from New York after resigning from her full time job managed to average from $6000-$8000 a month from freelancing at home… This is how she done ,,,,,,,,,,,,,,,HERE ►WWW.bizcash3.COM
- junaidajmal 10y agoStay at home mom Kelly Richards from New York after resigning from her full time job managed to average from $6000-$8000 a month from freelancing at home… This is how she done ,,,,,,,,,,,,,,,HERE ►WWW.bizcash3.COM