Hello,
I am relatively new to this community and have not yet accomplished anything
worthwhile but anyway.
Some thoughts expressed on this list.
->People do not want to work on the Hurd because they are not sure of its
status, future, et.al They would rather wait till something is finalised.
->The Hurd has organisational problems.

Response:
>From my organisational experience, leadership cannot be thrust down people's
throats. It evolves through the application of theory to practical
situations and constant reassessment of practice and corresponding
modification of theory ie., application of praxis. In the midst of this
leadership evolves.
People in the GNU, GNU/Hurd community have been working on different aspects
of development and are at different stages of this evolutionary process and
as long as each one plays their role in this ecosystem to the best of their
abilities the ecosystem will grow in a healthy manner.
The discussion that has come up is very healthy as it has identified certain
areas which needs more specific attention. But that should not be a reason
to sit back and wait for someone(such as a benovalent dictator) to hand us a
solution as this would only slow down or reverse whatever good is expected.
Rather, we need to jump in and get our hands dirty.
In order for us to meaningfully contribute to the ecosystem/process we need
practical experience combined with an indepth knowledge. By experimenting
with different microkernels, the Hurd hackers have gained an indepth insight
into what is needed and now, combined with innovative ideas, are working on
what is missing. If we are to be prepared to contribute we need to work on
the existing system, enable its evolution and grow in experience and then
when a newer and better microkernel comes along there will more and prepared
kernel hackers.
Towards praxis,
Vikram Vincent

Reply via email to