aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Thomas Van Lenten <thomasvl@google.com>2015-08-18 15:17:45 -0400
committerGravatar Thomas Van Lenten <thomasvl@google.com>2015-08-18 15:19:24 -0400
commit64750f4c7032b461614e22650e70b4e2219deed4 (patch)
tree6f1f4c7620072e42db05027743dbe0c4ceea1762
parentec189725d81a238ccf990bbf2bc015013abac913 (diff)
Update the project for github migration
- Update URL - Add README.md/License/Contributing info to be up to spec. - Remove a bunch of executable bits on sources.
-rw-r--r--CONTRIBUTING.md54
-rw-r--r--LICENSE (renamed from COPYING)4
-rw-r--r--README.md (renamed from ReleaseNotes.txt)9
-rw-r--r--[-rwxr-xr-x]iPhone/GTMFadeTruncatingLabel.h0
-rw-r--r--[-rwxr-xr-x]iPhone/GTMFadeTruncatingLabel.m0
5 files changed, 62 insertions, 5 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..faf7830
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,54 @@
+# How to contribute #
+
+We'd love to accept your patches and contributions to this project. There are
+a just a few small guidelines you need to follow.
+
+
+## Contributor License Agreement ##
+
+Contributions to any Google project must be accompanied by a Contributor
+License Agreement. This is not a copyright **assignment**, it simply gives
+Google permission to use and redistribute your contributions as part of the
+project.
+
+ * If you are an individual writing original source code and you're sure you
+ own the intellectual property, then you'll need to sign an [individual
+ CLA][].
+
+ * If you work for a company that wants to allow you to contribute your work,
+ then you'll need to sign a [corporate CLA][].
+
+You generally only need to submit a CLA once, so if you've already submitted
+one (even if it was for a different project), you probably don't need to do it
+again.
+
+[individual CLA]: https://developers.google.com/open-source/cla/individual
+[corporate CLA]: https://developers.google.com/open-source/cla/corporate
+
+
+## Submitting a patch ##
+
+ 1. It's generally best to start by opening a new issue describing the bug or
+ feature you're intending to fix. Even if you think it's relatively minor,
+ it's helpful to know what people are working on. Mention in the initial
+ issue that you are planning to work on that bug or feature so that it can
+ be assigned to you.
+
+ 1. Follow the normal process of [forking][] the project, and setup a new
+ branch to work in. It's important that each group of changes be done in
+ separate branches in order to ensure that a pull request only includes the
+ commits related to that bug or feature.
+
+ 1. Any significant changes should almost always be accompanied by tests. The
+ project already has good test coverage, so look at some of the existing
+ tests if you're unsure how to go about it.
+
+ 1. Do your best to have [well-formed commit messages][] for each change.
+ This provides consistency throughout the project, and ensures that commit
+ messages are able to be formatted properly by various git tools.
+
+ 1. Finally, push the commits to your fork and submit a [pull request][].
+
+[forking]: https://help.github.com/articles/fork-a-repo
+[well-formed commit messages]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[pull request]: https://help.github.com/articles/creating-a-pull-request
diff --git a/COPYING b/LICENSE
index a95e82a..d645695 100644
--- a/COPYING
+++ b/LICENSE
@@ -187,7 +187,7 @@
same "printed page" as the copyright notice for easier
identification within third-party archives.
- Copyright 2007 Google Inc.
+ Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
@@ -199,4 +199,4 @@
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
- limitations under the License. \ No newline at end of file
+ limitations under the License.
diff --git a/ReleaseNotes.txt b/README.md
index 986676e..b62c221 100644
--- a/ReleaseNotes.txt
+++ b/README.md
@@ -1,7 +1,10 @@
-Google Toolbox for Mac Release Notes
+# GTM: Google Toolbox for Mac #
-Project site: http://code.google.com/p/google-toolbox-for-mac/
-Discussion group: http://groups.google.com/group/google-toolbox-for-mac
+**Project site** <https://github.com/google/google-toolbox-for-mac><br>
+**Discussion group** <http://groups.google.com/group/google-toolbox-for-mac>
+
+
+## Release History ##
Release 2.0.??
Changes since 1.6.0
diff --git a/iPhone/GTMFadeTruncatingLabel.h b/iPhone/GTMFadeTruncatingLabel.h
index 5d9eb8c..5d9eb8c 100755..100644
--- a/iPhone/GTMFadeTruncatingLabel.h
+++ b/iPhone/GTMFadeTruncatingLabel.h
diff --git a/iPhone/GTMFadeTruncatingLabel.m b/iPhone/GTMFadeTruncatingLabel.m
index 58f0621..58f0621 100755..100644
--- a/iPhone/GTMFadeTruncatingLabel.m
+++ b/iPhone/GTMFadeTruncatingLabel.m