5a7ab54ee6
Also make it accessible by providing a mode argument to the install
function. Previously developers could just edit the url but we no longer
have the address bar as an app window, so now they must close the
default installer and run the following from the background page
console: `extension.install('standalone')`.
In the production build, this should result in an error since it is not
supported / the register page is not included there.
142 lines
6.3 KiB
Markdown
142 lines
6.3 KiB
Markdown
Contributor Guidelines
|
|
======================
|
|
|
|
## Installation
|
|
|
|
* Clone the repo
|
|
* Open Chrome
|
|
* Go to chrome://extensions/
|
|
* Enable developer mode (checkbox on the top right)
|
|
* Click "Load unpacked extension..."
|
|
* Point to the repo directory
|
|
|
|
## Developer Setup
|
|
|
|
Note that for development, you should always be using the staging server
|
|
Registrations on the staging server are completely partitioned from the
|
|
productions server that the mobile apps use. A production app from the Play
|
|
store or iTunes is hard-coded to connect to the production server. If you wish
|
|
to pair your phone and computer, or test sending between the browser and
|
|
mobile, you must build a mobile client that targets the staging server.
|
|
|
|
**Important!** The staging server uses a [self-signed ssl
|
|
certificate](https://github.com/WhisperSystems/TextSecure-Browser/issues/110).
|
|
By default, your browser will reject this certificate as insecure. Therefore,
|
|
in order to register or send and receive messages of any kind, you must first
|
|
visit <https://textsecure-service-staging.whispersystems.org/> in a new tab and
|
|
click through the warnings to allow the certificate. If at any time you notice
|
|
a console error about an "INSECURE RESPONSE" or "Handshake was canceled",
|
|
repeat this step.
|
|
|
|
## Pairing
|
|
|
|
Currently only the Android client supports multi-device pairing.
|
|
|
|
0. Upon installing the extension you will be presented with a qr code.
|
|
1. Build a staging-flavored Android client and install it on your phone.
|
|
2. Scan the qr code with an barcode/qr scanning app and open the resulting url ("tsdevice://...").
|
|
3. The phone will ask you to confirm adding the device. Click ok.
|
|
3. The browser will then ask you to confirm your phone number. Click ok and wait for setup to complete. Key generation can take up to a minute.
|
|
|
|
## Standalone Registration
|
|
**NOTE:** This is only for developers and will not be presented to users.
|
|
|
|
* Open the background page and run the following command in the console: `extension.install("standalone")`.
|
|
* Enter a real phone number (Google Voice numbers work too) and country
|
|
combination and choose to send an SMS. You will receive a real SMS.
|
|
* Enter the verification code you received by SMS.
|
|
* Wait for key generation to complete.
|
|
|
|
You should now be able to use the extension. If you need to re-register, open a
|
|
browser console within the extension options page (or inspect
|
|
`background.html`) and execute `localStorage.clear()` to delete your account
|
|
information.
|
|
|
|
## Chrome profiles
|
|
|
|
Don't have any friends to help you test the extension? Make a couple of Chrome
|
|
profiles. Each one will need its own Google account and Google Voice number.
|
|
Each one will have to repeat the setup process documented above, including
|
|
re-accepting the staging server cert under each profile. This is a tedious
|
|
process, but once you are done you will be able to send messages back and forth
|
|
between different profiles, allowing you to observe both endpoints of a
|
|
conversation.
|
|
|
|
## Pull requests
|
|
|
|
So you wanna make a pull request? Please observe the following guidelines.
|
|
|
|
* Rebase your changes on the latest master branch, resolving any conflicts
|
|
that may arise. This ensures that your changes will merge cleanly when you
|
|
open your PR.
|
|
* Run the tests locally by opening the test page in your browser. A
|
|
test-breaking change will not be merged.
|
|
* Make sure the diff between our master and your branch contains only the
|
|
minimal set of changes needed to implement your feature or bugfix. This will
|
|
make it easier for the person reviewing your code to approve the changes.
|
|
Please do not submit a PR with commented out code or unfinished features.
|
|
* Don't have too many commits. If your branch contains spurious commits along
|
|
the lines of "Oops, reverted this change" or "Just experiementing, will
|
|
delete this later", please squash or rebase those changes out.
|
|
* Don't have too few commits. If you have a complicated or long lived feature
|
|
branch, it may make sense to break the changes up into logical atomic chunks
|
|
to aid in the review process.
|
|
* Provide a well written and nicely formatted commit message. See [this
|
|
link](http://chris.beams.io/posts/git-commit/)
|
|
for some tips on formatting. As far as content, try to include in your
|
|
summary
|
|
1. What you changed
|
|
2. Why this change was made (including git issue # if appropriate)
|
|
3. Any relevant technical details or motivations for your implementation
|
|
choices that may be helpful to someone reviewing or auditing the commit
|
|
history in the future. When in doubt, err on the side of a longer
|
|
commit message.
|
|
|
|
## Dependencies
|
|
|
|
**Note**: Unless you need to make changes to dependencies, you can skip this
|
|
section and just use the checked in versions.
|
|
|
|
Dependencies are managed by [bower](http://bower.io) and built with
|
|
[grunt](http://gruntjs.com). To change them, you'll need to install node and
|
|
npm, then run `npm install` to install bower, grunt, and related plugins.
|
|
|
|
### Adding a bower component
|
|
|
|
Add the package name and version to bower.json under 'dependencies' or `bower
|
|
install package-name --save`
|
|
|
|
Next update the "preen" config in bower.json with the list of files we will
|
|
actually use from the new package, e.g.:
|
|
```
|
|
"preen": {
|
|
"package-name": [
|
|
"path/to/main.js",
|
|
"directory/**/*.js"
|
|
],
|
|
...
|
|
}
|
|
```
|
|
If you'd like to add the new dependency to js/components.js to be included on
|
|
all html pages, simply append the package name to the concat.app list in
|
|
`bower.json`. Take care to insert it in the order you would like it
|
|
concatenated.
|
|
|
|
Now, run `grunt` to delete unused package files and build `js/components.js`.
|
|
|
|
Finally, stage and commit changes to bower.json, `js/components.js`,
|
|
and `components/`. The latter should be limited to files we actually use.
|
|
|
|
## Tests
|
|
Please write tests! Our testing framework is
|
|
[mocha](http://mochajs.org/) and our assertion library is
|
|
[chai](http://chaijs.com/api/assert/).
|
|
|
|
To run tests, open `test/index.html` in your browser. Note that
|
|
|
|
* Some tests depend on the native client module. These will fail unless you
|
|
load the test page from the `chrome-extension://` namespace (as opposed to
|
|
the `file://` namespace or via a local webserver.
|
|
* Some tests may read, write or clear localStorage. It is recommended that you
|
|
create a Chrome user profile just for running tests to avoid clobbering any
|
|
existing account and message data.
|