Initial release

Author: Emilio Pavia

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.gitignore

@@ -0,0 +1,41 @@
+## Build generated
+build/
+DerivedData/
+
+## Protos
+third_party/sciencejournal/ios/Protos/*.pbobjc.*
+
+## Various settings
+*.pbxuser
+!default.pbxuser
+*.mode1v3
+!default.mode1v3
+*.mode2v3
+!default.mode2v3
+*.perspectivev3
+!default.perspectivev3
+xcuserdata/
+
+## Other
+*.moved-aside
+*.xcuserstate
+.DS_Store
+
+## Obj-C/Swift specific
+*.hmap
+*.ipa
+*.dSYM.zip
+*.dSYM
+
+## CocoaPods
+Pods/
+ScienceJournal.xcworkspace
+
+## Generated Plist
+Info-Combined.plist
+
+## Local option overrides for SwiftLint
+.swiftlint.options.local
+
+## fastlane
+fastlane/

.swiftlint.yml

@@ -0,0 +1,36 @@
+# This config file defines the rules, but it should not be used to specify
+# which paths are linted. Build Phase scripts exclusive to each build are
+# responsible for referencing this config file and the paths to lint.
+
+line_length:
+  warning: 130
+
+file_length:
+  warning: 1000 # We have some longer file length we should reduce.
+
+function_body_length:
+  warning: 110 # We have some longer function bodies we should reduce.
+
+function_parameter_count:
+  warning: 8 # We use a lot of dependency injection. TODO: pass dependencies in groups.
+
+nesting:
+  type_level: 2 # We compartmentalize a lot of views and data with nesting.
+
+type_body_length:
+  warning: 314 # We have some offenders that should be cleaned up.
+
+force_cast:
+  severity: warning
+
+disabled_rules:
+  - closure_parameter_position  # Newlines can conflict with having params on same line as opening brace.
+  - colon # Problematic for newlines.
+  - identifier_name # Generates false positives for max length.
+  - todo # We have todos and are ok with that.
+  - type_name # Types should be as verbose as needed, we also check during code review.
+  - trailing_comma # Google rules say we need a trailing comma.
+  - multiple_closures_with_trailing_closure # We're ok with this.
+  - cyclomatic_complexity # We'll catch future issues in code review.
+  - nesting # We have some cases where deeper nesting is desirable.
+  - trailing_whitespace # So annoying...

CHANGE_LIMITATIONS.md

@@ -0,0 +1,21 @@
+# What changes we can't accept
+
+While we wish we could accept all changes (especially changes that make the organization or readability of the project better), we can't due to technical limitations 😢.
+
+## What is up with this weird module map or strange import statement 🤷‍♂️?
+
+We host our source code in this repo and treat that as the “source of truth”. The internal build toolchain and dependency manager are not CocoaPods. In order to be able to work with both internal and external tooling, we’ve had to make some concessions with how the project is configured. There are a number of considerations you must make if you’re thinking about changing things that look non-standard. 
+
+### Module maps and import statements
+
+We use custom module maps that link directly to various dependencies like [SSOAuth](https://github.com/bcmi-labs/Science-Journal-iOS/blob/master/ModuleMaps/SSOAuth.modulemaps/module.modulemap). We can’t modify these as our internal dependency management tool has some requirements that necessitate the current import format. You can see that come into play where imports are prefixed with things like “[googlemac_iPhone](https://github.com/bcmi-labs/Science-Journal-iOS/blob/a172a0b2ec1987c214c29371bcdbc2ecbecc901a/ScienceJournal/Accounts/AccountsManager.swift#L19)”. Sadly, we must leave these in.
+
+### Updating Swift
+
+We want to be running the latest Swift 🏃‍♀️ as much as anybody. At this time we can’t accept Swift version update PRs. Our internal source of truth must be updated first. Because the internal source of truth has more code than the open source project, we’ll have to do the migration, and test it internally to make sure all of our tooling works—inside and outside of Google.
+
+### Podfile updates
+
+Adding new pods isn’t out of the question, but please be mindful as we only support Apache 2.0 and MIT licensed software.
+
+It is unlikely we'd be able to approve the removal or update of existing pods. We have more internal requirements that must be satisfied so we limit podfile updates to new features, bug fixes, and security updates that impact us.

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,49 @@
+# Contributing to Science Journal iOS
+
+## I have a question or want to report a problem
+
+### App Store downloaded Science Journal
+
+If you're having a problem with [Science Journal from the App Store](https://apps.apple.com/us/app/arduino-science-journal/id1518014927?mt=8), the fastest way to get support is by using the in-app feedback button. This can be found by navigating to the experiment list screen, tapping on the hamburger menu, and then tapping "Feedback".
+
+### Downloaded and built from GitHub
+
+If you built the app yourself, somebody else, or any other distribution channel that wasn't Apple's App Store, this section is for you!
+
+Before submitting a new GitHub issue, please make sure to
+
+- Check out our forums [Science Journal forums](https://forum.arduino.cc/index.php?board=131.0)
+- Check out the README in [this repo](https://github.com/bcmi-labs/Science-Journal-iOS/blob/master/README.md)
+- Search for [existing GitHub issues](https://github.com/bcmi-labs/Science-Journal-iOS/issues)
+
+If the above doesn't help, please [submit an issue](https://github.com/bcmi-labs/Science-Journal-iOS/issues) on GitHub and provide information about your setup.
+
+**Note**: If you want to report a regression in Science Journal iOS (something that has worked before, but broke with a new release), please mark your issue title as such using `[Regression] Your title here`. This enables us to quickly detect and fix regressions.
+
+## I want to contribute to Science Journal iOS
+
+- To start working on Science Journal iOS, check out [Your First PR](https://github.com/bcmi-labs/Science-Journal-iOS/blob/master/YOUR_FIRST_PR.md).
+- We have a few limits on what changes we can accept, from a techinical perspective. It might not be obvious, so please read [Change Limitations](https://github.com/bcmi-labs/Science-Journal-iOS/blob/master/CHANGE_LIMITATIONS.md).
+
+## Contributor License Agreement (CLA)
+
+Upon your first pull request to Science Journal iOS, we ask you to sign the [Contributor License Agreement](). Once the CLA has been accepted, the PR will be available to merge and you will not be asked to sign it again unless your GitHub username or email address changes.
+
+
+## Why did my issue/PR get closed?
+
+It's not you, it's us! Science Journal iOS might receive a lot of issues and PRs. In order to effectively work through them and give each the prompt attention it deserves, we need to keep a sharp focus on the work we have outstanding.
+
+One way we do this is by closing issues that we don't feel are immediately actionable. This might mean that we need more information in order to investigate or, it might mean that we haven't been able to reproduce it using the provided info. In this case we might close the issue while we wait for others to reproduce the problem and possibly provide some more info that unlocks the mystery.
+
+**A closed issue is not necessarily the end of the story!** If more info becomes available after an issue is closed, it can be reopened for further consideration.
+
+One of the best ways we can keep Science Journal iOS an approachable, stable, and dependable app is to be deliberate about how we choose to modify it. If we don't adopt your changes or new feature, that doesn't mean it was bad work! It may be that the Science Journal philosophy about how to accomplish a particular task doesn't align well with your approach. The best way to make sure that your time is well spent in contributing to Science Journal iOS is to **start your work** on a modification or new feature **by opening an issue to discuss the problem or shortcoming**. As the Science Journal iOS maintainers, we will do our best to give early feedback about whether a particular goal and approach is likely to be something we want to adopt!
+
+## Code of Conduct
+
+Help us keep Science Journal iOS open and inclusive. Please read and follow our [Code of Conduct](https://github.com/bcmi-labs/Science-Journal-iOS/blob/master/CODE_OF_CONDUCT.md).
+
+## License
+
+This project is licensed under the terms of the Apache 2.0 license. See the [LICENSE](https://github.com/bcmi-labs/Science-Journal-iOS/blob/master/LICENSE) file.