Update README.md file to be more up to date with AndroidX.
Test: None
Change-Id: Iddfd4c72a045e5f4443765cae04827a8218b66db
diff --git a/README.md b/README.md
index f6cdb65..968cbda 100644
--- a/README.md
+++ b/README.md
@@ -1,21 +1,22 @@
-# AOSP Support Library Contribution Guide
+# AOSP AndroidX Contribution Guide
## Accepted Types of Contributions
* Bug fixes (needs a corresponding bug report in b.android.com)
* Each bug fix is expected to come with tests
* Fixing spelling errors
* Updating documentation
* Adding new tests to the area that is not currently covered by tests
+* New features to existing libraries if the feature request bug has been approved by an AndroidX team member.
-We **are not** currently accepting new modules, features, or behavior changes.
+We **are not** currently accepting new modules.
## Checking Out the Code
**NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.**
Follow the [“Downloading the Source”](https://source.android.com/source/downloading.html) guide to install and set up `repo` tool, but instead of running the listed `repo` commands to initialize the repository, run the folowing:
- repo init -u https://android.googlesource.com/platform/manifest -b ub-supportlib-master
+ repo init -u https://android.googlesource.com/platform/manifest -b androidx-master-dev
-Now your repository is set to pull only what you need for building and running support library. Download the code (and grab a coffee while we pull down 7GB):
+Now your repository is set to pull only what you need for building and running Androix libraries. Download the code (and grab a coffee while we pull down 3GB):
repo sync -j8 -c
@@ -31,16 +32,16 @@
## Builds
### Full Build (Optional)
-You can do most of your work from Android Studio, however you can also build the full support library from command line:
+You can do most of your work from Android Studio, however you can also build the full AndroidX library from command line:
cd path/to/checkout/frameworks/support/
./gradlew createArchive
-### Building Support Library as part of your App build
-If you intend to repeatedly make changes to Support Library and to wish to see
+### Building AndroidX Libraries as part of your App build
+If you intend to repeatedly make changes to AndroidX Libraries and to wish to see
the results in your app, and you don't want to have to repeatedly build them as
separate Gradle projects, you can
-[configure your app build to build Support Library too](adding-support-library-as-included-build.md)
+[configure your app build to build AndroidX Libraries too](adding-support-library-as-included-build.md)
## Running Tests
@@ -51,10 +52,10 @@
### Full Test Package
1. In the project side panel open the desired module.
2. Find the directory with the tests
-3. Right-click on the directory and select `Run android.support.foobar`
+3. Right-click on the directory and select `Run androidx.foobar`
## Running Sample Apps
-Support library has a set of Android applications that exercise support library code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.
+AndroidX libraries has a set of Android applications that exercise AndroidX code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.
These applications are named support-\*-demos (e.g. support-4v-demos or support-leanback-demos. You can run them by clicking `Run > Run ...` and choosing the desired application.
@@ -72,5 +73,5 @@
## Getting reviewed
* After you run repo upload, open [r.android.com](http://r.android.com)
* Sign in into your account (or create one if you do not have one yet)
-* Add an appropriate reviewer (use git log to find who did most modifications on the file you are fixing)
+* Add an appropriate reviewer (use git log to find who did most modifications on the file you are fixing or check the OWNERS file in the project's directory)
