1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
|
Contributing to AsyncSSH
========================
Input on AsyncSSH is extremely welcome. Below are some recommendations of
the best ways to contribute.
Asking questions
----------------
If you have a general question about how to use AsyncSSH, you are welcome
to post it to the end-user mailing list at `asyncssh-users@googlegroups.com
<http://groups.google.com/d/forum/asyncssh-users>`_. If you have a question
related to the development of AsyncSSH, you can post it to the development
mailing list at `asyncssh-dev@googlegroups.com
<http://groups.google.com/d/forum/asyncssh-dev>`_.
You are also welcome to use the AsyncSSH `issue tracker
<https://github.com/ronf/asyncssh/issues>`_ to ask questions.
Reporting bugs
--------------
Please use the `issue tracker <https://github.com/ronf/asyncssh/issues>`_
to report any bugs you find. Before creating a new issue, please check the
currently open issues to see if your problem has already been reported.
If you create a new issue, please include the version of AsyncSSH you are
using, information about the OS you are running on and the installed
version of Python and any other libraries that are involved. Please also
include detailed information about how to reproduce the problem, including
any traceback information you were able to collect or other relevant output.
If you have sample code which exhibits the problem, feel free to include
that as well.
If possible, please test against the latest version of AsyncSSH. Also, if
you are testing code in something other than the master branch, it would
be helpful to know if you also see the problem in master.
Requesting feature enhancements
-------------------------------
The `issue tracker <https://github.com/ronf/asyncssh/issues>`_
should also be used to post feature enhancement requests. While I can't
make any promises about what features will be added in the future,
suggestions are always welcome!
Contributing code
-----------------
Before submitting a pull request, please create an issue on the `issue
tracker <https://github.com/ronf/asyncssh/issues>`_ explaining what
functionality you'd like to contribute and how it could be used.
Discussing the approach you'd like to take up front will make it far
more likely I'll be able to accept your changes, or explain what issues
might prevent that before you spend a lot of effort.
If you find a typo or other small bug in the code, you're welcome to
submit a patch without filing an issue first, but for anything larger than
a few lines I strongly recommend coordinating up front.
Any code you submit will need to be provided with a compatible license.
AsyncSSH code is currently released under the `Eclipse Public License
v2.0 <http://www.eclipse.org/legal/epl-2.0/>`_. Before submitting
a pull request, make sure to indicate that you are ok with releasing
your code under this license and how you'd like to be listed in the
contributors list.
Branches
--------
There are two long-lived branches in AsyncSSH:
* The master branch is intended to contain the latest stable version
of the code. All official versions of AsyncSSH are released from
this branch, and each release has a corresponding tag added
matching its release number.
* The develop branch is intended to contain new features and bug fixes
ready to be tested before being added to an official release. APIs
in the develop branch may be subject to change until they are
migrated back to master, and there's no guarantee of backward
compatibility in this branch. However, pulling from this branch
will provide early access to new functionality and a chance to
influence this functionality before it is released. Also, all
pull requests should be submitted against this branch.
|
