Skip to content

Commit 4dbdfcf

Browse files
committed
Added the CLA
Since this is a Google owned open-source repo, contributors will have to fill out a Contributor License Agreement.
1 parent e62d8c0 commit 4dbdfcf

File tree

1 file changed

+32
-1
lines changed

1 file changed

+32
-1
lines changed

README.md

Lines changed: 32 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,7 @@ FirebaseDataSource acts as a generic data source by providing common information
161161
- From your macbook that already has been granted permissions to Firebase Cocoapods, do `pod trunk push`
162162
- Update [firebase-versions](https://github.com/firebase/firebase-clients/blob/master/versions/firebase-versions.json) with the changelog for this release.
163163

164-
## Contributing
164+
## Local Setup
165165

166166
If you'd like to contribute to FirebaseUI for iOS, you'll need to run the
167167
following commands to get your environment set up:
@@ -171,3 +171,34 @@ $ git clone https://github.com/firebase/FirebaseUI-iOS.git
171171
$ cd FirebaseUI-iOS
172172
$ ./setup.sh
173173
```
174+
175+
## Contributor License Agreements
176+
177+
We'd love to accept your sample apps and patches! Before we can take them, we
178+
have to jump a couple of legal hurdles.
179+
180+
Please fill out either the individual or corporate Contributor License Agreement
181+
(CLA).
182+
183+
* If you are an individual writing original source code and you're sure you
184+
own the intellectual property, then you'll need to sign an [individual CLA]
185+
(https://developers.google.com/open-source/cla/individual).
186+
* If you work for a company that wants to allow you to contribute your work,
187+
then you'll need to sign a [corporate CLA]
188+
(https://developers.google.com/open-source/cla/corporate).
189+
190+
Follow either of the two links above to access the appropriate CLA and
191+
instructions for how to sign and return it. Once we receive it, we'll be able to
192+
accept your pull requests.
193+
194+
## Contributing A Patch
195+
196+
1. Submit an issue describing your proposed change to the repo in question.
197+
1. The repo owner will respond to your issue promptly.
198+
1. If your proposed change is accepted, and you haven't already done so, sign a
199+
Contributor License Agreement (see details above).
200+
1. Fork the desired repo, develop and test your code changes.
201+
1. Ensure that your code adheres to the existing style of the library to which
202+
you are contributing.
203+
1. Ensure that your code has an appropriate set of unit tests which all pass.
204+
1. Submit a pull request.

0 commit comments

Comments
 (0)