summaryrefslogtreecommitdiff
path: root/user
diff options
context:
space:
mode:
authorJeremie Koenig <jk@jk.fr.eu.org>2011-04-08 17:45:01 +0200
committerJeremie Koenig <jk@jk.fr.eu.org>2011-04-08 18:03:03 +0200
commitba3c75a2496401fc189006db19ea75fede28907d (patch)
treedcae81d80cf8134d71ee18f80af6ef498fa946e5 /user
parentcd48e7119c3634550411daa66c3a617082d39630 (diff)
gsoc2011 (java): random improvements
Diffstat (limited to 'user')
-rw-r--r--user/jkoenig/gsoc2011_proposal.mdwn27
1 files changed, 15 insertions, 12 deletions
diff --git a/user/jkoenig/gsoc2011_proposal.mdwn b/user/jkoenig/gsoc2011_proposal.mdwn
index e8f7679b..7179ff87 100644
--- a/user/jkoenig/gsoc2011_proposal.mdwn
+++ b/user/jkoenig/gsoc2011_proposal.mdwn
@@ -171,8 +171,8 @@ native code and
[link it statically](http://gcc.gnu.org/wiki/Statically_linking_libgcj)
using GCJ, should anyone want to use a
translator written in Java for booting. Note that Java is
-[being](http://oss.readytalk.com/avian/)
-[used](http://www.linuxjournal.com/article/8757)
+[being](http://www.linuxjournal.com/article/8757)
+[used](http://oss.readytalk.com/avian/)
in this manner for embedded development.
Java bindings would lower the bar for newcomers
@@ -471,6 +471,8 @@ to design and implement similar solutions for Java.
* A hurd-java package would contain the Java code developped
in the context of this project.
+ * The Java code would be documented using javadoc
+ and a tutorial for writing translators would be written as well.
* Modifications to MIG would be submitted upstream,
or a patched MIG package would be made available.
@@ -519,27 +521,28 @@ The dates listed are deadlines for the associated tasks.
Finish implementing pthread signal semantics.
* *June 5.*
Port OpenJDK
- * *June 19 (two weeks).*
+ * *June 12.*
Fix the remaining problems with GCJ and/or OpenJDK,
possibly port Eclipse or other big Java packages.
- * *June 26.*
+ * *June 19.*
Create the bindings for Mach.
- * *July 3.*
+ * *June 26.*
Work on some kind of basic Java libports
to handle receive rights.
- * *July 10.*
+ * *July 3.*
Test, write some documentation and examples.
- * *July 24 (two weeks).*
+ * *July 17 (two weeks).*
Add the Java target to MIG.
- * *July 31.*
+ * *July 24.*
Test, write some documentation and examples.
- * *August 7.*
+ * *August 7 (two weeks).*
+ Implement a modular libfoofs to help with translator development.
Try to write a basic but non-trivial translator
to evaluate the performance and ease of use of the result,
rectify any rough edges this would uncover.
- * *Last two weeks.*
- Polish the code,
- do the packaging.
+ * *August 22. (last two weeks)*
+ Polish the code and packaging,
+ finish writing the documentation.
## Conclusion