new README file based on Victoriia’s changes

README.rst

@@ -1,97 +1,118 @@
-==========
+**Free and Open decentralized data store**
-Tahoe-LAFS
-==========
 
-Tahoe-LAFS is a Free and Open decentralized cloud storage system. It
+|image0|
-distributes your data across multiple servers. Even if some of the servers
-fail or are taken over by an attacker, the entire file store continues to
-function correctly, preserving your privacy and security.
 
-For full documentation, please see
+`Tahoe-LAFS <https://www.tahoe-lafs.org>`__ (Tahoe Least-Authority File Store) is the first free software / open-source storage technology that distributes your data across multiple servers. Even if some servers fail or are taken over by an attacker, the entire file store continues to function correctly, preserving your privacy and security.
-http://tahoe-lafs.readthedocs.io/en/latest/ .
 
 |Contributor Covenant|  |readthedocs|  |travis|  |circleci|  |codecov|
 
 
-INSTALLING
+Table of contents
-==========
 
-There are three ways to install Tahoe-LAFS.
+-  `About Tahoe-LAFS <#about-tahoe-lafs>`__
 
-using OS packages
+-  `Installation <#installation>`__
-^^^^^^^^^^^^^^^^^
 
-Pre-packaged versions are available for several operating systems:
+-  `Contributing <#contributing>`__
 
-* Debian and Ubuntu users can ``apt-get install tahoe-lafs``
+-  `Issues <#issues>`__
-* NixOS, NetBSD (pkgsrc), ArchLinux, Slackware, and Gentoo have packages
-  available, see `OSPackages`_ for details
-* `Mac`_ and Windows installers are in development.
 
-via pip
+-  `Documentation <#documentation>`__
-^^^^^^^
 
-If you don't use an OS package, you'll need Python 2.7 and `pip`_. You may
+-  `Community <#community>`__
-also need a C compiler, and the development headers for python, libffi, and
-OpenSSL. On a Debian-like system, use ``apt-get install build-essential
-python-dev libffi-dev libssl-dev python-virtualenv``. On Windows, see
-`<docs/windows.rst>`_.
 
-Then, to install the most recent release, just run:
+-  `FAQ <#faq>`__
 
-* ``pip install tahoe-lafs``
+-  `License <#license>`__
 
-from source
+💡 About Tahoe-LAFS
-^^^^^^^^^^^
+-------------------
-To install from source (either so you can hack on it, or just to run
-pre-release code), you should create a virtualenv and install into that:
 
-* ``git clone https://github.com/tahoe-lafs/tahoe-lafs.git``
+Tahoe-LAFS helps you to store files while granting confidentiality, integrity, and availability of your data.
-* ``cd tahoe-lafs``
-* ``virtualenv --python=python2.7 venv``
-* ``venv/bin/pip install --upgrade setuptools``
-* ``venv/bin/pip install --editable .``
-* ``venv/bin/tahoe --version``
 
-To run the unit test suite:
+How does it work? You run a client program on your computer, which talks to one or more storage servers on other computers. When you tell your client to store a file, it will encrypt that file, encode it into multiple pieces, then spread those pieces out among various servers. The pieces are all encrypted and protected against modifications. Later, when you ask your client to retrieve the file, it will find the necessary pieces, make sure they haven’t been corrupted, reassemble them, and decrypt the result.
 
-* ``tox``
+| |image2|
+| *The image is taken from meejah's* \  `blog <https://blog.torproject.org/tor-heart-tahoe-lafs>`__ \  *post at Torproject.org.*
 
-You can pass arguments to ``trial`` with an environment variable.  For
+|
-example, you can run the test suite on multiple cores to speed it up:
 
-* ``TAHOE_LAFS_TRIAL_ARGS="-j4" tox``
+The client creates pieces (“shares”) that have a configurable amount of redundancy, so even if some servers fail, you can still get your data back. Corrupt shares are detected and ignored so that the system can tolerate server-side hard-drive errors. All files are encrypted (with a unique key) before uploading, so even a malicious server operator cannot read your data. The only thing you ask of the servers is that they can (usually) provide the shares when you ask for them: you aren’t relying upon them for confidentiality, integrity, or absolute availability.
 
-For more detailed instructions, read `<docs/INSTALL.rst>`_ .
+Tahoe-LAFS was first designed in 2007, following the "principle of least authority", a security best practice requiring system components to only have the privilege necessary to complete their intended function and not more.
 
-Once ``tahoe --version`` works, see `<docs/running.rst>`_ to learn how to set
+Please read more about Tahoe-LAFS architecture `here <https://tahoe-lafs.readthedocs.io/en/tahoe-lafs-1.12.1/architecture.html?highlight=usage>`__.
-up your first Tahoe-LAFS node.
 
-LICENCE
+✅ Installation
-=======
+---------------
 
-Copyright 2006-2018 The Tahoe-LAFS Software Foundation
+For more detailed instructions, read `docs/INSTALL.rst <https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/INSTALL.rst>`__ .
 
