Application Contributor

A burgeoning community is developing around Amahi. With the release of version 2.6 of the Amahi Home Server, a new class of community member has been created Application Contributor or Contributor for short.

A contributor is a trusted member of the community who does (or leads) the following for a specific application to be deployed on Amahi:

1. select an application you'd like to be the named contributor for
2. contact support at amahi.org, or find us in the irc channel, and request contributor status for the specified application
3. "Package" the application for deployment
4. test the package yourself
5. test the app with a select user base
6. release the application to the Amahi user community
7. upgrade/maintain the application

Here are some details on each step ..

Application Selection

Chances are you know what application you'd like to see running on Amahi! Contact us and we'll help you become the named contributor for that application.

If there is a particular application you'd like to see running on Amahi and you don't have the skills/time to be a contributor, let us know. We'll keep it on file.

Eventually http://www.amahi.org will have areas where community members can nominate applications for deployment on Amahi. This will make it easier for contributors to select applications.

Of course, the application you submit MUST be able to be legally distributed through the "one-click" mechanism. In most cases the application will be made available under an open source license that allows this.

Contact Amahi

Send an email to support at amahi.org, or find us in the IRC channel, indicating the application that you would like to become a contributor for, and some details on your level of experience. It may also be a good ideas to discuss in the developer forum or the amahi-devel mailing list.

The core Amahi team needs to get to know you a bit and review what you do. Applications are trust-based and we must ensure that applications do not do anything malicious (intentionally or not!). Chances are we'll give you access to the contributor area of amahi.org and you can proceed from there.

Package the Application

Packaging the application for deployment on Amahi involves

• Naming the application and describing it (short/long descriptions)
• Creating icons/screenshots for display
• pointing to source tarball, RPM, etc. as required
• setting up necessary installation/removal scripts
• Logo's should be 160x120 or 320x240
• Screenshots should be 320x240
• All logos and screenshots must be uploaded in the Amahi wiki and referenced from there in the app. Please do not link to any other site.

For a more detailed explanation refer to Application Packaging

Test Yourself/With Selected Users

Once you have packaged the application and you can "one-click" install it yourself you;re ready to release it to a "test community." This is a group of Amahi users who have volunteered to test new application installations.

Release the Application

The core Amahi team will review the application and then make it visible to the broad base of the Amahi user community. At this stage any member of the community can select the application for installation on their Amahi installation.

Maintain and Upgrade

Once the application is released you will be able to

• see the number of users who have tested the application
• review the number of "live" installations of your application
• monitor feedback from the Amahi community through a dedicated forum.

As the contributor for the application we hope that you will monitor the forum and understand any issues (bugs/features) that arise. If your application is successful we expect that many community members will help with this activity!

Tools

• Application packaging tools for windows

FAQ

• An app may have associated the following:
  • Database
  • Server
  • Web App
  • Share
• Does the DB get created before the install script
  • Yes!