[Python-Dev] Re: Sponsoring Python development via the PSF

[Ewa Jodlowska]

I'll comment on two posts in one go :)

On Wed, Jun 26, 2019 at 12:12 PM Ivan Pozdeev via Python-Dev <
python-dev@python.org> wrote:

> On 26.06.2019 10:41, Pau Freixes wrote:
>
> Hi,
>
> Why not the other way around? Having from the very beginning a clear goal
> with a speculative budget, companies would have visibilitty about the end
> goal of their donations. Otherwise is a bit a leap of faith.
>
>
> Over time, this will be a combination of both: directed towards specific
projects and supporting the general Python development fund. One of the
current goals of the PSF is to better support core development. We are just
starting with this support effort. Our goal overtime is to create a
spending plan with the help of the Steering Council, which will involve a
lot more than just individual donations. In the meantime, this fund is
there for those that want to donate specifically to things that support
Python development and maintenance. To what Brett said, if we see many
individual donors contributing, we can move faster to provide support. This
is our joined effort to start *somewhere*.


+1. That's why I never donate to charity. I can't see or control what my
> money is going to be used for.
>

The PSF strives to be transparent with its money and we continue to improve
upon that.  We go over our finances in detail at PyCon and EuroPython at
our member meetings. In addition to in person events, we recently published
our first Annual Impact Report (
https://www.python.org/psf/annual-report/2019/) and we'll continue to
upload our financials online (
https://www.python.org/psf/records/board/treasurer/) (2018 should be out
soon).

With regards to what the money will be used for: directed funding can only
be used for what it is intended for. Even though Python development and
maintenance is still a pretty broad category, the PSF will only use this
funding for that category.

For a non-profit there is also a downside to very specific fundraising. For
example, if we directed this donation to the September Core Dev Sprint in
London and received $100,000 in donations, we would only be able to use
that money for *that* specific thing. Even if we ordered fancy lunches and
dinners for the core devs daily, I am not sure we'd be able to spend all
that money :) At that point we'd also be asking ourselves if we are using
the funds to the best of their ability. The remaining funds would be
restricted and we wouldn't be able to use them for other important things.
Keeping it a bit general is helpful to ensure the money is used where it is
needed.

It is a bit of a leap of faith as well since we have never done this before
for core development. I do hope the PSF can soon instill that missing trust.

If anyone has any questions, don't hesitate to reach out!
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/VTYR5K7YZLLNQ5ZIM2W4AAGPCGGQ53ED/

[Python-Dev] Re: Sponsoring Python development via the PSF

[Ewa Jodlowska]

On Wed, Jun 26, 2019 at 8:28 PM Wes Turner  wrote:

> When companies donate as PyCon sponsors (and get brand recognition) do
> those donations also go to PSF?


Yes, the PSF produces PyCon. PyCon sponsorships are used to help offset
PyCon expenses. If PyCon has a surplus, it is the PSF's revenue. PyCon's
surplus is the biggest source of revenue for the PSF.

>
>
> You can add the **Python Software Foundation** to a Charity Navigator
> "Giving Basket" and get one receipt:
> https://www.charitynavigator.org/index.cfm?bay=search.profile&ein=043594598
>
> "Charity Navigator's Methodology"
>
> https://www.charitynavigator.org/index.cfm?bay=content.view&cpid=5593#rating
>
>
> Is there any way to donate cryptocurrency to PSF yet?
>

Currently, we do not.

>
> All of these orgs accept BTC donations:
> https://en.bitcoin.it/wiki/Donation-accepting_organizations_and_projects
>
> Just sending to an address doesn't get you a receipt for tax purposes;
> there are firms that support donations by exchanging for USD at that time
> and depositing to the configured account.
>

That's good to know! If you know more info on this, please let me know. I
can share it with our accounting team to review.
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/H6S63ZYTIFPUQTOJGEA54C7AH2MWSGEZ/

[Python-Dev] Re: Sponsoring Python development via the PSF

[Ewa Jodlowska]

On Thu, Jun 27, 2019 at 11:16 AM Wes Turner  wrote:

