[Pandas-dev] Tidelift

Marc Garcia garcia.marc at gmail.com
Thu Jun 13 10:18:51 EDT 2019


>From my side, happy to receive funds from anyone as far as they don't
expect anything unreasonable in exchange. And happy with Tidelift
conditions, sounds like a great deal to me.

To me it makes sense to spend the money in grants, like the NumFOCUS grant.
Based on the GSoC experience, where nobody from the team was interested in
mentoring junior people, I guess the grants would mainly be used by
maintainers or senior developers. While we're still far from FTEs, I think
the money we're discussing starts to be significant for people who could do
freelance work,... Based on Wes comments, I'd also be happy to give grants
for work already done, if anyone would like to claim that. I think other
formulas like giving the money to maintainers directly,... will be too
complex/controversial.

Regarding what it's expected from the money, I think it's worth to see what
Quansight is doing. We can check with Travis the exact details, but my
understanding is that companies can give funds to Quansight to get the
things in the project roadmaps done. The roadmaps of the projects they
support are here: https://www.quansight.com/projects I think having a "paid
work" roadmap would be great, so as a team we define what are the top
priorities, and if we find the right people we use the funds for the things
are not getting progress with volunteer work. I think Wes, Travis and other
people will have experience in this format, happy to follow their advice.

Slightly unrelated, but we're getting some progress with the docs. We're
building them in azure (available now at https://dev.pandas.io) and getting
close to build without warnings (and validate them in the CI), so we can
speed up changes. After that I'll work on changing the theme, and will
propose to have a "fancy" home page which IMO we can use to give credit to
companies supporting the project. Like what we're doing at
https://pandas.pydata.org/about.html, but more visible and hopefully with
many more visits. You can see a proof of concept from some time ago here:
http://dev.pandas.io/pandas-sphinx-theme/pr-datapythonista_base/. If people
is happy with the idea, we should probably define formally which company is
listed there (companies employing maintainers to work on pandas, big
donors,..).

On Wed, Jun 12, 2019 at 9:46 PM G Young <gfyoung17 at gmail.com> wrote:

> I second Joris' point here.  Logistically, it seems easier to determine
> the details of where the $$$ goes AFTER it comes through from Tidelift to
> NUMFOCUS
>
> On Wed, Jun 12, 2019 at 1:42 PM Joris Van den Bossche <
> jorisvandenbossche at gmail.com> wrote:
>
>> I find the idea of paying people (the core devs) for their maintenance
>> work intriguing, but also see a lot of obstacles (the ones Ralf mentioned,
>> what part of our volunteer time is considered maintenance work, who are
>> active maintainers, do we tie certain expectations to rewarding money,
>> ...?). I am not sure how it would work out in practice. In any case
>> something to discuss, as we should also discuss other possible ways that we
>> might want to spend the money if not paying the current maintainers.
>>
>> Just to be clear: even if we go with a NumFOCUS - Tidelift agreement, we
>> can decide to pay ourselves instead of letting Tidelift directly do that.
>> So that discussion can be done separately from deciding on going forward
>> with NumFOCUS making a contract with Tidelift (I don't think I heard any
>> pushback on that aspect itself, but just wanted to state this explicitly).
>>
>> Joris
>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org
>> https://mail.python.org/mailman/listinfo/pandas-dev
>>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20190613/8f82910c/attachment-0001.html>


More information about the Pandas-dev mailing list