GNU mach cleanup contribution

[faif]

> I apologise if this is not the right list to write about this issue.
>
> We are 2 friends who are interested in contributing to the "GNU Mach Code
> Cleanup", found in
> http://www.gnu.org/software/hurd/community/gsoc/project_ideas.html. We'd
> like to do it for both GSOC and voluntarily afterwards, but for now we can
> start just voluntarily to see how it goes.
>
> Just a couple of questions:
> a) Is this task related with debugging also, or just fixing warnings and
> improving C code? b) Do we need to register somewhere before starting?

Most programming discussions happen in bug-hurd@gnu.org, so that's the place
to start.

> a) Is this task related with debugging also, or just fixing warnings
> and improving C code?

The actual GSoC task is really about improving the code: if you find
something that looks wrong while working on it, you should try to fix it
of course; but trying to track down known bugs is not part of the task.

However, the major goal of GSoC is for new people to get into the
project -- you should learn quite a bit about Mach in the process, and
be able to do other work on it afterwards :-) This is indeed why I have
put this idea on the list.

Well, that's exactly what we want to do. To start learning about GNU/Hurd (even 
if we know that Mach might be replaced in the future) and then contribute in 
other parts also :)

> b) Do we need to register somewhere before starting?

Well, for actual GSoC participation you need to follow the usual
procedure, as explained in the FAQ. In either case, you are of course
most welcome to start working on it right away -- though it's highly
recommended that you stay in contact and let us know what you are doing
exactly :-)

OK, we can start doing it in our free time. Where should we start from? We both 
have already installed Debian GNU/Linux, and I was wondering which 
package(s)/repositories are needed for this job -- gnumach, gnumach-dbg 
(probably not), or gnumach-dev?

Thanks for the tips.