>
> From GuideStar (which, like Charity Navigator, also has nonprofit
> evaluation criteria)
>
> https://trust.guidestar.org/bitcoin-what-nonprofits-need-to-know-and-how-it-might-give-your-fundraising-a-competitive-advantage
> :
>
> > Accepting donations in Bitcoin can reduce the financial transaction fees
> a nonprofit owes.  With Bitcoin, the costs are significantly lower compared
> to checks, credit cards, and other digital options, and if your
> organization is a registered 501(c)(3), there are zero transaction fees on
> platforms such as Coinbase or Bitpay.  There is also no risk of bank
> charges accruing to the nonprofit in the case of a donor using a fraudulent
> credit card.
>
> * Merch: It may be worth accepting cryptocurrency payments for PSF merch
> like T-Shirts, Mugs, Polo shirts:
> https://www.python.org/community/merchandise/
>
>   * Coinbase Commerce integrates with a number of major eCommerce
> platforms:
> https://commerce.coinbase.com/integrate
>
>
> I'll share Coinbase with our team for review.


> * What mailing list and/or CRM can I opt-into with my PSF donation? Is
> there a periodic breakdown of expenses that I can backseat-drive and
> micromanage?
>

We go over our finances at the PSF member meetings at PyCon and the
EuroPython. In addition to what we have on python.org (
https://www.python.org/psf/annual-report/2019/,
https://www.python.org/psf/records/board/treasurer/), financials are also
sent to voting members (psf-v...@python.org). The 2018 financials will be
sent there this month. If anyone wants to become a voting member of the
PSF, let me know off-list and I'll be happy to share the available options!

>
> From Charity Navigator, it looks like PSF had about $ 2,500,000 in
> donation revenue a few years ago.
>

As of end of 2018, the PSF had almost 3.3M in assets. In 2018, we received
$515,000 from "Contributions, Membership Dues, and Grants" (
https://www.python.org/psf/annual-report/2019/). In 2016, our
"Contributions, Membership Dues, and Grants" totaled approximately $148,024
to give you a comparison of how things are developing over time.

The Annual Impact report also addresses the need for a financial reserve:

"The PSF will continue to research diversifying revenue streams, hiring
additional staff, and improving our fundraising efforts, which will all
affect future financials. We would like to continue to improve the services
we provide to the community, expand our programs, and better support
developers. We also need to consider risk mitigating factors such as having
diverse revenue streams instead of heavily relying on PyCon and a financial
reserve of at least 1.5 years (in operating costs). This will help ensure
the PSF’s viability for the long run."
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/QEENX2VX3HPTM4P7H2AZFQLW3OK6R7KF/

[Python-Dev] Steering Council Election Timeline for 2021 term

[Ewa Jodlowska]

Hi!

The timeline for this year's election will be the same as last year.

* The nomination period will begin Nov 1, 2020 (do not post nominations
until then)
* Nomination period will end Nov 15, 2020
* Voting will begin Dec 1, 2020
* Voting will end Dec 15, 2020

Nominations will be collected via https://discuss.python.org/ (more details
to follow on Nov 1).

New for this year: Ernest W. Durbin III will be running the vote along with
the assistance of Joe Carey, a PSF employee. They will be co-admins going
forward. I have cc'ed them in on this thread as well in case there are any
questions.

Thanks,

Ewa
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/JHYSU6FEYM3A5AZXSICO5OE3VAWDPGEJ/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Steering Council Update (July through October)

[Ewa Jodlowska]

Hey folks -

Here is an update from the Steering Council. It covers July through
October.

The update has been added to the Steering Council repo as well:
https://github.com/python/steering-council/blob/master/updates/2019-11-09-steering-council-update.md
.

# Steering Council Community Update
July 2019 through October 2019


## July recap:
- PSF and the Steering Council worked on a proposal to hire a project
manager to help with Python 2 EOL communication. The proposal was approved
by the PSF Board and Changeset Consulting was contracted to help with this
work. Progress is being tracked [here](
https://github.com/orgs/python/projects/1#card-26091749)
- Release cadence discussions happened.
- [PEP 1](https://www.python.org/dev/peps/pep-0001/)’s copyright/license
section was updated to include a dual license of public domain and
CC0-1.0-Universal.


## August recap:
- [PEP 572](https://www.python.org/dev/peps/pep-0572/) was updated to
replace `TargetScopeError` to `SyntaxError`:
https://github.com/python/peps/commit/cd292d89972476fa485a8ac1b14c1ed85b8c4867
- Vision document review and update happened.
- Release cadence discussions happened.
- Steering Council helped answer inquiries about proposed Python 2 EOL page.
- Steering Council reviewed the newly approved PSF Code of Conduct.


## September recap:
- Slide deck “Vision Doc” was created based off of the original Vision
Document and was discussed by the Steering Council. The Steering Council
decided to continue in this direction.
- The Steering Council discussed the Core Dev promotion topic and it was
suggested by the Steering Council that the Core Devs create a Work Group to
work on that:
https://discuss.python.org/t/concerns-about-how-we-vote-on-new-core-developers/2351/19
- A timeline was selected for the Steering Council election and informed
the Core Devs:
https://mail.python.org/archives/list/python-committ...@python.org/thread/PLDUMAJOLHM5W6FWOMSGUBN2Q7Z6D3JM/
- Release cadence discussions happened
- [Core Dev Sprint in London recap](
http://pyfound.blogspot.com/2019/10/cpython-core-developer-sprint-2019.html)


## October recap:
- Steering Council discussed the new Code of Conduct and agreed that it
should be sent out to the python-committers@ and python-dev@ mailing lists:
https://mail.python.org/archives/list/python-committ...@python.org/thread/6QIMLZ65D2HVBRGXRMOF2KOLFRXH4IRG/
- Steering Council plans on presenting the Vision Deck at PyCon pending any
changes made by future Steering Council.
- Steering Council discussed the proposal made by [Thomas Wouters](
https://mail.python.org/archives/list/python-committ...@python.org/thread/UWOU47BVULIOZHEOFWGVVQG6LPEXTDNG/)
for approval voting. The Steering Council guided Thomas in the direction of
a [PR](https://github.com/python/peps/pull/1197) and a formal vote. That
resulted in a change to [PEP 13](https://www.python.org/dev/peps/pep-0013/)
stating core team members can vote for zero or more of the candidates for
the Steering Council.
- Steering Council discussed communal ownership of Python repo. It was
decided that the Steering Council will send an email to python-committers
about the topic. Brett sent the email on Nov 6:
https://mail.python.org/archives/list/python-committ...@python.org/message/DCKAPZVXEQHP7OPS3GLEVNDXMXX5QAE6/
.
- Steering Council met with GitHub team about the b.p.o. migration, PEP
[581](https://www.python.org/dev/peps/pep-0581/)/[588](
https://www.python.org/dev/peps/pep-0588/) plan and discussed next steps.
Next steps for Python include finding a point person to lead the work (will
be a project manager), the Steering Council to find out more information
about search features and how mapping will work.
- The SC reviewed and discussed PEP 602 (1 year release cycle proposal by
Łukasz Langa) and PEP 605 (Nick Coghlan and Steve Dower's 2 year proposal)
and selected [PEP 602](https://www.python.org/dev/peps/pep-0602/).
- [PEP 484](https://www.python.org/dev/peps/pep-0484/) policy for inclusion
of stubs in typeshed was discussed and the [PR](
https://github.com/python/peps/pull/1218/) around it. It was decided that a
sentence would be changed to make type stubs an opt-out situation and not
opt-in.
- [PEP 608](https://www.python.org/dev/peps/pep-0608/) and [discussion](
https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539)
were reviewed by the Steering Council. It was decided that the PEP as is
would be rejected, but that the buildbot CI option will work. Nick has
responded to the [discussion on Discourse](
https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539/22)
with the decision and suggestion.
- It was decided that Ewa will help put together the Community Updates so
they happen monthly.



Thank you,

Ewa

---
*As a non-profit organization, the PSF depends on sponsorships and
donations to support the Python community. Check out our Annual Impact
Report for more details: https://www.python.org/psf/annual-report/2019/

[Python-Dev] Steering Council Update (November through December)

[Ewa Jodlowska]

Hello!

Below is an update from the Steering Council. It covers November and
December.

The update has been added to the Steering Council repo:
https://github.com/python/steering-council/blob/master/updates/2020-01-06-steering-council-update.md
(added
to README as well).



# Steering Council Community Update for November - December 2019

## November recap:
- Steering Council assigned one another tasks to check-in on and clean up
29 open PEPs in November (Nov 5 and Nov 12 meetings). See [PEP repo](
https://github.com/python/peps/) for details.
- Steering Council decided that going forward, only one person will need to
approve the minutes and the group will try to rotate that responsibility.
Additionally, to keep meetings efficient we will:
-  1. have a person responsible for the agenda to make sure the agenda
is accurate and timed appropriately
-  2. have a person run the actual meeting to make sure we stay on
topic and cut discussions when topics go over time.
- Steering Council discussed ideas on how to lower the count of PRs. It was
decided that Brett would start a discussion on Discourse with the idea to
close enhancement PRs. This has been done [here](
https://discuss.python.org/t/automatically-close-all-enhancement-prs-for-code-lacking-an-expert/2697).
At a later time, it was decided the idea would be shut down since many
folks did not approve.
- Steering Council discussed how a hiring plan can coincide with the Vision
Deck and how it would work with sponsor/corporate collaborations. The
Vision Deck is an overview document the Steering Council is drafting, which
will help develop Python's roadmap for the next 5 years. Goal is to have
the Vision Deck complete by PyCon 2020.
- Steering Council had a brief discussion about encouraging more candidates
to run for the next steering council and that everyone would work on
raising awareness for this.

## December recap:
- The Steering Council reviewed [PEP 584](
https://www.python.org/dev/peps/pep-0584/) (“Add + and += operators to the
built-in dict class”) and decided that Guido would let the PEP authors know
| and |= was preferred and that the PEP needed some editing. [This was
done](
https://mail.python.org/archives/list/python-id...@python.org/message/P46F7NKO2EG6M4ZGFAKKWDSYEVVIBQR5/).
At a later time it was decided that Guido will be BDFL-Delegate.
- The Steering Council decided it would meet after the 2020 Steering
Council vote ended. The Steering Council will meet December 10 and December
17th. The hand-off meeting will happen the first week of January. Ewa will
send out a Doodle for the first full week of January once the new Steering
Council members are known. It was decided that on January 8th, 2020 the
Steering Council will have a hand-off meeting between the 2019 team and
2020 team.
- Steering Council decided that we would send out ballots to Marc-Andre
Lemburg, Alex Martelli, and Kurt B. Kaiser. [Brett responded to thread](
https://mail.python.org/archives/list/python-committ...@python.org/message/HK4LNQEA3CMSZTGOZTC766NIS4CNPG7O/)
noting this decision and future plans for [PEP 13](
https://www.python.org/dev/peps/pep-0013/).
- Steering Council discussed [PEP 611](
https://www.python.org/dev/peps/pep-0611/). Barry [emailed the python-dev@
list](
https://mail.python.org/archives/list/python-dev@python.org/message/KY46EXGLKNTFMQZXKHMMYWD2GIM5PDL5/)
with the outcome of the discussion.
- Steering Council discussed PyPI’s typosquatting issues.
- Group discussed the status of the GitHub migration plan. Ewa drafted a
job description for the Project Manager role to help with the GitHub
migration for the Dec 17th SC meeting. The Steering Council reviewed it and
Ewa scheduled a call with the GitHub team for late January for next steps.
- Steering Council decided to keep Zulip since the Packaging-wg plans on
using it. We will re-evaluate usage next year. Guido informed the
[Discourse thread](
https://discuss.python.org/t/should-we-continue-using-zulip/2816/7). Brett
[posted an announcement](
https://python.zulipchat.com/#narrow/stream/116742-core.2Fhelp/topic/Engagement.20here.20might.20be.20winding.20down)
in Zulip.


Thank you,

Ewa

---
*As a non-profit organization, the PSF depends on sponsorships and
donations to support the Python community. Check out our Annual Impact
Report for more details: https://www.python.org/psf/annual-report/2019/
*
*Please contribute to PSF; we can't continue our work without your
support! https://www.python.org/psf/donations/
*
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/UD2BVX55