| 1 |
Contact |
| 2 |
======= |
| 3 |
|
| 4 |
You can get in touch with the developer & user community in any of the |
| 5 |
following ways: |
| 6 |
|
| 7 |
* Bug reports and feature requests: first read `contribution-guide.org |
| 8 |
<https://contribution-guide.org>`_, then check out our `GitHub page |
| 9 |
<https://github.com/pyinvoke/invoke>`_. |
| 10 |
* Blog posts: https://bitprophet.org/categories/invoke/ |
| 11 |
* Twitter: you've got a few options here: |
| 12 |
|
| 13 |
* `@bitprophet <https://twitter.com/bitprophet>`_ is the canonical source |
| 14 |
for updates, but is also the developer's personal account (hint: you can |
| 15 |
turn off retweets and only see original content!) |
| 16 |
* `@pyfabric <https://twitter.com/pyfabric>`_ is a much lower-traffic, |
| 17 |
announcement-only account that also serves the `Fabric |
| 18 |
<https://fabfile.org>`_ project; given how much Fabric is built directly |
| 19 |
on top of Invoke, many of the posts will be relevant to Invoke-only |
| 20 |
users. |
| 21 |
* `@pyinvoke <https://twitter.com/pyinvoke>`_ was set up for |
| 22 |
Invoke-specific announcements, but it only has a dozen followers so we've |
| 23 |
unfortunately let it languish. Should we automate our release process |
| 24 |
further, this account may get posts again, and we'll update this page |
| 25 |
accordingly. |