[OWASP-LEADERS] New Member and 1st step to getting more organized
mark at curphey.com
Sat Jan 25 23:01:29 EST 2003
Its really exciting to see the portal code coming on and hearing about a
WebGoat release and CodeSeeker release real soon.
I think everyone agrees we are getting to a stage when we need to get
more structure and consistency. Not rules but guidelines, so everyones
comfortable with how and what stuff happens.
In another OWASP twist of fate (and as I was about to start working on
some outlines with Alex) I got an email from Manavenda volunteering
himself. As you can see from his resume attached, he has great
experience and skills and I am hoping he can help us with the project
documentation we all need, but no one has time to do.
His initial thoughts were as follows.
1. Coding Standards
2. Code Review Checklist
3. Release notes guidelines
4. Build Process guidelines
5. Release Process guidelines - including packaging (internal
builds) as well as actual)
6. Delivery control checklist
7. Technology-specific best practices
8. Bug reporting and tracking mechanism
9. Defect tracking mechanism
10. CVS access guidelines
I am proposing we do these in DocBook XML and they get rendered to the
portal as HTML for everyone to see and use. Lets face it good project
documentation is as much apart of building a secure app as some other
So welcome Manav. If anyone else has any ideas, please let this list
know. Anything else etc ?
Manav, after some discussion and feedback can we build a schedule for
these docs ? We should also talk about the app to render then to the
Thanks and have a great SuperBowl Sunday ! Go Raiders !!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 60928 bytes
Desc: not available
Url : https://lists.owasp.org/mailman/private/owasp-leaders/attachments/20030125/caf00317/attachment.doc
More information about the OWASP-Leaders