Skip to content

Rebrand Migration: NighthawkCodingSociety -> OpenCodingSociety  #21

@Flying-Book

Description

@Flying-Book

Overview

We're officially rebranding NighthawkCodingSociety to OpenCodingSociety. This change affects all codebases, configuration files, deployments, and documentation.

Goal
Ensure a complete, atomic migration to the new branding with:

  • No lingering static references
  • No broken links, builds, or services
  • Consistent naming across all environments and documentation

Task List (ETA: July 10th) - Risha and Nolan

1. Audit and Identify All Static References

  • Search for all instances of nighthawkcodingsociety or similar variants in:
    • Code (URLs, fetch calls, environment variables)
    • Config files (.env, docker-compose.yml, YAMLs, etc.)
    • CI/CD workflows (GitHub Actions, Jenkins, etc.)
    • Markdown files and documentation
    • Frontend UI (titles, branding, footers)
  • Create a report listing:
    • Repository name
    • File path(s)
    • Line numbers (if possible)
    • Current value
    • Suggested replacement

2. DockerHub & Container Update (Do this together on call) - Everyone

  • Rename or re-publish Docker images under the opencodingsociety namespace
  • Update all references to old images in:
    • docker-compose.yml
    • GitHub Actions

3. Registry Server & DNS (Do this together on call) - Everyone

  • Update any static URLs pointing to internal/external registries or services (e.g., Docker registry, API gateway, custom services)
  • Replace all DNS and domain references (e.g., *.nighthawkcodingsociety.com) with new *.opencodingsociety.com
  • Remove all deprecated DNS entries

4. Workspace, Folder, and Naming Conventions (Do this together on call)

  • Rename relevant folders, namespaces, or workspace identifiers
  • Refactor internal scripts/tools that rely on static names

5. Documentation & Branding (ETA: July 14th) - Risha and Nolan

  • Update with help of ChatGPT:
    • README.md, CONTRIBUTING.md, docs/
    • Diagrams and logos
    • Public descriptions (GitHub org, DockerHub, etc.)
  • Write a changelog or section in the README that documents the rebranding

Scheduled Main Change Call: TBD

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions