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.

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

Revert "Remove bitcoin.pdf" #744

Closed
wants to merge 1 commit into from
Closed

Conversation

@Legogris
Copy link

@Legogris Legogris commented Jan 21, 2021

This reverts commit c131308 in PR #740.

This reverts commit c131308.
@i-rme
Copy link

@i-rme i-rme commented Jan 21, 2021

Some proof that Bitcoin.pdf is MIT licensed

In March 2009, nakamoto2 added the bitcoin.pdf file with License: MIT License to Sourceforge.

image
https://web.archive.org/web/20090106201347/https://sourceforge.net/projects/bitcoin/

@Cobra-Bitcoin
Copy link

@Cobra-Bitcoin Cobra-Bitcoin commented Jan 21, 2021

ACK.

1 similar comment
@n1rna
Copy link
Contributor

@n1rna n1rna commented Jan 21, 2021

ACK.

@kFTY
Copy link

@kFTY kFTY commented Jan 21, 2021

MIT license is only valid for software

including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software

@Cobra-Bitcoin
Copy link

@Cobra-Bitcoin Cobra-Bitcoin commented Jan 21, 2021

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software")

@kFTY

@i-rme
Copy link

@i-rme i-rme commented Jan 21, 2021

MIT license is only valid for software

including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software

No, it's on the first line of the license text:

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software")

The software and associated documentation files is called the Software.

Also we could argue that a PDF file is software as a set of instructions.

@rndhouse
Copy link

@rndhouse rndhouse commented Jan 21, 2021

Wait a while before merging so as not to repeat the procedural mistake (merging too fast) of #740 . Allow time for this PR to win all challenges. No rush ;)

@Legogris
Copy link
Author

@Legogris Legogris commented Jan 21, 2021

@randomhouse Assigning blame is not relevant to this PR. Take that elsewhere.

@rndhouse
Copy link

@rndhouse rndhouse commented Jan 21, 2021

I don't like pointing out an individual either, so I've deleted my comment. But, this PR exists because merging procedure was broken. That needs to be reviewed.

@bitcoin-core bitcoin-core locked as too heated and limited conversation to collaborators Jan 21, 2021
@laanwj laanwj closed this Jan 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

7 participants