LICENSE 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101
  1. The Probably Open Source License (1.0)
  2. (also known as POSS, for short)
  3. (and the "Common Sense CoC") [CoC - Code of Conduct]
  4. What?
  5. The POSS license takes a different approach on open-source, avoiding any political views and focusing on some core
  6. low-iq apprehensible values like "not being a dick".
  7. Also replace the O in the acronym to an I for comedic purposes.
  8. Why?
  9. In our 21st century-based "evolved society" it seems that politics ruins the core values of having a singular opinion, and even will seep into our software.
  10. A license should be simple not have fifty sub-points showing how to breathe and digest without insulting someone else.
  11. Furthermore, there seem to be people on the internet that go as far as modify old use terms like "black and white"-lists because history, and because we need to be
  12. "better and more accepting beings", even if we developers just want to code, and the consumers just want to use a product that isn't restrained by three hundred terms
  13. regarding how X, Y and Z is called and pronounced.
  14. We as a society have devolved to removing eggs from emojis, because it can hurt someone's poor feelings.
  15. (literally no-one cares)
  16. Differences over other Licenses:
  17. - Less scary looking legal text.
  18. Because, be honest, how many of you have actually read a EULA, License or any other legally bound document?
  19. - Address 2 birds with one stone.
  20. Because why not?
  21. - Does politics politically.
  22. Because both sides are equally bad, centrists included.
  23. - Uses Common Sense(TM)
  24. Because thinking these days is quite rare.
  25. Also is a great antivirus solution.
  26. The License:
  27. The following table shows the state of the current program and will have rules below that apprehended to table.
  28. The software developer must fill in this table before using this license.
  29. Main rule table:
  30. ---------------------------------------------
  31. - SOFTWARE_OS: [YES/NO] -
  32. ---------------------------------------------
  33. - SOFTWARE_PAID: [YES/NO] -
  34. ---------------------------------------------
  35. - SOFTWARE_3P_STUFF: [YES/NO] -
  36. ---------------------------------------------
  37. - SOFTWARE_WARRANTY: NO -
  38. ---------------------------------------------
  39. Subset rule table:
  40. ---------------------------------------------
  41. - ENFORCE_TRUE_OSS: [YES/NO] -
  42. ---------------------------------------------
  43. - ALLOW_PAID_FREE: [YES/NO] -
  44. ---------------------------------------------
  45. SOFTWARE_OS: (a.k.a. Is the software open-source?)
  46. The license has a strict term on making OSS (Open Source Software) into closed source software.
  47. If the software is open-source and you wish to make it closed-source, then sorry to ruin your day, but this license prohibits that.
  48. Although adding closed-source blobs is perfectly fine, as long it is disclosed that it includes them.
  49. (!!!) Software marked with ENFORCE_TRUE_OSS: Requires all parts of it to be open, this includes blobs.
  50. If the software is closed-source and you wish to make it open-source, then you can, although you cannot go back.
  51. Of course, closed-source blobs are exempt from this.
  52. (!!!) Software marked with ENFORCE_TRUE_OSS: Blobs must be made open-source too, or must not be included.
  53. If the answer is no, then the license treats it as a "view/analysis/research/use" only, meaning no republishing can made.
  54. SOFTWARE_PAID: (a.k.a. Is the software commercialized?)
  55. The license has strict enforcement on paid and free software definitions too.
  56. (!!!) ENFORCE_TRUE_OSS: The software must be free as in beer, no-buts.
  57. YES: (and the software IS NOT a fork)
  58. Then go nuts.
  59. YES: (and the software IS a fork)
  60. Then it depends the on the fork, if it is paid already, then you are allowed.
  61. However, if it is NOT paid, then you a forbidden from re-sale of what is already free.
  62. NO:
  63. Then it is free, even if forked or modified.
  64. (!!!) However if it is a fork then check if ALLOW_PAID_FREE is allowed, because if it isn't then you must set SOFTWARE_PAID to "YES (ORIGINAL)"
  65. SOFTWARE_3P_STUFF: (a.k.a Does the software contain any third-party libraries/etc.?)
  66. This license has laid back enforcement of attribution to third-party libraries.
  67. SOFTWARE_WARRANTY: (a.k.a Does the software have warranty?)
  68. No. This license DOES NOT support any warranty.
  69. It has so little warranty that here's some scary looking legal text to prove it.
  70. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
  71. EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
  72. MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
  73. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
  74. OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
  75. ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
  76. OTHER DEALINGS IN THE SOFTWARE.
  77. The Code of Conduct:
  78. The Common Sense Code of Conduct
  79. - Don't be an asshole.
  80. - Sometimes you need to be called out for your shit.
  81. - Old terminology doesn't need to be replaced.
  82. - Code != Politics
  83. - No fun allowed :)