* Contribute to this wiki! That is probably the most direct and quick way to contribute. Your experience helps others install and run their HDA!
* Share your experience in the area or running a server and answer questions in the [http://forums.amahi.org community forums] or in the [https://lists.sourceforge.net/lists/listinfo/amahi-users users mailing list]. If you are an experienced user, others will appreciate your efforts and this will make the project more usable and successful in the long run
* Talk about Amahi! Let people know what Amahi is about, help them install their HDA
* Promote Amahi, such as doing a presentation to your local LUG (Linux User Group), share your presentation with others!
* Blog or tweet about your experience with Amahi
* Make recommendations
* Do reviews or HOWTOs
* Help us create a polished "press kit" of sorts that we can give when managines magazines and website editors ask us about Amahi
* [[How to Create a new Theme|Create a theme or two]]
* Help us write a "manual" so that it's printable (in pdf and also [http://lulu.com, in paper])
* Submit to other sites that may like it! :-)
Aside from the above, there are two major ways to contribute in a more active role.
= Becoming an Application Types of Contributor =
* This is very easy. Whether you are an expert or you only know the basics We have three types of some application installation and configurationcontributor, this is a great way from less involved to contribute* Read the [[Application Contributor]] Guidemore involved:
= What if I want to contribute but don* 't have ''Editor:''' editing the time to package an app? =apps "visual" part for English readability, HTML validation, logo/screenshot "shininess" and generally making beta apps look good* '''Tester''': testing, rating and sending feedback on beta apps* '''Packager''': packaging apps. no programming required
Well heres a solution, you You can find some apps for our developement team become any (or all) of these three roles by making yourself known to package the community in the forums or in the IRC channel and we can do that for you. All you have asking to do is supply become a link to the apps homepage and we will jump right on it. [[New_App_Ideas|Click Here]] to add you app ideas to the list. Any and all apps are ok.contributor!
= Contributing Code Becoming an Application Packager/Contributor =
* Join This is very easy. Whether you are an expert or you only know the [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list]basics of some application installation and configuration, this is a great way to contribute* Grab a copy of Read the git repo[[Application Contributor]] Guide
git clone git://git.amahi.org/amahi.git= Other Ways to Contribute =
* Get yourself familiar with What if I want to contribute but don't have the pieces, and ask questions!* Make some changes time to the code, then test them:* e.g. for testing the platform:package an app?
cd platform/platform/html Well here's a solution: you can find some apps for our developement team to package and we can do that for you. All you have to do is supply a link to the apps homepage and we will jump right on it. [[New_App_Ideas|NEW app ideas]] to add you app ideas to the list. Any and all apps are ok./script/server
and access it at http://hda:3000 * You can see your changes with two git tools: status and diff git status * The status gives you a list of what files were modified, added or removed. you can see changes in your area with: git diff --cached * When you know you want to modify a file, you add it to the changes to be committed, for example, say a README file: git add README * For the parts that are added and checked in, you can see the changes with git diff * This is what will be committed! * Then actually commit your changes to your git repo: git commit * After that you can generate a patch to be sent upstream, e.g. for a patch of the latest commit.: git format-patch HEAD^..HEAD * This will generate a file called 0001-my-patch.mbox or similar (type ls -l 00*), which then you can email or pastebin it to someone to be committed upstream. You probably want to [[Configure Git]] to your liking first to display the email properly. * Please note, once the patch is applied upstream, your name and email WILL be officially in the [http://git.amahi.org amahi git repo] as as contributor, which mean it's in the open and it's crawlable, so please use your name/email accordingly.= Contributing Code =
* For more details, ask in the Follow this page to [http://forums.amahi.org forums[contribute code], [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list], or come by the [http://embed.mibbit.com/?server=irc.freenode.net&channel=%23amahi&noServerNotices=true&noServerMotd=true&autoConnect=true IRC channel]
