On Tue, May 31, 2011 at 12:22 AM, Jordan Justen <jljus...
> Hi. I have some advice for this project as a potential new
> contributor trying to discover how to become involved with this
> 1. Document major status of project on monoxna.org
> I think the homepage should make it clear the general status of
> monoxna. Ie, pre-alpha, and it can't run most XNA applications at
> this point. This will weed out potential users from potential
I agree. That is why we started this page http://code.google.com/p/monoxna/wiki/Status
a while back. It could
use some work though.
> 2. Support & IRC
> I don't think IRC should be listed as the main point of support, since
> it does not have much activity. I think a mailing list is more
> appropriate at this stage.
I've opened up the mailing list so that everyone can join again.
> Are the forums really worthwhile at this stage? There is such low
> traffic with the project right now, it might be best to funnel it all
> to one place. (Ie, the mailing list.)
The home page at this point is no where near the stage that I would
like it to be, so I have been thinking of removing the link from the
google code page for a while. I really like the idea of having a
dedicated homepage in principle, but that would require the manpower
to manage the site.
> 3. Document how to submit changes
This should obviously be part of this page http://code.google.com/p/monoxna/wiki/Helping
. I'll try to add it
before bed tonight.
> 4. Move to github for code hosting
> This will enable potential developers to easily fork and send
> pull/merge requests.
> There is a natural home for this project under the mono organization at
The monoxna project has moved in the past as well, so I would prefer
it if we could stay on google code for now. I'll look into the whole
github thing myself to see if I think the benefits are to great to
> 5. Document the relationship to MonoGame
> I don't quite understand this ... Why should I contribute to monoxna
> vs. MonoGame?
Actually the MonoGame was news to me, but it looks like it's a rename
of the XnaTouch project? If that's the case, they've taken a slightly
different approach than the idea behind MonoXNA. Like Mono we aspire
to be binary compatible with the .NET equivalent (XNA). I don't think
that's the case with MonoGame though. They just provide the same API.
If I'm not mistaken they based the first version heavily on our
codebase, with the underlying API's changed. They certainly have a
bigger community than MonoXNA, so the best argument I can make for
joining MonoXNA instead is the underlying philosophy of providing a
cross platform alternative, that in addition to being binary
compatible, provides an equivalent development environment.
> Thanks for your time,
> You received this message because you are subscribed to the Google Groups "MonoXNA" group.
> To post to this group, send email to email@example.com.
> To unsubscribe from this group, send email to firstname.lastname@example.org.
> For more options, visit this group at http://groups.google.com/group/monoxna?hl=en.