Adds salmon links to xrd.

These endpoints are completed in the routes, but without them in the
xrd, no ostatus client would know how to reach an rstat.us node user.
That would make me sad. All three links are required, but normally they
all point to the same route. This is true for us and status.net, so
don't be alarmed by it. I'm not sure why anybody would want to
distinguish them by route since the envelope exposes this, and this
distinction does not make it a separate resource at all. :(
Documenting our Brand New Commit Bit Policy!
Wrapping the README at 80 chars
Clarifying policy in regards to branches other than master
Removing commented out lines in xrd.haml.

Let's use source control!
Adds tests to ensure that the salmon urls exist in the user xrd.

I added a section to the webfinger tests which test that the xrd served
by a webfinger request contain the three salmon urls necessary to get
salmon notifications. Again, the three are not necessary, but it is nice
to provide all three even if they are the same url.

I will add more tests for the remaining things in the xrd to this set of
acceptance tests.
Merge pull request #601 from wilkie/bugfix/salmon-links-in-xrds

Bugfix/salmon links in xrds
Merge pull request #604 from chrismdp/master

Fix for #592 - using fully qualified domain name
Adding chrismdp to the about page!! :heart: :heart:
Merge pull request #595 from carols10cents/commit_policy

Adopting rubinius' commit bit policy
Merge pull request #606 from carols10cents/add_contributors

Adding chrismdp to the about page!! :heart: :heart:
Adds test for host-meta webfinger uri.

This uri is used by webfinger clients to determine how to find the xrd
for a particular user. We need to ensure it is an absolute uri and that
it points to the correct user route.
Adds webfinger xrd test for account name.

This test ensures that the subject matches the user when the user's xrd
is retrieved.
Adds alias checks on webfinger user xrds.

The alias field denotes how a user is identified. A user of rstat.us is
identified by both the profile url and the feed url. Both checks are
made.
Adds check for profile url in webfinger user xrd.

Another node or ostatus client will want a link to the profile of the
user on our system. This is given within a profile-page webfinger field.
This test checks to see if that matches the user's profile page on the
site.

This can also be used for discovery, but that should be tested
separately from webfinger.
Adds subscription url test to webfinger user xrd.

This url is the url used to subscribe to a feed and therefore the one
tied to a pubsubhubbub url for our users. This ensures that it is
present in the xrd for xrd-based discovery of the feed.
Adds the entry url for incoming subscriptions to the webfinger user xrd.

This url is used to actually establish a subscription and verify
authorship and authenticity. This is generally the same for all users
where the template is filled with the user uri necessary to identify
them (given in the http://schemas.google.com/g/2010#updates-from field).
Fixes the subscribe url such that it is correctly listed as a template
and not an href.

Although redfinger doesn't read this attribute, it is nonetheless
important to fit the specification. The subscribe rel needs a template
attribute. I, of course, have no idea if this works on a remote just
yet. :)
Merge pull request #607 from wilkie/bugfix/webfinger-tests

Bugfix/webfinger tests and xrd fixes