Add CONTRIBUTING file

Add CONTRIBUTING file

This will help to direct those who stumble upon the new github mirror
to the proper channels for contributing code.

BUG=
R=jcgregorio@google.com

Committed: https://code.google.com/p/skia/source/detail?r=13044

[borenet, 2014-01-10 22:05:40]

I didn't really know what to put in here, so I'm open to suggestions.  Adding
this file will cause a handy "guidelines for contributing" bar to show up on the
github page: https://github.com/blog/1184-contributing-guidelines

[hcm, 2014-01-11 05:50:02]

On 2014/01/10 22:05:40, borenet wrote:
> I didn't really know what to put in here, so I'm open to suggestions.  Adding
> this file will cause a handy "guidelines for contributing" bar to show up on
the
> github page: https://github.com/blog/1184-contributing-guidelines

Looks good- we want to beef up the guidelines but only maintain one copy and
that should be the right landing page for the foreseeable future.

[jcgregorio, 2014-01-13 13:30:26]

Should this be CONTRIBUTING.md so that the URL shows up as a link?

[borenet, 2014-01-13 14:01:43]

On 2014/01/13 13:30:26, jcgregorio wrote:
> Should this be CONTRIBUTING.md so that the URL shows up as a link?

It can be, but I didn't want to commit to using (or learning) markdown.

[jcgregorio, 2014-01-13 14:04:58]

On 2014/01/13 14:01:43, borenet wrote:
> On 2014/01/13 13:30:26, jcgregorio wrote:
> > Should this be CONTRIBUTING.md so that the URL shows up as a link?
> 
> It can be, but I didn't want to commit to using (or learning) markdown.

OK, we'll try this and see if the link shows up, if not I can convert it to a
CONTRIBUTING.md in another CL.

[borenet, 2014-01-13 14:07:12]

On 2014/01/13 14:04:58, jcgregorio wrote:
> On 2014/01/13 14:01:43, borenet wrote:
> > On 2014/01/13 13:30:26, jcgregorio wrote:
> > > Should this be CONTRIBUTING.md so that the URL shows up as a link?
> > 
> > It can be, but I didn't want to commit to using (or learning) markdown.
> 
> OK, we'll try this and see if the link shows up, if not I can convert it to a
> CONTRIBUTING.md in another CL.

SGTM

[commit-bot: I haz the power, 2014-01-13 14:09:48]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a lowly provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[jcgregorio, 2014-01-13 14:10:14]

lgtm

[commit-bot: I haz the power, 2014-01-13 14:11:28]

CQ is trying da patch. Follow status at
https://skia-tree-status.appspot.com/cq/borenet@google.com/134663003/30001

[commit-bot: I haz the power, 2014-01-13 14:11:30]

Can't process patch for file CONTRIBUTING.
Filename can't start with 'CON'.

[rmistry, 2014-01-13 14:17:23]

On 2014/01/13 14:11:30, I haz the power (commit-bot) wrote:
> Can't process patch for file CONTRIBUTING.
> Filename can't start with 'CON'.

Interesting. In line 75 in
http://src.chromium.org/viewvc/chrome/trunk/tools/depot_tools/patch.py
The patch fails if a filename starts with CON or COM.

+ iannucci

Robbie, Do you remember why this was done? (this does not impact us too much but
just curious)

[rmistry, 2014-01-13 14:17:43]

On 2014/01/13 14:17:23, rmistry wrote:
> On 2014/01/13 14:11:30, I haz the power (commit-bot) wrote:
> > Can't process patch for file CONTRIBUTING.
> > Filename can't start with 'CON'.
> 
> Interesting. In line 75 in
> http://src.chromium.org/viewvc/chrome/trunk/tools/depot_tools/patch.py
> The patch fails if a filename starts with CON or COM.
> 
> + iannucci
> 
> Robbie, Do you remember why this was done? (this does not impact us too much
but
> just curious)

line 75 -> line 57

[borenet, 2014-01-13 15:06:29]

Committed patchset #2 manually as r13044 (presubmit successful).