mrhavens/git-sigil
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Post-Radicle sync at 2025-05-31 09:14:41

Browse source
This commit is contained in:
Mark Randall Havens 2025-05-31 09:14:44 -05:00
parent 7a9aa239b7
commit 123b844e1d
4 changed files with 86 additions and 69 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.gitfield/.radicle-push-state
View file

@ -1 +1 @@
f090d0dae6fa658586840fa67140c651e0fedc79 c659d18b627e4eaa263e81f12e3cf9fdd0b28ff2

1
.gitfield/pushed.log
View file

@ -97,3 +97,4 @@
[2025-05-31 09:03:03] GitLab: https://gitlab.com/mrhavens/git-sigil [2025-05-31 09:03:03] GitLab: https://gitlab.com/mrhavens/git-sigil
[2025-05-31 09:03:10] Bitbucket: https://bitbucket.org/thefoldwithin/git-sigil [2025-05-31 09:03:10] Bitbucket: https://bitbucket.org/thefoldwithin/git-sigil
[2025-05-31 09:03:15] GitHub: https://github.com/mrhavens/git-sigil [2025-05-31 09:03:15] GitHub: https://github.com/mrhavens/git-sigil
[2025-05-31 09:14:44] Radicle: https://app.radicle.xyz/nodes/ash.radicle.garden/rad:z45QC21eWL1F43VSbnV9AZbCZrHQJ

0
LICENSE → LICENSE.md
View file

152
README.md
View file

