Skip to content

Commit 67d75f3

Browse files
authored
DOC: replace developer meeting with contributor community page (#48990)
1 parent 56d82a9 commit 67d75f3

File tree

4 files changed

+119
-32
lines changed

4 files changed

+119
-32
lines changed

doc/redirects.csv

+1
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,7 @@ contributing_docstring,development/contributing_docstring
4545
developer,development/developer
4646
extending,development/extending
4747
internals,development/internals
48+
development/meeting,development/community
4849

4950
# api moved function
5051
reference/api/pandas.io.json.json_normalize,pandas.json_normalize

doc/source/development/community.rst

+117
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,117 @@
1+
.. _community:
2+
3+
=====================
4+
Contributor community
5+
=====================
6+
7+
pandas is a community-driven open source project developed by a large group
8+
of `contributors <https://github.com/pandas-dev/pandas/graphs/contributors>`_
9+
and a smaller group of `maintainers <https://pandas.pydata.org/about/team.html>`_.
10+
The pandas leadership has made a strong commitment to creating an open,
11+
inclusive, and positive community. Please read the pandas `Code of Conduct
12+
<https://pandas.pydata.org/community/coc.html>`_ for guidance on how to
13+
interact with others in a way that makes the community thrive.
14+
15+
We offer several meetings and communication channels to share knowledge and
16+
connect with others within the pandas community.
17+
18+
Community meeting
19+
-----------------
20+
21+
The pandas Community Meeting is a regular sync meeting for the project's
22+
maintainers which is open to the community. Everyone is welcome to attend and
23+
contribute to conversations.
24+
25+
The meetings take place on the second Wednesday of each month at 18:00 UTC.
26+
27+
The minutes of past meetings are available in `this Google Document <https://docs.google.com/document/d/1tGbTiYORHiSPgVMXawiweGJlBw5dOkVJLY-licoBmBU/edit?usp=sharing>`__.
28+
29+
30+
New contributor meeting
31+
-----------------------
32+
33+
On the third Wednesday of the month, we hold meetings to welcome and support
34+
new contributors in our community.
35+
36+
| 👋 you all are invited
37+
| 💬 everyone can present (add yourself to the hackMD agenda)
38+
| 👀 anyone can sit in and listen
39+
40+
Attendees are new and experienced contributors, as well as a few maintainers.
41+
We aim to answer questions about getting started, or help with work in
42+
progress when possible, as well as get to know each other and share our
43+
learnings and experiences.
44+
45+
The agenda for the next meeting and minutes of past meetings are available in
46+
`this HackMD <https://hackmd.io/@pandas-dev/HJgQt1Tei>`__.
47+
48+
Calendar
49+
--------
50+
51+
This calendar shows all the community meetings. Our community meetings are
52+
ideal for anyone wanting to contribute to pandas, or just curious to know how
53+
current development is going.
54+
55+
.. raw:: html
56+
57+
<iframe src="https://calendar.google.com/calendar/embed?src=pgbn14p6poja8a1cf2dv2jhrmg%40group.calendar.google.com" style="border: 0" width="800" height="600" frameborder="0" scrolling="no"></iframe>
58+
59+
You can subscribe to this calendar with the following links:
60+
61+
* `iCal <https://calendar.google.com/calendar/ical/pgbn14p6poja8a1cf2dv2jhrmg%40group.calendar.google.com/public/basic.ics>`__
62+
* `Google calendar <https://calendar.google.com/calendar/[email protected]>`__
63+
64+
Additionally, we'll sometimes have one-off meetings on specific topics.
65+
These will be published on the same calendar.
66+
67+
`GitHub issue tracker <https://github.com/pandas-dev/pandas/issues>`_
68+
----------------------------------------------------------------------
69+
70+
The pandas contributor community conducts conversations mainly via this channel.
71+
Any community member can open issues to:
72+
73+
- Report bugs, e.g. "I noticed the behavior of a certain function is
74+
incorrect"
75+
- Request features, e.g. "I would like this error message to be more readable"
76+
- Request documentation improvements, e.g. "I found this section unclear"
77+
- Ask questions, e.g. "I noticed the behavior of a certain function
78+
changed between versions. Is this expected?".
79+
80+
Ideally your questions should be related to how pandas work rather
81+
than how you use pandas. `StackOverflow <https://stackoverflow.com/>`_ is
82+
better suited for answering usage questions, and we ask that all usage
83+
questions are first asked on StackOverflow. Thank you for respecting are
84+
time and wishes. 🙇
85+
86+
Maintainers and frequent contributors might also open issues to discuss the
87+
ongoing development of the project. For example:
88+
89+
- Report issues with the CI, GitHub Actions, or the performance of pandas
90+
- Open issues relating to the internals
91+
- Start roadmap discussion aligning on proposals what to do in future
92+
releases or changes to the API.
93+
- Open issues relating to the project's website, logo, or governance
94+
95+
The developer mailing list
96+
--------------------------
97+
98+
The pandas mailing list `[email protected] <mailto://pandas-dev@python
99+
.org>`_ is used for long form
100+
conversations and to engages people in the wider community who might not
101+
be active on the issue tracker but we would like to include in discussions.
102+
103+
Community slack
104+
---------------
105+
106+
We have a chat platform for contributors, maintainers and potential
107+
contributors. This is not a space for user questions, rather for questions about
108+
contributing to pandas. The slack is a private space, specifically meant for
109+
people who are hesitant to bring up their questions or ideas on a large public
110+
mailing list or GitHub.
111+
112+
If this sounds like the right place for you, you are welcome to join! Email us
113+
at `[email protected] <mailto://[email protected]>`_ and let us
114+
know that you read and agree to our `Code of Conduct <https://pandas.pydata.org/community/coc.html>`_
115+
😉 to get an invite. And please remember the slack is not meant to replace the
116+
mailing list or issue tracker - all important announcements and conversations
117+
should still happen there.

doc/source/development/index.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -23,4 +23,4 @@ Development
2323
developer
2424
policies
2525
roadmap
26-
meeting
26+
community

doc/source/development/meeting.rst

-31
This file was deleted.

0 commit comments

Comments
 (0)