Hi everyone, >From time to time people ask me how they can get started helping DataMapper. Some people want to dive in, and start forking everything and sending pull requests. Others aren't sure how much time they'll have, but still want to help make a difference. I decided to put together a quick list of things for the latter group, as well as a few tips for the former. Feel free to reply to this email if you have further suggestions, or want some clarification on any points mentioned.
Some of these tasks help either to push DataMapper directly forward through code/spec/doc contributions, or indirectly forward because you're helping with something that allows other contributors to spend more time on code, specs and docs. I've listed the tasks from least to most time consuming, which is also the priority -- the earlier in the list, the more you help me out. Specifically it frees up my time to work on the dkubb/dm-core spec rewrite project, which the faster I can get it done benefits us all as a number of bug fixes have been made and overall it's far more stable. Without further ado, here are some things that come to mind: * Sync up dkubb/dm-core, sam/dm-more, sam/extlib, sam/do from github, and use "rake spec" to run their specs locally. All specs *should* pass. NOTE: when testing sam/dm-more, please use the latest dm-core gem because I am currently refactoring parts of dkubb/dm-core and that it may not be fully compatible with dm-more at the moment -- I plan to fix this shortly, once I've cleaned everything up. * Use "rake install" to install those gems and run your own app's specs and tests to make sure the functionality has not changed. (note you may get deprecation warnings, but that may be normal, what we're looking for is errors) * Report any issues to http://datamaper.lighthouseapp.com/ (search first to make sure you don't submit a dupe ticket) Note that at this time, dkubb/dm-core may be incompatible with sam/dm- more while we rearrange things a bit. You'll likely see alot of failures in the dm-more specs for the near future. Before reporting a dm-more issue try installing sam/dm-core (or the dm-core gem) and re- run the specs. * Review the unconfirmed tickets and provide stand-alone scripts that confirm or show the problem is fixed. For non-critical tickets, if it's fixed in dkubb/dm-core, we mark it as resolved. If it does not pass we check it against sam/dm-core. * Ask me (dkubb) for an invite to Lighthouse so that you can mark tickets as confirmed, not-applicable, or resolved. * Mark tickets as accepted if you are going to work on them, so that others don't attempt to duplicate your work on the ticket. * Provide patches for confirmed tickets. If the ticket is for dm-core, but is not critical, please supply the patch against dkubb/dm-core. sam/dm-core is in maintenance mode and only critical fixes are being applied against it. * Test out other patches for confirmed tickets locally, and add comments to confirm that it works with edge. * View the classes at the bottom of http://github.com/dkubb/dm-core/wikis/home and "adopt" one to work on. See that page for more information on what we're doing. Review the specs and docs that are already written, specifically those for Collection, to see the style we're using. * If you have experience writing Java, ping myabc to ask if you can help with the do_jdbc drivers. JRuby is going to become a first-class citizen in the DM world, and will be one of the primary Ruby's we test against. * Update the dm-more plugins so that the specs can be more easily executed against the In Memory Adapter. Possibly backport the InMemory adapter from dubbb/dm-core to sam/dm-core. This will allow early JRuby testing to happen against the dm-more plugins prior to do_jdbc from being ready. * Speak with dbussink on IRC and ask him about updating the DO specs to match the conventions we are using in dkubb/dm-core. -- Thanks, Dan (dkubb) P.S. I will follow up in the next few days on the status of the rewrite, and outline what I think the DM 1.0 Roadmap should look like. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
