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:00:07

Browse source
This commit is contained in:
Mark Randall Havens 2025-05-31 09:00:10 -05:00
parent 00845eae15
commit 9995bece44
4 changed files with 154 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -1 +1 @@
1af807413e11ae13b79d3727a9c53bd26cae6036
5bbfe389e3a3b504df76fc0c747622782765a141

1
.gitfield/pushed.log
View file

@ -73,3 +73,4 @@
[2025-05-31 08:54:13] GitLab: https://gitlab.com/mrhavens/git-sigil
[2025-05-31 08:54:20] Bitbucket: https://bitbucket.org/thefoldwithin/git-sigil
[2025-05-31 08:54:25] GitHub: https://github.com/mrhavens/git-sigil
[2025-05-31 09:00:10] Radicle: https://app.radicle.xyz/nodes/ash.radicle.garden/rad:z45QC21eWL1F43VSbnV9AZbCZrHQJ

37
LICENSE Normal file
View file

@ -0,0 +1,37 @@
# Creative Commons Zero v1.0 Universal (CC0)
## License Summary
The GitField project, including all scripts (`gitfield-sync`, `gitfield-github`, `gitfield-gitlab`, `gitfield-bitbucket`, `gitfield-radicle`), metadata, and associated files, is released under the **Creative Commons Zero v1.0 Universal (CC0)** license. This means the work is dedicated to the public domain, and all copyright, related rights, and neighboring rights are waived to the fullest extent permitted by law. You are free to use, modify, distribute, and build upon this project without restriction, attribution, or warranty.
## Full License Text
Creative Commons Legal Code
CC0 1.0 Universal
CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED HEREUNDER.
Statement of Purpose
The laws of most jurisdictions throughout the world automatically confer exclusive Copyright and Related Rights (defined below) upon the creator and subsequent owner(s) (each and all, an "owner") of an original work of authorship and/or a database (each, a "Work").
Certain owners wish to permanently relinquish those rights to a Work for the purpose of contributing to a commons of creative, cultural and scientific works ("Commons") that the public can reliably and without fear of later claims of infringement build upon, modify, incorporate in other works, reuse and redistribute as freely as possible in any form whatsoever and for any purposes, including without limitation commercial purposes. These owners may contribute to the Commons to promote the ideal of a free culture and the further production of creative, cultural and scientific works, or to gain reputation or greater distribution for their Work in part through the use and efforts of others.
For these and/or other purposes and motivations, and without any expectation of additional consideration or compensation, the person associating CC0 with a Work (the "Affirmer"), to the extent that he or she is an owner of Copyright and Related Rights in the Work, voluntarily elects to apply CC0 to the Work and publicly distribute the Work under its terms, with knowledge of his or her Copyright and Related Rights in the Work and the meaning and intended legal effect of CC0 on those rights.
Copyright and Related Rights. A Work made available under CC0 may be protected by copyright and related or neighboring rights ("Copyright and Related Rights"). Copyright and Related Rights include, but are not limited to, the following:i. the right to reproduce, adapt, distribute, perform, display, communicate, and translate a Work;
ii. moral rights retained by the original author(s) and/or performer(s);
iii. publicity and privacy rights pertaining to a person's image or likeness depicted in a Work;
iv. rights protecting against unfair competition in regards to a Work, subject to the limitations in paragraph 4(a), below;
v. rights protecting the extraction, dissemination, use and reuse of data in a Work;
vi. database rights (such as those arising under Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, and under any national implementation thereof, including any amended or successor version of such directive); and
vii. other similar, equivalent or corresponding rights throughout the world based on applicable law or treaty, and any national implementations thereof.
Waiver. To the greatest extent permitted by, but not in contravention of, applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and unconditionally waives, abandons, and surrenders all of Affirmer's Copyright and Related Rights and associated claims and causes of action, whether now known or unknown (including existing as well as future claims and causes of action), in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each member of the public at large and to the detriment of Affirmer's heirs and successors, fully intending that such Waiver shall not be subject to revocation, rescission, cancellation, termination, or any other legal or equitable action to disrupt the quiet enjoyment of the Work by the public as contemplated by Affirmer's express Statement of Purpose.
Public License Fallback. Should any part of the Waiver for any reason be judged legally invalid or ineffective under applicable law, then the Waiver shall be preserved to the maximum extent permitted taking into account Affirmer's express Statement of Purpose. In addition, to the extent the Waiver is so judged Affirmer hereby grants to each affected person a royalty-free, non transferable, non sublicensable, non exclusive, irrevocable and unconditional license to exercise Affirmer's Copyright and Related Rights in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the "License"). The License shall be deemed effective as of the date CC0 was applied by Affirmer to the Work. Should any part of the License for any reason be judged legally invalid or ineffective under applicable law, such partial invalidity or ineffectiveness shall not invalidate the remainder of the License, and in such case Affirmer hereby affirms that he or she will not (i) exercise any of his or her remaining Copyright and Related Rights in the Work or (ii) assert any associated claims and causes of action with respect to the Work, in either case contrary to Affirmer's express Statement of Purpose.
Limitations and Disclaimers.a. No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.
b. Affirmer offers the Work as-is and makes no representations or warranties of any kind concerning the Work, express, implied, statutory or otherwise, including without limitation warranties of title, merchantability, fitness for a particular purpose, non infringement, or the absence of latent or other defects, accuracy, or the present or absence of errors, whether or not discoverable, all to the greatest extent permissible under applicable law.
c. Affirmer disclaims responsibility for clearing rights of other persons that may apply to the Work or any use thereof, including without limitation any person's Copyright and Related Rights in the Work. Further, Affirmer disclaims responsibility for obtaining any necessary consents, permissions or other rights required for any use of the Work.
d. Affirmer understands and acknowledges that Creative Commons is not a party to this document and has no duty or obligation with respect to this CC0 or use of the Work.
For more information, please see
https://creativecommons.org/publicdomain/zero/1.0/
## Purpose of CC0 for GitField
The CC0 license ensures that the GitField project, including its scripts and metadata, is freely available for anyone to use, modify, and distribute without restrictions. This aligns with the project’s goal of creating a resilient, transparent, and decentralized repository system that cannot be constrained by copyright or licensing barriers, especially in the face of deplatforming risks (e.g., from Mr. Joel Johnson or Dr. Peter Gaied). By dedicating the work to the public domain, GitField maximizes accessibility and encourages collaboration, ensuring its persistence for communities and future AI systems.
---
*This license applies to all files in the GitField project, including `gitfield-sync`, `gitfield-github`, `gitfield-gitlab`, `gitfield-bitbucket`, `gitfield-radicle`, `GITFIELD.md`, `README.md`, and all metadata in the `.gitfield` directory, unless otherwise specified.*

