borg/docs/support.rst

.. include:: global.rst.inc
.. _support:

Support
=======

Please first read the docs, the existing issue tracker issues and mailing
list posts -- a lot of stuff is already documented / explained / discussed /
filed there.

Issue Tracker
-------------

If you've found a bug or have a concrete feature request, please create a new
ticket on the project's `issue tracker`_.

For more general questions or discussions, IRC or mailing list are preferred.

Chat (IRC)
----------
Join us on channel #borgbackup on chat.freenode.net.

As usual on IRC, just ask or tell directly and then patiently wait for replies.
Stay connected.

You could use the following link (after connecting, you can change the random
nickname you get by typing "/nick mydesirednickname"):

http://webchat.freenode.net/?randomnick=1&channels=%23borgbackup&uio=MTY9dHJ1ZSY5PXRydWUa8


Mailing list
------------

To find out about the mailing list, its topic, how to subscribe, how to
unsubscribe and where you can find the archives of the list, see the
`mailing list homepage
<https://mail.python.org/mailman/listinfo/borgbackup>`_.

Bounties and Fundraisers
------------------------

We use `BountySource <https://www.bountysource.com/teams/borgbackup>`_ to allow
monetary contributions to the project and the developers, who push it forward.

There, you can give general funds to the borgbackup members (the developers will
then spend the funds as they deem fit). If you do not have some specific bounty
(see below), you can use this as a general way to say "Thank You!" and support
the software / project you like.

If you want to encourage developers to fix some specific issue or implement some
specific feature suggestion, you can post a new bounty or back an existing one
(they always refer to an issue in our `issue tracker`_).

As a developer, you can become a Bounty Hunter and win bounties (earn money) by
contributing to |project_name|, a free and open source software project.

We might also use BountySource to fund raise for some bigger goals.
deduplicate and refactor the docs README.rst (shown on github and also at the start of the html docs) shall be like an elevator speech - convince readers in a very short time. this is most important, everything else can come after we got the reader's interest. include README into docs to avoid duplication. also include CHANGES into docs. add developer docs, move examples from tox.ini there add separate support docs remove glossary, most of what was there can be understood by an admin from context move attic and compatibility note to the end 2015-08-06 10:59:51 +00:00			`.. include:: global.rst.inc`
			`.. _support:`

			`Support`
			`=======`

docs: updates and fixes 2016-02-01 02:22:02 +00:00			`Please first read the docs, the existing issue tracker issues and mailing`
			`list posts -- a lot of stuff is already documented / explained / discussed /`
docs: improve faq and support section 2015-08-29 02:16:03 +00:00			`filed there.`
compression: update / refine docs 2015-08-15 13:45:15 +00:00
deduplicate and refactor the docs README.rst (shown on github and also at the start of the html docs) shall be like an elevator speech - convince readers in a very short time. this is most important, everything else can come after we got the reader's interest. include README into docs to avoid duplication. also include CHANGES into docs. add developer docs, move examples from tox.ini there add separate support docs remove glossary, most of what was there can be understood by an admin from context move attic and compatibility note to the end 2015-08-06 10:59:51 +00:00			`Issue Tracker`
			`-------------`

			`If you've found a bug or have a concrete feature request, please create a new`
docs: improve faq and support section 2015-08-29 02:16:03 +00:00			ticket on the project's `issue tracker`_.
deduplicate and refactor the docs README.rst (shown on github and also at the start of the html docs) shall be like an elevator speech - convince readers in a very short time. this is most important, everything else can come after we got the reader's interest. include README into docs to avoid duplication. also include CHANGES into docs. add developer docs, move examples from tox.ini there add separate support docs remove glossary, most of what was there can be understood by an admin from context move attic and compatibility note to the end 2015-08-06 10:59:51 +00:00
			`For more general questions or discussions, IRC or mailing list are preferred.`

update frontpage / support docs less items in frontpage link list add IRC chat link minor other changes 2016-07-04 20:37:24 +00:00			`Chat (IRC)`
			`----------`
deduplicate and refactor the docs README.rst (shown on github and also at the start of the html docs) shall be like an elevator speech - convince readers in a very short time. this is most important, everything else can come after we got the reader's interest. include README into docs to avoid duplication. also include CHANGES into docs. add developer docs, move examples from tox.ini there add separate support docs remove glossary, most of what was there can be understood by an admin from context move attic and compatibility note to the end 2015-08-06 10:59:51 +00:00			`Join us on channel #borgbackup on chat.freenode.net.`

			`As usual on IRC, just ask or tell directly and then patiently wait for replies.`
			`Stay connected.`

support docs: add freenode web chat link, fixes #1175 2016-06-24 19:48:21 +00:00			`You could use the following link (after connecting, you can change the random`
update frontpage / support docs less items in frontpage link list add IRC chat link minor other changes 2016-07-04 20:37:24 +00:00			`nickname you get by typing "/nick mydesirednickname"):`
support docs: add freenode web chat link, fixes #1175 2016-06-24 19:48:21 +00:00
			`http://webchat.freenode.net/?randomnick=1&channels=%23borgbackup&uio=MTY9dHJ1ZSY5PXRydWUa8`


deduplicate and refactor the docs README.rst (shown on github and also at the start of the html docs) shall be like an elevator speech - convince readers in a very short time. this is most important, everything else can come after we got the reader's interest. include README into docs to avoid duplication. also include CHANGES into docs. add developer docs, move examples from tox.ini there add separate support docs remove glossary, most of what was there can be understood by an admin from context move attic and compatibility note to the end 2015-08-06 10:59:51 +00:00			`Mailing list`
			`------------`

rephrase the mailing list section 2015-12-13 20:59:33 +00:00			`To find out about the mailing list, its topic, how to subscribe, how to`
			`unsubscribe and where you can find the archives of the list, see the`
			`mailing list homepage
			<https://mail.python.org/mailman/listinfo/borgbackup>`_.
new mailing list borgbackup@python.org also: remove mailing list and irc channel address from development docs, it is enough to have this information on the main page and on the support page. 2015-11-18 14:40:23 +00:00
support docs: write some words about BountySource 2015-08-20 22:25:24 +00:00			`Bounties and Fundraisers`
			`------------------------`

			We use `BountySource <https://www.bountysource.com/teams/borgbackup>`_ to allow
			`monetary contributions to the project and the developers, who push it forward.`

			`There, you can give general funds to the borgbackup members (the developers will`
			`then spend the funds as they deem fit). If you do not have some specific bounty`
			`(see below), you can use this as a general way to say "Thank You!" and support`
			`the software / project you like.`

			`If you want to encourage developers to fix some specific issue or implement some`
docs: improve faq and support section 2015-08-29 02:16:03 +00:00			`specific feature suggestion, you can post a new bounty or back an existing one`
			(they always refer to an issue in our `issue tracker`_).
support docs: write some words about BountySource 2015-08-20 22:25:24 +00:00
docs: improve faq and support section 2015-08-29 02:16:03 +00:00			`As a developer, you can become a Bounty Hunter and win bounties (earn money) by`
			`contributing to \|project_name\|, a free and open source software project.`
support docs: write some words about BountySource 2015-08-20 22:25:24 +00:00
			`We might also use BountySource to fund raise for some bigger goals.`