develooper Front page | perl.perl6.language | Postings from June 2005

State of Design Documents

Thread Next
From:
Joshua Gatcomb
Date:
June 10, 2005 09:51
Subject:
State of Design Documents
Message ID:
941eab84050610095127f067b8@mail.gmail.com
All:
Designing a language isn't easy - I get that.  Opening up the design
process to the entire community and filtering everyone's "good" ideas
certainly doesn't make this any easier.  My concern is that these
difficulties are being aggravated because the design documents
(Synopses) are not kept up to bleeding edge date.

There are currently 12 Synopses available to implement code from but
there are still 19 more unpublished (I excluded formats in chapter 7
for obvious reasons).  See "Perl6 Timeline By Apocalypse" for details:

http://perlmonks.org/index.pl?node_id=332117

I am sure that a great deal of that unpublished work has already been
decided and yet there is no end to revisiting old problems on this
list and musings of "didn't @larry say 'X' about that?".

I know that decisions are subject to change but having the current
state of decisions in a single location (Synopses) would be a great
benefit to all.  I am a firm believer in not complaining unless you
have an idea about how to solve the problem, so here goes:

Put the design documents into public change control.  Read access to
be granted globally with write access to be limited to @larry
initially.  The community posts patches where the bulk of the work is
done and @larry makes any necessary modifications and commits.  If
even that work load proves to be too much, perhaps common mortals get
granted commit access on a case-by-case basis.

Cheers,
Joshua Gatcomb
a.k.a. Gat
(240) 568-5675

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About