-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
accompany each release with a document: entry points for help / input #1370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
In relation to issues #1369, #1355, #433, #1368, #1180, I suggest issue each with each release a list of items where other than core developers can come in and help out. This shall be low hanging fruits which are independant of API changes that may orrur in such a quick development like its currently happening in pandas:
I think by provinding such smaller chunks it could be more attractive for non-fulltime coders to contribute and a better work share between core devs and wider community around. |
I think this is a good suggestion. Ideally we would like to have labels indicating where we'd like to get community involvement and then have the developer page dynamically update to include these issues. However, this does involve a decent amount of work upfront for us to setup and then also more continued time to provide extra context and explanations in the tagged issues. We are very focused on pandas development right now and are stretched very thin so this isn't something we have time to do in a full-fledged way. What I will do is add a "community" label for issues that would be great to have community involvement in and add a blurb on the developer page about those. In cases where we haven't provided a lot of guidance, there are some common sense rules you can follow:
|
So will you add this to: or is there a Sphinx RST source of that page that I could modify? |
I will add it to developers.html |
Added note and link in http://pandas.pydata.org/developers.html |
No description provided.
The text was updated successfully, but these errors were encountered: