update histoircal

.github/ISSUE_TEMPLATE/community_submission.yaml

@@ -8,8 +8,8 @@ body:
   - type: markdown
     attributes:
       value: |
-        Submit **one object** or an **array of objects** that matches the community submission [schema](https://github.com/PlaneQuery/OpenAirframes/blob/main/schemas/community_submission.v1.schema.json). Reuse existing tags from the schema when possible.
-        
+        Submit **one object** or an **array of objects** that matches the community submission schema.
+
         **Rules (enforced on review/automation):**
         - Each object must include **at least one** of:
           - `registration_number`
@@ -27,7 +27,7 @@ body:
         ```json
         {
             "registration_number": "N12345",
-            "tags": {"owner": "John Doe", "photo": "https://example.com/photo.jpg"},
+            "tags": {"owner": "John Doe"},
             "start_date": "2025-01-01"
         }
         ```
@@ -77,5 +77,6 @@ body:
     id: notes
     attributes:
       label: Notes (optional)
+      description: Any context, sources, or links that help validate your submission.
     validations:
       required: false

.github/workflows/update-community-prs.yaml

@@ -48,52 +48,29 @@ jobs:
             git fetch origin "$branch_name"
             git checkout "$branch_name"
             
+            # Merge main into PR branch
             git config user.name "github-actions[bot]"
             git config user.email "github-actions[bot]@users.noreply.github.com"
             
-            # Get the community submission file(s) and schema from this branch
-            community_files=$(git diff --name-only origin/main...HEAD -- 'community/' 'schemas/')
-            
-            if [ -z "$community_files" ]; then
-              echo "  No community/schema files found in PR #$pr_number, skipping"
-              git checkout main
-              continue
-            fi
-            
-            echo "  Files to preserve: $community_files"
-            
-            # Save the community files content
-            mkdir -p /tmp/pr_files
-            for file in $community_files; do
-              if [ -f "$file" ]; then
-                mkdir -p "/tmp/pr_files/$(dirname "$file")"
-                cp "$file" "/tmp/pr_files/$file"
+            if git merge origin/main -m "Merge main to update schema"; then
+              # Regenerate schema for this PR's submission (adds any new tags)
+              python -m src.contributions.regenerate_pr_schema || true
+              
+              # If there are changes, commit and push
+              if [ -n "$(git status --porcelain schemas/)" ]; then
+                git add schemas/
+                git commit -m "Update schema with new tags"
+                git push origin "$branch_name"
+                echo "  Updated PR #$pr_number with schema changes"
+              else
+                git push origin "$branch_name"
+                echo "  Merged main into PR #$pr_number"
               fi
-            done
-            
-            # Reset branch to main (clean slate)
-            git reset --hard origin/main
-            
-            # Restore the community files
-            for file in $community_files; do
-              if [ -f "/tmp/pr_files/$file" ]; then
-                mkdir -p "$(dirname "$file")"
-                cp "/tmp/pr_files/$file" "$file"
-              fi
-            done
-            rm -rf /tmp/pr_files
-            
-            # Regenerate schema with current main + this submission's tags
-            python -m src.contributions.regenerate_pr_schema || true
-            
-            # Stage and commit all changes
-            git add community/ schemas/
-            if ! git diff --cached --quiet; then
-              git commit -m "Community submission (rebased on main)"
-              git push --force origin "$branch_name"
-              echo "  Rebased PR #$pr_number onto main"
             else
-              echo "  No changes needed for PR #$pr_number"
+              echo "  Merge conflict in PR #$pr_number, adding comment"
+              gh pr comment "$pr_number" --body $'⚠️ **Merge Conflict**\n\nAnother community submission was merged and this PR has conflicts.\n\nA maintainer may need to:\n1. Close this PR\n2. Remove the `approved` label from the original issue\n3. Re-add the `approved` label to regenerate the PR'
+              git merge --abort
+              fi
             fi
             
             git checkout main

README.md

@@ -1,50 +1 @@
-# OpenAirframes.org
-
-OpenAirframes.org is an open-source, community-driven airframes database.
-
-The data includes:
-- Registration information from Civil Aviation Authorities (FAA)
-- Airline data (e.g., Air France)
-- Community contributions such as ownership details, military aircraft info, photos, and more
-
----
-
-## For Users
-
-A daily release is created at **06:00 UTC** and includes:
-
-- **openairframes_community.csv**  
-  All community submissions
-
-- **openairframes_faa.csv**  
-  All [FAA registration data](https://www.faa.gov/licenses_certificates/aircraft_certification/aircraft_registry/releasable_aircraft_download) from 2023-08-16 to present (~260 MB)
-
-- **openairframes_adsb.csv**  
-  Airframe information derived from ADS-B messages on the [ADSB.lol](https://www.adsb.lol/) network, from 2026-02-12 to present (will be from 2024-01-01 soon). The airframe information originates from [mictronics aircraft database](https://www.mictronics.de/aircraft-database/) (~5 MB).
-
-- **ReleasableAircraft_{date}.zip**  
-  A daily snapshot of the FAA database, which updates at **05:30 UTC**
-
----
-
-## For Contributors
-
-Submit data via a [GitHub Issue](https://github.com/PlaneQuery/OpenAirframes/issues/new?template=community_submission.yaml) with your preferred attribution. Once approved, it will appear in the daily release. A leaderboard will be available in the future.
-All data is valuable. Examples include:
-- Celebrity ownership (with citations)
-- Photos
-- Internet capability
-- Military aircraft information
-- Unique facts (e.g., an airframe that crashed, performs aerobatics, etc.)
-
-Please try to follow the submission formatting guidelines. If you are struggling with them, that is fine—submit your data anyway and it will be formatted for you.
-
----
-
-## For Developers
-All code, compute (GitHub Actions), and storage (releases) are in this GitHub repository Improvements are welcome. Potential features include:
-- Web UI for data
-- Web UI for contributors
-- Additional export formats in the daily release
-- Data fusion from multiple sources in the daily release
-- Automated airframe data connectors, including (but not limited to) civil aviation authorities and airline APIs
+Downloads [`https://registry.faa.gov/database/ReleasableAircraft.zip`](https://registry.faa.gov/database/ReleasableAircraft.zip). Creates a daily GitHub Release at 06:00 UTC containing the unaltered `ReleasableAircraft.zip` and a derived CSV file with all data from FAA database since 2023-08-16. The FAA database updates daily at 05:30 UTC.