develooper Front page | perl.bootstrap | Postings from July 2000

Re: ok, fire away

Thread Previous | Thread Next
From:
horos
Date:
July 24, 2000 16:31
Subject:
Re: ok, fire away
Message ID:
200007242331.QAA21556@earth.he.net
> >A short but meaningful title and one concise paragraph.
> >Remember, there'll be a clarification stage later before any voting.
> 
> Do these "complaints & defects" refer to bugs as well as annoyances?
----
ok, a couple of clarifications:

I would assume that 'bugs' should be confined to p5p; I'm looking for things 
that apply to perl5 *if it worked as intended*. Since bugs are by definition 
broken, no I'd say that these things do not apply. If on the other hand you 
think a particular piece of syntax is broken by nature, then I'd include it.

> Is it also a wishlist?

No, I don't think it is a wish list. Although certain annoyances would 
(I'm sure) suggest solutions.  Document the problem, not the potential solution.

> Does it apply to non-code things like documentation?

Yes, definitely. In fact I'd encourage people to complain about other things 
besides syntax issues. Syntax issues are important, but there are other fish
to fry:

	1) documentation && resource availability

	2) architecture (CPAN, build process, source control, etc.)

	3) integration with other languages

	4) social engineering ( mailing lists, how forums work, 
						bug reporting && fixing, 
						licenses, advocacy  )

	5) cross-platform issues 

As Larry said, I think that a complaint list forms the foundation for rebuilding
the perl porters *community* as well as rebuilding perl itself.   As such, we h
ave to document all problems perl - only then can we truly figure out how to 
fix them.

Ed

Thread Previous | 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