C
Christian Tismer
(re-sent and modified, after I recognized that my
hardware-clock is broken, need a new note-buck)
Dear community,
I would love to publish Stackless 3.1, of course.
Also I know that there is some inherent bug in it.
This is the state of the art sine four months.
I am currently in a very tight project and have no
time to dig into this problem.
BUT IT IS URGENT!
I'm seeking for a person who would take the job to
find the buglet. He would need to debug and
nail down a commercial application, which I cannot
make public. (S)He would need to sign an NDA with me.
The success payment would be $500, minimum. If the problem
shows up to be very hard (to some undefined definition
of very hard, to be negotiated), it can be increased
to $1000.
If my app works afterwards, Stackless 3.1 is just fine
and can go out to the public..
If it doesn't work, no payment happens.
The identified problem needs to be documented by a
reproducible test case.
If somebody is interested, please contact me privately.
And be aware, this is really no easy stuff. You need to
be a real hardcore system hacker with many years of
experience.
(Armin, Bob, Jeff, Lutz, Richard, Stefan, Stephan?)
Here is the CVS path to the dev trunk:
CVSROOT=server:[email protected]:/home/cvs
cvs co slpdev/src/2.3/dev
The cheapest complete solution wins. Hurry up
Sincerely -- chris
--
Christian Tismer :^) <mailto:[email protected]>
tismerysoft GmbH : Have a break! Take a ride on Python's
Carmerstr. 2 : *Starship* http://starship.python.net/
10623 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 31 86 04 18 home +49 30 802 86 56 mobile +49 173 24 18 776
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/
hardware-clock is broken, need a new note-buck)
Dear community,
I would love to publish Stackless 3.1, of course.
Also I know that there is some inherent bug in it.
This is the state of the art sine four months.
I am currently in a very tight project and have no
time to dig into this problem.
BUT IT IS URGENT!
I'm seeking for a person who would take the job to
find the buglet. He would need to debug and
nail down a commercial application, which I cannot
make public. (S)He would need to sign an NDA with me.
The success payment would be $500, minimum. If the problem
shows up to be very hard (to some undefined definition
of very hard, to be negotiated), it can be increased
to $1000.
If my app works afterwards, Stackless 3.1 is just fine
and can go out to the public..
If it doesn't work, no payment happens.
The identified problem needs to be documented by a
reproducible test case.
If somebody is interested, please contact me privately.
And be aware, this is really no easy stuff. You need to
be a real hardcore system hacker with many years of
experience.
(Armin, Bob, Jeff, Lutz, Richard, Stefan, Stephan?)
Here is the CVS path to the dev trunk:
CVSROOT=server:[email protected]:/home/cvs
cvs co slpdev/src/2.3/dev
The cheapest complete solution wins. Hurry up
Sincerely -- chris
--
Christian Tismer :^) <mailto:[email protected]>
tismerysoft GmbH : Have a break! Take a ride on Python's
Carmerstr. 2 : *Starship* http://starship.python.net/
10623 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 31 86 04 18 home +49 30 802 86 56 mobile +49 173 24 18 776
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/