@@ -23,16 +23,16 @@ contribution.
23
23
Project Management
24
24
------------------
25
25
26
- Setuptools is maintained primarily in Github at `this home
26
+ Setuptools is maintained primarily in GitHub at `this home
27
27
<https://github.com/pypa/setuptools>`_. Setuptools is maintained under the
28
28
Python Packaging Authority (PyPA) with several core contributors. All bugs
29
- for Setuptools are filed and the canonical source is maintained in Github .
29
+ for Setuptools are filed and the canonical source is maintained in GitHub .
30
30
31
31
User support and discussions are done through the issue tracker (for specific)
32
- issues, through the distutils-sig mailing list, or on IRC (Freenode) at
32
+ issues, through the ` distutils-sig mailing list <https://mail.python.org/mailman3/lists/distutils-sig.python.org/>`_ , or on IRC (Freenode) at
33
33
#pypa.
34
34
35
- Discussions about development happen on the pypa-dev mailing list or on
35
+ Discussions about development happen on the distutils-sig mailing list or on
36
36
`Gitter <https://gitter.im/pypa/setuptools>`_.
37
37
38
38
-----------------
@@ -44,7 +44,7 @@ describing the motivation behind making changes. First search to see if a
44
44
ticket already exists for your issue. If not, create one. Try to think from
45
45
the perspective of the reader. Explain what behavior you expected, what you
46
46
got instead, and what factors might have contributed to the unexpected
47
- behavior. In Github , surround a block of code or traceback with the triple
47
+ behavior. In GitHub , surround a block of code or traceback with the triple
48
48
backtick "\`\`\`" so that it is formatted nicely.
49
49
50
50
Filing a ticket provides a forum for justification, discussion, and
0 commit comments