Skip to content

Conversation

@filipesaraiva
Copy link
Contributor

@filipesaraiva filipesaraiva commented Apr 20, 2020

If you're adding a project to the Python 3 statement, please ensure you have:

  • Discussed dropping Python 2 support with all maintainers
  • Discussed signing the statement with all maintainers

About the 2 points above, see this commit in Cantor repository at KDE Invent.

  • Added a suitable logo if the project has one
    • Approximately square logos generally fit better than banners
    • Compressed the logo to save bandwidth (run scripts/squash-images.sh on it)
  • Checked the Netlify preview made from the pull request

@takluyver
Copy link
Member

@Carreau @tacaswell @asmeurer - how do we feel about adding new projects to the statement? I had kind of thought it was complete once we hit 2020, but we never updated the page to say so, and I don't think there's any harm in adding new projects now.

@hugovk
Copy link
Contributor

hugovk commented Apr 22, 2020

This project got a shoutout from the 2.7 release manager in the final 2.7.18 release announcement:

Python 3 would be nowhere without the critical work of the wider community. Library
maintainers followed CPython by maintaining Python 2 support for many years but also threw
their weight behind the Python 3 statement (https://python3statement.org). Linux distributors
chased Python 2 out of their archives. Users migrated hundreds of millions of lines of
code, developed porting guides, and kept Python 2 in their brain while Python 3 gained 10
years of improvements.

https://mail.python.org/archives/list/python-dev@python.org/thread/OFCIETIXLX34X7FVK5B5WPZH22HXV342/#OFCIETIXLX34X7FVK5B5WPZH22HXV342

This project definitely helped, thanks to everyone involved!

@Carreau
Copy link
Member

Carreau commented Apr 22, 2020

how do we feel about adding new projects to the statement? I had kind of thought it was complete once we hit 2020, but we never updated the page to say so, and I don't think there's any harm in adding new projects now.

I'm ok with that as well, the project says "drop support for Python 2.7 no later than 2020" and we are still in 2020, so project still have 6 month ? We can update the language slightly and I would also keep pointing to resource and guideline into staying up to data with Python version (NEP 29) as a guideline as to what some community project are doing.

A note that the project is now under less maintenance and the we may not renew domain/hosting...

This project got a shoutout from the 2.7 release manager in the final 2.7.18 release announcement:

Whooo ! Happy it had it effect, time to write a "python4statement" :-)

Copy link
Collaborator

@tacaswell tacaswell left a comment

Choose a reason for hiding this comment

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

I am 👍 on continuing to add projects for the rest of 2020.

@mscuthbert
Copy link
Collaborator

While no site can be renewed forever, drop me a note if $$ is an issue for domain renewal costs -- happy to help keep it going for a few more years; at least till MacOS is shipping with Python 3.

@takluyver
Copy link
Member

Thanks @mscuthbert . I believe @asmeurer has been kindly paying for the domain out of his own pocket so far. Its current registration runs until November. Aaron, thank-you, and please speak up if you want to stop paying it yourself, or split the bill.

Anyway, it sounds like we're happy to keep adding projects, and this looks good to me, so in it goes.

If anyone has a bright idea how to nicely rank non-Github projects (such as Cantor), please open an issue about it.

@takluyver takluyver merged commit c9c8571 into python3statement:master Apr 23, 2020
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

Successfully merging this pull request may close these issues.

6 participants