diff options
author | Miguel de Icaza <miguel@gnome.org> | 2003-07-04 22:10:48 +0400 |
---|---|---|
committer | Miguel de Icaza <miguel@gnome.org> | 2003-07-04 22:10:48 +0400 |
commit | d3090ee9f81c2f8e5d204308ca9976b53357ad10 (patch) | |
tree | 611c9b174868367c765601506b5b9a944f98fa08 /web/mono-todo | |
parent | d0de9914659f3badb830c709b6b9de69b35e2af7 (diff) |
use webformat
svn path=/trunk/mono/; revision=15928
Diffstat (limited to 'web/mono-todo')
-rw-r--r-- | web/mono-todo | 102 |
1 files changed, 59 insertions, 43 deletions
diff --git a/web/mono-todo b/web/mono-todo index 4555cb1c0bb..699fa1569ce 100644 --- a/web/mono-todo +++ b/web/mono-todo @@ -1,52 +1,68 @@ -<h2>Mono hacking TODO list</h2> - -From time to time people that want to contribute to Mono ask on the mailing list -what they can help with. The generic answer is always:<br> -<ul> - <li>Write documentation. - <li>Write regression tests. - <li>Complete the implementations of the class libraries. - <li>Help fix the bugs filed in our bugzilla database. -</ul> - -The proposed tasks are very important for the Mono project and are suitable for people -that can dedicate even just an hour per week to contribute. -But some people may need something more -focused to work on, such as students that want to do a thesis -on their contribution to Mono. For such people (and also for professors who want -ideas for thesis regarding JIT or VM technologies), here is a list of tasks that -need attention.<p> -The estimated time to complete any of the tasks is between 1 week to several months -to accomodate for different hacking possibilities.<br> - -Note on the time estimates: they are very rough estimates, a smart and dedicated hacker -can complete the tasks in half of the minimum time, a part-time hacker that also has a -social life can take more than double the max time, but there's nothing to worry as long as -progress is being done:-).<p> -If some people (or group of people) want to take on a task, they should write to -the mono-devel mailing list and in the relative bugzilla bug report. Discussions -about how to implement a feature or additional information on the task should be mailed to -the list or in the bugzilla report as well so that people can keep informed on the -progress or have the information needed to start contributing.<p> - -Mono is an excellent platform for research on JITs, virtual machines and specifically -the CLR because it provides an advanced free software implementation that can be used as -a basis for more optimizations, new approaches to problems and new features.<p> -There are different areas of interest where high-level contributions can be made: -<ul> - <li><b>JIT compiler</b>: tasks can be: adding more optimizations, reducing +* Mono hacking TODO list + + From time to time people that want to contribute to Mono ask + on the mailing list what they can help with. The generic + answer is always: + <ul> + * Write documentation. + * Write regression tests. + * Complete the implementations of the class libraries. + * Help fix the bugs filed in our bugzilla database. + </ul> + + The proposed tasks are very important for the Mono project and + are suitable for people that can dedicate even just an hour + per week to contribute. But some people may need something + more focused to work on, such as students that want to do a + thesis on their contribution to Mono. For such people (and + also for professors who want ideas for thesis regarding JIT or + VM technologies), here is a list of tasks that need attention. + + The estimated time to complete any of the tasks is between 1 + week to several months to accomodate for different hacking + possibilities. + + Note on the time estimates: they are very rough estimates, a + smart and dedicated hacker can complete the tasks in half of + the minimum time, a part-time hacker that also has a social + life can take more than double the max time, but there's + nothing to worry as long as progress is being done. + + If some people (or group of people) want to take on a task, + they should write to the mono-devel mailing list and in the + relative bugzilla bug report. Discussions about how to + implement a feature or additional information on the task + should be mailed to the list or in the bugzilla report as well + so that people can keep informed on the progress or have the + information needed to start contributing. + + Mono is an excellent platform for research on JITs, virtual + machines and specifically the CLR because it provides an + advanced free software implementation that can be used as a + basis for more optimizations, new approaches to problems and + new features. + + There are different areas of interest where high-level + contributions can be made: + + <ul> + * <b>JIT compiler</b>: tasks can be: adding more optimizations, reducing compile time, porting to different architectures. - <li><b>AOT compiler</b>: optimizing the compiler output and the AOT loader, + + * <b>AOT compiler</b>: optimizing the compiler output and the AOT loader, better support for multiple application domains. - <li><b>VM runtime</b>: optimizing the runtime data structures, experimenting with + + * <b>VM runtime</b>: optimizing the runtime data structures, experimenting with different garbage collectors, integration with different component models. - <li><b>Class library</b>: many opportunities in the implementation of regular + + * <b>Class library</b>: many opportunities in the implementation of regular expressions, Xml related technologies (XPath, XLST, etc). - <li><b>Compilers</b>: writing compilers, interpreters and runtimes for langauges + + * <b>Compilers</b>: writing compilers, interpreters and runtimes for langauges so that they run on the CLR (using Reflection.Emit support, for example). -</ul> + </ul> -Happy hacking!<p> +Happy hacking! <table border=1 cellspacing="0" cellpadding="0"> <tr> |