-You may use this package under the GNU General Public License, version 2 or,
+-  Building Tahoe-LAFS on Windows: https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/windows.rst
-at your option, any later version. You may use this package under the
-Transitive Grace Period Public Licence, version 1.0, or at your option, any
-later version. (You may choose to use this package under the terms of either
-licence, at your option.) See the file `COPYING.GPL`_ for the terms of the
-GNU General Public License, version 2. See the file `COPYING.TGPPL`_ for
-the terms of the Transitive Grace Period Public Licence, version 1.0.
 
-See `TGPPL.PDF`_ for why the TGPPL exists, graphically illustrated on three
+-  | OS-X Packaging:
-slides.
+      | https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/OS-X.rst
 
-.. _OSPackages: https://tahoe-lafs.org/trac/tahoe-lafs/wiki/OSPackages
+Once tahoe --version works, see `docs/running.rst <https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/running.rst>`__ to learn how to set up your first Tahoe-LAFS node.
-.. _Mac: docs/OS-X.rst
-.. _pip: https://pip.pypa.io/en/stable/installing/
-.. _COPYING.GPL: https://github.com/tahoe-lafs/tahoe-lafs/blob/master/COPYING.GPL
-.. _COPYING.TGPPL: https://github.com/tahoe-lafs/tahoe-lafs/blob/master/COPYING.TGPPL.rst
-.. _TGPPL.PDF: https://tahoe-lafs.org/~zooko/tgppl.pdf
 
-----
+🤗 Contributing
+---------------
 
+As a community-driven open source project, Tahoe-LAFS welcomes contributions of any form:
+
+-  `Code patches <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Patches>`__
+
+-  `Documentation improvements <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Doc>`__
+
+-  `Bug reports <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/HowToReportABug>`__
+
+-  `Patch reviews <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/PatchReviewProcess>`__
+
+Before authoring or reviewing a patch, please familiarize yourself with the `Coding Standard <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/CodingStandards>`__ and the `Contributor Code of Conduct <https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/CODE_OF_CONDUCT.md>`__.
+
+🤖 Issues
+---------
+
+Tahoe-LAFS uses the Trac instance to track `issues <https://www.tahoe-lafs.org/trac/tahoe-lafs/wiki/ViewTickets>`__. Please email jean-paul plus tahoe-lafs at leastauthority dot com for an account.
+
+📑 Documentation
+----------------
+
+You can find the full Tahoe-LAFS documentation at our `documentation site <http://tahoe-lafs.readthedocs.io/en/latest/>`__.
+
+💬 Community
+------------
+
+Get involved with the Tahoe-LAFS community:
+
+-  Chat with Tahoe-LAFS developers at #tahoe-lafs chat on irc.freenode.net or `Slack <https://join.slack.com/t/tahoe-lafs/shared_invite/zt-jqfj12r5-ZZ5z3RvHnubKVADpP~JINQ>`__.
+
+-  Join our `weekly conference calls <https://www.tahoe-lafs.org/trac/tahoe-lafs/wiki/WeeklyMeeting>`__ with core developers and interested community members.
+
+-  Subscribe to `the tahoe-dev mailing list <https://www.tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev>`__, the community forum for discussion of Tahoe-LAFS design, implementation, and usage.
+
+-  Familiarize yourself with our `Contributor Code of Conduct <https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/CODE_OF_CONDUCT.md>`__.
+
+❓ FAQ
+------
+
+Need more information? Please check our `FAQ page <https://www.tahoe-lafs.org/trac/tahoe-lafs/wiki/FAQ>`__.
+
+📄 License
+----------
+
+Copyright 2006-2020 The Tahoe-LAFS Software Foundation
+
+You may use this package under the GNU General Public License, version 2 or, at your option, any later version. You may use this package under the Transitive Grace Period Public Licence, version 1.0, or at your choice, any later version. (You may choose to use this package under the terms of either license, at your option.) See the file `COPYING.GPL <https://github.com/tahoe-lafs/tahoe-lafs/blob/master/COPYING.GPL>`__ for the terms of the GNU General Public License, version 2. See the file `COPYING.TGPPL <https://github.com/tahoe-lafs/tahoe-lafs/blob/master/COPYING.TGPPL.rst>`__ for the terms of the Transitive Grace Period Public Licence, version 1.0.
+
+See `TGPPL.PDF <https://tahoe-lafs.org/~zooko/tgppl.pdf>`__ for why the TGPPL exists, graphically illustrated on three slides.
+
+.. |image0| image:: docs/_static/media/image2.png
+   :width: 3in
+   :height: 0.91667in
+.. |image2| image:: docs/_static//media/image1.png
+   :width: 6.9252in
+   :height: 2.73611in
 .. |readthedocs| image:: http://readthedocs.org/projects/tahoe-lafs/badge/?version=latest
     :alt: documentation status
     :target: http://tahoe-lafs.readthedocs.io/en/latest/?badge=latest

newsfragments/3545.other

@@ -0,0 +1 @@
+new README based on Victoriia's changes after integrating the team's feedback.