On Mon, Dec 04, 2000 at 07:56:21AM +, Alan Burlison wrote:
> How about a design document (format to be decided) and a 'design +
> commentary' document which is the design document with the condensed email
> discussion inserted into it as the commentary. That way there is a design
> spec for
> I'm planning to write (in my copious free time) an
> open-source-licensed book on the implementation and design of Perl
> 6, which should capture for posterity the sense of the discussions
> we will have had while hammering out the design:
This reminds me of:
Hmm, doubtful. The source code ge
On Mon, Dec 04, 2000 at 07:56:21AM +, Alan Burlison wrote:
> How are you going to publish the design? Asking people to follow email
> discussions and try to piece together what is proposed from that doesn't
> seem a very optimal way to go about it. How about a design document
> (format to be
Hmmm, both long *and* late. Network outages are never a good thing.
This was promised this weekend, but I couldn't get it out. It's a
little long: actual ideas and proposals begin around "Perl Masters."
-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The Perl Apprenticeship Program: Developing Perl Developers
I
As another example of a process that seems to be working well (as far
as I can tell by being a lurker) check out the xml-dist-app mailing list
archives at http://lists.w3.org/Archives/Public/xml-dist-app/
They have a draft up in the web [1] and the Subject lines directly
refer to such and such se
On Sat, 2 Dec 2000, Nathan Torkington wrote:
> * it's difficult for the design to happen through the questions
Is that really true? Have we tried? As far as I can tell we've got a
lot of well-intentioned people that for whatever reason are spending very
little time making Perl 6 happen.
Let
On Mon, 04 Dec 2000, Steve Fink wrote:
> One comment -- an apprenticeship is a two-sided relationship. Bryan, I
> think you've done a great job of describing the apprentice's
> responsibility to the master. But what about the master's responsibility
> to the apprentice? The apprentice is enteri
Nice. An apprentice is an administrative assistant with a career
path. If people are happy to do this, we'd be happy to use them. The
chairs proved weak at reporting on their list's activities (I know I
was) so being able to delegate that to someboy who wanted to do it and
help, would be good.
On Mon, 04 Dec 2000, Nathan Torkington wrote:
> Nice. An apprentice is an administrative assistant with a career
> path. If people are happy to do this, we'd be happy to use them. The
> chairs proved weak at reporting on their list's activities (I know I
> was) so being able to delegate that to
On Mon, Dec 04, 2000 at 06:29:47PM -0700, Nathan Torkington wrote:
> Nice. An apprentice is an administrative assistant with a career
> path. If people are happy to do this, we'd be happy to use them. The
I like the idea too.
> chairs proved weak at reporting on their list's activities (I kno
Bryan C. Warnock wrote:
> On Mon, 04 Dec 2000, Nathan Torkington wrote:
>
>> Nice. An apprentice is an administrative assistant with a career
>> path. If people are happy to do this, we'd be happy to use them. The
>> chairs proved weak at reporting on their list's activities (I know I
>> was)
Alan Burlison writes:
> seem a very optimal way to go about it. How about a design document
> (format to be decided) and a 'design + commentary' document which is the
> design document with the condensed email discussion inserted into it as
> the commentary. That way there is a design spec for t
Simon Cozens writes:
> As for me, I hate this "self-selection" thing because it forces me to be
> immodest. Oh well, better get used to it: Me. I think I'd be useful.
Excellent. Anyone else who wants to be part of the initial design
team, now is the time to speak up. If you have perl5 internals
Nathan Torkington <[EMAIL PROTECTED]> wrote:
> How about we do this to design the architecture and API:
>
> perl6-internals-design is for a team of no more than 10 people. These
> people should have experience either with perl5 or with a similar
> system. Mail to this list goes to perl6-interna
> I am slightly worried about the "career path" dead-ending at personal
> lackey,
> however. But, hey, that's why we're getting paid the big bucks, right?
I do have some concerns, but before I express them, I have a sidetrack
comment in this direction.
I have been programming in Perl since befo
for more on this apprenticeship concept in the software world, check out
http://www.mengwong.com/Apprenticeship/
it is a good read and the author is writing it with input from many
people.
the apprentice is given the shit work to do in return for being around
the master and learning directly h
16 matches
Mail list logo
