jsr-io
Not Require Github Account
I prefer using Codeberg, some may prefer to use Gitea or Github.
Please allow devs to use JSR without requiring a Github account.
This is a complicated issue since we require GitHub accounts currently to interract with the GitHub API, and as such having other log-in systems will make features and other usages not possible.
NPM is a closed source package repository. JSR is supposed to be the open source JSR package repository. I do not think JSR should require you to have a proprietary Github account to release packages on the JSR.
And I believe NPM does not require a Github account to have a NPM account.
It would be most appreciated if Github was not required for having a JSR account and other git services like Gitlab, Gitea, Forgejo (Codeberg) were allowed for mirroring packages from.
As :octocat: is owned by Microsoft, I am concerned about what would happen if GitHub were to impose sanctions on my country one day - It is not without precedent 😥
(...) we require GitHub accounts currently to interract with the GitHub API
deno publish doesn't require hosting code on GitHub, thankfully. However jsr.io relies on using a GitHub account, which is not consistent. Why isn't GitHub login optional ?
Because deno is tied to jsr so much, deno basically expects developers to lock into GitHub. I absolutely love deno but I also cherish code freedom and data ownership, which is why I think this issue is pretty disturbing.
This is a big issue for me. I'm really interested in hosting my code on alternative platforms like tangled.sh and getting out of the GitHub lock-in.
I understand not having to make an account and having automatic access to repos is a top-tier developer experience but that shouldn't be the only account mechanism.
What happens when GitHub pulls a Twitter/Reddit and makes their API expensive? This reliance is honestly the achilles heel for JSR right now.
This is a complicated issue since we require GitHub accounts currently to interract with the GitHub API, and as such having other log-in systems will make features and other usages not possible.
@crowlKats having a standard username & password login method doesn't mean a GitHub account can't be connected to use those APIs.
Looking through the codebase, this would basically require putting all GH API usage behind a connection check, and adding the ability to add any Git repo URL for the source.
An open-source package registry shouldn't help to enshrine a monopoly of a closed source platform or turn away devs who use open-source alternatives.
Just as you wouldn't want a platform to require a JS package be linked through NPM, a new Git hosting platform wouldn't want Git, an open source standard that should be vendor agnostic, to be reduced to one hosting company.
I'm planning to abandon Github to use Gitea because I don't like letting my code be used to train AI models without receiving anything in return. It's great that there's an alternative like JSR for NPM, but sticking to Github alone is like turning it into a Microsoft product, just like NPM already is. So it would be really cool if JSR allowed integration with standard formats like Gitlab, Gitea, Google, OpenID, etc.
I'm planning to abandon Github to use Gitea because I don't like letting my code be used to train AI models without receiving anything in return. It's great that there's an alternative like JSR for NPM, but sticking to Github alone is like turning it into a Microsoft product, just like NPM already is. So it would be really cool if JSR allowed integration with standard formats like Gitlab, Gitea, Google, OpenID, etc.
gitlab is currently in WIP https://github.com/jsr-io/jsr/pull/1150
