Contributing to MV3D
MV3D is a very ambitious project, and it needs your help! First thing you'll want to do is to register for an account on the forums and wiki. You should then probably email mike at mv3d dot com to get your accounts activated (darn spammers). MV3D is developed with Scrum. Development is broken up into sprints (milestones in trac), and each sprint, tickets to be worked on are pulled from the backlog. All work to be done (bugs and features) have associated tickets. Basically, MV3D follows UQDS. In short, a ticket is created, it's assigned to a milestone. A branch is created for all work done in that ticket and someone starts working on it. When ready, they submit the ticket for review and the reviewer checks over the changes and either approves it or hands it back with suggestions. If you don't have svn write access, then the process is similar, but just attach a patch to the ticket when submitting for review. MV3D uses Divmod's coding standard for all code.
If you're looking for something to do, here's a list of tickets no one is working on:
- #179
- Some way to get trimesh colliders for arbitary 3d models
- #320
- Web asset group editor wizard for zipped bunches of assets
- #419
- Clean up IGE user interface
- #420
- Investigate making ui layout code more generic
- #25
- Use SSL for connections
- #62
- Server side event propagation
- #69
- Internationalize text messages
- #80
- Create advanced Sky features
- #81
- Add Day-Night cycle ability to realms
- #124
- Download assets for things that are outside the view range
- #138
- In game bug reporting
- #141
- Add server list to clients. And add ability to download more servers.
- #168
- Add Weather to Realms
- #170
- Create Patch System
- #292
- Incoming chat messages should make a sound.
- #294
- Untrusted authorization for web services.
- #330
- Add ability to create a login within the client
- #383
- Docstrings and tests for mv3d.client.view.area
- #384
- Docstrings and tests for mv3d.client.view.object
- #385
- Docstrings and tests for mv3d.client.view.player
- #386
- Docstrings and tests for mv3d.client.view.realm
- #387
- Remove mv3d.client.view.TerrainView
- #388
- More tests for mv3d.client.view.visual
- #389
- Need tests for mv3d.client.asset
- #390
- Need more tests for mv3d.client.player
- #391
- Split up mv3d.test.test_net
- #392
- More tests for mv3d.test.test_securable
- #393
- More tests for mv3d.phys.biped
- #394
- More tests for mv3d.phys.body
- #395
- More tests for mv3d.phys.collider
- #396
- More tests for mv3d.phys.mesh
- #397
- More tests for mv3d.red
- #398
- More tests for mv3d.reporter.event
- #399
- More tests for mv3d.reporter.guilog
- #400
- More tests for mv3d.resource.ogre3d
- #401
- More tests and docstrings for mv3d.resource.url
- #402
- Remove ige.Properties and other old ige stuff that isn't used
- #403
- More tests and docstrings for mv3d.server.model.area
- #404
- Remove old code from mv3d.server.model.object and add tests if needed
- #405
- More tests for mv3d.server.model.physical
- #406
- More tests for mv3d.server.model.realm
- #407
- More docstrings for mv3d.server.model.view
- #408
- More tests for mv3d.server.account
- #409
- More tests for mv3d.server.login
- #410
- More tests for mv3d.server.player
- #411
- More tests for mv3d.server.realm
- #412
- More tests for mv3d.server.sim
- #413
- More tests for mv3d.util.classgen
- #414
- More tests for mv3d.util.conductor
- #415
- More tests and docstrings for mv3d.util.container
- #416
- Evaluate removing mv3d.util.date
- #417
- New docstrings for mv3d.util.math3d
- #418
- More tests for mv3d.util.noise and quick look for performance boost
Ticket Conventions
In addition to the standard trac workflow, we also use keywords to denote a secondary status for tickets. Use the 'review' keyword to specify that a ticket is ready for review. The 'stealable' keyword should be used on tickets that are up for grabs for anyone to take on.
