Apr 14, 2022, 14:06 by 0xloem@gmail.com:
> Hi Martin,
>
>> I think we all agree that it'd be good to have test racks that have all of the boards in the coreboot repository for verification, however that's currently not practical with the resources we have. The whole thing just isn't a simple problem to solve.
>>
>
> Often the biggest impediment to something like this is simply holding it as a shared goal, and continuing to do so when issues arise.
>
> If public test labs were desired, a callout for donations of space and hardware could be placed on the main page. If somebody had the capacity to do more than that, then local makerspaces and hackerspaces could be reached out to.
>
It's a good point. Maybe we can put up a webpage with how an individual can help the coreboot project. Put up a list of boards to be adopted for testing and how to find which commit broke them if they're broken.
Hoping I'm not derailing too far here: Could we consider modeling this based on
http://appdb.winehq.org ? I.e., people can contribute test results per board, and upload things like "which commit hash did you build with", "what's your .config", etc?
We could even consider plumbing that into the build system. "make submit_test_result" perhaps ;)
>> I'm actually also not completely convinced that just testing the boards is the solution to whether or not we keep a board/chip on the mastre branch. If there really aren't any people using coreboot on their quark boards, then personally, I don't see any need to keep it in the master branch. I know others feel differently, but as I said earlier in this thread, I don't think there's actually any harm in moving an aging or little-used platform to be maintained on a branch.
>>
>
> Sounds like there is a difference of opinion in the community.
>
Always. ;-)
> It seems obvious to me that there would be people using coreboot on their quark boards. The world is gigantic.
>
> But you have a different opinion, which is fine.
>
> It seems to me the reason to include a board is because people care about doing so.
>
Agreed. Currently we have no way of knowing whether or not anyone cares about a board. There are two ways people typically make it known - by working on a board or by testing a board.
> I care enough about including boards that I'd test this one if it was needed to do so to retain it. But I'm just a visitor. And it seems more productive to discuss public test labs that could grow to support more boards.
>
Sure, and I'm not trying to advocate that we remove anything. Mostly right now I'm trying to figure out how we should decide when things should or should not be moved to a branch to make it easier going forward.
Take care
Martin
_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-leave@coreboot.org