community/gsoc/project_ideas: (Lisp, (Python), ... bindings): Add some links.

1 files changed, 12 insertions, 7 deletions

diff --git a/community/gsoc/project_ideas.mdwn b/community/gsoc/project_ideas.mdwn
index c845eef9..3d81a83e 100644
--- a/community/gsoc/project_ideas.mdwn
+++ b/community/gsoc/project_ideas.mdwn
@@ -19,11 +19,10 @@ contact us -- on [[IRC]] or using [[mailing_lists]].
 
 ## Lisp, (Python), ... bindings
 
-*NOTE* someone is already working on python bindings!
-
 The main idea of the Hurd design is giving users the ability to easily
-modify/extend the system's functionality. This is done by creating filesystem
-translators, or sometimes other kinds of Hurd servers.
+modify/extend the system's functionality.  This is done by creating
+[[filesystem_translators|hurd/translator]], or sometimes other kinds of Hurd
+servers.
 
 However, in practice this is not as easy as it should, because creating
 translators and other servers is quite involved -- the interfaces for doing
@@ -37,21 +36,27 @@ high-level language, that helps quickly creating simple programs, are highly
 welcome.
 
 Several approaches are possible when creating such bindings. One way is simply
-to provide wrappers to all the available C libraries (libtrivfs, libnetfs
+to provide wrappers to all the available C libraries ([[hurd/libtrivfs]], [[hurd/libnetfs]]
 etc.). While this is easy (it requires relatively little consideration), it may
 not be the optimal solution. It is preferable to hook in at a lower level, thus
 being able te create interfaces that are specially adapted to make good use of
 the features available in the respective language.
 
 These more specialised bindings could hook in at some of the lower level
-library interfaces (libports, glibc, etc.); use the mig-provided RPC stubs
-directly; or even create native stubs directly from the interface definitions.
+library interfaces ([[hurd/libports]], [[hurd/glibc]], etc.); use the
+[[microkernel/mach/MIG]]-provided [[microkernel/mach/RPC]] stubs directly; or
+even create native stubs directly from the interface definitions.
 
 The task is to create easy to use Hurd bindings for a language of the student's
 choice, and some example servers to prove that it works well in practice. This
 project will require gaining a very good understanding of the various Hurd
 interfaces. Skills in designing nice programming interfaces are a must.
 
+(!) There has already been some [earlier work on Python
+bindings](http://www.sigill.org/files/pytrivfs-20060724-ro-test1.tar.bz2), that
+perhaps can be re-used.
+
+
 ## virtualization using Hurd mechanisms
 
 The main idea behind the Hurd design is to allow users to replace almost any