Actions

Contributing to Mahara: Difference between revisions

From Mahara Wiki

(remove importer noise)
(→‎Submit bug reports and feature requests: remove duplicate link to bug tracker)
Line 3: Line 3:
==Submit bug reports and feature requests==
==Submit bug reports and feature requests==


This is an easy one :). If you find a bug in Mahara, and you're sure that it's not a result of any customisations you have made to your Mahara, then [http://mahara.org/tracker/ make a bug report for it on the tracker]. And if you think there's a feature you'd like to see in Mahara, [http://mahara.org/tracker/ submit a feature request] so that we can examine, and hopefully implement, your idea!
This is an easy one :). If you find a bug in Mahara, and you're sure that it's not a result of any customisations you have made to your Mahara, then [http://mahara.org/tracker/ make a bug report for it on the tracker]. And if you think there's a feature you'd like to see in Mahara, submit a feature request on the same tracker so that we can examine, and hopefully implement, your idea!


==Improve the documentation on this wiki==
==Improve the documentation on this wiki==

Revision as of 12:37, 29 March 2012

If you wish to contribute to Mahara, go for it! There are many ways you can help contribute:

Submit bug reports and feature requests

This is an easy one :). If you find a bug in Mahara, and you're sure that it's not a result of any customisations you have made to your Mahara, then make a bug report for it on the tracker. And if you think there's a feature you'd like to see in Mahara, submit a feature request on the same tracker so that we can examine, and hopefully implement, your idea!

Improve the documentation on this wiki

If you find a spelling mistake, a factual error, know something about Mahara that wiki doesn't, or understand another language, there's lots you can do simply by browsing around the wiki and correcting/adding what you can. Especially if you know another language, consider starting a page for it like the existing languages have (see the Spanish and Japanese pages for example). The most important page you can translate - other than this one of course - is the installation instructions.

Become a helpful member of the forums

How easy is this! All you have to do is subscribe to any forums you like, and answer people's questions and enquiries. There are forums for pedagogy and an open discussion forum, as well as technical forums, so it doesn't matter what kind of background you have. There are even entire groups for specialist subjects like Moodle/Mahara integration.

Become a Mahara Partner

The term "Mahara" and related terms are protected by trademark internationally. See our Trademark Policy for a list of permitted uses.

You don't have to become a partner to sell services based on Mahara - but if you'd like to be listed on the Partners page and support the project financially, please consider joining the programme.

In addition to the right to use the Mahara trademark commercially (see the partner programme for details), partners receive several benefits such as being featured on mahara.org and gaining access to partner-only support. If your organisation is interested in becoming a partner, please fill out the registration form.

Translate Mahara into another language

Speaking a language other than English and having a small understanding of Mahara is all you need to be able to translate Mahara into another language. It might pay to ask in the translations forum to check if someone is already translating your language - you may be able to help with the existing effort.

We're in the process of writing documentation to help new translators out, but for now you might want to check out the translations forum and read this wiki page.

Write a new plugin

People with a good understanding of PHP and an idea should be able to write plugins for Mahara. There is not much developer documentation at this time, but we're working on this. You can look around the Mahara source tree and try to gather a picture of how things work, and join #mahara on freenode to have realtime chat with the developers.

If you want a plugin but are unable to develop it yourself, consider getting in touch with the developers or a Mahara Partner in your area, who should be able to help you. And if you are able to develop a plugin, you should definitely get in contact with the core developers - we will be able to suggest how your work could be architectured, and developed in such a way that it has the best chance of getting into the Mahara core distribution.

The developers can be contacted through the forums or the #mahara IRC channel on freenode.

Fix bugs in Mahara itself

If you have skills with any of the technologies underlying Mahara - the main ones being PHP, PostgreSQL/MySQL, Apache and Linux - you are well placed to help out by finding and fixing bugs. Submitting bug reports with patches attached is a great way to earn yourself a beer next time one of us core developers is in your area :). Not to mention the associated fame of being listed as a contributor on Ohloh!

If you have itchy coding fingers and want a bug to fix, check out the tracker - there's a big list of them there just waiting for you! Details on how to get the latest code from git / gitorious are on the Download Mahara page.

Make a Case Study View on mahara.org

If you've been using Mahara, we'd love to hear about how things are working out for you. A good way to do that is to make a View on mahara.org as a Case Study of your usage of Mahara. There's a template View already created that you can use to get started, and it doesn't have to be too detailed or take you much time. Read the forum post for more information.