* 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

* Blog or tweet about your experience with Amahi

* Help us create a polished "press kit" of sorts that we can give when manazines magazines and website editors ask us about Amahi

* Help us write a "manual" so that it's printable (in pdf and also [http://lulu.com, in paper])

* '''Editor:''' editing the apps "visual" part for English readability, HTML validation, logo/screenshot "shinynessshininess" and generally making beta apps look good

= What if I want Other Ways to contribute but don't have the time to package an app? Contribute =

What if I want to contribute but don't have the time to package an app? Well heres 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|Click HereNEW app ideas]] to add you app ideas to the list. Any and all apps are ok.

* Join the [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list]* If it's your first time, grab a copy of the git repo  git clone git://git.amahi.org/amahi.git * If not, pull any changes from the master repo  cd amahi (the root of the git tree) git pull * Get yourself familiar with the pieces, and ask questions!* Make some changes to the code, then test them:* e.g. for testing the platform:  cd platform/platform/html ./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 Follow this page 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 PUBLIC name/email accordingly. * For more details, ask in the [http://forums.amahi.org forumscontribute 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]