Advertisement
Guest User

Untitled

a guest
Jul 21st, 2011
306
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.19 KB | None | 0 0
  1. Recipients: opensource@netgear.com, legal@netgear.com, sales@netgear.com, Ralph Böhme <rb@netafp.com>, support@netgear.com, netatalk-devel@lists.sourceforge.net, license-violation@gnu.org
  2.  
  3. Subject: Re: Open Letter to the Netatalk Community
  4.  
  5. -----BEGIN PGP SIGNED MESSAGE-----
  6. Hash: SHA1
  7.  
  8. Ralph,
  9.  
  10. I have changed my mind, I don't want a support contract because I have now been distributed your binaries.
  11.  
  12. Netgear Reps & Ralph,
  13.  
  14. I have come in to possession of netatalk 2.2 binaries as distributed by netgear in the readynas x86 4.2.18 update. Please provide me the sources.
  15.  
  16. I demand that you release the GPL code you are holding hostage.
  17.  
  18. (Please see: http://pastebin.com/jzXWdCzJ for origination of this thread.)
  19.  
  20. On Jul 21, 2011, at 4:07 PM, Douglas Huff wrote:
  21.  
  22. >>-----BEGIN PGP SIGNED MESSAGE-----
  23. >>Hash: SHA1
  24. >>
  25. >>Ok, so, what are my payment options for a 20 user support contract? (I only have 2 users but that is your smallest option.) I can't wait weeks/months to have functioning backups. If I'm doing the conversion correctly it's $860 USD, yes?
  26. >>
  27. >>I more than meet your technical requirements of being able to provide my own second level support: http://www.linkedin.com/profile/view?id=69353266&locale=en_US&trk=tab_pro
  28. >>
  29. >>On Jul 21, 2011, at 1:33 AM, Ralph Böhme wrote:
  30. >>
  31. >>Douglas,
  32. >>
  33. >>let me start this reply with a big *sigh*. Fortunately I haven't only received largish complaints like yours (and others), others, including Netatalk project members (inactive for long time), understand my move and wished me success.
  34. >>
  35. >>This is an effort to establish a sustainable infrastructure in order to ensure Netatalk doesn't end where it once ended in 2005 where all serious developers left. It was 2005 when Netatalk version 2.0.3 was released. In the following years there was one french dev who did a few minor commits but basically development grinded to a halt.
  36. >>
  37. >>It was 2009 (!), four years later, when Frank started contributing code to the project and he's been the contributor of 98% of the code since then. 2.0.4 was then released in 2009 four years after the prior version. Frank implemented DHX2 authentication module (in 2009, now mandatory for Lion), ACL support, Extended Attribute support, AFP 3.3 support and much, much more in the time. Without Frank's achievements Netatalk would be an unusable rotten piece of gargabe, not usable with modern OS X clients. Now, Frank is still the only serious dev working on the code.
  38. >>
  39. >>We're now at a point, either those who benefit from the project ensure the development can continue or we move on, in which case you'll have rotten code again in a few years. I don't know why so few developers contribute to this project, probably due do it's nature of briding the FOS world with the closed, commercial world of Apple, so in case you may think others devs would start working on it I'm pretty sure that wouldn't happen.
  40. >>
  41. >>Ok, now I've gone into great length covering some history and stuff, I'll now reply to some of your writeup inline.
  42. >>
  43. >>Subject: Re: Open Letter to the Netatalk Community
  44. >>
  45. >>Seriously?
  46. >>
  47. >>So you posted an inflammatory article in January because vendors with their own
  48. >>support/technical resources aren't paying for your support services while you
  49. >>offer no other services. [1]
  50. >>
  51. >>I can assure you, these vendors have no support/technical resources capable of fixing anything serious.
  52. >>
  53. >>You're surprised that they continued not purchasing your services. [2]
  54. >>
  55. >>No, I wasn't suprised, that was as expected.
  56. >>
  57. >>You're mad said vendors are making money off of open source software that, for
  58. >>the most part, you did not write.
  59. >>
  60. >>I'm mad for other reasons. We're just trying to have NAS OEMs see the whole picture. Many other corporations have realized that they must ensure that projects they depend upon and make money from are funded and well being one way or the other.
  61. >>
  62. >>The same software that has enabled you to make any money through this endeavor
  63. >>at all. Thanks to previous contributors' licensing choice.
  64. >>
  65. >>So; now, you're withholding a working version, with additions you did write
  66. >>with the help of community testers[3][4] and feedback[5], ...
  67. >>
  68. >>We've developed, tested and enhanced the current working version spending weeks of our time (that's what I get paid for) working on customer bug reports. Community contributes about 2% to this.
  69. >>
  70. >>⦠for the OS X 10.7 launch
  71. >>in what I can only assume is an attempt to alienate your end users in addition
  72. >>to the vendors you are upset with.
  73. >>
  74. >>Classy. Real classy.
  75. >>
  76. >>Your behaviour is unprofessional and unbecoming. You complain that vendors are
  77. >>not paying you for your efforts, which you chose to make, while not even
  78. >>providing end users and community members a means of donating, monitarily, to
  79. >>your efforts. In fact you go so far as to explicitly discourage people, on your
  80. >>product description page, from purchasing your services and then have the gall
  81. >>to whine that they don't.
  82. >>
  83. >>It's bad enough Apple has killed unofficial nfs support for time machine by
  84. >>adding an AFP specific ioctl call before starting a backup. Especially
  85. >>considering that all their extensions to AFP since 1.x have done almost nothing
  86. >>but implement guaranteed behavior of the NFS protocol which has had multiple
  87. >>working implementations for greater than twenty years. Not to mention that they
  88. >>now have a functional NFSv4 implementation and they've fixed kerberos where you
  89. >>could feasibly get it to mount data channel encrypted NFS through system
  90. >>daemons and then explicitly broke one of the main reason you'd want either.
  91. >>
  92. >>Your actions are no better. In fact: they're worse. You're holding code, that
  93. >>you have no right to, hostage because your business model has turned out to not
  94. >>be profitable.
  95. >>
  96. >>We're complying with the GPL.
  97. >>
  98. >>RedHat learned this lesson 10 years ago. You can not subsist on
  99. >>support contracts alone. Welcome to the cruel, harsh, real world.
  100. >>
  101. >>They've learned other lessons as well, the one that is relevant for us here is that they learned to pay (or hire) developers working on relevant projects.
  102. >>
  103. >>Preventing exactly what you have done is why the license was changed to the GPL
  104. >>in the first place. It is; in fact, the entire reason the GPL exists. Your
  105. >>responses to others' reactions tends to indicate that you don't care[6].
  106. >>
  107. >>I'm sorry that you are not currently able to make your living doing what you
  108. >>love to do, I truly am, neither can I. I understand this can be frustrating and
  109. >>demoralizing. Your actions are counter productive and are just ensuring that
  110. >>advocates for open software will think twice before contributing to your work
  111. >>in the future.
  112. >>
  113. >>To be clear: I, as often as time and funds allow, donate to open projects I use
  114. >>either through code[7][8] and testing[8] (where I am capable and there is a need) or
  115. >>monetarily[9][10]. Whether you eventually release this code or not I now can not see
  116. >>myself giving you any type of support. I'm sure I am not alone in this.
  117. >>
  118. >>Probably. But please there have been opposite receptions as well, see some recent post on the Netatalk mailing lists.
  119. >>
  120. >>I make no money off your work nor have I, to my knowledge, in the past. I am
  121. >>just an end user. I don't purchase products from the people you're mad at. I
  122. >>wouldn't even be looking into the project you've taken over if Apple had not
  123. >>intentionally broken NFS support.
  124. >>
  125. >>This entire situation is mind boggling.
  126. >>
  127. >>You have not the slightest idea how mind boggling this situation really is for me. Luckily, probably in a few weeks/months this will all be sorted out.
  128. >>
  129. >>There are so many corellary projects
  130. >>that do not take this extortion route and continue to operate just
  131. >>fine[11][12][13][14].
  132. >>
  133. >>Bad examples to make your point. All these projects are funded by large corporations, hiring developers (Samba: IBM, Cisco, RedHat; Linux: IBM, Cisco, RedHat, â¦; GCC: IBM, Cisco, RedHat, ...) or working with third parties (eg SerNet and Samba).
  134. >>
  135. >>Regards,
  136. >>Ralph
  137. >>
  138. >>- --
  139. >>We've done our best, but if it breaks, the code is free, both halves are yours.
  140. >>If you need a supported and longterm reliable product, we invite you to work with us.
  141. >>
  142. >>Ralph Böhme <rb@netafp.com>
  143. >>Netatalk Developer | Support | Services
  144. >>Phone: +49-40-2294-8534
  145. >>http://www.netafp.com/
  146. >>
  147. >>
  148. >>- --
  149. >>Douglas Huff
  150. >>
  151. >>
  152. >>-----BEGIN PGP SIGNATURE-----
  153. >>Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
  154. >>Comment: GPGTools - http://gpgtools.org
  155. >>
  156. >>iQIcBAEBAgAGBQJOKJTqAAoJEEPHkQabDWHPgmsP/0F0UbdqE3e+xZXWLc8FtKvF
  157. >>78WZzlzAr9mFAwBNysvqkDQV+4yljmjciYoNh6s3e4B7u0/AYhsAn1r3EGjYvlaK
  158. >>CDIMJrhYyxzFq9t/SI097xKlKq9ziT7kwXcbbRJXuL2HLRziu6mkg8W+ZS+D0by0
  159. >>FYr1ooSZU7/Tg73D0Esp/mi07OIiDBOOqnleKPpP3EV1/xvSc9tqqgfIug+a6liR
  160. >>yQ+S7L5xfHgNju9LFaqGPK6a0Mege/zH9qNP8JjJlRGMF+K4TIKfFlIeFjrBUzQ6
  161. >>vGPeLSpm1BNyU8AopK6Un0dEQ02eeSoPQEzQCCLS1jyeUN5FtEXJgWEjRnu+DjjP
  162. >>yKzLtvaPmfx6VOWrTlDzyGKnmlAmLwSXj7imNtCa5qy7bjyofN5X+YKbmt4DwggN
  163. >>uoJ5hsqOUWvqi9pPaN1pNh0l4EpR6HakscGvbya0KcXh6DAs4CwggrTAr8AJOeMS
  164. >>apyYukDZedeACnMbQ0AWjfxyt9y7bknNI7tHgv2RtNG83him+kCMQRIuYFuhH3S2
  165. >>/WPYg8BkCaCvMEM0d3wSYJWae4h2DloU1heL1obdzgL6CoyJdKsqa+1DQB2rPRED
  166. >>snGqbmgiyXwIxf1L5oK3zsiKhJL9h+xCsrTnUoW8U1um7l9fHN8kvrlm+HTNedo0
  167. >>VTq+Z5NRQWWa6pEWID7a
  168. >>=CT6d
  169. >>-----END PGP SIGNATURE-----
  170.  
  171.  
  172. - --
  173. Douglas Huff
  174.  
  175.  
  176. -----BEGIN PGP SIGNATURE-----
  177. Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
  178. Comment: GPGTools - http://gpgtools.org
  179.  
  180. iQIcBAEBAgAGBQJOKKg5AAoJEEPHkQabDWHP/1YP/2xJdgOHKaLvL2CBtUuy4w7D
  181. /4k9RoK/UDDgpUnquoAYsfzC36v0kPe/UU5rUP+hPqeM1j31AEweTtKDYZdpFvLt
  182. a2Ko3xXE3U5my3/Xb+2IQNgBe7THNlVrwe3jG4isey1xqgy0+f3me2e/76a6TNNQ
  183. 1HKJEkj5McB670Bz8OSUOqKxyPFp8VHh/rI0rdt5FHbgo2XYz7Botnu1tcecQrna
  184. gN6T6+Zl3GLD3W05iIcESVpbpOqtSk4WxDJt0/f/hQFQ6AKJPlelr3Wfb6B648bU
  185. GlE9VlBxcI0LRqIeztOC+z6M8InxdyAKcr3q9mxZ69TuDIDUgFhEB4x8P8YHEC+j
  186. n6PKkrpjipufI9L1bJKb49WCP0H9/9EXFb5bcORg2edL6kIpQwo4WSFRev9++Cuo
  187. nJOU8h9ubtB41V8izEoX50bFfEj6U5QQ+mlIZmRL+zQf+jAJbt/FQycjDvrPgmVD
  188. w8o7WZLnsdJoYqdTX+8D0BEXS7+ltxNO4RElLUoK8InUTjZdys6FAzMlFZLVUC+k
  189. o9/6iurbW+6mPNTJhBMozdeli5gt5YoB7bgeUwXTZk5g89ZuD66aG6mw+1dTlqOO
  190. S7HCvOxHUKOJX0ajFKbemGfkrWE4c42Udb2CWmalw8wWan/HO77ae7+8A9rSGO9t
  191. u8GjLrNAOq8qUpIFXJPc
  192. =URl0
  193. -----END PGP SIGNATURE-----
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement