[HN Gopher] Organic Maps migrates to Forgejo due to GitHub accou...
       ___________________________________________________________________
        
       Organic Maps migrates to Forgejo due to GitHub account blocked by
       Microsoft
        
       Author : mraniki
       Score  : 94 points
       Date   : 2025-03-30 16:32 UTC (6 hours ago)
        
 (HTM) web link (mastodon.social)
 (TXT) w3m dump (mastodon.social)
        
       | mraniki wrote:
       | Why blocked? > We have a temporary glitch with GitHub--probably
       | some contributor was geolocated in a sanctioned region (no
       | details yet). All required documents to unlock the account have
       | been uploaded. Don't blame Microsoft/GitHub - it is just U.S.
       | law. Please be patient. It should be unblocked soon.
       | 
       | https://mastodon.social/@organicmaps/114155428924741370
        
         | tomrod wrote:
         | > the account have been uploaded. Don't blame Microsoft/GitHub
         | - it is just U.S. law.
         | 
         | "I was just following orders" is an invalid defense.
        
           | throwawaymaths wrote:
           | i mean ok but no one is being killed or tortured or even
           | kidnapped here.
        
             | bauruine wrote:
             | I think it's not bad to remember people from time to time
             | that "just following orders" oder "Just doing my job" isn't
             | an universal excuse and that we hanged people rightfully
             | for "just" doing that. If that's your only excuse for what
             | you're doing you may should at least deeply think again if
             | what you're doing is excusable.
             | 
             | They only want to protect MS in this case, I guess to
             | increase their chance to resolve it positively.
             | 
             | But I just recently thought about this. If you develop
             | exploits for say NSO und a journalist gets tortured to
             | death. Should you be put on trial? I'm not sure why not
             | tbh.
        
             | doublerabbit wrote:
             | > no one is being killed or tortured or even kidnapped
             | here.
             | 
             | Maybe not but the vibe feels more like open source being
             | gunpoint.
             | 
             | "Upload documents or else"
        
           | FirmwareBurner wrote:
           | So a corporation should be in contempt with US law just to
           | uphold a moral high ground for a some random user?
        
             | mcv wrote:
             | Sounds like another reason not to repy on US-based
             | services.
        
         | throw_a_grenade wrote:
         | > Don't blame Microsoft/GitHub
         | 
         | I don't think this is a question of blame, rather than
         | suitability. In the spirit of blameless postmortem, I'll state
         | that GitHub was found unsuitable for hosting a FOSS project.
         | 
         | Why it's unsuitable is truly a secondary question, but it
         | shouldn't prevent us, Free Software maintainers, from drawing
         | necessary conclusions.
        
         | happymellon wrote:
         | Sounds like a reasonable reason to dump a service that will
         | just block you.
         | 
         | Nothing you put there sounds like a reason not to move, in fact
         | it sounds like all the more reason to do it.
        
           | FirmwareBurner wrote:
           | _> Sounds like a reasonable reason to dump a service that
           | will just block you. _
           | 
           | ANY and I mean absolutely ANY service can just block you if
           | they think you're violating ToS, including Google/Android and
           | Apple.
        
         | zamalek wrote:
         | > it is just <country> law
         | 
         | Ah, a chief among the causes of brain drain.
        
       | anonym29 wrote:
       | Glad to see more and more organizations moving to rights-
       | respecting platforms, away from the intelligence community's
       | surveillance + social control dragnets of choice.
        
       | sschueller wrote:
       | I didn't know forgejo existed and I have been using gitlab ce
       | which is getting more and more difficult to deal with for just
       | home use. All of a sudden I see that I am no longer getting minor
       | updates because my debian version isn't the latest and during my
       | last update it broke the db again.
       | 
       | forgejo seems to have everything I need including CI pipeline and
       | container registry so I am definitely going to give it a try
       | before trying to update gitlab.
        
         | omnimus wrote:
         | It's also way easier than Gitlab to selfhost. Been running it
         | for some time on small office NAS and it's solid.
        
         | jalict wrote:
         | Switched from Gitlab to Forgejo at work and it is working
         | fantastic for us. I am also using at home.
         | 
         | Using both container registry and self-hosted runners, etc.
         | 
         | I was personally very frustrated with ACL and generally
         | inheritance rules in gitlab and it is much more sensible and
         | easy in Forgejo.
        
         | dizhn wrote:
         | FYI it's a fork of gitea, and like gitea, only a single go
         | binary. Super easy to upgrade. I have been running gitea first
         | and now forgejo under docker. It's literally a 5 minute deal to
         | install once you know how it works.
        
           | doubled112 wrote:
           | I did a bare metal to Docker container migration in about 30
           | minutes a couple of weeks ago. It's not a very complicated
           | setup, with few surprises, and this system admin appreciates
           | that.
        
         | mdaniel wrote:
         | > including CI pipeline
         | 
         | You'll want to be cautious, because readme and promises are not
         | software; they're attempting to squat on[1] nektos/act[2] which
         | itself is the 20/80 of GitHub Actions
         | 
         | You'll almost certainly be happier using woodpecker[3] or some
         | other "external" CI system so you don't have to hopes-and-
         | prayers your CI system
         | 
         | 1: https://code.forgejo.org/forgejo/act
         | 
         | 2:
         | https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#...
         | and
         | https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#...
         | 
         | 3: https://github.com/woodpecker-ci/woodpecker _(Apache 2)_
        
       | wvbdmp wrote:
       | What's the latest in Forgejo vs. Gitea?
        
         | omnimus wrote:
         | Sometime in 2024 Forgejo became hard fork no longer merging
         | Gitea code so both projects slowly diverge. But i think
         | momentum is on Forgejo side. Codeberg is popular and
         | development seems to be stable and solid.
        
       | fitblipper wrote:
       | Organic Maps is great and I'm hoping the transition to Forgejo
       | goes smoothly for the project.
       | 
       | I've recently started hiking and just generally going outside in
       | my community more. When I relied on Google Maps I would get some
       | random business highlighted when navigating around. Since I
       | switched to Organic Maps I see trails, artwork, parks, scenic
       | views, etc, etc that I never knew existed even in my own
       | neighborhood. I also love the idea that if I find something not
       | right on it I can just open up Open Street Map, make a simple
       | edit, and improve the life of everyone else using the app that
       | comes after me.
        
         | mcv wrote:
         | I love Organic Maps too. The UI could be a bit nicer, and
         | sometimes it struggles to find where I want to go, but bicycles
         | routes are far superior to those from Google.
        
       ___________________________________________________________________
       (page generated 2025-03-30 23:01 UTC)