Hi,
Does anyone have comments on the following?
1. Coding Standards
I take it as a given that we need some coding standards for the
P5EE project if/when we produce code.
* Does anyone have a URL for a Perl Coding Standards doc?
(similar to the Sun Java Coding Standard)
The only document I know of is "perldoc perlstyle".
If I don't get any feedback on this, I will start a coding standards
page that starts with "perlstyle".
2. Package/Module Naming Conventions
I would imagine that we would name modules according to the following
guidelines.
* All P5EE components which have *broad* support from the
[EMAIL PROTECTED] list would go into the "P5EE" package
* Naming style is similar to other modules on CPAN
* Naming choice draws from precedent of other modules on CPAN
* Naming choice draws from precedent of J2EE
I suggest that module names for Configuration and Security components
identified so far be
P5EE::Config
P5EE::Authen
P5EE::Authz
("Security" is so broad a word, I thought against "P5EE::Security".)
3. RFC Process
The simplest way that I can think of to start the RFC process for
a component is:
* get the blessing from the P5EE list for a top-level package name
* begin a CPAN-able source directory skeleton
* write the spec (no code) as POD inside the target module
* publish HTML to the web
* announce whenever progress is made so that comments can be sought
* code is added after there is broad support for the API spec
and supporting doc
Unless there are better suggestions, I will begin doing this.
Stephen
http://www.officevision.com/pub/p5ee
