Post B0rTuXbFee9FxmhSbI by gvwilson@mastodon.social
 (DIR) More posts by gvwilson@mastodon.social
 (DIR) Post #ArriGqu1pXJVncbEA4 by gvwilson@mastodon.social
       2025-03-08T20:18:46Z
       
       0 likes, 0 repeats
       
       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.
       
 (DIR) Post #ArriGrSlkN6RXMqyJM by tomjennings@tldr.nettime.org
       2025-03-09T03:19:51Z
       
       0 likes, 0 repeats
       
       @gvwilson When was all eggs in one basket a good idea? Never.
       
 (DIR) Post #B0rTuVloSPPMHxcrmi by jayalane@mastodon.online
       2025-03-08T21:48:59Z
       
       0 likes, 0 repeats
       
       @gvwilson should be pretty easy to do a filter tree script that would look at all PRs in a commit and then add a file to a new directory with the text of the PR panel and any associated issue panels, into the history. It is a mistake to have any important information not in or buildable from the source tree. Then just clone all your repos every so often.
       
 (DIR) Post #B0rTuXbFee9FxmhSbI by gvwilson@mastodon.social
       2025-03-08T22:24:56Z
       
       0 likes, 0 repeats
       
       @jayalane thank you - what I'm after right now is worked-out plans I can learn from (preferably ones that people have actually implemented and corrected) - a detailed checklist amended by experience would be great as well.
       
 (DIR) Post #B0rTuYXk9Aw6tC4Als by strypey@mastodon.nzoss.nz
       2025-12-03T05:27:45Z
       
       0 likes, 0 repeats
       
       (1/2)@gvwilson > what I'm after right now is worked-out plans I can learn fromFor what exactly? Choose one or more of;* Exporting a full org/ repo and all associated data from a forge* choosing a new forge* Importing those orgs/ repos into a forge* Local-first code collaboration using web forges only as dumb syncs (eg Nostr)* Federating projects across forges, so no one forge is a SPoFA few approaches have been tried for most of these.#ForgeFederation@jayalane
       
 (DIR) Post #B0rU1m3mI5A0pzUZGK by strypey@mastodon.nzoss.nz
       2025-12-03T05:29:07Z
       
       0 likes, 0 repeats
       
       (2/2)Appreciate the reference to SourceForge elsewhere in the thread. I think that's just the precedent folks need to be thinking about for the current enshittification of GritHub.