Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(139)

Side by Side Diff: pkg/analysis_server/CONTRIBUTING.md

Issue 2685913002: Update the contributing file for the analysis server. (Closed)
Patch Set: Created 3 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « pkg/analysis_server/.gitignore ('k') | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 Want to contribute? Great! First, read this page (including the small print at 1 ## Contributing
2 the end).
3 2
4 ### Before you contribute 3 Contributions welcome! Please follow the guide in [Contributing][contributing].
5 Before we can use your code, you must sign the
6 [Google Individual Contributor License Agreement](https://cla.developers.google. com/about/google-individual)
7 (CLA), which you can do online. The CLA is necessary mainly because you own the
8 copyright to your changes, even after your contribution becomes part of our
9 codebase, so we need your permission to use and distribute your code. We also
10 need to be sure of various other things—for instance that you'll tell us if you
11 know that your code infringes on other people's patents. You don't have to sign
12 the CLA until after you've submitted your code for review and a member has
13 approved it, but you must do it before we can put your code into our codebase.
14 4
15 Before you start working on a larger contribution, you should get in touch with 5 ## Building
16 us first through the issue tracker with your idea so that we can help out and
17 possibly guide you. Coordinating up front makes it much easier to avoid
18 frustration later on.
19 6
20 ### Code reviews 7 If you want to build Dart yourself, here is a guide to
21 All submissions, including submissions by project members, require review. 8 [getting the source, preparing your machine to build the SDK, and
9 building][building].
22 10
23 ### File headers 11 There are more documents on our [wiki](https://github.com/dart-lang/sdk/wiki).
24 All files in the project must start with the following header. 12 Once set up to build the SDK, run:
25 13
26 // Copyright (c) 2015, the Dart project authors. Please see the AUTHORS fil e 14 ```
27 // for details. All rights reserved. Use of this source code is governed by a 15 ./tools/build.py -mrelease create_sdk
28 // BSD-style license that can be found in the LICENSE file. 16 ```
29 17
30 ### The small print 18 ## Running tests
31 Contributions made by corporations are covered by a different agreement than the 19
32 one above, the 20 To run analyzer tests:
33 [Software Grant and Corporate Contributor License Agreement](https://developers. google.com/open-source/cla/corporate). 21
22 ```
23 ./tools/test.py -mrelease pkg/analyzer/test/
24 ```
25
26 To run all analysis server tests:
27
28 ```
29 ./tools/test.py -mrelease pkg/analysis_server/test/
30 ```
31
32 To run just the analysis server integration tests:
33
34 ```
35 ./tools/test.py -mrelease pkg/analysis_server/test/integration/
36 ```
37
38
39 [building]: https://github.com/dart-lang/sdk/wiki/Building
40 [contributing]: https://github.com/dart-lang/sdk/wiki/Contributing
OLDNEW
« no previous file with comments | « pkg/analysis_server/.gitignore ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698