Hello pypy-dev, As some of you may know, this past year I wrote a chapter about PyPy for Architecture of Open Source Applications Volume 2. It has brought to my attention that my communication with the PyPy community about it was poor. Since it deeply involved the PyPy project, I should have been more public in its writing; I should have sent it to pypy-dev for review and comments. Now that this has been pointed out to me, it's painfully obvious that I fell short. Next time such an opportunity arises, I look forward to working fully with the PyPy community on it. Please accept my apologies, Benjamin
On Mon, May 14, 2012 at 10:08 PM, Benjamin Peterson <benjamin@python.org>wrote:
Hey Benjamin, Without wanting to step on anyone's toes, I don't think you had any obligation to notify us. I haven't read your chapter, but I look forward to it and the rest of AOSA. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero
Hi all, On Tue, May 15, 2012 at 4:11 AM, Alex Gaynor <alex.gaynor@gmail.com> wrote:
Accepted, thank you for writing this mail.
I agree, no obligation. But it would still have been much fairer to do it, given that both open source as well as science work based on reputation. Cheers, Carl Friedrich
Hi Benjamin, On Tue, May 15, 2012 at 4:08 AM, Benjamin Peterson <benjamin@python.org> wrote:
As some of you may know, this past year I wrote a chapter about PyPy for Architecture of Open Source Applications Volume 2.
Great, congratulation :-)
It has brought to my attention that my communication with the PyPy community about it was poor.
Don't worry about it. Armin
Hi Benjamin, On Mon, May 14, 2012 at 19:08 -0700, Benjamin Peterson wrote:
I quick-read the chapter and like it. Congrats! Probably makes sense to link to it from pypy docs. I also think it's a good idea to share information about such endeavours early and especially if a third party intends to talk to the "pypy" project as whole (no clue if that was the case here). best, holger
Benjamin Peterson <benjamin <at> python.org> writes:
Hi Benjamin, That's nice to read the description of PyPy innards. Great work! Is seems possible to reuse this text and enhance it for PyPy docs, isn't it? So the opportunity is not lost. =) In the end it could become as visually entertaining as NaCl stuff: https://developers.google.com/native-client/dev/overview Looking forward to more pictures. =)
On Mon, May 14, 2012 at 10:08 PM, Benjamin Peterson <benjamin@python.org>wrote:
Hey Benjamin, Without wanting to step on anyone's toes, I don't think you had any obligation to notify us. I haven't read your chapter, but I look forward to it and the rest of AOSA. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero
Hi all, On Tue, May 15, 2012 at 4:11 AM, Alex Gaynor <alex.gaynor@gmail.com> wrote:
Accepted, thank you for writing this mail.
I agree, no obligation. But it would still have been much fairer to do it, given that both open source as well as science work based on reputation. Cheers, Carl Friedrich
Hi Benjamin, On Tue, May 15, 2012 at 4:08 AM, Benjamin Peterson <benjamin@python.org> wrote:
As some of you may know, this past year I wrote a chapter about PyPy for Architecture of Open Source Applications Volume 2.
Great, congratulation :-)
It has brought to my attention that my communication with the PyPy community about it was poor.
Don't worry about it. Armin
Hi Benjamin, On Mon, May 14, 2012 at 19:08 -0700, Benjamin Peterson wrote:
I quick-read the chapter and like it. Congrats! Probably makes sense to link to it from pypy docs. I also think it's a good idea to share information about such endeavours early and especially if a third party intends to talk to the "pypy" project as whole (no clue if that was the case here). best, holger
Benjamin Peterson <benjamin <at> python.org> writes:
Hi Benjamin, That's nice to read the description of PyPy innards. Great work! Is seems possible to reuse this text and enhance it for PyPy docs, isn't it? So the opportunity is not lost. =) In the end it could become as visually entertaining as NaCl stuff: https://developers.google.com/native-client/dev/overview Looking forward to more pictures. =)
participants (6)
-
Alex Gaynor -
anatoly techtonik -
Armin Rigo -
Benjamin Peterson -
Carl Friedrich Bolz -
holger krekel