Conversation

Notices

1. Embed this notice
   Greg Wilson (gvwilson@mastodon.social)'s status on Sunday, 09-Mar-2025 06:37:21 JST Greg Wilson

   Q for research friends: have you started planning what to do if the US gov't suddenly restricts access to GitHub? Could happen in several ways, e.g., Microsoft has to filter DEI content to stay eligible for federal contracts or a "nothing Ukrainian" rule, but the mechanism doesn't matter: what does it that it's no longer impossible. Yes, you have a clone of your repo, but not of your issues, and how will you reconnect with contributors? If you have a plan, please share a link - thx.

   • Blaise Pabón - controlpl4n3 repeated this.
   • Embed this notice
     Blaise Pabón - controlpl4n3 (blaise@hachyderm.io)'s status on Sunday, 09-Mar-2025 06:37:21 JST Blaise Pabón - controlpl4n3

     in reply to

     @gvwilson
     Over in the #Tahoe_LAFS project we've been discussing this for the past year.
     Findings:
     - it's very easy to devolve into bike shedding.
     - it's a multi stakeholder situation, so high level user stories are helpful ("as a maintainer, I expect to update CI flows and credentials")
     - consider separating version control from issue tracking (I like Gerrit but did not prevail)
     - codeberg.org is practically a drop in replacement for GitHub.

   • Embed this notice
     Eric Jelli (ericjelli02@academiccloud.social)'s status on Sunday, 09-Mar-2025 06:38:09 JST Eric Jelli

     in reply to

     @gvwilson
     I have not tested it yet, but there are already ideas around on how to mirror GitHub repositories in #codeberg:
     - https://codeberg.org/Recommendations/Mirror_to_Codeberg/src/branch/dev/README.md
     - https://codeberg.org/wl/GithubCodebergMirror

   • Embed this notice
     Greg Wilson (gvwilson@mastodon.social)'s status on Sunday, 09-Mar-2025 06:39:39 JST Greg Wilson

     in reply to

     • Eric Jelli

     @ericjelli02 Thanks for the links - there are several options, but my question is "who has actually started making a plan and trying things out" ? If we wait until we need it, we're going to have a repeat of our near-miss with SourceForge (almost) going offline, and as recent events have shown, even a partial unplanned interruption of collaboration can take a long time to recover from.

   • Embed this notice
     Blaise Pabón - controlpl4n3 (blaise@hachyderm.io)'s status on Sunday, 09-Mar-2025 06:45:20 JST Blaise Pabón - controlpl4n3

     in reply to

     • Leonardo Uieda
     • b3n
     • Fatiando a Terra

     @leouieda @gvwilson @fatiando
     Yes, issues, PR and discussions are harder to sync...

     ( Hey @b3n , Maybe it's worth building a bit of automation and hosting it somewhere?)

   • Embed this notice
     Leonardo Uieda (leouieda@bertha.social)'s status on Sunday, 09-Mar-2025 06:45:22 JST Leonardo Uieda

     in reply to

     • Fatiando a Terra

     @gvwilson the core team of @fatiando and my lab have been chatting. Current plan is to try to mirror on Codeberg. First trying to just sync the repo content but issues and PRs are harder to sync. We use templates and referencing issues etc will likely break in the mirror. We're expecting some loss of information and trouble setting things up. Once we have a functional mirror, we could move there but it's not worth mirroring the organization fully until we commit to a migration.