Advertisement
Guest User

Crazy Bugs

a guest
Jul 14th, 2015
236
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.76 KB | None | 0 0
  1. You think that you help to make the best browser in the world?
  2. It is really so.
  3. Mozilla task is to make better for the people.
  4.  
  5. But is it possible to make better for people by force, by torture, by
  6. humiliation and bullying?
  7. Or some people at the expense of others people?
  8.  
  9. Once in the USSR, some people believed that the state knows better how many
  10. tomatoes and cucumbers need to each particular person.
  11. It turned out to be a mistake.
  12. Would you like to help the officials of the USSR?
  13. We would not want to help such officials.
  14.  
  15.  
  16. Now Mozilla has decided that it knows best what and how FireFox extensions the
  17. people can use, and what and how the people cannot use.
  18. As the developer of the extension, now I'll have to compile FireFox just to use
  19. their extension.
  20.  
  21. Officials Mozilla actually have not listen to us. It's just torture.
  22. They were warned about all the problems. But in the end did what is not
  23. justified on any things.
  24. For example, Mozilla blocked the AMO beta-channels for fully reviewed
  25. extensions. With that, then they're going to open them again.
  26. It is not justified absolutely nothing.
  27. Here already as 1.5 years I am saying that the situation with the time of the
  28. AMO review is invalid.
  29. However, Mozilla is introducing even more complex and time-consuming procedure
  30. review, although Mozilla not the way to maintain the proper level of even this.
  31. People maintain the developing add-ons for free. And get Mozilla all to stop
  32. their development.
  33. To humiliate these people. Mozilla make it impossible for even a simple test
  34. for the extensions. (FireFox DE is not suitable for this)
  35.  
  36. This is the openness of FireFox? Internet freedom? Respect for users and
  37. developers?
  38.  
  39. Mozilla officials just don't listen to any arguments and don't even think about
  40. how to faithfully fulfil at least their own decisions.
  41.  
  42. Helping for Mozilla now, you help for the mad officials.
  43. You are harming to people.
  44. You're helping to torture and bullying under extension developers.
  45. You are help to make evil.
  46.  
  47. I write this only because FireFox is a really good browser. I don't want to use
  48. another!
  49. Help me as you can.
  50. Stop you work. Do not help Mozilla to bear evil and turn from a good company at
  51. a mad officials like the deceased USSR.
  52.  
  53. It depends on each. It depends on you.
  54. There are no excuses for condoning of torture.
  55. Bad case cannot be justified by anything. Neither the problems nor a benefit to
  56. society.
  57.  
  58.  
  59.  
  60. Copy of the previous mail for the some mozilla members
  61. -------------------------------------------------------------------------------
  62. --------------------
  63.  
  64. cbeard@mozilla.org, ben@mozilla.org, mbrubeck@mozilla.com, mgrimes@mozilla.com,
  65. myk@mozilla.org
  66. Mozilla policies
  67. Hello
  68.  
  69.  
  70. Below in this letter you can find information for the following issues:
  71. 1. The Mozilla communication policy with other people is offensive and
  72. ineffective. It brings to rabies and harms the health (I had a hypertensive
  73. crisis).
  74. 2. The AMO extensions review policy is well, but its implementation is
  75. offensive and unacceptable about prevent of the extensions development.
  76. 3. The extensions signing policy is bad, and its implementation make an
  77. unacceptable obstacle for the extensions developers. This policy is
  78. unprofessional implemented.
  79.  
  80. In advance I apologize, if it's not interesting. However, the policy of Mozilla
  81. does not allow me to make it to the competent specialists. At the same time,
  82. Mozilla causes me considerable moral and material harm. I am compelled to
  83. appeal to the greatest number of people, so the problem became known.
  84.  
  85.  
  86. -------------------------------------------------------------------------------
  87. ------
  88. -------------------------------------------------------------------------------
  89. ------
  90.  
  91. 1. Turning to the support specialist of any company, I expect he intends to
  92. solve the problem if possible and appropriate. I also expect that if this is
  93. not possible, then specialist tell to explain to me why and how can I minimize
  94. the damage.
  95. If I developing the FireFox extension, I expect that Mozilla will not interfere
  96. with me to the extension development. Because it is profitable for Mozilla.
  97. Also I expect the understanding that I work for free. Which means they have the
  98. very limited resources, and it is a personal resources. I spend my life for the
  99. extension development.
  100.  
  101. However, Mozilla is doing the opposite.
  102.  
  103. For example.
  104. 1) for a recent discussion of the new policy of the extension signing, the
  105. developer community have been specified in advance all the problems that arose
  106. later in its implementation. However, nobody listened to the developers. And
  107. issues that have been predicted, there was really.
  108. 2) Mozilla is in no way took into account the opinion of the developers, nor
  109. the degree of the harm inflicted. Not even bothering to explain what critical
  110. reason has forced Mozilla to do so. I don't think the explanation about the
  111. increase in security FireFox here may be the true explanation. Because the harm
  112. to developers far more than any benefit from the introduction of the new policy
  113. (see 3. item).
  114. 3) AMO editors constantly demanding for me the requirements that are not
  115. described (clearly or generally) in AMO extensions review policy.
  116. Obviously, if AMO required any requirements for me, I should be able to know in
  117. advance about the availability of these requirements. Otherwise I can't do
  118. them.
  119. For example, if AMO required for me to make the test plan of extension, this
  120. requirement should be clearly described. Otherwise I imposed unreasonable
  121. demands, as if it was my fault that I did not provide this plan. (And what
  122. could be the test plan, if AMO declares that reads all the code of the
  123. extension??? How do they read?)
  124. 4) Some of the requirements should not be submitted. For example, the
  125. requirement to replace the nsIObserverService to sdk/system/events. There is no
  126. harm for using nsIObserverService. The developer determines what interfaces it
  127. uses. However, AMO editors believe that they can interfere in the creative
  128. process of the extension developing.
  129. 5) Not everyone is equal before the Mozilla policy. Known extensions are review
  130. faster. Simple extension (that is useless) passes review faster then a
  131. difficult extensions.
  132. Some additions described violate policy Mozilla. Because they "allowed".
  133. However, many others cannot. Where such privileges?
  134.  
  135. I don't need to explain the reasons for such problems. Just decide them! These
  136. reasons are disposable.
  137.  
  138.  
  139.  
  140. There was no mechanism for complaints. So, complaints about inadequate
  141. requirements AMO editors to go Jorge Villalobos (must die).
  142. Complaints about the harm of Mozilla's policies go to Jorge Villalobos (must
  143. die) too.
  144. Complaints Jorge Villalobos go to Jorge Villalobos (must die) too.
  145. However, he is not going to listen for arguments. Does not intend to amend the
  146. policy or to solve problems. He has "no time" for me. He has "thousands of
  147. add-ons". Why you need Jorge, if he has no time for anyone?
  148. He is not going to listen. He is not going to solve the problem.
  149. This man serves to pretend only that listening to me.
  150.  
  151. This will not work. I'm not stupid. I understand, when people listening to me,
  152. and when people make me to going.
  153. Why would Mozilla to produce of enemies? You so want to them?
  154.  
  155.  
  156. Conclusions:
  157. 1) Any action by authorised persons must be posiible to challenged by other
  158. authorised persons.
  159. 2) Don't make authorised persons who pretend to listen. But do not have the
  160. authority, ability and willingness.
  161. 3) Problems must have solve, and do not tell how difficult it to solve and
  162. their causes.
  163. It are possible to resolving. If there are no people, then you must admit that
  164. there are no people. And to make the procedure to simpler.
  165.  
  166. -------------------------------------------------------------------------------
  167. ------
  168. -------------------------------------------------------------------------------
  169. ------
  170.  
  171. 2. The Existing extension review policy does not update the add-on in good
  172. time. Updating them takes at least several months. I talking about useful
  173. extensions. That is about complex extensions.
  174. 1) AMO is unable to support the declared certification (review) policy for
  175. extensions.
  176. 2) AMO should to cancel the all extensions checks, except for security checks.
  177. Check is good, but AMO is unable to hold them.
  178. 3) As suggested by another person, if the AMO does not have time to certify the
  179. extension within 10 days, it should be published without certification (only
  180. for extensions with certificated versions).
  181. 4) The developer channel should work with automatic signature in any case (only
  182. for extensions with certificated versions). The lack of a developer channel
  183. makes it impossible to solve many problems.
  184. 5) If 10 days is too low, set a longer period, subject to item 3) .
  185.  
  186. Extension development impossible without it. Notice, the NoScript extension and
  187. the some other extensions obviously gets earlier reviews of other. And the only
  188. reason he lives.
  189.  
  190. -------------------------------------------------------------------------------
  191. ------
  192. -------------------------------------------------------------------------------
  193. ------
  194.  
  195. 3.
  196. To the extension signing must check only what you can really check. No
  197. statically check by regex for the preferences name. It can be bypassed.
  198. I don't know what caused such a critical change in policy. Why are they so
  199. quick that there is no way to keep up with them. But, in any case, protecting
  200. some people, no need to kill others people.
  201.  
  202. I think that if the extension in AMO more than 1 year, then it is quite
  203. possible to enable automatic signing the developer channel.
  204. The problem is too acute, to be neglected by developers.
  205. Even I myself will soon not be able to use their own addition, if all of this
  206. continues to be so. DE and Nightly not meant for everyday use. But there is no
  207. other version, which would take unsigned extensions.
  208.  
  209. It, including, will affect the quality of testing extensions. Since before the
  210. publication of the extension, the developer will now not be able to use it
  211. independently in usual daily work. Thus, many errors will not be found by the
  212. developer and the users.
  213.  
  214. -------------------------------------------------------------------------------
  215. ------
  216. -------------------------------------------------------------------------------
  217. ------
  218.  
  219. And again, people who participate in discussions by Mozilla, must be
  220. authoritative. Jorge Villalobos must die. He doesn't make decisions. And Jorge
  221. not qualified to evaluate what the developers say. He can't even explain why
  222. adopted one or the other.
  223. He can only ban.
  224. And no one person can do this. Or FireFox developers should make the complaint
  225. themselves or Mozilla will also, as before, to torment the extensions
  226. developers.
  227.  
  228.  
  229. STOP MOCK ON THE EXTENSION DEVELOPERS!
  230.  
  231. Ask for help from everyone. Bullying and torturing under people is
  232. unacceptable!
  233.  
  234. END.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement