Migrate Gitlab repositories #3

New issue

bitwise · 2025-12-26T18:30:54Z

bitwise commented

2025-12-26 18:30:54 +00:00

Forgejo as the Primary Coordination Source for CommunityCoins

The GitLab repository hub for CommunityCoins
(https://gitlab.com/c4319) was originally created in 2021 as a practical consolidation of two earlier efforts:

an intermediary based on Sandstorm (https://sandstorm.org), and
a previous GitLab setup (https://gitlab.com/Communitycoins1).

At the time, GitLab offered a convenient and accessible platform for collaboration. However, over the years it has become increasingly clear that long-term reliance on a single hosted platform introduces avoidable risks: platform lock-in, shifting policies, pricing changes, and potential external pressure.

To address this, we have decided to make a fresh start with Forgejo, a Git environment that is:

fully self-hostable,
open source by design,
easy to mirror, federate, and replicate by independent CommunityCoins teams,
and explicitly not dependent on a single commercial provider.

In doing so, we arrived at a principle that aligns well with open-source and decentralised development:

Host your own accomplishments as the primary source of truth,
and mirror them to well-established public hubs (GitLab, GitHub, etc.) for visibility and convenience.

This approach preserves:

autonomy and long-term continuity,
resilience against platform-level disruptions,
and broad discoverability for contributors and users.

Purpose of this issue

This issue serves as a reminder and coordination point to ensure that:

All relevant GitLab repositories are migrated to Forgejo as the primary source.
Backward mirroring is set up so that repositories remain visible on GitLab (and optionally GitHub).
Each CommunityCoins team mirrors repositories under its own domain or infrastructure, reinforcing decentralisation and shared ownership.

The goal is not to abandon existing platforms, but to invert the dependency:
Forgejo becomes the canonical coordination node, while external platforms function as mirrors and distribution channels.

This strengthens the CommunityCoins ecosystem as a whole and ensures that no single service becomes a point of failure — technically, organisationally, or politically.

## Forgejo as the Primary Coordination Source for CommunityCoins The GitLab repository hub for CommunityCoins (<https://gitlab.com/c4319>) was originally created in 2021 as a practical consolidation of two earlier efforts: - an intermediary based on Sandstorm (<https://sandstorm.org>), and - a previous GitLab setup (<https://gitlab.com/Communitycoins1>). At the time, GitLab offered a convenient and accessible platform for collaboration. However, over the years it has become increasingly clear that long-term reliance on a single hosted platform introduces avoidable risks: platform lock-in, shifting policies, pricing changes, and potential external pressure. To address this, we have decided to make a fresh start with **Forgejo**, a Git environment that is: - fully **self-hostable**, - **open source** by design, - easy to **mirror, federate, and replicate** by independent CommunityCoins teams, - and explicitly **not dependent on a single commercial provider**. In doing so, we arrived at a principle that aligns well with open-source and decentralised development: > **Host your own accomplishments as the primary source of truth, > and mirror them to well-established public hubs (GitLab, GitHub, etc.) for visibility and convenience.** This approach preserves: - autonomy and long-term continuity, - resilience against platform-level disruptions, - and broad discoverability for contributors and users. --- ## Purpose of this issue This issue serves as a reminder and coordination point to ensure that: 1. **All relevant GitLab repositories are migrated to Forgejo** as the primary source. 2. **Backward mirroring is set up** so that repositories remain visible on GitLab (and optionally GitHub). 3. **Each CommunityCoins team mirrors repositories under its own domain or infrastructure**, reinforcing decentralisation and shared ownership. The goal is not to abandon existing platforms, but to **invert the dependency**: Forgejo becomes the canonical coordination node, while external platforms function as mirrors and distribution channels. This strengthens the CommunityCoins ecosystem as a whole and ensures that no single service becomes a point of failure — technically, organisationally, or politically.

bitwise added this to the Communitycoins Overall Coordination project

2025-12-26 18:37:53 +00:00

bitwise pinned this

2025-12-26 18:49:58 +00:00

bitwise commented

2025-12-29 18:56:31 +00:00

The main repos are migrated:

Those that are actively maintained receive a mirror statement as part of the README.md document. This way visitors see that Gitlab is no longer the canonical source
A set of inactive project are put in the organisation (Archive)[https://git.communitycoins.org/Communitycoins.Archive]

What remains open is an effort to try to redistribute the library/hub contents to other communitycoins

The main repos are migrated: - Those that are actively maintained receive a mirror statement as part of the README.md document. This way visitors see that Gitlab is no longer the canonical source - A set of inactive project are put in the organisation (Archive)[https://git.communitycoins.org/Communitycoins.Archive] What remains open is an effort to try to redistribute the library/hub contents to other communitycoins

bitwise closed this issue

2025-12-29 18:56:32 +00:00

bitwise changed title from ~~Migrate Gitlab repositories and redistribute~~ to Migrate Gitlab repositories

2026-01-01 14:01:04 +00:00

Sign in to join this conversation.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Communitycoins.Rooty/README#3

Rows
Columns