Skip to content

CC0_RESTORATION_PLAN.md

Latest commit

 

History

History
180 lines (128 loc) · 5.08 KB

CC0_RESTORATION_PLAN.md

File metadata and controls

180 lines (128 loc) · 5.08 KB

CC0 Foundation Restoration Plan

Executive Summary

The cc0-foundation branch has been created from commit 03cbd6b (September 12, 2025), the last commit under CC0 license. This document outlines the plan to restore factual content and original contributions while maintaining legal compliance.

Foundation Established ✅

Branch: cc0-foundation
Commit: 03cbd6b - "Add resource: stt-mcp-server-linux (#182)"
Date: September 12, 2025, 12:00 PM
License: CC0 1.0 Universal (Public Domain)
Location: Local repository (needs to be pushed)

Automation Changes Analysis

Question: Did automation change after September 15?

Answer: Minimal changes to core automation between Sept 12-15. The infrastructure at commit 03cbd6b includes:

✅ Workflow Files (.github/workflows/):

  • submit-resource.yml - Issue form processing
  • auto-approve.yml - Automatic PR approval
  • Various validation workflows

✅ Scripts (scripts/):

  • validate.py - URL and format validation
  • generate.py - README generation
  • CSV processing utilities

✅ Templates (templates/):

  • README structure
  • Category templates

Conclusion: All core automation existed in CC0 era. Any post-Sept-15 modifications are minimal and we can use the CC0 versions.

Restoration Steps

Phase 1: Content Identification ✅

Identify three types of content to restore:

  1. Factual Project Submissions (Not Copyrightable)

    • Project names
    • URLs
    • GitHub usernames
    • License information
    • Basic project descriptions (factual only)

  2. Original @thedotmack Content (Your Copyright)

    • GATEKEEPING_ANALYSIS.md
    • GATEKEEPING_SUMMARY.md
    • RESOLUTION.md
    • FORK_README.md
    • Any other docs you created

  3. Infrastructure (From CC0 Era)

    • Already included in foundation commit
    • No restoration needed

Phase 2: Restore Factual Submissions

Action: Compare THE_RESOURCES_TABLE.csv from foundation vs. current version

# On cc0-foundation branch
git show 03cbd6b:THE_RESOURCES_TABLE.csv > /tmp/cc0_resources.csv

# On current main
git show origin/main:THE_RESOURCES_TABLE.csv > /tmp/current_resources.csv

# Find new entries (factual additions only)
comm -13 <(sort /tmp/cc0_resources.csv) <(sort /tmp/current_resources.csv)

Restore: Add new factual project entries to CSV

Phase 3: Restore Original @thedotmack Content

Action: Copy your original documentation files

Files to restore:

  • ✅ GATEKEEPING_ANALYSIS.md (your analysis)
  • ✅ GATEKEEPING_SUMMARY.md (your summary)
  • ✅ RESOLUTION.md (your resolution)
  • ✅ Any other docs you authored

Important: Do NOT restore any modified upstream files. Only restore files YOU created from scratch.

Phase 4: Apply CC0 License

Action: Keep LICENSE file as CC0 1.0 Universal

The LICENSE file at commit 03cbd6b already contains the full CC0 1.0 Universal text, which dedicates all content to the public domain. We maintain this license for maximum openness and consistency with the foundation.

Update pyproject.toml if needed:

[project]
license = {text = "CC0-1.0"}

Phase 5: Force Push

WARNING: This is destructive. Ensure you're ready.

# Verify you're on cc0-foundation
git checkout cc0-foundation

# Push to origin (this will be your new main)
git push -f origin cc0-foundation:main

# Or create new main branch
git branch -M main
git push -f origin main

Verification Checklist

Before force-pushing, verify:

  • Foundation commit is CC0 (03cbd6b)
  • All automation is from CC0 era
  • Only factual project data added (no copyrighted descriptions)
  • Only YOUR original documents included
  • No post-Sept-15 upstream modifications included
  • CC0 license maintained
  • CC0_FOUNDATION.md documentation present

Legal Position

This approach is legally sound because:

  1. CC0 Dedication is Irrevocable: Content released under CC0 remains public domain
  2. Facts Are Not Copyrightable: Project names, URLs, basic info can't be copyrighted
  3. Your Original Work: You own copyright to docs you created
  4. No Derivative from Restricted Content: We don't use post-Sept-15 upstream changes

Timeline

Completed:

  • ✅ Investigation of license history
  • ✅ Identification of CC0 commit
  • ✅ Creation of cc0-foundation branch
  • ✅ Legal documentation

Remaining:

  • ⏭️ Analyze and restore factual submissions
  • ⏭️ Restore your original documentation
  • ⏭️ Maintain CC0 license
  • ⏭️ Force push to remove post-CC0 content

Commands Reference

View CC0 License in Foundation

git show 03cbd6b:LICENSE | head -20

Compare Resource Lists

git diff 03cbd6b..origin/main THE_RESOURCES_TABLE.csv

List Your Original Files

git log --author="thedotmack" --name-only --oneline | grep -v "^[a-f0-9]"

Check Automation Files

git show 03cbd6b:.github/workflows/
git show 03cbd6b:scripts/

Status: Foundation established, ready for content restoration
Next: User to review plan and proceed with restoration steps
Timeline: Can be completed in 1-2 hours