A very interesting proposal. A couple of thoughts...
Can we have an executive summary of how your proposed approach differs from those of PyPy, Unladen Swallow, and various other attempts? You suggest that payment should be on delivery, or meeting the target, rather than up-front. That's good for the PSF, but it also means that the contractor not only takes all the risk of failure, but also needs an independent source of income, or at least substantial savings (enough for, what, eighteen months development per stage?). Doesn't that limit the available pool of potential contractors? I think there's always tension between community driven development and paid work. If the PSF pays person A to develop something, might not people B, C, D and E feel slighted that they didn't get paid? On the other hand, I guess we already deal with that. There are devs who are paid by their employers to work on Python for N hours a months, for some value of N, or to develop something and then open source it. And then there are devs who aren't. You have suggested that the cost of each stage be split 50:50 between development and maintenance. But development is a one-off cost; maintenance is an forever cost, and unpredictable, and presumably some of that maintenance will be done by people other than the contractor. A minor point, and I realise that the costs are all in very round figures, but they don't quite match up: $2 million split over five stages is $400K per stage, not $500K. > 1. I already have working code for the first stage. I don't mean to be negative, or hostile, but this sounds like you are saying "I have a patch for Python that will make it 1.5 times faster, but you will never see it unless you pay me!" I realise that is a very uncharitable way of looking at it, sorry about that, it's nothing personal. But $500K is a lot of money. If the PSF says "No thanks", what happens to your code? - delete it; - donate it to Python for free; - fork Python and try to make a commercial, non-FOSS version that you can sell to recoup your development time; - something else? If this was a closed-source proprietary project, there would be no question in my mind. You took a bet that you could sell the code, and you lost. You swallow your loss and move on, that's how the proprietary world works. But this is FOSS and community driven, and I don't think that fits well with that model. -- Steve _______________________________________________ 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/OFQKVMU4QPKVD2NIOTZOK5H4HA2RQLHK/ Code of Conduct: http://python.org/psf/codeofconduct/
