Thank You for Your answer.
The reason, why I self think that there is
still some productivity in my posts about the
monetary inefficiency of the MINIX project, despite
the posts not being _VERY_ productive, is that
social systems are also SYSTEMS, like mechanical SYSTEMS,
electrical SYSTEMS, sofware SYSTEMS.
If there is some elephant sitting in the room,
then that elephant can "clog the gears". For example,
the Debian Linux project is not just a technical
project, but it is also a social project.
(2016 11 xx Mini DebConf at Cambridge Session by
Lucy Wayland About Diversity and Inclusion BoF)
https://www.youtube.com/watch?v=a7yyWpIpeUgThe way I see it, it is precisely the fact that the
social aspects, the SOCIAL SYSTEM, have been taken
care of, what allowed both, the Linux, and the Debian
projects to get huge amounts of developers working on it.
On the other hand, the MINIX project seems to lack
manpower and volunteers and that is not some
"rumour by Martin Vahi", but a statement that has been
claimed by MINIX3 core developers at the MINIX3 Google Groups
forum and at GitHub discussion threads.
The difference between the MINIX and Linux+Debian is
that in the case of Linux and Debian the projects did
not get millions for the core group. That set the
expectations low for the rest of the volunteers and
by the time the IBM and the rest came in with their
truckloads of money, the Linux was pretty much
up and running. In the case of MINIX there exists
the question, why should a volunteer make a great
effort to contribute to the project, if the core
team is "swimming in money" and has not even made
sufficient effort to get those features
that are important for the volunteers, like the SMP,
completed.
Censoring me here is not going to make the problem
go away, but addressing the problem might help
the MINIX project as a SOCIAL SYSTEM, not just as a
technical project, to get some wind under its wings.
I was hoping that I don't have to spell it out
like that, but it seems that people didn't figure
it out on their own.
Basically, the way I see it, the path forward might be
to offer the nonpaid volunteers a FULLY FUNCTIONAL SYSTEM
(read: has SMP,GCC,pthreads, etc.) and then
the nonpaid volunteers can contribute small bits,
port packages/ports, add drivers, etc. like it is done
in Linux and with Wikipedia articles. But currently,
the leap for porting GCC, which is needed for GCC specific
userland software, and the leap for fixing the SMP,
which even the paid team found "too big amount of work", is
unrealistically huge things to ask from unpaid volunteers,
not to mention, if even the paid team, who already knew the project
internals, didn't do it, then why should the volunteers,
who have to start learning the project internals.
All in all it seems to me that the MINIX has been a
research project first and production project for
"real life" applications second. The requirements for a university
research projects tend to differ a lot from the
requirements of an open source software project that
is meant to be in production use. For example, the
prioritization of interesting scientific articles over
basic SMP support is clearly one such difference. Neither can
any production oriented operating system project ignore
the userland software that just happens to be GCC specific.
So, some transition period from one development model
to another, social system wise and priorities wise,
can be expected.
P.S. I'll shut up in this thread now, which means that
if I answered any followup questions in this thread,
then I would break my pledge to shut up in this thread :-D