Just threw $100 your way.
I'm a big believer in this type of model and having you be a Django core contributor and South developer makes it a no brainer. Paying for quality open source is always a win in my book.
Godspeed!
I'm a big believer in this type of model and having you be a Django core contributor and South developer makes it a no brainer. Paying for quality open source is always a win in my book.
Godspeed!
I've been using django since 2006. This has been a suggestion since then. Why hasn't it been implemented if it is so necessary? It doesn't require a massive core shift, it doesn't even require that much work it seems? So why hasn't it been done with so many eyes on so well documented a platform on so accessible a language with so many commercial deployments? If no one has scratched this itch then paying for someone to scratch an itch you may think you are go
Will the person be deprived of their normal source of income for exactly the time period required to do the work? How is that justified as a cost? Maybe they are a contractor who will take the time out. If that is the case how can there be expandable requirements (longer goal objectives for more money? It could be this whole thing sits very well with their day to day job, but in the western world that is unlikely. I'm sure all intentions are good but it also strikes me as a bit questionable to do these things when lots of other people have committed much more centrally to the project with little immediate remuneration.
I also have a day a week free for this, so there's no concern of this robbing income - that day a week was previously used for learning to fly, and now I'm done with that it needs to have something that pays in order to keep me going. If the choice for that is freelance or open source work, and they pay closely, you can bet I'm going for the open source work.
Heck I've got a list of about 13 projects that are roughly affiliated with my day job but because of whom i work for and the time I have free being used up for other much more frivolous things I havn't had a chance in a year.
Perhaps it is just jealousy on my part :)
I'm sure Andrew would work on this even if the kickstarter had failed - he built South without one after all :)
But having a funded project helps in many ways. It frees him from the distraction of contract work, proves that a lot of people really care about the issue, and finally is a thank-you-donation for the work on Django in the past and the future.
Stuff like this is how I contribute. I, either personally or via companies I've worked for, have done this kind of thing a lot: approach the developer and ask for our bug or feature to get pushed up the priority queue. Sometimes it's a small tip but one company gave out a $10K contract for a bunch of work.
I don't really contribute to open source, my contribution is mostly bug reports and being willing to help the real contributors track down issues.
If this continues do you risk drying up other non-compensated commits or risk contributors waiting for funding before pushing code? You might see a small decrease, but I'd be willing to bet the same dynamics that have kept the open source community moving forward will continue - you just might see more targeted, rapid progress in areas people are willing to fund and a small cottage industry emerge that makes money contributing to projects.
"Will the person be deprived of their normal source of income for exactly the time period required to do the work?"
Does it matter? It will most likely be on his free time, which for me is many times more valuable than my normal income.
This is why developing open source is going down a dangerous path: When you work for free once, people expect you to work for free always.
Maybe this is the way we'll get good, solid Python3 support for Django, quickly. I'll be more than happy to fund (in part) efforts for getting work done on other Django plugins so they work with Python3. The Django book can do with a little concentrated focus too.