README: misleading lock-in statement #647
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
toastal
force-pushed
the
readme
branch
5 times, most recently
from
20f511a to
9d67044
Compare
|
This is cool, thanks! |
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)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The documentation is wildly misleading. Everything in this project gets locked behind a US-based, 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)