Skip to content

Introduce the concept of sponsors #903

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Mar 5, 2019
Merged

Introduce the concept of sponsors #903

merged 2 commits into from
Mar 5, 2019

Conversation

brettcannon
Copy link
Member

No description provided.

@brettcannon brettcannon requested a review from willingc March 1, 2019 22:08
willingc
willingc approved these changes Mar 2, 2019
View reviewed changes
Copy link
Contributor

@willingc willingc left a comment

Choose a reason for hiding this comment

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

Thanks @brettcannon. A small wording suggestion.

@jdemeyer
Copy link
Contributor

jdemeyer commented Mar 3, 2019 •
edited
Loading

If "The sponsor's job is to provide guidance to the PEP
author to help them through the PEP process (somewhat acting like mentor)", then wouldn't it better be called "mentor" instead of "sponsor"? To me, the word "sponsor" conveys a somewhat different meaning, namely that the sponsor should also strongly support the actual PEP.

@jdemeyer
Copy link
Contributor

jdemeyer commented Mar 3, 2019

We should just be careful not to make it more difficult for non-core developers to submit a PEP. This should help people to get a PEP drafted instead of being an additional hurdle.

@willingc
Copy link
Contributor

willingc commented Mar 3, 2019

We should just be careful not to make it more difficult for non-core developers to submit a PEP. This should help people to get a PEP drafted instead of being an additional hurdle.

Agreed. The intent is to help non-core developers to navigate the PEP process.

gvanrossum
gvanrossum reviewed Mar 4, 2019
View reviewed changes
pep-0001.txt
@@ -488,6 +490,7 @@ optional and are described below. All other headers are required. ::
PEP: <pep number>
Title: <pep title>
Author: <list of authors' real names and optionally, email addrs>
* Sponsor: <real name of core developer sponsoring>
Copy link
Member

Choose a reason for hiding this comment

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

Beware that this requires a change to the pep2html.py script.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yep, that's the next step before merging. 😄 I just wanted to make sure the idea had traction and support before I did the coding work.

Copy link
Member Author

Choose a reason for hiding this comment

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

#911

@brettcannon brettcannon mentioned this pull request Mar 5, 2019
Merged
@brettcannon brettcannon merged commit c58d32c into master Mar 5, 2019
@brettcannon brettcannon deleted the sponsor-idea branch March 5, 2019 01:34
@brettcannon
Copy link
Member Author

Thanks everyone for the reviews! I'll email python-dev shortly about the change.

@willingc willingc mentioned this pull request Mar 6, 2019
Open
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@willingc willingc willingc approved these changes

@gvanrossum gvanrossum gvanrossum left review comments

@warsaw warsaw warsaw approved these changes

@ncoghlan ncoghlan ncoghlan approved these changes

Assignees
No one assigned
Labels
CLA signed
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
7 participants
@brettcannon @jdemeyer @willingc @warsaw @ncoghlan @gvanrossum @the-knights-who-say-ni