Contribute code - Revision history

Bigfoot65 at 22:01, 7 April 2014

2014-04-07T22:01:16Z

Bigfoot65: /* Testing your code */

2014-04-07T21:34:22Z

Testing your code

Bigfoot65: /* Testing your code */

2014-04-07T21:34:05Z

Testing your code

Cpg at 02:49, 10 May 2013

2013-05-10T02:49:27Z

Cpg at 19:56, 7 July 2012

2012-07-07T19:56:51Z

Shayneb at 05:08, 8 April 2011

2011-04-08T05:08:05Z

Cpg: Created page with "This is a quick guide for contrinuting code, fixes or develop native apps on Amahi. * Join the [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel ..."

2011-02-10T06:30:24Z

Created page with "This is a quick guide for contrinuting code, fixes or develop native apps on Amahi. * Join the [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel ..."

New page

This is a quick guide for contrinuting code, fixes or develop native apps on Amahi.

* 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.:

1. Go into the patch folder located in the root of the git tree.
2. git format-patch HEAD^..HEAD

NOTE: When creating the patch title(first line) please put it in YYMMDD-PATCHSEQUENCE#-long-patch-name.patch format. In the long name please include what module you are working on. AKA what application etc..

* 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 PUBLIC name/email accordingly.

* For more details, ask in the [http://forums.amahi.org forums], [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list], or come by the [http://talk.amahi.org IRC channel]

@@ Line 3: / Line 3: @@
 * Join the [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list]
 * If you are new to git, you may find this [http://try.github.com/ interactive git tutorial] a nice intro to git
 * If it's your first time, grab a copy of our main git repo

← Older revision		Revision as of 21:34, 7 April 2014
Line 58:		Line 58:
	* 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.		* 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 forums], [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list], or come by the [http://talk.amahi.org IRC channel]	+	* For more details, ask in the [http://forums.amahi.org forums], [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list], or come by the [http://talk.amahi.org IRC channel].

← Older revision		Revision as of 19:56, 7 July 2012
Line 2:		Line 2:

	* Join the [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list]		* Join the [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list]
		+	* If you are new to git, you may find this [http://try.github.com/ interactive git tutorial] a nice intro to git
	* If it's your first time, grab a copy of the git repo		* If it's your first time, grab a copy of the git repo

@@ Line 54: / Line 54: @@
-* 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.
+* 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|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 forums], [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list], or come by the [http://talk.amahi.org IRC channel]

@@ Line 3: / Line 3: @@
 * Join the [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list]
 * If you are new to git, you may find this [http://try.github.com/ interactive git tutorial] a nice intro to git
-* If it's your first time, grab a copy of the git repo
+* If it's your first time, grab a copy of our main git repo
-       git clone git://git.amahi.org/amahi.git
+       git clone git@github.com:amahi/platform.git
 * If not, pull any changes from the master repo
-       cd amahi                (the root of the git tree)
+       cd platform                (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
+       rails s
       and access it at http://hda:3000

@@ Line 19: / Line 19: @@
       and access it at http://hda:3000
+     you will probably want to turn off
 * You can see your changes with two git tools: status and diff