8000 Move "Request a new feature" from How-to to Contributing by timhoffm · Pull Request #17842 · matplotlib/matplotlib · GitHub
[go: up one dir, main page]

Skip to content

Move "Request a new feature" from How-to to Contributing #17842

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

Merged
merged 1 commit into from
Jul 15, 2020

Conversation

timhoffm
Copy link
Member
@timhoffm timhoffm commented Jul 5, 2020

PR Summary

Part of moving all contribution related info from How-to to the developers guide. (Related/follow up to #17837 and #17825.)

I've removed mentioning the mailing list:

The best way to get started is to email the developer mailing list <matplotlib-devel@python.org>_ for discussion.

I suppose this is just outdated. One could add it as an alternative to the issue tracker, but OTOH the issue tracker makes management of feature requests much simpler, and personally, I would not want to have feature requests coming via the malinglist.

Not mentioning the mailinglist here was discussed and approved in the last dev call.

Comment on lines 57 to 58
The Matplotlib developers will give feedback on the feature proposal. After
acceptance, the feature can be implemented. Since Matplotlib is an open source
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does acceptance mean? this may be a longer discussion for the call, but should be pinned down.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want to express that not every feature request may be deemed an appropriate extension of Matplotlib by core developers. We welcome if somebody proposes a feature and also implements it, but it may be good to first get feedback before you start implementing.

I don't want to go into possible details of the feedback/approval/acceptance process here.

Thinking again, I think we can leave the sentence out.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"If there is significant support, you can try implementing the feature"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the proposal. I have the impression that it might fee a little intimidating. "significant" is a strong word and may be a barrier for people considering a propsal. Also, the phrasing might give the false impression that the proposer must also implement it.

I'm going with removing the sentence. I think it's clear enough; and it's also not the end of the world if a PR is opened before a feature is fully discussed. Sometimes you may even need it to illustrate the intention.

@timhoffm timhoffm force-pushed the doc-feature-request branch from 6e393fb to 5b213a5 Compare July 14, 2020 19:11
@jklymak jklymak merged commit 5a9191b into matplotlib:master Jul 15, 2020
@timhoffm timhoffm deleted the doc-feature-request branch July 16, 2020 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0