[pytest-dev] Partnership possibility with Pytest
alex at seedanddew.com
Tue Jul 31 12:13:01 EDT 2018
>are there any plans to adjust the cut should the financial situation ever
allow it at scale?
I haven't given this much thought but it's an option
>I`m also wondering if connecting parties in need of direct/indirect work
on/with the project with freelancers/companies surrounding the projects is
on the horizon.
Can you explain this again? I'm not sure I understand it.
>Where would the money go?
We actually work with an organization called OpenCollective (
https://opencollective.com/) that creates a non-profit for you. The idea is
they handle the legalese and create an account where donations can go. All
donations and expenses are also on the site, so it becomes fully
transparent. I believe their cost structure is 5% of donations. We can send
money straight to them. Does that work for you guys?
>I'm also not sure if this works out. I use pytest a lot, but I rarely
>look at its documentation.
Not even as reference? Does that apply to other projects where you're not a
dev as well? I've heard this feedback before and its fair but my hypothesis
is that people still go back every now and then for reference and this
applies evenly across all projects, so it should lead to the same
proportion of revenue on a larger time frame.
>At the same time, I might spend a lot of time
>looking at documentation of something I just want to try out but never
This seems fair too. You will be giving this project a one time burst of
revenue and then never come back. In the longer time frame this should mean
less revenue for the unused project and more for the one you actually use.
I would actually consider this a feature since that small project gets
something. In the current world, larger, more established projects and
those that are good at marketing their funding requirements tend to get a
lions share of donations while smaller projects get next to nothing. Our
approach is to try to increase the pool of people that make those donations
and allows the smaller projects to get some piece of that as well.
Does that seem fair?
On Tue, Jul 31, 2018 at 1:23 AM, Florian Bruhin <me at the-compiler.org> wrote:
> some random thoughts:
> FWIW I'm -1 on this (mainly because we don't have a good way to recieve
> and distribute money; and I doubt there is one at all), but currently a
> bit in a hurry.
> On Tue, Jul 31, 2018 at 09:46:10AM +0200, RonnyPfannschmidt wrote:
> > i like the Idea i`m def +1 on adding this and seeing how it plays out,
> Where would the money go?
> > The subscription revenue will be distributed based on the amount of
> > time users spend reading documentation of the respective project
> > which I anticipate will correspond well with actual use. So if a
> > user spends 10% of their time reading the Pytest documentation, you
> > get 10% of the subscription revenue.
> I'm also not sure if this works out. I use pytest a lot, but I rarely
> look at its documentation. At the same time, I might spend a lot of time
> looking at documentation of something I just want to try out but never
> use again.
> https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP)
> GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
> I love long mails! | https://email.is-not-s.ms/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pytest-dev