, though we are rather fond of them for obvious reasons.
Submitted by tcurtis on Tue, 05/03/2011 - 05:17
Hello, I'm Tyler Curtis (tcurtis on #parrot), and once again, I have the fortune to be doing Google Summer of Code for Parrot. This summer, I will be writing a LALR parser generator targetting Parrot. My proposal contains a tentative schedule and some amount of explanation of what my project involves. I plan to produce some further explanation in a future blog post, as well.
Submitted by soh_cah_toa on Thu, 04/28/2011 - 00:53
My name is Kevin Polulak (a.k.a. soh_cah_toa) and I am one of the seven newest additions to the Parrot community. This is going to be my first Google Summer of Code. The goal of my project is to build a language-independent symbolic debugger for Parrot. My proposal can be read here.
Submitted by rohit_nsit08 on Wed, 04/27/2011 - 14:28
Hello, My name is Rohit Jangid and I have been selected as a Google Summer of Code student.
I am an undergrad in Department of Computer Engineering in NSIT India.
Submitted by benabik on Tue, 04/26/2011 - 18:19
My name is Brian Gernhardt and I'm a Google Summer of Code student. My project is Migrating PAST to NQP and newPOST. The full description of my project is there, along with a short biography, but for those who want to skip the nitty gritty details, I'll give a short version here.
Submitted by Whiteknight on Tue, 04/19/2011 - 23:43
Nor is there any embarrassment in the fact that we're ridiculous, isn't it
true? For it's actually so, we are ridiculous, light-minded, with bad
habits, we're bored, we don't know how to look, how to understand, we're
all like that, all, you, and I, and they! Now, you're not offended when
I tell you to your face that you're ridiculous? And if so, aren't you
material? You know, in my opinion it's sometimes even good to be
ridiculous, if not better: we can the sooner forgive each other, the
sooner humble ourselves; we can't understand everything at once, we can't
Submitted by gerd on Tue, 03/15/2011 - 09:17
On behalf of the Parrot team, I'm proud to announce Parrot 3.2.0,
also known as "Nanday Parakeet". Parrot
is a virtual machine aimed at running all dynamic languages.
Parrot 3.2.0 is available on Parrot's FTP
site, or by following the download
instructions. For those who want to hack on Parrot or languages that run on top of Parrot,
we recommend our organization page on GitHub,
or you can go directly to the official Parrot Git repo on Github
Submitted by mikehh on Tue, 02/15/2011 - 18:19
Always store beer in a dark place.
—Robert A. Heinlein
On behalf of the Parrot team, I'm proud to announce Parrot 3.1.0 "Budgerigar"
Parrot is a virtual machine aimed at running all dynamic languages.
Parrot 3.1.0 is available on Parrot's FTP site, or follow the download instructions. For those who would like to develop on Parrot, or help develop Parrot itself, we recommend using the git repository to get the latest and best Parrot code.
(git clone git://github.com/parrot/parrot.git).
Submitted by jkeenan on Wed, 02/09/2011 - 01:21
Those who have known me for the past decade may be thinking, "Jim Keenan is a
Perl programmer. Why would he want anything done for Python's sake?"
Submitted by jkeenan on Mon, 02/07/2011 - 03:11
Over the last week I've been gathering feedback on the January 29 Parrot Developers Summit (PDS). Some of this feedback came by reading posts on parrot-dev; the balance came via email correspondence and telephone conversations with several Parrot developers. Here I share some of that feedback and how I think it should affect the way we organize ourselves in pursuit of our goals and objectives over the coming year.
Submitted by jkeenan on Sat, 01/22/2011 - 13:53
Next weekend we'll be conducting our quarterly Parrot Developers Summit. This summit is important because it will set our roadmap goals for supported releases in April, July, October and January 2012. In preparation for this summit, this weekend I'll be speaking with other Parrot Foundation directors and with the Project Architect. These are the kind of questions I'll be asking (and which I expect them to ask of me):
- How do you assess the general state of the Parrot project at this time?
- How do you feel about your own participation in the Parrot project at this time?
- Within the last four months you assumed the role of Parrot __________. How has that changed your participation in the project? How would you characterize your functioning in that role?
- In my parrot.org blog posts, I have argued that the project needs self-identified teams and that its roadmap goals should exclude any that are not being pursued by such teams. Do you agree with this argument?
- Assuming you agree with the argument, what teams now exist within the project?
- Assuming you agree with the argument, what should be our roadmap goals for 3.3, 3.6, 3.9 and 4.0? Who are on the teams that will pursue those goals? Who leads those teams?
- To the extent that you do not agree with the argument, what alternative ways of organizing the project should we pursue?
- How do we encourage the participation of people in the Parrot project if their primary interests or talents are not the roadmap goals?