@@ -219,4 +219,34 @@ We can now use that in our activity to allow sending a message:
219
219
220
220
Et voila: a minimal, yet fully functional, chat app in about 30 lines of code. Not bad, right?
221
221
222
- ## Contributing to the library
222
+
223
+ ## Contributor License Agreements
224
+
225
+ We'd love to accept your sample apps and patches! Before we can take them, we
226
+ have to jump a couple of legal hurdles.
227
+
228
+ Please fill out either the individual or corporate Contributor License Agreement
229
+ (CLA).
230
+
231
+ * If you are an individual writing original source code and you're sure you
232
+ own the intellectual property, then you'll need to sign an [ individual CLA]
233
+ (https://developers.google.com/open-source/cla/individual ).
234
+ * If you work for a company that wants to allow you to contribute your work,
235
+ then you'll need to sign a [ corporate CLA]
236
+ (https://developers.google.com/open-source/cla/corporate ).
237
+
238
+ Follow either of the two links above to access the appropriate CLA and
239
+ instructions for how to sign and return it. Once we receive it, we'll be able to
240
+ accept your pull requests.
241
+
242
+ ## Contributing A Patch
243
+
244
+ 1 . Submit an issue describing your proposed change to the repo in question.
245
+ 1 . The repo owner will respond to your issue promptly.
246
+ 1 . If your proposed change is accepted, and you haven't already done so, sign a
247
+ Contributor License Agreement (see details above).
248
+ 1 . Fork the desired repo, develop and test your code changes.
249
+ 1 . Ensure that your code adheres to the existing style of the library to which
250
+ you are contributing.
251
+ 1 . Ensure that your code has an appropriate set of unit tests which all pass.
252
+ 1 . Submit a pull request.
0 commit comments