Pillow/docs/about.rst

About
=====

Goals
-----

The fork author's goal is to foster and support active development of PIL through:

- Continuous integration testing via `Travis CI`_ and `AppVeyor`_
- Publicized development activity on `GitHub`_
- Regular releases to the `Python Package Index`_

.. _Travis CI: https://travis-ci.org/python-pillow/Pillow
.. _AppVeyor: https://ci.appveyor.com/project/Python-pillow/pillow
.. _GitHub: https://github.com/python-pillow/Pillow
.. _Python Package Index: https://pypi.python.org/pypi/Pillow

License
-------

Like PIL, Pillow is `licensed under the MIT-like open source PIL Software License <https://raw.githubusercontent.com/python-pillow/Pillow/master/LICENSE>`_

Why a fork?
-----------

PIL is not setuptools compatible. Please see `this Image-SIG post`_ for a more detailed explanation. Also, PIL's current bi-yearly (or greater) release schedule is too infrequent to accommodate the large number and frequency of issues reported.

.. _this Image-SIG post: https://mail.python.org/pipermail/image-sig/2010-August/006480.html

What about PIL?
---------------

.. note::

    Prior to Pillow 2.0.0, very few image code changes were made. Pillow 2.0.0
    added Python 3 support and includes many bug fixes from many contributors.

As more time passes since the last PIL release, the likelihood of a new PIL release decreases. However, we've yet to hear an official "PIL is dead" announcement. So if you still want to support PIL, please `report issues here first`_, then `open corresponding Pillow tickets here`_.

.. _report issues here first: https://bitbucket.org/effbot/pil-2009-raclette/issues

.. _open corresponding Pillow tickets here: https://github.com/python-pillow/Pillow/issues

Please provide a link to the first ticket so we can track the issue(s) upstream.
Shorten title; Clarify these are rst files - Shorten "About Pillow" to Pillow (the reader likely already knows we're talking about Pillow) - Clarify reference to rst files by using rst extension; Sphinx seems to recognize either convention, but humans (like me) forget exactly what Sphinx is doing sometimes. 2015-09-30 13:21:52 +03:00			`About`
			`=====`
Copy/move a bunch of README content to the doc site 2013-10-09 04:13:06 +04:00
			`Goals`
			`-----`

Wording [ci skip] 2015-04-04 15:41:58 +03:00			`The fork author's goal is to foster and support active development of PIL through:`
Copy/move a bunch of README content to the doc site 2013-10-09 04:13:06 +04:00
Added AppVeyor to the continuous integration description [ci skip] 2016-02-02 15:46:23 +03:00			- Continuous integration testing via `Travis CI`_ and `AppVeyor`_
Copy/move a bunch of README content to the doc site 2013-10-09 04:13:06 +04:00			- Publicized development activity on `GitHub`_
			- Regular releases to the `Python Package Index`_

Replace python-imaging with python-pillow (but yet not Coveralls) 2014-06-03 14:02:44 +04:00			`.. _Travis CI: https://travis-ci.org/python-pillow/Pillow`
Added AppVeyor to the continuous integration description [ci skip] 2016-02-02 15:46:23 +03:00			`.. _AppVeyor: https://ci.appveyor.com/project/Python-pillow/pillow`
Replace python-imaging with python-pillow (but yet not Coveralls) 2014-06-03 14:02:44 +04:00			`.. _GitHub: https://github.com/python-pillow/Pillow`
Copy/move a bunch of README content to the doc site 2013-10-09 04:13:06 +04:00			`.. _Python Package Index: https://pypi.python.org/pypi/Pillow`

Wording [ci skip] 2014-02-20 03:39:20 +04:00			`License`
			`-------`

Added Pillow to LICENSE [ci skip] 2016-04-02 02:41:10 +03:00			Like PIL, Pillow is `licensed under the MIT-like open source PIL Software License <https://raw.githubusercontent.com/python-pillow/Pillow/master/LICENSE>`_
Wording [ci skip] 2014-02-20 03:39:20 +04:00
Copy/move a bunch of README content to the doc site 2013-10-09 04:13:06 +04:00			`Why a fork?`
			`-----------`

Wording [ci skip] 2015-04-04 15:41:03 +03:00			PIL is not setuptools compatible. Please see `this Image-SIG post`_ for a more detailed explanation. Also, PIL's current bi-yearly (or greater) release schedule is too infrequent to accommodate the large number and frequency of issues reported.
Copy/move a bunch of README content to the doc site 2013-10-09 04:13:06 +04:00
			`.. _this Image-SIG post: https://mail.python.org/pipermail/image-sig/2010-August/006480.html`

Wording [ci skip] 2014-02-20 03:39:20 +04:00			`What about PIL?`
			`---------------`
Copy/move a bunch of README content to the doc site 2013-10-09 04:13:06 +04:00
			`.. note::`

			`Prior to Pillow 2.0.0, very few image code changes were made. Pillow 2.0.0`
			`added Python 3 support and includes many bug fixes from many contributors.`

Wording [ci skip] 2015-04-04 15:41:03 +03:00			As more time passes since the last PIL release, the likelihood of a new PIL release decreases. However, we've yet to hear an official "PIL is dead" announcement. So if you still want to support PIL, please `report issues here first`_, then `open corresponding Pillow tickets here`_.
Copy/move a bunch of README content to the doc site 2013-10-09 04:13:06 +04:00
			`.. _report issues here first: https://bitbucket.org/effbot/pil-2009-raclette/issues`

Wording [ci skip] 2015-04-04 15:41:03 +03:00			`.. _open corresponding Pillow tickets here: https://github.com/python-pillow/Pillow/issues`
Copy/move a bunch of README content to the doc site 2013-10-09 04:13:06 +04:00
Wording [ci skip] 2015-04-04 15:41:03 +03:00			`Please provide a link to the first ticket so we can track the issue(s) upstream.`