> It seems no effort was put into securing the project's continuity in the long term.
But it's no small challenge, right? I'd suppose that regression testing these features against a bunch of devices requires lots of human interaction or complex test scenario descriptions.
I meant more along the lines of documenting your build process or noting where any of the binary blobs were sourced from. Simple things that make coming in as a new contributor viable. As it is now, basic, essential information vanishes along with each maintainer who loses interest in the project.
The question of what version of the OEM system image to use isn't always super clear. I've definitely seen situations where rom devs will mix and match whatever it takes to get their desired results.
In which case the instructions start with, "Go to the following URL, download the file named foo, and use the following command to extract bar and baz." But write those instructions!
But it's no small challenge, right? I'd suppose that regression testing these features against a bunch of devices requires lots of human interaction or complex test scenario descriptions.