Merge branch 'main' into google-maps-ios

ColoradoSchoolOfMines · Oct 10, 2023 · d6aa0da · d6aa0da
2 parents 708a51c + 178ea0a
commit d6aa0da
Show file tree

Hide file tree

Showing 34 changed files with 3,660 additions and 38 deletions.
diff --git a/.github/workflows/nodejs-lint.yaml b/.github/workflows/nodejs-lint.yaml
@@ -1,6 +1,10 @@
 name: Lint-Node
 
-on: [push, pull_request]
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
 
 jobs:
   lint-node:
@@ -17,4 +21,4 @@ jobs:
       - name: run eslint
         working-directory: ./frontend/
         run: |
-          npx eslint App.tsx `find ./src -type f \( -name "*.ts" -o -name "*.tsx" \)` --debug
+          npx eslint App.tsx `find ./src -type f \( -name "*.ts" -o -name "*.tsx" \)` --debug
diff --git a/.github/workflows/python-lint.yaml b/.github/workflows/python-lint.yaml
@@ -1,6 +1,10 @@
 name: Lint-Python
 
-on: [push, pull_request]
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
 
 jobs:
   lint-python:
@@ -15,4 +19,4 @@ jobs:
       - run: black --check --diff ./backend/
       - run: isort --check --diff ./backend/
       - run: mypy ./backend/
-      - run: pylint -E ./backend/
+      - run: pylint -E ./backend/
diff --git a/.hooks/pre-push b/.hooks/pre-push
diff --git a/CODEOWNERS b/CODEOWNERS
@@ -0,0 +1,10 @@
+# Leads
+* @OreCart/leads
+
+# general
+backend/ @OreCart/backend @OreCart/code-reviewers
+frontend/ @OreCart/frontend @OreCart/code-reviewers
+
+# DevOps Things
+.github/ @tbwrigh
+docker-compose.yml @tbwrigh
diff --git a/LICENSE b/LICENSE
@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2023 The OreCart Team
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
diff --git a/README.md b/README.md
@@ -1,10 +1,28 @@
-# Ore Cart App
+# Ore Cart App [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
 
-For more details please see the Google Drive.
+The master monorepo for all OreCart app software! The OreCart app includes a backend made with [FastAPI](https://fastapi.tiangolo.com) and a crossplatform mobile app made with [React-Native](https://reactnative.dev).
 
-The frontend and backend folders have READMEs with more information about developing in each as well.
+For full documentation and project details, please see our Google Drive (contributors can gain access by talking with the leads). The frontend and backend folders have READMEs with more information about developing in each as well.
 
-## General Requirements
+## General Environment Setup
 
-Please use feature branches and PRs. Do not commit to Main!
+For this project you will need [Docker](https://www.docker.com), [Node.js](https://nodejs.org/en), and [Python 3](https://www.python.org).
 
+To start up the PostgreSQL database, run `docker compose up -d`.
+
+To stop the PostgreSQL database, run `docker compose down`.
+
+## Contribution Guidelines
+
+Contributors (aka "The OreCart Team") must be approved by the current [OreCart/leads](https://github.com/orgs/OreCart/teams/leads) team.
+Outside contributors are not allowed unless explicit approval is granted by leads.
+
+Do not push code directly to main -- the branch is locked for this anyways! Please use branches for each new feature and submit a pull request when ready.
+Branch names should be short but descriptive, and all lowercase.
+
+Each pull request requires a **minimum of two relevant reviewers** (leads or team members) for approval and merging.
+
+## Legal Notices
+
+Any references to Colorado School of Mines (aka "Mines", "CSM"), Innov8x, or official OreCart brand identity are used with
+permission for this project, however, this project is not owned by Mines or Mines ACM itself. See the [LICENSE](https://github.com/OreCart/OreCart-App/blob/main/LICENSE) for more details.
diff --git a/backend/.env.template b/backend/.env.template
@@ -0,0 +1,7 @@
+DB_USER="postgres"
+DB_PASS="password"
+DB_ADDR="localhost"
+DB_PORT="5432"
+DB_DBNAME="postgres"
+
+DATABASE_URL="postgresql://${DB_USER}:${DB_PASS}@${DB_ADDR}:${DB_PORT}/${DB_DBNAME}"
diff --git a/backend/README.md b/backend/README.md
@@ -2,14 +2,13 @@
 
 ## Development Overview 🌟
 
-
 The backend will be used to store locations of the shuttles, serve that data to the frontend, and make statistics about the Ore Cart queryable.
 
 ## Development Expectations 📌
 
 ### Dependencies 📦
 
-Keeping track of dependencies can be hard and frustrating. As such, we have a `requirements.txt` file that can be used to install the dependencies with `pip install -r requirements.txt`. If you add a dependency and know how to update the `requirements.txt` accordingly please do, if you do not know how to update it, run `pip freeze > requirements.txt`. 
+Keeping track of dependencies can be hard and frustrating. As such, we have a `requirements.txt` file that can be used to install the dependencies with `pip install -r requirements.txt`. If you add a dependency and know how to update the `requirements.txt` accordingly please do, if you do not know how to update it, run `pip freeze > requirements.txt`.
 
 One side note regarding updating the `requirements.txt`, please do not add anything unnecessary to it! We want to minimize bloat for everyone, but also because our CI build needs to install the requirements.txt frequently, so adding unnecessary dependencies will slow down our CI.
 
@@ -28,7 +27,7 @@ python3 -m venv venv
 Before you start working on this project, activate the venv. To that run the following command (again this may vary by system):
 
 ```
-./venv/bin/activate
+source venv/bin/activate
 ```
 
 When you are done working on this project, deactivate the venv. The following command deactivate the venv (This should be fairly standardized):
@@ -39,6 +38,24 @@ deactivate
 
 ---
 
+### Running the server
+
+To run the backend, ensure your venv is running:
+
+```
+source venv/bin/activate
+```
+
+Then execute the following command:
+
+```
+uvicorn src.main:app --reload
+```
+
+The server will be running on `localhost:8000`!
+
+---
+
 ### Formatting, Linting, Typing, and More 🛠️
 
 Our repository has CI running and checking the code passes several checks (black, mypy, isort, and pylint). If you want to know what the checks are and how to check locally read below! 🧹
@@ -54,6 +71,3 @@ Lastly, we are using pylint to verify that our python doesn't have any obvious e
 ---
 
 Feel free to reach out if you have any questions or need further clarification on any of these development expectations! 🙌
-
-
-
diff --git a/backend/backend-schema-proposal.md b/backend/backend-schema-proposal.md
@@ -3,7 +3,6 @@
 ## Hardware->Backend
 
 POST `/location/{van_id}`
-seperate
 
 - `van_id` is an 8-bit integer
 - Message body is `(lat, lon, timestamp)`, where `lat` & `lon` are 64-bit doubles,