Skip to content
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

Pledge -> statement? #1

Closed
takluyver opened this issue Apr 20, 2016 · 2 comments
Closed

Pledge -> statement? #1

takluyver opened this issue Apr 20, 2016 · 2 comments

Comments

@takluyver
Copy link
Member

Pledge:

A solemn binding promise to do, give, or refrain from doing something

It sounds a bit dramatic and self-sacrificing. That has its good points - a 'pledge' might get more attention than a 'statement'. But I think it will also be harder to get people to sign if it sounds like they're promising to do something risky.

I favour publicly calling this a 'statement', with the implication that we're just highlighting what we were already going to do. The common base level should be "we won't support Python 2 beyond 2020", which doesn't feel controversial or dramatic. Then individual projects can add details to go further, e.g. bugfixes only for Python 2, or ending support before 2020.

@Carreau
Copy link
Member

Carreau commented Apr 20, 2016

Sure no problem with renaming it. You are the english speaker.

Can we rename an org ?

@Carreau
Copy link
Member

Carreau commented Apr 20, 2016

Also just playing around with timelines:

screen shot 2016-04-20 at 12 27 33

(random dates of course)

@takluyver takluyver mentioned this issue Apr 28, 2016
takluyver pushed a commit that referenced this issue Sep 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants