Adding icalendar to thanks.dev - funding

[niccokunzmann]

https://thanks.dev is a dependency funding platform. While Github Sponsors and Open Collective fund single projects, this one funds all dependencies. I would like to try it out to add icalendar to thanks.dev and wanted to start a discussion here as to how to approach it as this is also within the Plone community.

Open questions:

• Where does the money go?
  • Should not be much at the start.
  • We can pass it to our dependencies for example.
  • Should it go to Plone?

I had a call with Armin from thanks.dev and we can have one together. I think, thanks.dev are interested in having some projects like this because a lot of projects depend on this one. I already added mine because funding FOSS is an interest of mine at the moment.

What are your thoughts on this?
@geier @mauritsvanrees @jacadzaca and the others who have contributed in the last months? And anyone reading this.

[niccokunzmann]

I also informed the Plone community about this discussion: https://community.plone.org/t/future-of-icalendar-looking-for-maintainer/15445/3?u=niccokunzmann

[jacadzaca]

Hi @niccokunzmann, thanks.dev looks promising. To my knowledge, icalendar's only dependencies are pytest, tox and sphinx, but these probably aren't on thanks.dev, so from what I understand we wouldn't be able to pass the donations to them, right?

How about using the potential funds we'd gather for setting up a bounty system for the pending issues? Would that be possible to integrate with Github? Would accepting 'targeted donations' from people who'd really want to see an issue resolved be implementable?

[anehzat]

It seems like this to me:

1. People use thanks.dev to donate to their dependencies

2. money goes to the icalendar collective - funds are publicly viewable and where they go (Example from open-web-calendar: https://opencollective.com/open-web-calendar )

3. We can send them to bountysource (Example from weblate: https://app.bountysource.com/issues/81891384-markdown-files-support )

   • TODO: How does that integrate with PayPal - that seems to be the only option on bountysource

4. We choose an issue to fund.

5. Once the issue is solved, by some rules of bounty-source, the money is released.

I think, this is a very transparent process in every step. If people fund the project, I think, they would expect something like this to go on. So, this looks like a nice thing to try out. I do not see any problems. At the start the amounts will probably be small if there are any. This is what I see for my project which accounts for about 1/4 of icalendar usage:

No donors found for your projects yet.
Hang in there – we're working on it!

I was on a call with one of the founders of thanks.dev. I think, I will post the next one here, too, so you can join in if you like. I hope, they will focus on FOSS and not so much on the network effect that can be used to make it big.

So, I think, it is nice to try it out, no money will flow in the next months either way. So, there is plenty of time to get prepared. I will be waiting a little for answers from the Plone community.

What are your thoughts on this?

BTW. We are working with Paypal to see if they can work something out as a way for us to better support open source maintainers.

[niccokunzmann]

I scheduled a call with thanks.dev on Sunday, 16th April at 22:00 UTC. If you like to partake, send me an email.

[niccokunzmann]

In order to fund work on single issues, I requested that https://polar.sh has access to write to the issues.
See the example:

Using polar.sh, we can actually allow people to click on a funding button below the issues.

[mauritsvanrees]

I have approved the request to allow polar.sh on the collective/icalendar repo.

polar.sh is now "Connecting your amazing repositories", which it has been doing for several minutes now, so I wonder if it is stalled or is doing too much.

In my own settings on GitHub I see:

polar.sh can access your account mauritsvanrees to:

Verify your GitHub identity
Know what resources you can access
Act on your behalf
View your email addresses

polar.sh has been installed on 1 account you have access to: collective.

That sounds like I gave it access to my own account as well, so maybe I did too much.
But in the settings of the collective org it only has access to the icalendar repo, so seen from icalendar it should be fine this way.

[niccokunzmann]

I opened this issue: polarsource/polar#2938
There, you can see that I do not have access to edit the org. I wonder: On the top-left, can you choose icalendar as an option to configure?