# HG changeset patch # User Jie Kang # Date 1479393045 18000 # Node ID 336d4a36b6d51954b697c61beae324e88fc34df7 # Parent 8de0821725f4903b480ca7522fe0b965ecec4e1c Fix panel divs in contribute page to be inline with other pages. diff -r 8de0821725f4 -r 336d4a36b6d5 content/contribute/content.html --- a/content/contribute/content.html Mon Oct 31 16:23:48 2016 -0400 +++ b/content/contribute/content.html Thu Nov 17 09:30:45 2016 -0500 @@ -4,96 +4,100 @@

Contributing to Thermostat

-

- Contributions to Thermostat are always appreciated. If you have any questions, please find us on IRC or join the mailing - list and send us an e-mail so that we can help you get started. -

-
- Mailing List - Thermostat IRC -
-

- Tasks in Thermostat are usually tracked in Trello, or through the IcedTea bugzilla. Feel free to take a look for things to - work on. -

-
- Trello Board - IcedTea Bugzilla -
-

Step 1: Build Thermostat

-

- The first step is to get Thermostat source code on your machine and to get the required dependencies to build Thermostat. - For Fedora you can run the following in a terminal: -

-

+

+
+

+ Contributions to Thermostat are always appreciated. If you have any questions, please find us on IRC or join the mailing + list and send us an e-mail so that we can help you get started. +

+
+ Mailing List + Thermostat IRC +
+

+ Tasks in Thermostat are usually tracked in Trello, or through the IcedTea bugzilla. Feel free to take a look for things to + work on. +

+
+ Trello Board + IcedTea Bugzilla +
+

Step 1: Build Thermostat

+

+ The first step is to get Thermostat source code on your machine and to get the required dependencies to build Thermostat. + For Fedora you can run the following in a terminal: +

+

$ sudo dnf install mercurial maven mongodb mongodb-server java-1.8.0-openjdk libsecret-devel make gcc gtk2-devel autoconf automake libtool

-

+

$ hg clone http://icedtea.classpath.org/hg/thermostat

-

- This installs the development dependendcies and downloads the Thermostat main repository into the folder thermostat. -

-

- Thermostat uses the Maven build system. To build, run: -

-

+

+ This installs the development dependendcies and downloads the Thermostat main repository into the folder thermostat. +

+

+ Thermostat uses the Maven build system. To build, run: +

+

$ mvn clean integration-test

-

Step 2: Find something to work on

-

- Any pet peeves you have with using Thermostat would be perfect to work on. Tasks or bugs can be found on the Trello board - and in the IcedTea Bugzilla. You can also ask on the mailing list or in the IRC channel and people will have lots - of ideas to share. If you come up with something, it's best to talk about it with the community through an e-mail - or through IRC. -

-

Step 3: Complete the task

-

- Working on the task is up to you. If you need any assistance, just ask for help. For style, please see the HACKING and README - files in the repository. Your best bet is to look at what other people have done and follow their style. There are - also a lot of resources in the Thermostat wiki targeting developers. Javadocs are also hosted online. -

-
- Wiki - Javadocs for 1.6 +

Step 2: Find something to work on

+

+ Any pet peeves you have with using Thermostat would be perfect to work on. Tasks or bugs can be found on the Trello board + and in the IcedTea Bugzilla. You can also ask on the mailing list or in the IRC channel and people will have + lots of ideas to share. If you come up with something, it's best to talk about it with the community through + an e-mail or through IRC. +

+

Step 3: Complete the task

+

+ Working on the task is up to you. If you need any assistance, just ask for help. For style, please see the HACKING and README + files in the repository. Your best bet is to look at what other people have done and follow their style. There + are also a lot of resources in the Thermostat wiki targeting developers. Javadocs are also hosted online. +

+
+ Wiki + Javadocs for 1.6 +
+

Step 4: Get your work reviewed

+

+ Once you have something that works, it's time to send it for review. This is done by sending an e-mail to the mailing list + with a title following the format: "[PATCH] Commit-Message", a body explaining the patch, and the patch attached + as a '.patch'' file. For example if you wish to send a patch with commit message "Fix issue with blob in blah", + then the title would be: "[PATCH] Fix issue with blob in blah". The body of the e-mail should contain a description + of the patch including what it does and why it does so. +

+
+

+ To generate a patch file from uncommitted changes, use: +

+ $ hg diff > file-name.patch. +
+
+

+ To generate a patch from your latest commit use: +

+ $ hg export > file-name.patch +
+

+ From here, the review process starts. Committers will look over the patch and reply to your e-mail with changes. It becomes + an iterative process where you respond to the changes with a revised patch and the reviewer looks it over again, + repeating till the reviewer is satisfied with the patch. +

+

Step 5: Get your work into the tree

+

+ If you do not have commit rights, when the patch is satisfactory, the reviewer will ask for a patch file with the commit + message included. This will be committed into the tree and pushed in your stead. For committers, they can push + the changes into the tree themselves. TODO How to get commit rights +

+

Step 6: Repeat

+

+ Congratulations and thank you for your contribution! From here feel free to repeat with new work. Once you have a number + of nontrivial fixes, you may recieve nomination as an IcedTea hacker from which point you can push work yourself + after it has been reviewed. +

+
-

Step 4: Get your work reviewed

-

- Once you have something that works, it's time to send it for review. This is done by sending an e-mail to the mailing list - with a title following the format: "[PATCH] Commit-Message", a body explaining the patch, and the patch attached - as a '.patch'' file. For example if you wish to send a patch with commit message "Fix issue with blob in blah", then - the title would be: "[PATCH] Fix issue with blob in blah". The body of the e-mail should contain a description of - the patch including what it does and why it does so. -

-
-

- To generate a patch file from uncommitted changes, use: -

- $ hg diff > file-name.patch. -
-
-

- To generate a patch from your latest commit use: -

- $ hg export > file-name.patch -
-

- From here, the review process starts. Committers will look over the patch and reply to your e-mail with changes. It becomes - an iterative process where you respond to the changes with a revised patch and the reviewer looks it over again, - repeating till the reviewer is satisfied with the patch. -

-

Step 5: Get your work into the tree

-

- If you do not have commit rights, when the patch is satisfactory, the reviewer will ask for a patch file with the commit - message included. This will be committed into the tree and pushed in your stead. For committers, they can push the - changes into the tree themselves. -

-

Step 6: Repeat

-

- Congratulations and thank you for your contribution! From here feel free to repeat with new work. Once you have a number - of nontrivial fixes, you may recieve nomination as an IcedTea hacker from which point you can push work yourself - after it has been reviewed. -

\ No newline at end of file