Contribute to Magnolia
Help Wanted!
If you have some time on your hands and like what you see, why not participate and make Magnolia even better? There are many ways you can support us: spread the word, write code, or simply share time, knowledge or funds with us. We need you!
Answer questions on the mailing lists
Even if you just got started with Magnolia, you might know more than the guy asking a question. You are very welcome to share your knowledge on our users mailing list.Write documentation
If you like to write documentation and have some time on your hands, there are many issues that need documenting. If you have learned something, write it down and share it. No need to get fancy with graphics and stuff. A small how-to in plain text is a good start. If you had to write documentation for your users, your IT department or your grandma, why not share it with the rest of the Magnolia community. They might have grandmas, too.Translate the Magnolia User Interface
Magnolia comes with an internationalized UI. This allows Magnolia to have its user interface in any language you like. Even if you do not have the ambitions to completely translate Magnolia, you might have time to add a couple of translations or correct erroneous ones in your own language.Report bugs
If you use Magnolia and find a bug, report it. Make sure it's a bug (and not simply a configuration issue), check the bug tracker if it has been reported before, and add it to the bug tracker if no one else has done so.If you don't know if something is a bug or a configuration problem, check the mailing list archives for similar problems. If in doubt, post it on the list, and if the general agreement is that its a bug, go add it to the bug tracker.
Writing bug reports is a fantastic way to contribute to a project, and we are very thankful for each well written bug report. The better your report is researched and written, the faster the bug will be fixed. Need we say more?
Of course you are also welcome to download the latest code from Subversion and test it.
Spread the word!
If you like Magnolia, one way to help us is to promote us - spread the word about Magnolia. Here are a couple of ideas.Report Magnolia sites and success stories
If you have built a website with Magnolia, let us know about it - we will add you to the growing list of references.Write about Magnolia
If you have the possibility to write an article about Magnolia, do so. Publish it on your blog, your website or in a newspaper. Let us know about it, we might put a back link to it.Talk about Magnolia
You are a conference speaker? Great! Talk about Magnolia - even if you only mention it, you will help Magnolia to gain more popularity. Of course, you are also welcome to speak about Magnolia on the Radio or the TV evening news. If all else fails, talk to your dog. It is unlikely to significantly promote Magnolia, but maybe it helps your dog.Link to Magnolia
You have created a website with Magnolia or simply like what we do? Link to us! You can download the "Made with Magnolia" logo or simply put a link on your web page. Of course we are also happy if you let us know about your Magnolia site, so that we can link to you.Other ideas? Let us know! Are you the creative type? Share your wicked ideas of promoting Magnolia with us!
Write Code!
Code contributions in its various forms are very welcome - check our list of ideas!For all code contributions, we require that you sign the Contribution License. It's easy, safe and you get to use a machine that was invented more than 160 years ago - the fax machine, patented in 1843. (of course you can also use the even older postal service, first established in China 900 BC).
Create patches
If you found a bug, you are welcome to fix it. Once you have made sure that it actually fixes the problem, attach it to the appropriate issue on Jira, where one of the committers will take care of it.To create a patch file from your modified version of the trunk, simply issue the following command from the root of the project:
svn diff > myfix.patch
myfix would actually be a self-descriptive name of what you're patching, or the id of the Jira issue this is about.