Hi members,
I would like to start contributing to Moodle core development. I've setup moodle stable 2.5 copy from Git and have registered with Forum and Moodle account. Now please advice me how can I start contributing with bug fixing for Moodle release.
I've professional 8 years of experience in web development on LAMP stack.
Thanks,
Raheel
The best way to learn your way around is to start fixing bugs (or small new features) in existing code. Search in the tracker, find something that seems interesting/doable, make a patch, push it to github, ask for peer review.
More detail on http://docs.moodle.org/dev/Process.
Here are a list of issues that have been marked 'Easy' and are not assigned to anyone: https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20Difficulty%20%3D%20Easy%20AND%20assignee%20IS%20EMPTY
Thanks Tim for your guidance.
Let me go through your suggested links and if I will have any question regarding submit my patch from Git to community then I will again contact you
Thanks again
Raheel
Thanks Nano.
It's really a good start to dig the Moodle development.
Can you please guide me how can I make a ground for this feature on local. I mean what should I follow the steps like: create course, create student, student submit some stuffs and then teacher will accept activity etc...
I'm new to Moodle therefore I require some help regarding get started with it.
BTW, I understood the feature requirement like: there will be an option to manually complete the activity by teacher and that's it. But it will require to inject this check with existing automated process.
Thanks,
Raheel
The issue described doesn't yet have a triaged label, which makes it less well defined and not easily clear how a new developer should proceed. My quick reading of Sam H's comments suggest that it's going to need a capability created. As a relatively new developer myself, I wouldn't feel confident to tackle a task like that just yet.
A quick review of the Easy list Tim posted suggests something like https://tracker.moodle.org/browse/MDL-26872 might be easier to start with. It will allow you to do the code work easily as the fix is basically listed in the tracker item. As the fix is easy from a code point of view it will allow you to focus on understanding the development process. Which can have a few pitfalls as I'm currently discovering.
I would also suggest reading http://www.slideshare.net/poltawski/how-to-guarantee-your-change-is-integrated-to-moodle-core as a good guide to what to look out for in your journey to your first bugfix. http://docs.moodle.org/dev/Developer_documentation and the pages that link from it are also a good starting resource.
I hope that helps get you started.
Russell
All right Russell.
I think now you guys helped me to feed useful information and links to get started Now I will read them thoroughly.
Thanks again!
