Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

README: misleading lock-in statement #647

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

README: misleading lock-in statement #647

wants to merge 1 commit into from

Commits on Aug 15, 2024

  1. README: misleading lock-in statement 

    The documentation is wildly misleading. Everything in this project gets
locked behind a for-profit, closed source, proprietary service in
Microsoft GitHub. It’s misleading to say that this isn’t tracked and has
no lock-in, when it clearly does. We would be better off leveraging the
*decentralized* part of distributed version control systems (DVCS)
instead of centralizing around a service like Microsoft GitHub.

Feel free to close and fix the wording yourself. The rewording is
facetious on purpose, but there is truth to the sentiment. (Merge
requests always get more attention, and I’d email you a patch, but we’re
locked into this platform’s source control model)
    @toastal
    toastal committed Aug 15, 2024
    Configuration menu
    Copy the full SHA
    97dbac4 View commit details
    Browse the repository at this point in the history