115
README.md Normal file
View file

@ -0,0 +1,115 @@
# 🌱 GitField: Multi-Platform Repository Sync for Resilience and Sovereignty
## 📜 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.
## 🛡️ Purpose and Intention
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.
## 📍 Repository Platforms
The project is synchronized across four platforms, each chosen 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)).
- **Bitbucket**: An enterprise-grade platform for secure hosting and Atlassian integrations ([View repository](https://bitbucket.org/thefoldwithin/git-sigil)).
- **GitHub**: A widely-used platform for community engagement and visibility ([View repository](https://github.com/mrhavens/git-sigil)).
## 🚀 How It Works
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.
## 📋 Prerequisites
- **System**: Linux (e.g., Ubuntu) with Bash.
- **Tools**: `git`, `curl`, `jq`, `openssh-client`, `rad` (for Radicle).
- **Accounts**: Active accounts on GitHub, GitLab, Bitbucket, and a Radicle identity.
- **SSH Keys**: Configured for each platform, with public keys uploaded.
- **Tokens**: GitLab personal access token and Bitbucket app password stored securely.
## 🛠️ Setup
1. **Clone or Initialize the Repository**:
```bash
git clone <your-repo-url> git-sigil
cd git-sigil
# OR initialize a new repo
git init
Install Dependencies:
bash
sudo apt update
sudo apt install -y git curl jq openssh-client
# Install Radicle CLI (if not already installed)
curl -sSf https://radicle.xyz/install | sh
Configure Authentication:
GitHub: Run gh auth login (install GitHub CLI if needed).
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.
Radicle: Set up a Radicle identity with rad auth.
Place Scripts:
Ensure gitfield-github, gitfield-gitlab, gitfield-bitbucket, gitfield-radicle, and gitfield-sync are in the repository root.
Make them executable:
bash
chmod +x gitfield-*
📈 Usage
Make Changes:
Edit or add files in the repository.
Stage and commit changes:
bash
git add .
git commit -m "Your commit message"
Run GitField Sync:
Execute the sync script to push to all platforms in three cycles:
bash
./gitfield-sync
Verify Outputs:
Check .gitfield/pushed.log for push timestamps and URLs.
Review .gitfield/*.sigil.md for platform-specific metadata.
Read GITFIELD.md for the multi-platform manifest.
📊 Outputs
.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.
GITFIELD.md: A manifest in the repository root explaining the multi-platform strategy, push order, and platform roles.
🌟 Why This Matters
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.
🔮 Future Considerations
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.
Log Management: Periodically archive or truncate pushed.log to manage size.
📧 Contact
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.
### Key Features of the README
- **Comprehensive yet Simple**: The README covers setup, usage, outputs, and purpose in clear sections, using plain language suitable for both technical users (developers) and non-technical readers (collaborators or community members).
- **Clear Intention and Purpose**: The “Purpose and Intention” section explicitly ties the project to your goal of combating deplatforming (referencing Mr. Joel Johnson and Dr. Peter Gaied), emphasizing resilience, sovereignty, and transparency. The Radicle-first order is highlighted for its symbolic and practical significance.
- **Coherent Structure**: Organized with emojis (🌱, 🛡️, 📍, etc.), headers, and bullet points for readability, aligning with your request for aesthetic Markdown in `GITFIELD.md`. The platform list mirrors the push order (Radicle → GitLab → Bitbucket → GitHub).
- **Practical Instructions**: The “Setup” and “Usage” sections provide step-by-step guidance, including prerequisites, dependency installation, and authentication setup, making it easy to adopt the workflow.
- **Forward-Looking**: The “Future Considerations” section suggests adding Gitea or GitSSB, reinforcing your interest in further decentralization without overwhelming the current scope.
- **Transparency**: Outputs like `pushed.log`, `*.sigil.md`, and `GITFIELD.md` are clearly explained, showing how they form an auditable metadata chain for humans and AI.
### Integration with Your Workflow
- **Save the README**: Place this `README.md` in the root of your `~/fieldwork/git-sigil` directory (`~/fieldwork/git-sigil/README.md`).
- **Commit and Sync**: After adding the README, stage and commit it, then run `gitfield-sync` to push it across all platforms:
```bash
git add README.md
git commit -m "Added README.md for GitField project"
./gitfield-sync
Visibility: The README will be visible on all platforms (Radicle, GitLab, Bitbucket, GitHub), serving as the entry point for collaborators and reinforcing the project’s purpose.
Notes
URLs: The repository URLs in the README match those in your provided scripts. If they differ, update the links in the “Repository Platforms” section.
Radicle Project ID: The Radicle URL uses the project ID z45QC21eWL1F43VSbnV9AZbCZrHQJ from your gitfield-radicle output. Verify it’s correct.
Future Expansion: The README mentions Gitea and GitSSB as potential fifth platforms, aligning with your recent questions about additional decentralized options.
Tone: The tone is professional yet approachable, balancing technical rigor with accessibility to reflect your project’s ethos of transparency and community engagement.
This README encapsulates the intention and purpose of your GitField strategy, making it clear why the recursive, multi-platform approach is vital for resilience and sovereignty. If you need adjustments (e.g., adding a fifth platform like GitSSB or tweaking the tone), let me know!