On Thu, 22 Nov 2007, Kai Blin wrote: [...]
I know some projects did an introductory quiz to figure out the student's coding skills, I'm not convinced the knowledge needed for Wine can be tested in a quiz. What do you think?
Maybe just asking them to compile Wine and submit their include/config.h or make test results. This can be used to check that their config does not have big problems like a bad fontforge or 64/32bit issues that could cause them problems when they start their project.
Asking them to submit conformance tests is an interesting idea too, but depending on the area it can be quite a bit of work. For some projects it may also not be possible to write relevant tests (e.g. we cannot test ExitWindows() or KDE/Gnome theme integration). But for those projects where it makes sense it could be a good idea.
The other ideas, public git repository, public blog / more frequent public updates, all seem like good ideas that could address the relative opacity of past SoCs.