feat: configurable reference frame for a north-referenced azimuth

.github/FUNDING.yaml

@@ -0,0 +1 @@
+github: tlserver

.github/ISSUE_TEMPLATE/Bug.yaml

@@ -0,0 +1,118 @@
+name: Bug Report
+description: File a report if you've encountered a bug with FlutterRotationSensor.
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        # 🐛 Bug Report
+
+        Thank you for using FlutterRotationSensor! Before you submit your bug report, please:
+
+        - Review the [documentation](https://pub.dev/documentation/flutter_map_location_marker/latest/).
+        - Search for similar issues in both [open and closed tickets](https://github.com/tlserver/flutter_rotation_sensor/issues?q=is%3Aissue).
+        - Discuss non-bug-related questions on [GitHub discussions](https://github.com/tlserver/flutter_rotation_sensor/discussions) or [Stack Overflow](https://stackoverflow.com/).
+
+        If you're certain the issue you're experiencing is a bug, please provide as much detail as possible in this report so we can help you resolve it.
+
+        **Note:** Bug reports not adhering to this template may be closed for incomplete information.
+
+  - type: checkboxes
+    id: self-checks
+    attributes:
+      label: Preliminary Bug Check
+      description: Ensure you've taken these steps before submitting a bug.
+      options:
+        - label: I've searched the issue tracker for similar bug reports.
+          required: true
+        - label: I've checked Google and Stack Overflow for solutions.
+          required: true
+        - label: I've read the plugin's documentation.
+          required: true
+        - label: I'm using the latest plugin version and all dependencies are updated with `flutter pub upgrade`.
+          required: true
+        - label: I've executed `flutter clean`.
+          required: true
+        - label: I've tried running the example project.
+          required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: Plugin Version
+      description: What version of the plugin are you using?
+      placeholder: e.g., 1.0.0
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What did you expect to happen?
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happened? Please include as much detail as possible.
+    validations:
+      required: true
+
+  - type: textarea
+    id: code
+    attributes:
+      label: Code Sample
+      render: dart
+      description: |
+        Provide a minimal code sample or a link to a gist that reproduces the error. Ideally, share a main.dart file that we can run to see the issue.
+    validations:
+      required: false
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to Reproduce
+      description: Detail the exact steps to reproduce the bug.
+    validations:
+      required: true
+
+  - type: input
+    id: platform
+    attributes:
+      label: Platform Details
+      description: Which platform and version did the issue occur on (e.g., Android, iOS)?
+      placeholder: e.g., Android 12, iOS 14
+    validations:
+      required: true
+
+  - type: input
+    id: sdk
+    attributes:
+      label: Flutter SDK Version
+      description: Provide the version of the Flutter SDK you are using.
+      placeholder: e.g., 3.0.0
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs
+      render: shell
+      description: |
+        Attach the full output of `flutter run --verbose`. If there's an exception, ensure the log includes enough detail to diagnose the issue.
+    validations:
+      required: true
+
+  - type: textarea
+    id: doctor
+    attributes:
+      label: Flutter Doctor Output
+      render: shell
+      description: What is the output of `flutter doctor -v`? This provides us with your development environment details.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/FeatureRequest.yaml

@@ -0,0 +1,77 @@
+name: Feature Request
+description: Suggest an idea or enhancement for the FlutterRotationSensor plugin.
+title: "[Feature Request]: "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        # ✨ Feature Request
+
+        Thank you for taking the time to suggest a feature for FlutterRotationSensor!
+
+        Before submitting your feature request, please consider the following:
+        - Check if a similar feature request [has already been submitted](https://github.com/tlserver/flutter_rotation_sensor/issues?q=is%3Aissue+label%3Aenhancement).
+        - Review the [documentation](https://pub.dev/documentation/flutter_map_location_marker/latest/) to ensure your feature doesn't already exist.
+
+        If you have a specific idea in mind, fill out the template below. Detailed proposals have a higher chance of being considered.
+
+  - type: input
+    id: feature-summary
+    attributes:
+      label: Feature Summary
+      description: A short, descriptive title for your feature request.
+      placeholder: e.g., Support for XYZ sensor data
+    validations:
+      required: true
+
+  - type: textarea
+    id: feature-description
+    attributes:
+      label: Detailed Description
+      description: Provide a detailed description of your feature request. What problem does it solve or functionality does it add?
+    validations:
+      required: true
+
+  - type: textarea
+    id: potential-benefits
+    attributes:
+      label: Potential Benefits
+      description: Explain the benefits this feature would provide to users or developers.
+    validations:
+      required: true
+
+  - type: textarea
+    id: possible-solutions
+    attributes:
+      label: Possible Solutions
+      description: If you have ideas on how to implement this feature, please share them here.
+    validations:
+      required: false
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: Describe any alternative solutions or features you've considered.
+    validations:
+      required: false
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Add any other context, links, or screenshots about the feature request here.
+    validations:
+      required: false
+
+  - type: checkboxes
+    id: additional-checks
+    attributes:
+      label: Preliminary Checks
+      description: Ensure you've considered what's necessary before we proceed with this feature request.
+      options:
+        - label: I've checked if this feature request does not already exist.
+          required: true
+        - label: I've considered and outlined any potential impact on existing functionality.
+          required: true

.github/dependabot.yaml

@@ -0,0 +1,34 @@
+version: 2
+updates:
+
+  - package-ecosystem: "pub"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    rebase-strategy: "disabled"
+    commit-message:
+      prefix: "chore"
+
+  - package-ecosystem: "pub"
+    directory: "/example"
+    schedule:
+      interval: "weekly"
+    rebase-strategy: "disabled"
+    commit-message:
+      prefix: "chore"
+
+  - package-ecosystem: "gradle"
+    directory: "/android"
+    schedule:
+      interval: "monthly"
+    rebase-strategy: "disabled"
+    commit-message:
+      prefix: "chore"
+
+  - package-ecosystem: "gradle"
+    directory: "/example/android"
+    schedule:
+      interval: "monthly"
+    rebase-strategy: "disabled"
+    commit-message:
+      prefix: "chore"

.github/workflows/stale.yaml

@@ -0,0 +1,21 @@
+name: 'Stale'
+on:
+  schedule:
+    - cron: '16 10 * * *'
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v5
+        with:
+          repo-token: ${{ github.token }}
+          stale-issue-message: 'This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.'
+          stale-pr-message: 'This PR is stale because it has been open for 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.'
+          close-issue-message: 'This issue was closed because it has been stalled for 7 days with no activity.'
+          close-pr-message: 'This PR was closed because it has been stalled for 14 days with no activity.'
+          close-issue-reason: 'not_planned'
+          days-before-issue-stale: 30
+          days-before-issue-close: 7
+          days-before-pr-stale: 60
+          days-before-pr-close: 14

.gitignore

@@ -7,7 +7,6 @@
 .dart_tool/
 .flutter-plugins
 .flutter-plugins-dependencies
-.fvm/flutter_sdk
 .packages
 .pub-cache/
 .pub/
@@ -17,7 +16,7 @@ lib/generated_plugin_registrant.dart
 # For library packages, don’t commit the pubspec.lock file.
 # Regenerating the pubspec.lock file lets you test your package against the latest compatible versions of its dependencies.
 # See https://dart.dev/guides/libraries/private-files#pubspeclock
-pubspec.lock
+/pubspec.lock
 
 # Android related
 **/android/**/gradle-wrapper.jar
@@ -178,4 +177,7 @@ fabric.properties
 # https://plugins.jetbrains.com/plugin/8053-azure-toolkit-for-intellij
 .idea/**/azureSettings.xml
 
-# End of https://www.toptal.com/developers/gitignore/api/jetbrains,flutter
+# End of https://www.toptal.com/developers/gitignore/api/jetbrains,flutter
+
+# FVM Version Cache
+.fvm/