Merge lp:~aacid/unity8/coding_update into lp:unity8

[Albert Astals Cid]

Point to the web

Let's not maintain two copies of the same thing that will get old and unsynced at different stages

 * Are there any related MPs required for this MP to build/function as expected?
No

 * Did you perform an exploratory manual test run of your code change and any related functionality?
N/A

 * Did you make sure that your branch does not contain spurious tags?
Yes

 * If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
N/A

 * If you changed the UI, has there been a design review?
N/A

[Daniel d'Andrada (dandrader)]

I prefer to keep those as close to the code as possible. They are more prone to getting outdated if kept separately.

I would rather do the other way around and build the web page from the this text file, like online documentation of libs.

review: Disapprove

[Michael Zanetti (mzanetti)]

I'm in favor of removing redundancy. Whether it is removing them here or generate the website out of it, I don't have a strong opinion. Generating the website out of it would be definitely more work tho.

[PS Jenkins bot (ps-jenkins)]

FAILED: Continuous integration, rev:2022
http://jenkins.qa.ubuntu.com/job/unity8-ci/6643/
Executed test runs:
    UNSTABLE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-vivid-touch/5014
    FAILURE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-xenial-touch/58/console
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-vivid/1355
    FAILURE: http://jenkins.qa.ubuntu.com/job/unity8-qmluitest-xenial-amd64/58/console
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity8-vivid-amd64-ci/1250
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity8-vivid-i386-ci/1251
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity8-xenial-amd64-ci/57
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity8-xenial-i386-ci/57
    UNSTABLE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/4025
    SUCCESS: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/5011
        deb: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/5011/artifact/work/output/*zip*/output.zip
    SUCCESS: http://s-jenkins.ubuntu-ci:8080/job/touch-flash-device/24903
    SUCCESS: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-xenial-armhf/58
        deb: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-xenial-armhf/58/artifact/work/output/*zip*/output.zip

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/unity8-ci/6643/rebuild

review: Needs Fixing (continuous-integration)

[PS Jenkins bot (ps-jenkins)]

FAILED: Continuous integration, rev:2022
http://jenkins.qa.ubuntu.com/job/unity8-ci/6646/
Executed test runs:
    FAILURE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-vivid-touch/5019/console
    FAILURE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-xenial-touch/61/console
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-vivid/1358
    FAILURE: http://jenkins.qa.ubuntu.com/job/unity8-qmluitest-xenial-amd64/61/console
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity8-vivid-amd64-ci/1253
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity8-vivid-i386-ci/1254
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity8-xenial-amd64-ci/60
    SUCCESS: http://jenkins.qa.ubuntu.com/job/unity8-xenial-i386-ci/60
    FAILURE: http://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/4030/console
    SUCCESS: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/5016
        deb: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/5016/artifact/work/output/*zip*/output.zip
    SUCCESS: http://s-jenkins.ubuntu-ci:8080/job/touch-flash-device/24912
    SUCCESS: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-xenial-armhf/61
        deb: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-xenial-armhf/61/artifact/work/output/*zip*/output.zip

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/unity8-ci/6646/rebuild

review: Needs Fixing (continuous-integration)

[Albert Astals Cid (aacid)]

Ok, it seems it didn't get enough consensus, someone else have to fix this duplication then.

Unmerged revisions

2022. By Albert Astals Cid on 2015-11-04

Point to the web

Let's not maintain two copies that will get old and unsynced at different stages

=== modified file 'CODING'
--- CODING	2015-06-23 07:51:27 +0000
+++ CODING	2015-11-04 14:42:14 +0000
@@ -1,131 +1,9 @@
 Building Unity 8
 ================
 
-Only Ubuntu 14.04 (trusty) is supported as a developement environment.
-
-download source
----------------
-- create a parent folder to not pollute your setup. so that you can have different unity
-  branches there (trunk, WIP etc)
-
-  $ mkdir ~/unity8
-
-- fetch Unity 8 source
-  $ sudo apt-get install bzr
-  $ bzr branch lp:unity8 ~/unity8/trunk
-  $ cd ~/unity8/trunk
-
-install dependencies
---------------------
-If its your first time, install build dependencies
-
-$ cd ~/unity8/trunk
-$ ./build.sh --setup
-
-  this will:
-  - install the required dependencies to build, as well as run on the desktop
-  - it should also install unity-scope-home and unity-lens-application which
-    are technically "recommends", not strict dependencies
-
-build Unity 8
--------------
-
-$ cd ~/unity8/trunk
-$ ./build.sh
-
-You may also rebuild with the -c for clean, which just deletes the build
-directory.
-
-
-Running Unity 8 on your desktop
-===============================
-
-run the Unity 8 shell
----------------------
-$ cd ~/unity8/trunk
-$ ./run.sh
-
-Options can be passed to test the lock screen
-$ ./run.sh -p OR -k
-
--p is for pin lock, for which the default prompt answer is "1234"
--k is for keylock passphrase, for which the default prompt answer is "password"
-
-Notes
------
-- to navigate, utilize the mouse left button as you would your finger
-- to get the translations work, currently you have to do make install to
-  put the *.mo files into correct structure. We'll look for a better solution
-  later.
-  $ cd builddir; make install
-- if you wish to populate contacts
-  $ sudo apt-get install gir1.2-ebook-1.2
-  $ manage-address-book.py create
-  this will:
-    - Create an EDS address book
-    - Populate the address book with sample data
-
-
-Running Unity 8 on devices
-==========================
-- Ubuntu Touch builds are currently only available in 14.04 flavour
-- supported hardware should match one of those listed here
-  https://wiki.ubuntu.com/Touch/Devices#Running_fine
-- follow the Ubuntu Touch install instructions for your chosen device
-  https://wiki.ubuntu.com/Touch/Install
-- make sure your device is connected to a network
-- also make sure you have your SSH key in ~/.ssh/id_rsa.pub (or install one
-  on the device yourself)
-
-$ cd ~/unity/trunk
-$ ./run_on_device.sh --setup
-  this will:
-  - install your public SSH key on the device
-  - install the needed dependencies
-
-$ ./run_on_device.sh
-  this will:
-  - rsync the code to the device
-  - build on the device
-  - replace the running shell
-
-Options can be passed to test the lock screen
-$ ./run_on_device.sh -p OR -k
-
--p is for pin lock, for which the default prompt answer is "1234"
--k is for keylock passphrase, for which the default prompt answer is "password"
-
-Notes
------
-- using adb over TCP has some advantages, Google will be of help here
-  - NOTE: this is not yet available for flipped images
-  - TL;DR: `adb tcpip 5555; adb connect $your_device_ip`
-  - you can persist the above via `adb shell setprop persist.adb.tcp.port 5555`
-  - it's unsafe - anyone can connect to your device
-  - with TCP the Nexus 10 doesn't drop the adb connection when locking
-    the screen
-- exporting ANDROID_SERIAL=$your_device_serial or
-  ANDROID_SERIAL=$your_device_ip:5555 will make adb not complain about
-  multiple devices
-- you can export TARGET_IP=$your_device_ip TARGET_SSH_PORT=22 for run_on_device.sh
-  to not use adb forwarding - useful if you use multiple devices
-- using Ninja (package ninja-build - run_on_device.sh -s installs this now)
-  will improve build times (especially in the nothing-to-build case)
-
-
-Coding guidelines
-=================
-The work-in-progress coding guidelines are available under:
-https://launchpad.net/canonical-client-development-guidelines
-
-
-Development Environment
-=======================
-QtCreator (available via the Software Center) is the best IDE to hack on
-Unity 8.
-
-If using VIM, make sure you install some syntax highlighting for QML, like
-https://github.com/peterhoeg/vim-qml
+Please see
+  https://unity.ubuntu.com/getinvolved/development/unity8/
+for Building and running instructions
 
 Running tests
 =============