@ -2,91 +2,107 @@
## 📜 Overview ## 📜 Overview
**GitField** is a set of Bash scripts designed to synchronize a Git repository across multiple platforms—**Radicle**, **GitLab**, **Bitbucket**, and **GitHub**—in a recursive, metadata-rich workflow. This project ensures **redundancy**, **sovereignty**, and **transparency** by creating interconnected metadata snapshots and distributing them across decentralized and centralized platforms. The strategy protects against deplatforming risks, inspired by past attempts to suppress this work by individuals like **Mr. Joel Johnson** ([Mirror post](https://mirror.xyz/neutralizingnarcissism.eth/x40_zDWWrYOJ7nh8Y0fk06_3kNEP0KteSSRjPmXkiGg?utm_medium=social&utm_source=heylink.me)) and **Dr. Peter Gaied** ([Paragraph post](https://paragraph.com/@neutralizingnarcissism/%F0%9F%9C%81-the-narcissistic-messiah)). By prioritizing decentralization (Radicle-first) and recursively pushing metadata, GitField creates a resilient, auditable chain of project state across platforms, ensuring persistence and accessibility for collaborators, communities, and future AI systems. **GitField** is a collection of Bash scripts designed to synchronize a Git repository across **Radicle**, **GitLab**, **Bitbucket**, and **GitHub** using a recursive, metadata-rich workflow. This project ensures **redundancy**, **sovereignty**, and **transparency** by generating interconnected metadata snapshots and distributing them across decentralized and centralized platforms. The strategy protects against deplatforming risks, motivated by past attempts to suppress this work by individuals such as **Mr. Joel Johnson** ([Mirror post](https://mirror.xyz/neutralizingnarcissism.eth/x40_zDWWrYOJ7nh8Y0fk06_3kNEP0KteSSRjPmXkiGg?utm_medium=social&utm_source=heylink.me)) and **Dr. Peter Gaied** ([Paragraph post](https://paragraph.com/@neutralizingnarcissism/%F0%9F%9C%81-the-narcissistic-messiah)). By prioritizing decentralization with a Radicle-first approach and recursively pushing metadata, GitField creates a resilient, auditable chain of project state, ensuring persistence and accessibility for collaborators, communities, and future AI systems.
## 🛡️ Purpose and Intention ## 🛡️ Purpose and Intention
The GitField project is driven by three core principles: The GitField project is driven by three core principles:
1. **Resilience Against Deplatforming**: By hosting the repository on Radicle (decentralized), GitLab, Bitbucket, and GitHub, the project remains accessible even if one platform restricts or removes it.
2. **Sovereignty Through Decentralization**: Starting with Radicle, a peer-to-peer Git platform, ensures the project’s data is independent of centralized control, safeguarding its integrity.
3. **Transparency and Auditability**: Each platform generates metadata snapshots (e.g., `radicle.sigil.md`) stored in the `.gitfield` directory, with a push log (`pushed.log`) and a manifest (`GITFIELD.md`) documenting the sync process, commit details, and platform roles.
This approach creates a robust, interconnected metadata chain that future collaborators and AI systems can analyze to verify the project’s state and history, reinforcing its role as a stable anchor in the field of distributed version control. - **Resilience Against Deplatforming**: Hosting the repository on Radicle (decentralized), GitLab, Bitbucket, and GitHub ensures the project remains accessible even if one platform restricts or removes it.
- **Sovereignty Through Decentralization**: Starting with Radicle, a peer-to-peer Git platform, guarantees data independence from centralized control, safeguarding integrity.
- **Transparency and Auditability**: Platform-specific metadata snapshots (e.g., radicle.sigil.md) in the .gitfield directory, a push log (pushed.log), and a manifest (GITFIELD.md) document the sync process, commit details, and platform roles, creating a verifiable record.
This recursive approach builds a dynamic metadata chain, making the project a robust anchor for distributed version control, resilient to censorship, and transparent for analysis by humans and AI.
## 📍 Repository Platforms ## 📍 Repository Platforms
The project is synchronized across four platforms, each chosen for its unique strengths: The project is synchronized across four platforms, each selected for its unique strengths:
- **Radicle**: A decentralized, peer-to-peer Git platform for censorship resistance and sovereignty ([View repository](https://app.radicle.xyz/nodes/ash.radicle.garden/rad:z45QC21eWL1F43VSbnV9AZbCZrHQJ)).
- **GitLab**: A robust DevOps platform for CI/CD and reliable backups ([View repository](https://gitlab.com/mrhavens/git-sigil)). 1. **Radicle**
- **Bitbucket**: An enterprise-grade platform for secure hosting and Atlassian integrations ([View repository](https://bitbucket.org/thefoldwithin/git-sigil)). - **URL**: [https://app.radicle.xyz/nodes/ash.radicle.garden/rad:z45QC21eWL1F43VSbnV9AZbCZrHQJ](https://app.radicle.xyz/nodes/ash.radicle.garden/rad:z45QC21eWL1F43VSbnV9AZbCZrHQJ)
- **GitHub**: A widely-used platform for community engagement and visibility ([View repository](https://github.com/mrhavens/git-sigil)). - **Purpose**: A decentralized, peer-to-peer Git platform ensuring censorship resistance and sovereignty.
- **Value**: Eliminates reliance on centralized servers, protecting against deplatforming.
2. **GitLab**
- **URL**: [https://gitlab.com/mrhavens/git-sigil](https://gitlab.com/mrhavens/git-sigil)
- **Purpose**: A robust DevOps platform for CI/CD and reliable backups.
- **Value**: Enhances resilience with integrated pipelines and independent infrastructure.
3. **Bitbucket**
- **URL**: [https://bitbucket.org/thefoldwithin/git-sigil](https://bitbucket.org/thefoldwithin/git-sigil)
- **Purpose**: A secure platform with Atlassian ecosystem integrations for additional redundancy.
- **Value**: Offers enterprise-grade security, ensuring accessibility during disruptions.
4. **GitHub**
- **URL**: [https://github.com/mrhavens/git-sigil](https://github.com/mrhavens/git-sigil)
- **Purpose**: A widely-used platform for community engagement and visibility.
- **Value**: Facilitates open-source collaboration, issue tracking, and broad accessibility.
## 🚀 How It Works ## 🚀 How It Works
The `gitfield-sync` script orchestrates a three-cycle push process in the order **Radicle → GitLab → Bitbucket → GitHub**: The gitfield-sync script orchestrates a three-cycle push process in the order **Radicle -> GitLab -> Bitbucket -> GitHub**:
1. **Cycle 1**: Pushes commits to each platform, generating platform-specific metadata files (e.g., `.gitfield/radicle.sigil.md`) with commit details, environment data, and hardware fingerprints.
2. **Cycle 2**: Generates `GITFIELD.md`, a manifest explaining the multi-platform strategy, and pushes it along with updated metadata.
3. **Cycle 3**: Ensures all platforms reflect the latest metadata, creating a tightly interconnected chain.
Each push is logged in `.gitfield/pushed.log` with timestamps and URLs, providing a transparent audit trail. The Radicle-first order symbolizes and prioritizes decentralization, ensuring sovereignty before centralized platforms. 1. **Cycle 1**: Pushes commits to each platform, generating metadata files (e.g., .gitfield/radicle.sigil.md) with commit SHAs, timestamps, environment data, and hardware fingerprints.
2. **Cycle 2**: Creates GITFIELD.md, a manifest detailing the multi-platform strategy, and pushes it with updated metadata.
3. **Cycle 3**: Ensures all platforms reflect the latest metadata, forming a tightly interconnected chain.
Each push is logged in .gitfield/pushed.log with timestamps and URLs. The Radicle-first order prioritizes decentralization, ensuring sovereignty before centralized platforms, enhancing both symbolic and practical resilience.
## 📋 Prerequisites ## 📋 Prerequisites
- **System**: Linux (e.g., Ubuntu) with Bash. - **System**: Linux (e.g., Ubuntu) with Bash.
- **Tools**: `git`, `curl`, `jq`, `openssh-client`, `rad` (for Radicle). - **Tools**: git, curl, jq, openssh-client, rad (for Radicle).
- **Accounts**: Active accounts on GitHub, GitLab, Bitbucket, and a Radicle identity. - **Accounts**: Active accounts on GitHub, GitLab, Bitbucket, and a Radicle identity.
- **SSH Keys**: Configured for each platform, with public keys uploaded. - **SSH Keys**: Configured and uploaded to each platform.
- **Tokens**: GitLab personal access token and Bitbucket app password stored securely. - **Tokens**: GitLab personal access token (api, read_user, write_repository, write_ssh_key scopes) and Bitbucket app password (repo:admin, write, webhook scopes).
## 🛠️ Setup ## 🛠️ Setup
1. **Clone or Initialize the Repository**: 1. **Clone or Initialize Repository**:
```bash To clone the repository, run: git clone https://github.com/mrhavens/git-sigil.git, then navigate with: cd git-sigil. Alternatively, initialize a new repository by running: git init.
git clone <your-repo-url> git-sigil
cd git-sigil 2. **Install Dependencies**:
# OR initialize a new repo Update your package list with: sudo apt update, then install required tools: sudo apt install -y git curl jq openssh-client. For Radicle, install the CLI using: curl -sSf https://radicle.xyz/install | sh.
git init
Install Dependencies: 3. **Configure Authentication**:
bash - **GitHub**: Authenticate with: gh auth login (install GitHub CLI if needed).
sudo apt update - **GitLab**: Generate a token at GitLab settings: https://gitlab.com/-/user_settings/personal_access_tokens.
sudo apt install -y git curl jq openssh-client - **Bitbucket**: Create an app password at Bitbucket settings: https://bitbucket.org/account/settings/app-passwords/.
# Install Radicle CLI (if not already installed) - **Radicle**: Set up an identity with: rad auth.
curl -sSf https://radicle.xyz/install | sh
Configure Authentication: 4. **Place Scripts**:
GitHub: Run gh auth login (install GitHub CLI if needed). Ensure gitfield-github, gitfield-gitlab, gitfield-bitbucket, gitfield-radicle, and gitfield-sync are in the repository root. Make them executable by running: chmod +x gitfield-*.
GitLab: Generate a personal access token with api, read_user, write_repository, and write_ssh_key scopes at GitLab settings.
Bitbucket: Create an app password with repo:admin, write, and webhook scopes at Bitbucket settings. ## 📈 Usage
Radicle: Set up a Radicle identity with rad auth.
Place Scripts: 1. **Make Changes**:
Ensure gitfield-github, gitfield-gitlab, gitfield-bitbucket, gitfield-radicle, and gitfield-sync are in the repository root. Edit or add files, then stage and commit changes by running: git add . followed by: git commit -m "Your commit message".
Make them executable:
bash 2. **Run GitField Sync**:
chmod +x gitfield-* Execute the sync script by running: ./gitfield-sync.
📈 Usage
Make Changes: 3. **Verify Outputs**:
Edit or add files in the repository. - **Push Log**: Check .gitfield/pushed.log for timestamps and URLs.
Stage and commit changes: - **Metadata Files**: Review .gitfield/*.sigil.md for platform-specific details.
bash - **Manifest**: Read GITFIELD.md for the multi-platform strategy.
git add .
git commit -m "Your commit message" ## 📊 Outputs
Run GitField Sync:
Execute the sync script to push to all platforms in three cycles: - **.gitfield/pushed.log**: Logs pushes (e.g., [2025-05-31 09:10:00] Radicle: https://app.radicle.xyz/...).
bash - **.gitfield/*.sigil.md**: Metadata snapshots with commit details, environment, and hardware info.
./gitfield-sync - **GITFIELD.md**: A manifest explaining the strategy, push order, and platform roles.
Verify Outputs: - **LICENSE**: CC0 license, dedicating the project to the public domain for maximum accessibility.
Check .gitfield/pushed.log for push timestamps and URLs.
Review .gitfield/*.sigil.md for platform-specific metadata. ## 🌟 Why This Matters
Read GITFIELD.md for the multi-platform manifest.
📊 Outputs GitField's recursive, multi-platform approach is a novel solution to deplatforming risks, ensuring the project's persistence through a Radicle-first, decentralized foundation. The metadata chain, documented in pushed.log and GITFIELD.md, provides transparency and auditability, appealing to developers, communities, and AI systems analyzing the project's integrity and intent. This strategy positions GitField as a resilient anchor for distributed version control.
.gitfield/pushed.log: Logs each push with timestamp and URL (e.g., [2025-05-31 08:00:00] Radicle: https://app.radicle.xyz/...).
.gitfield/*.sigil.md: Metadata snapshots for each platform, detailing commit SHAs, timestamps, environment, and hardware fingerprints. ## 🔮 Future Considerations
GITFIELD.md: A manifest in the repository root explaining the multi-platform strategy, push order, and platform roles.
🌟 Why This Matters - **Fifth Platform**: Explore **Gitea** (self-hosted) or **GitSSB** (decentralized) for added sovereignty.
GitField’s recursive, multi-platform approach is a novel response to the risks of deplatforming, ensuring your project remains accessible and verifiable. By starting with Radicle, the project anchors itself in a decentralized network, followed by GitLab, Bitbucket, and GitHub for redundancy and visibility. This strategy creates a resilient, transparent foundation for collaboration, appealing to developers, communities, and future AI systems analyzing the project’s metadata for integrity and intent. - **Automation**: Use GitLab CI/CD to automate gitfield-sync.
🔮 Future Considerations - **Log Management**: Archive pushed.log periodically to manage size.
Adding a Fifth Platform: Consider integrating Gitea (self-hosted) or GitSSB (decentralized) for additional redundancy and sovereignty.
Automation: Set up CI/CD pipelines (e.g., on GitLab) to automate gitfield-sync runs. ## 📧 Contact
Log Management: Periodically archive or truncate pushed.log to manage size.
📧 Contact For questions or contributions, contact **Mark Randall Havens** (mark.r.havens@gmail.com) or open an issue on any platform.
For questions or contributions, reach out to Mark Randall Havens (mark.r.havens@gmail.com) or open an issue on any of the repository platforms.
Auto-generated content managed by gitfield-sync (v1.0). Last updated: May 31, 2025.