Implement Standardized Licensing Across Project Repositories

[Bana0615]

Title: Chore: Implement Standardized Licensing Across Project Repositories

Description:

• Problem/Goal: Our project repositories currently lack explicit LICENSE files, creating legal ambiguity for both our team and external developers viewing our code. The goal is to implement a clear, strategic licensing model across all projects to protect our intellectual property where necessary and encourage community engagement for portfolio pieces.
• Context/Background: Based on a recent analysis, we have decided on a tiered licensing strategy. The license for each project will depend on its primary goal—whether it's a core business asset, a simple portfolio piece, or a complex original game with commercial potential.
• Proposed Solution/Approach: We will audit and update our repositories according to the following guidelines:
  1. Main Websites & Game Hubs: These are proprietary business assets. They will remain "All Rights Reserved" by not including a license file and adding a copyright notice.
  2. Simple Arcade Games (e.g., Pong): These are portfolio pieces meant to showcase skills. They will be licensed under the permissive MIT License.
  3. Complex Original Games (e.g., Tower Defense): To protect potential commercial value, this will start as proprietary ("All Rights Reserved"). We can choose to apply a license later if we decide against commercialization.

Acceptance Criteria:

• For Main Website & Hub Repositories (onebuffalogames.com, etc.):
  • Verify that no LICENSE file exists in the repository root.
  • The README.md file contains the notice: Copyright © 2025 One Buffalo Labs. All Rights Reserved.
• For Simple Arcade Game Repositories (Pong, Snake, etc.):
  • A LICENSE file containing the full, standard text of the MIT License is present in the repository root.
• For the Complex Original Game Repository (Tower Defense):
  • Verify that no LICENSE file exists in the repository root at this time.
  • The README.md file contains the notice: Copyright © 2025 One Buffalo Labs. All Rights Reserved.

Labels: chore, legal, documentation, repo-management

Priority: High - Applying correct licenses is critical for protecting our intellectual property and setting clear expectations for our public-facing code.