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 ---

> On Nov 19, 2025, at 12:01 PM, Jonas Lochmann <[email protected]> wrote:
> 
> Am Wed, Nov 19, 2025 at 08:56:20AM -0700, schrieb Philip Prindeville via 
> openwrt-devel:
>> I’ve got a PR left for jshn_get_index which retrieves the index of an object 
>> (the currently selected object) inside an array. 
>> It’s the last PR needed for Kea migration from ISC-DHCP compatible UCI 
>> configs.
> 
> Please be honest. It's not needed at all for this migration. It is
> needed for your implementation of the migration - that I consider
> questionable, but still OK.

Being honest... We need a migration path from ISC-DHCP and bikeshedding or 
downright apathy has been an impediment to that happening.

There are multiple ways to solve most engineering problems.  I picked one that 
got me the most dependenable path forward given my skills and the time 
available to test and develop.

But be honest: ucode isn't the only way to solve this, is it?

If I'm going to be maintaining this indefinitely, then I'd think I'd get some 
lattitude in how I pick to solve this particular problem.


> I could also cry that my PRs are required for working IPv6. But I
> am honest. Due to this, they are not considered important enough to
> check soon. So technically, I am running and depending on a fork of
> OpenWrt. But we already discussed that in the list.

I think this isn't an apples-to-apples comparison.  I'm the maintainer for 12 
packages, and you maintain.... zero.

I've made a commitment to the project.  It would be good to get some 
reciprocity for my efforts.  That's all any contributor asks for.

-Philip



--- End Message ---
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to