Christian Tismer <tismer@stackless.com> writes:
Hi all,
Next #pypy-sync meeting on freenode.net is tomorrow Thursday at 1pm as usual.
I'll try to remember when it starts, this time...
Regular topics --------------
* activity reports (3 prepared lines of info) * resolve conflicts/blockers
Here is my draft proposal of
Topics of the week ------------------
A quick point about IRC logging
I (Chris) have set up an eggdrop server on tismerysoft.de. This server logs #pypy, #pypy-funding (password), #pypy-sync, #pypy-tb. Let me know tomorrow if it should log something else. To make this service more reliable, I would like to add a second server. I could use another one of mine, but this makes no sense in using the same network. I'd like to ask which other server to use, maybe codespeak, maybe Armin's new server. Anyway, I'd like to take responsibility and the rights to set that up, since I did it before.
The starship? I think you already have an account there :)
Participation on the CCC congress in Berlin
Is the event in German? I guess from the fact that the website it, the event probably is too...
Current optimization activities and allocation of work
There are currently several ongoings on optimization, where I can't remember that they were assigned officially in any way. Practice seems to be to justpick an issue which has a good chance to provide a 200 % speedup and then go for it. I am personally not really happy with this and would like to ask about opinions. My proposal is to have a more informal way to decide about activities, by issuing a short IRC meeting and giving everybody a chance to ask for participation. We should also be open to discuss reasons for an individual's rejection. This might be painful, but setting facts by just doing things is a worse practice IMHO.
It seems to me that rather than saying "inlining will make us faster" or "string interning will make us faster" or whatever, some effort needs to go into finding out why we are slow.
Making money out of PyPy
Jacob asked me on the last sprint, if it is possible to make money out of PyPy right now.
Well, my uninformed opinion would be "no, not right now".
I passed this around once, but would like to insist. I am personally interested to make PyPy move away a bit from its purely academical status and to think a little bit about how we can create practical applications in the near future, which allow to grow marketable services for our members, in order to reduce PyPy's dependency from the EU sponsoring.
Lots of people are interested (though maybe they shouldn't be) in a non-GIL implementation of Python. Offering different concurrency models is a really big selling point of PyPy, I think. Cheers, mwh -- That one is easily explained away as massively intricate conspiracy, though. -- Chris Klein, alt.sysadmin.recovery