support.rst 2.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586
  1. .. include:: global.rst.inc
  2. .. _support:
  3. Support
  4. =======
  5. Please first read the docs, the existing issue tracker issues and mailing
  6. list posts -- a lot of stuff is already documented / explained / discussed /
  7. filed there.
  8. Issue Tracker
  9. -------------
  10. If you've found a bug or have a concrete feature request, please create a new
  11. ticket on the project's `issue tracker`_.
  12. For more general questions or discussions, IRC or mailing list are preferred.
  13. Chat (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. You could use the following link (after connecting, you can change the random
  19. nickname you get by typing "/nick mydesirednickname"):
  20. http://webchat.freenode.net/?randomnick=1&channels=%23borgbackup&uio=MTY9dHJ1ZSY5PXRydWUa8
  21. .. _mailing_list:
  22. Mailing list
  23. ------------
  24. To find out about the mailing list, its topic, how to subscribe, how to
  25. unsubscribe and where you can find the archives of the list, see the
  26. `mailing list homepage
  27. <https://mail.python.org/mailman/listinfo/borgbackup>`_.
  28. Twitter
  29. -------
  30. Follow @borgbackup for announcements. You can also add @borgbackup if you
  31. would like to get retweeted for a borg related tweet.
  32. Please understand that Twitter is not suitable for longer / more complex
  33. discussions - use one of the other channels for that.
  34. Bounties and Fundraisers
  35. ------------------------
  36. We use `BountySource <https://www.bountysource.com/teams/borgbackup>`_ to allow
  37. monetary contributions to the project and the developers, who push it forward.
  38. There, you can give general funds to the borgbackup members (the developers will
  39. then spend the funds as they deem fit). If you do not have some specific bounty
  40. (see below), you can use this as a general way to say "Thank You!" and support
  41. the software / project you like.
  42. If you want to encourage developers to fix some specific issue or implement some
  43. specific feature suggestion, you can post a new bounty or back an existing one
  44. (they always refer to an issue in our `issue tracker`_).
  45. As a developer, you can become a Bounty Hunter and win bounties (earn money) by
  46. contributing to Borg, a free and open source software project.
  47. We might also use BountySource to fund raise for some bigger goals.
  48. .. _security-contact:
  49. Security
  50. --------
  51. In case you discover a security issue, please use this contact for reporting it privately
  52. and please, if possible, use encrypted E-Mail:
  53. Thomas Waldmann <tw@waldmann-edv.de>
  54. GPG Key Fingerprint: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393
  55. The public key can be fetched from any GPG keyserver, but be careful: you must
  56. use the **full fingerprint** to check that you got the correct key.
  57. `Releases <https://github.com/borgbackup/borg/releases>`_ are signed with this GPG key,
  58. please use GPG to verify their authenticity.