contribution_guide.html 6.1KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  2. "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  3. <html xmlns="http://www.w3.org/1999/xhtml">
  4. <head>
  5. <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  6. <title>How to contribute &mdash; searx 0.8.0 documentation</title>
  7. <link rel="stylesheet" href="../_static/style.css" type="text/css" />
  8. <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
  9. <script type="text/javascript">
  10. var DOCUMENTATION_OPTIONS = {
  11. URL_ROOT: '../',
  12. VERSION: '0.8.0',
  13. COLLAPSE_INDEX: false,
  14. FILE_SUFFIX: '.html',
  15. HAS_SOURCE: true
  16. };
  17. </script>
  18. <script type="text/javascript" src="../_static/jquery.js"></script>
  19. <script type="text/javascript" src="../_static/underscore.js"></script>
  20. <script type="text/javascript" src="../_static/doctools.js"></script>
  21. <link rel="top" title="searx 0.8.0 documentation" href="../index.html" />
  22. <link rel="next" title="Installation" href="install/installation.html" />
  23. <link rel="prev" title="Search syntax" href="../user/search_syntax.html" />
  24. <link media="only screen and (max-device-width: 480px)" href="../_static/small_flask.css" type= "text/css" rel="stylesheet" />
  25. <meta name="viewport" content="width=device-width, initial-scale=0.9, maximum-scale=0.9">
  26. </head>
  27. <body role="document">
  28. <div class="document">
  29. <div class="documentwrapper">
  30. <div class="bodywrapper">
  31. <div class="body" role="main">
  32. <div class="section" id="how-to-contribute">
  33. <h1>How to contribute<a class="headerlink" href="#how-to-contribute" title="Permalink to this headline">¶</a></h1>
  34. <div class="section" id="prime-directives-privacy-hackability">
  35. <h2>Prime directives: Privacy, Hackability<a class="headerlink" href="#prime-directives-privacy-hackability" title="Permalink to this headline">¶</a></h2>
  36. <p>Searx has 2 prime directives, privacy-by-design and hackability. The
  37. hackability comes in at least 3 levels:</p>
  38. <ul class="simple">
  39. <li>support for search engines</li>
  40. <li>plugins for altering search behaviour</li>
  41. <li>hacking searx itself.</li>
  42. </ul>
  43. <p>Happy hacking. Observe the lack of &#8220;world domination&#8221; among the
  44. directives, searx has no intentions for wide mass-adoption, rounded
  45. corners, etc. The prime directive: &#8220;privacy&#8221; - deserves a seperate
  46. chapter, as it&#8217;s quite uncommon unfortunately, here it goes:</p>
  47. <div class="section" id="privacy-by-design">
  48. <h3>Privacy-by-design<a class="headerlink" href="#privacy-by-design" title="Permalink to this headline">¶</a></h3>
  49. <p>Searx is a privacy-respecting, hackable meta-search engine. It was born
  50. out of the need for a privacy-respecing search facility that can be
  51. expanded easily to maximise both its search and it&#8217;s privacy protecting
  52. capabilities.</p>
  53. <p>Consequences of Privacy-by-design are that some widely used features
  54. work differently or not by default or at all. If some feature reduces
  55. the privacy perserving aspects of searx, it should by default be
  56. switched of, if implemented at all. There is enough search engines
  57. already out there providing such features. =&nbsp;Since privacy-preservation
  58. is a prime goal, if some feature does reduce the protection of searx and
  59. is implemented, care should be taken to educate the user about the
  60. consequences of choosing to enable this. Further features which
  61. implement widely known features in a manner that protects privacy but
  62. thus deviate from the users expectations should also be explained to the
  63. user. Also if you think that something works weird with searx, maybe
  64. it&#8217;s because of the tool you use is designed in a way to interfere with
  65. privacy respect, submiting a bugreport to the vendor of the tool that
  66. misbehaves might be a good feedback for the vendor to reconsider his
  67. disrespect towards his customers (e.g. GET vs POST requests in various
  68. browsers).</p>
  69. <p>Remember the other prime directive of searx is to be hackable, so if the
  70. above privacy concerns do not fancy you, simply fork it.</p>
  71. </div>
  72. </div>
  73. <div class="section" id="code">
  74. <h2>Code<a class="headerlink" href="#code" title="Permalink to this headline">¶</a></h2>
  75. <p>Code modifications are accepted in pull requests, don&#8217;t forget to add
  76. yourself to the AUTHORS file.</p>
  77. <p>Python code follows all the pep8 standards except maximum line width
  78. which is 120 char.</p>
  79. <p>Please be sure that the submitted code doesn&#8217;t break existing tests and
  80. follows coding conventions.</p>
  81. <p>If new functionality implemented, tests are highly appreciated.</p>
  82. </div>
  83. <div class="section" id="translation">
  84. <h2>Translation<a class="headerlink" href="#translation" title="Permalink to this headline">¶</a></h2>
  85. <p>Translation currently happens on
  86. <a class="reference external" href="https://transifex.com/projects/p/searx">transifex</a>. Please do not
  87. update translation files in the repo.</p>
  88. </div>
  89. <div class="section" id="documentation">
  90. <h2>Documentation<a class="headerlink" href="#documentation" title="Permalink to this headline">¶</a></h2>
  91. <p>The main place of the documentation is this wiki, updates are welcome.</p>
  92. </div>
  93. </div>
  94. </div>
  95. </div>
  96. </div>
  97. <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
  98. <div class="sphinxsidebarwrapper"><div class="sidebar_container body">
  99. <h1>Searx</h1>
  100. <ul>
  101. <li><a href="../index.html">Home</a></li>
  102. <li><a href="https://github.com/asciimoo/searx">Source</a></li>
  103. <li><a href="https://github.com/asciimoo/searx/wiki">Wiki</a></li>
  104. <li><a href="https://github.com/asciimoo/searx/wiki/Searx-instances">Public instances</a></li>
  105. </ul>
  106. <hr />
  107. <ul>
  108. <li><a href="https://twitter.com/Searx_engine">Twitter</a></li>
  109. <li><a href="https://flattr.com/submit/auto?user_id=asciimoo&url=https://github.com/asciimoo/searx&title=searx&language=&tags=github&category=software">Flattr</a></li>
  110. <li><a href="https://gratipay.com/searx">Gratipay</a></li>
  111. </ul>
  112. </div>
  113. </div>
  114. </div>
  115. <div class="clearer"></div>
  116. </div>
  117. <div class="footer">
  118. &copy; Copyright 2015, Adam Tauber.
  119. </div>
  120. </body>
  121. </html>