Typica is a free program for professional coffee roasters. https://typica.us
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

LICENSE 3.8KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394
  1. From QextSerialPort 1.2-beta on, we use MIT license for QextSerialPort project.
  2. == License ==
  3. Copyright (c) 2000-2003 Wayne Roth
  4. Copyright (c) 2004-2007 Stefan Sander
  5. Copyright (c) 2007 Michal Policht
  6. Copyright (c) 2008 Brandon Fosdick
  7. Copyright (c) 2009-2010 Liam Staskawicz
  8. Copyright (c) 2011 Debao Zhang
  9. Web: http://code.google.com/p/qextserialport/
  10. Permission is hereby granted, free of charge, to any person obtaining
  11. a copy of this software and associated documentation files (the
  12. "Software"), to deal in the Software without restriction, including
  13. without limitation the rights to use, copy, modify, merge, publish,
  14. distribute, sublicense, and/or sell copies of the Software, and to
  15. permit persons to whom the Software is furnished to do so, subject to
  16. the following conditions:
  17. The above copyright notice and this permission notice shall be
  18. included in all copies or substantial portions of the Software.
  19. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
  20. EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
  21. MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
  22. NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
  23. LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
  24. OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
  25. WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
  26. == Why license needed? ==
  27. Many users complains that, without a proper licence they can not use this library.
  28. * http://groups.google.com/group/qextserialport/browse_thread/thread/0e8756920b01da82
  29. Hi,
  30. we are considering using a modified version of QExtSerialPort in one of our
  31. projects (Qt Creator, http://qt.gitorious.org/qt-creator).
  32. Would it be possible to add license header information or a license file to the
  33. QExtSerialPort code base? - This would make re-use of the code base easier.
  34. If that is not possible, could we redistribute the source code with BSD-
  35. license headers manually added?
  36. And
  37. I am also considering packaging the software for Debian, but I
  38. couldn't do it yet just because of the license.
  39. * http://code.google.com/p/qextserialport/issues/detail?id=8
  40. Questions:
  41. Can I use qextserialport in a commercial product?
  42. If yes, how?
  43. Compile it in? I guess no.
  44. If I can use it as a library, how should the README be formulated?
  45. Is the "MIT license" from 2008 appropriate?
  46. == Why can we use MIT? ==
  47. Form the history of [http://lists.trolltech.com/qt-interest/2004-12/msg01022.html qt-interest mail list]
  48. * Wayne Roth, the original author of the project, had said that:
  49. the code is in the public domain. Do whatever you like with it. Right
  50. now I have too many other things to do to put any serious time into
  51. fixing it. Trolltech should be aware of this already; they asked
  52. about a license when they offered to host the tarball.
  53. * Stefan Sander, the maintainer of qextserialport on sourceforge, said that
  54. Hello,
  55. My project registration at !SourceForge have been approved.
  56. http://www.sf.net/projects/qextserialport
  57. I thought an initial licence of Public Domain would be best solution.
  58. Someone wrote: - Because its public domain, some could fork it under different licenses -
  59. And from [http://groups.google.com/group/qextserialport/browse_thread/thread/fbcddbfb4a0b5a51?pli=1 this thread] on qesp mail list, we can see that, current maintainers and users agree with a MIT licence.
  60. * Brandon Fosdick,
  61. I would vote for BSD or MIT :)
  62. * Liam Staskawicz,
  63. That works for me - let's call it MIT and go for it :)
  64. And from [[https://groups.google.com/forum/?fromgroups#!topic/qextserialport/P_5TrNHBICE this other thread]] on the same mailing list:
  65. * Michal Policht,
  66. I agree to license.