google-code-export / monoxna

Automatically exported from code.google.com/p/monoxna
Other
1 stars 1 forks source link

Helpy helpy #35

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi, I am not sure if this is the best place to post this, but I didn't 
want to `pollute' the wiki, so here goes.

I would very much like to help on this project but it is quite difficult 
to work out where one can `leap in'. The todo list is fairly vague and 
surely doesn't cover all needed tasks? Would it be possible to point me in 
the direction of a set of smallish tasks to do... even if it is something 
as mundane as documentation, that'd be a nice place to start from.

I have coded in C#/XNA, but not on a particularly large scale, though I 
have experience in larger projects in other languages.

Hope I can help,
Michael.

Original issue reported on code.google.com by tubw...@googlemail.com on 21 Jul 2009 at 8:51

GoogleCodeExporter commented 9 years ago
I'm well aware of the lack of helpful information in the todo list, but I 
haven't had
the time to do it properly. I updated the list a week or something back, but 
all the
tasks are somewhat complex.

I know there's plenty to be done in the runtime assembly, but I haven't gotten 
around
to checking the current status. I've been focusing on the content pipeline 
support. 

At the present time the best thing would be if someone could do just that. 
Check the
current status by developing test applications, and to help build the Status 
wiki.
Another task I've put off so far is to either clean up the old google group or 
to
find new ways of communicating. 

Original comment by lav...@gmail.com on 21 Jul 2009 at 10:55

GoogleCodeExporter commented 9 years ago
Join the irc channel #monoxna on irc.gimp.net to communicate more directly

Original comment by lav...@gmail.com on 29 Jul 2009 at 8:40

GoogleCodeExporter commented 9 years ago
The status of the project is now more known and there are growing activity both 
in
contributions and on the irc channel.

Original comment by lav...@gmail.com on 20 Sep 2009 at 9:25