Paul Menzel wrote:
Problem: People do not know who is working on porting what board.
Solution from Corey:
Under the premise that every developer would do his development in that “development” repository (I guess in his own branch) or would commit his effort at the end of the day, people could track what they are working on. So everybody would be up to date what ports are being worked on.
we're running several internal coreboot repositories here at coresystems, but creating yet another open repository would not mean we can easily commit to those, as a lot of that code has to go through legal clearance first before we can make it publically available. I guess that issue applies for a lot of (all?) people working on modern (non-amd) chipsets these days
So I don't see how another repository would improve the situation more than just sending patches or URLs to trees to the list?
We can add new repositories if there is need for it, and we can also add a git bridge if people desire that. But the past showed that we did a lot of this stuff and it never got used really. So I'm trying to keep things simple. coreboot is a complex thing. Adding 5 more repositories (or just 1 more) will not make it easier for newcomers to get started.
Stefan