Skip to content

Conversation

@kbodwin
Copy link
Contributor

@kbodwin kbodwin commented May 14, 2025

Closes #5675

This PR incorporates changes, in compliance with our recent acceptance to be fiscally sponsored by NumFOCUS.

Please do not merge until:

  • Donation and landing page links are verified; current ones are placeholders.

  • NumFOCUS onboarding has taken place and everything has been reviewed.

(ping @TysonStanley)

kbodwin added 4 commits May 13, 2025 23:32
Add Powered by NumFocus
fix badge location
Add link (not yet active) to NumFOCUS donation page.

Add tax language from NumFOCUS.

Remove placeholder text for pre-NumFOCUS funding structure.
@kbodwin kbodwin requested a review from MichaelChirico as a code owner May 14, 2025 06:46
@codecov
Copy link

codecov bot commented May 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.69%. Comparing base (1593221) to head (b4a261a).
Report is 38 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #6979   +/-   ##
=======================================
  Coverage   98.69%   98.69%           
=======================================
  Files          79       79           
  Lines       14676    14676           
=======================================
  Hits        14485    14485           
  Misses        191      191           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

GOVERNANCE.md Outdated
# Finances and Funding

There is currently no mechanism for the data.table project to receive funding as an entity.
The data.table project is fiscally sponsored by [NumFOCUS](https://numfocus.org/). Donations to the project can be made at [numfocus.org/donate-to-data-table](https://numfocus.org/donate-to-data-table)
Copy link
Member

@jangorecki jangorecki May 14, 2025

Choose a reason for hiding this comment

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

I don't really know how NumFOCUS funding works, but as long as there are no funds coming from it, I would phrase it "project can be fiscally sponsored via NumFOCUS".

Copy link
Member

Choose a reason for hiding this comment

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

This is a good point that it can be assumed that funding is automatically coming in based on this but I do believe it is correct is say "is fiscally sponsored by" as NUMFocus is taking on the project now and any funds that do come to data.table will be supported by them.

Would it be useful to say "The data.table project is fiscally sponsored by NumFOCUS based on donations and grant funding when available. Donations to the project can be made at numfocus.org/donate-to-data-table

Copy link
Member

@jangorecki jangorecki May 15, 2025

Choose a reason for hiding this comment

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

Saying that "project is [already] fiscally sponsored" is a bit more discouraging new potential sponsors, comparing to saying "project can be fiscally sponsored". Ultimately I don't have strong opinion on that, let's see what others think.

Copy link
Contributor Author

@kbodwin kbodwin May 23, 2025

Choose a reason for hiding this comment

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

This language came directly from NumFOCUS, but I agree with Jan's take - we'll ask them in our meeting next week if the language can be tweaked to clarify in some way that we receive sponsorship via donations through the NumFOCUS platform.

fix donation link and tweak language
@TysonStanley TysonStanley merged commit 5bbc4d5 into Rdatatable:master May 31, 2025
10 checks passed
@ben-schwen
Copy link
Member

@TysonStanley, could you also please make sure to squash when merging so that we have a clean history? (I know that GitHub has changed the default option here, which makes it more tedious.)

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.

NumFOCUS funding

4 participants