bcm4908: NetGear OEM firmware for R7900P identical to R8000P
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- The information supporting the Subject is documented in this OpenWRT forum thread: https://forum.openwrt.org/t/kernel-patches-netgear-r8000p-r7900p/114540 My neighbor has a R7900P and it is likely to be unsupported from a security point-of-view shortly (Netgear stops all support 3 years after the last unit is manufactured). I was going to try to build a R7900P image labeled as such but am not sure what to do with the kernel 5.10 patches. Duplicating the patches might work for my build, but the projects bulk builds would patch a previously patched kernel. I previously added the TRENDnet TEW-810DR which had the same Board ID as the D-Link DIR-810L which did not involve kernel patches. Any guidance on how to deal with the patches? -- J. Scott Heppler --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
bcm4908: NetGear OEM firmware for R7900P identical to R8000P
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- The information supporting the Subject is documented in this OpenWRT forum thread: https://forum.openwrt.org/t/kernel-patches-netgear-r8000p-r7900p/114540 My neighbor has a R7900P and it is likely to be unsupported from a security point-of-view shortly (Netgear stops all support 3 years after the last unit is manufactured). I was going to try to build a R7900P image labeled as such but am not sure what to do with the kernel 5.10 patches. Duplicating the patches might work for my build, but the projects bulk builds would patch a previously patched kernel. I previously added the TRENDnet TEW-810DR which had the same Board ID as the D-Link DIR-810L. It did not involve kernel patches. Any guidance on how to deal with the patches? -- J. Scott Heppler --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [Suggestions] Streamline localization by using Weblate for the project, use LiberaPay or OpenCollective to enable people to donate
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- ‐‐‐ Original Message ‐‐‐ On Tuesday, September 24, 2019 1:13 AM, Paul Spooren wrote: > > I think that's a good idea! As it doesn't need to be directly integrated > in any existing workflow nor requires privileges on any Git, it's > basically just a fancy front-end with translation suggestions for .po > files right? > > Out of curiosity I requested a libre account for a quick evaluation, if > anyone is in serious doubt on evaluation it I'll instantly cancel the > request. However I think this is in line with > https://openwrt.org/meetings/hamburg2019/start#luci_translations > Correct, it needs no privileges to update Weblate's .po copy from the repository and if you want to commit the localization that has been made by contributors you can opt to have the Weblate commit automatically if you're feeling daring, or you can just opt to have manually triggered PR where someone with merge permission can review per usual contribution workflow. The Continuous Localization documentation documents the workflow and possibilities pretty well: https://docs.weblate.org/en/latest/admin/continuous.html Yep, Weblate is largely a browser based localization tool frontend with a pinch of middleware components to update Weblate's copy, send out notifications, and make commits or PR's. Thanks again for your time. If I can help pilot any, etc let me know! -Scott --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [Suggestions] Streamline localization by using Weblate for the project, use LiberaPay or OpenCollective to enable people to donate
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- First and foremost, as a user of OpenWrt and LuCI by way of TurrisOS thanks for everyone who has contributed to OpenWrt. As someone who's seeking to give back to the project via localization I noticed that while OpenWrt has relatively straightforward documentation on contributing localization (https://github.com/openwrt/luci/wiki/i18n), the process could be streamlined a great deal more. In particular by using Weblate thus making easier it for those who don't know Git and providing significant quality of life improvements even for those who do know Git. Those who want to do offline localization could continue to do so w/o issue. For those who aren't familiar with localization, Weblate is basically a web based tool that allows to contribute by simply entering in a localized string and hitting 'suggest' rather than having to Git clone, download an offline client like Lokalize, and then make a PR. There's also a good number of nice things to improve localization. It's easy to visually see what languages need localization work, you can be notified when there's new strings or a few other trigger events, and you can utilize not only the 'translation memory' of OpenWrt itself, but other FOSS such as related routing projects like Foris. The great thing is that while you can self host your own Weblate server, because OpenWrt is FOSS, the folk behind Weblate would likely offer free hosting given their Gratis for libre projects pricing. To better see what I'm talking about in action please check out: https://hosted.weblate.org/projects/ As a secondary note in what sounds like was written in late 2016, there were private discussions about public crowdfunding to help pay for servers (https://openwrt.org/infrastructure). Talking with tmomas on the forums it sounds like the current bottleneck is people power. Any surplus donations beyond infrastructure could be used to pay for part or full time development or for bounties. Between the LiberaPay and OpenCollective, OpenCollective may be preferable because it is designed to allow both reoccurring and one off donations. Thanks for your time and efforts, Scott --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
