NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Perlbuzzkill
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
every Perl script that says:
"Don't be stupid."
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
I could, sure... (Score:2)
It's not about me, it's about everyone else. I'm not the one asking where it's at, because I know the "it'll be done when it's done answer." It's for everyone else. It's for the guys at the Linux user group meeting I went to last night who when they heard I used Perl immediately asked "When is Perl 6 coming out?"
Why is it so awful that people wan
--
xoa
ye olde liste of arcane documentes (Score:1)
chromatic has been posting meeting minutes from the p6 developers for ages - http://use.perl.org/~chromatic/journal [perl.org]
There's a Pugs Wiki [pugscode.org] with links to lots of useful stuff like the documentation [perlcabal.org],
the Pugs Blog [blogs.com], logs of the Pugs IRC channel [perlgeek.de], a "run perl 6 in your browser [pugscode.org] interface, and the TPF Perl 6 Wiki [perlfoundation.org].
I found those by using only one resource as a starting point: Google for "perl 6" and clicking around.
It would be nice if perl.org's information on Perl 6 was not so outdated. Maybe its perl6 pages could just link to the wiki. It would be nice if the p6l summaries started again, but I sure as hell don't have the time, and I don't know who does.
I think everyone working on Perl 6 knows that the outside world is wondering how long it will take. The longer they spend saying, "We're really working hard!" then the less work they get done. Worse, when they *do* take the time to try and publish information -- and not, mind you, in the form of arcane commits, but actual detailed notes like the ones Peter posted -- the still get asked, "Where is it already? Why can't you give us information?"
If I went to the trouble to stop coding an tell my non-paying and non-participating audience just what I'd been up to, I'd like to think that the audience members might then be willing to relay that information to others when asked, rather than say, "Yeah isn't it crazy that they aren't giving us information?"
It seems like there is a huge amount of information about what's going on with Perl 6, and maybe insufficient links to any one supply of it to hit the top of the results for googling perl 6. Fixing that seems like the right solution. Then, people can be pointed to Google, as is the general solution to anything.
rjbs
Reply to This
Parent
Re: (Score:1)
I'm sure I could find a way to update them once in a while, but I certainly don't have the time to maintain them as a long-term project (and I think I ought to be writing code or documentation instead). This is one of our biggest problems; we don't know where peo
Re: (Score:1)
Pie would be nice, too. Chocolate silk with a graham cracker crust. Mmm!
Is the Perl 6 wiki the most kept-up-to-date place? I wouldn't mind spending a little time finding and trying to deal with a few of the top Google results to get them to point to the right place, either with a link or a redirection. Like, a few hours at least. Let me know and I'll give it a quick go.
rjbs
Re: (Score:1)
Let's use it that way for now. If you (or anyone reading this) updates the wiki, I'll get parrotcode.org and dev.perl.org/perl6 updated to point to the wiki.
Re: (Score:1)
rjbs
Re: (Score:2)
However, if TPF doesn't want to keep things like dev.perl.org up to date, then the horses don't even have the option of water. I guess that would be a question for someone in TPF's PR department.