2
0

support.rst 1.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  1. .. include:: global.rst.inc
  2. .. _support:
  3. Support
  4. =======
  5. Please first read the docs and the FAQ section in the docs, a lot of stuff is
  6. documented / explained there.
  7. Issue Tracker
  8. -------------
  9. If you've found a bug or have a concrete feature request, please create a new
  10. ticket on the project's `issue tracker`_ (after checking whether someone else
  11. already has reported the same thing).
  12. For more general questions or discussions, IRC or mailing list are preferred.
  13. IRC
  14. ---
  15. Join us on channel #borgbackup on chat.freenode.net.
  16. As usual on IRC, just ask or tell directly and then patiently wait for replies.
  17. Stay connected.
  18. Mailing list
  19. ------------
  20. There is a mailing list for Borg on librelist_ that you can use for feature
  21. requests and general discussions about Borg. A mailing list archive is
  22. available `here <http://librelist.com/browser/borgbackup/>`_.
  23. To subscribe to the list, send an email to borgbackup@librelist.com and reply
  24. to the confirmation mail.
  25. To unsubscribe, send an email to borgbackup-unsubscribe@librelist.com and reply
  26. to the confirmation mail.
  27. Bounties and Fundraisers
  28. ------------------------
  29. We use `BountySource <https://www.bountysource.com/teams/borgbackup>`_ to allow
  30. monetary contributions to the project and the developers, who push it forward.
  31. There, you can give general funds to the borgbackup members (the developers will
  32. then spend the funds as they deem fit). If you do not have some specific bounty
  33. (see below), you can use this as a general way to say "Thank You!" and support
  34. the software / project you like.
  35. If you want to encourage developers to fix some specific issue or implement some
  36. specific feature suggestion, you can post a bounty or back an existing one (they
  37. always refer to an issue in our `issue tracker`_).
  38. As a developer, you can become a Bounty Hunter and win bounties by contributing
  39. to |project_name|, a free and open source software project.
  40. We might also use BountySource to fund raise for some bigger goals.