xref: /aosp_15_r20/external/gemmlowp/CONTRIBUTING (revision 5f39d1b313f0528e11bae88b3029b54b9e1033e7)
1*5f39d1b3SJooyung HanWant to contribute? Great! First, read this page (including the small print at the end).
2*5f39d1b3SJooyung Han
3*5f39d1b3SJooyung Han
4*5f39d1b3SJooyung HanBefore you contribute
5*5f39d1b3SJooyung Han=====================
6*5f39d1b3SJooyung Han
7*5f39d1b3SJooyung HanBefore we can use your code, you must sign the Google Individual Contributor
8*5f39d1b3SJooyung HanLicense Agreement (CLA),
9*5f39d1b3SJooyung Han
10*5f39d1b3SJooyung Han  https://developers.google.com/open-source/cla/individual?csw=1
11*5f39d1b3SJooyung Han
12*5f39d1b3SJooyung Hanwhich you can do online. The CLA is necessary mainly because you own the
13*5f39d1b3SJooyung Hancopyright to your changes, even after your contribution becomes part of our
14*5f39d1b3SJooyung Hancodebase, so we need your permission to use and distribute your code. We also
15*5f39d1b3SJooyung Hanneed to be sure of various other things—for instance that you'll tell us if you
16*5f39d1b3SJooyung Hanknow that your code infringes on other people's patents. You don't have to sign
17*5f39d1b3SJooyung Hanthe CLA until after you've submitted your code for review and a member has
18*5f39d1b3SJooyung Hanapproved it, but you must do it before we can put your code into our codebase.
19*5f39d1b3SJooyung HanBefore you start working on a larger contribution, you should get in touch with
20*5f39d1b3SJooyung Hanus first through the issue tracker with your idea so that we can help out and
21*5f39d1b3SJooyung Hanpossibly guide you. Coordinating up front makes it much easier to avoid
22*5f39d1b3SJooyung Hanfrustration later on.
23*5f39d1b3SJooyung Han
24*5f39d1b3SJooyung Han
25*5f39d1b3SJooyung HanGetting in touch with the gemmlowp community
26*5f39d1b3SJooyung Han============================================
27*5f39d1b3SJooyung Han
28*5f39d1b3SJooyung HanThe central point of communication around gemmlowp is the mailing list,
29*5f39d1b3SJooyung Han  https://groups.google.com/forum/#!forum/gemmlowp
30*5f39d1b3SJooyung Han
31*5f39d1b3SJooyung Han
32*5f39d1b3SJooyung HanTODO items and projects
33*5f39d1b3SJooyung Han=======================
34*5f39d1b3SJooyung Han
35*5f39d1b3SJooyung HanWe try to keep a current list of TODO items in the todo/ directory.
36*5f39d1b3SJooyung HanPlease feel free to pick one to work on, and to ask current maintainers for
37*5f39d1b3SJooyung Hanguidance. The gemmlowp mailing list is a good place for that.
38*5f39d1b3SJooyung Han
39*5f39d1b3SJooyung Han
40*5f39d1b3SJooyung HanCode reviews
41*5f39d1b3SJooyung Han============
42*5f39d1b3SJooyung Han
43*5f39d1b3SJooyung HanAll submissions, including submissions by project members, require review.
44*5f39d1b3SJooyung HanFor this purpose, we use Github pull requests against this repository:
45*5f39d1b3SJooyung Han
46*5f39d1b3SJooyung Han  https://github.com/google/gemmlowp
47*5f39d1b3SJooyung Han
48*5f39d1b3SJooyung Han
49*5f39d1b3SJooyung HanThe small print
50*5f39d1b3SJooyung Han===============
51*5f39d1b3SJooyung Han
52*5f39d1b3SJooyung HanContributions made by corporations are covered by a different agreement than
53*5f39d1b3SJooyung Hanthe one above, the Software Grant and Corporate Contributor License Agreement.
54