Stefan Behnel wrote: > One problem I see here is the current release schedule. We keep getting > more and more away from the "release early, release often" principle. > Getting 0.12 out in one way or another would finally make all the great > trunk improvements available to regular users. Thing is: every release > needs a driver, so that's the first place where we could benefit from a > dedicated helping hand. I mean, Sun pays the Jython project lead, even > full-time. Guido is payed half-time for CPython evolution. I wonder if > there isn't enough commercial interest in Cython by now that could express > itself in contributed project time or financing. A developer day invested > in Cython development can easily pay off by making your own code easier to > write and/or faster to execute. Remember, we write C so you don't have to! > > (maybe we should put the last two sentences on the front page ;)
:-) I think they'd fit nicely. As for commercial interest... well, if nothing else, figuring out whether anyone's employable and for what tasks (might want to take that off-list perhaps) and ask "officially" for monetary donations on the list would at least give an indication on whether it is the case. (I guess we can always solicit for manpower as well, in particular for "simple" tasks like doc writing and Windows testing as well.) Making a decision to request donations isn't a trivial issue though -- one time this was discussed earlier there was concern that having people paid (beyond GSoC money) could stifle other contributions and be seen as against the current open development nature. It's a very valid concern, though in the exact situation we're in now I don't have issues with it myself. Then there's fear of sending a signal that makes people afraid of Cython dying if we can't get donations (which isn't true IMO). >> Cython can thrive without this too though! Looking at the coming >> half-to-three-quarter year, here's what I'm guessing will happen: >> >> - I might get the new memoryviews from summer finished and merged with >> trunk > > I wouldn't mind putting major new features off for 0.13 and releasing 0.12 > sooner. +1. I wasn't by any means setting up a list of priorities, more a list of what people were likely to work on over the next 1/2-1 year in no particular order. I'm fine with putting off memoryviews until 0.12 is released, and definitely agree that 0.12 should be put out without waiting for merges. >> - Fwrap released > > Independent of Cython's own schedule, except if there's a requirement for > better integration on Cython side (which would be fine for 0.13). Yes, there is, but 0.13 is fine (but again this was merely "what is likely to happen" that's Cython-related). -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
