[Owasp-guide] Step 6: Email the list weekly with your status

[Clint Laskowski]

Status Update - Clint Laskowski - March 11, 2010

- I've joined the mail-list
- I've made Mike Boberski aware of my interest in helping the OWASP
Development Guide project
- I've been assigned to the Security Architecture section of the guide
[OWASP-100]
- I've let the leader of that section know of my interest in helping
- Yesterday I heard back from the OWASP-100 section lead (sorry, name is not
available to me right now)
- I'm expecting an assignment or I will propose a task in the next few days
and begin working on it
- My thought is to start building an outline for the section
- I have not gotten SVN to work with Google Code yet, but I only spent 5
minutes on it
- I'm sure I'll get SVN working tontie

-- Clint

Clint Laskowski, CISSP
email: clint.laskowski at gmail.com
twitter: Clint326


On Thu, Mar 11, 2010 at 3:16 PM, Boberski, Michael [USA] <
boberski_michael at bah.com> wrote:

>  Hi,
>
>
>
> A gentle reminder:
>
>
>
> *Step 6: Email the list weekly with your status *
>
> Mike sends out a project status email once a week. Please email the OWASP
> Development Guide with a brief summary of what you worked on during the past
> week, what you plan on working on the next, and any issues or requests for
> assistance. Please try to email your status by COB Thursday Eastern time
> (Mike is located in the greater Washington DC area).
>
>
>
> Tough for me to e.g. help anyone or to help folks understand what each
> other is up to without doing this, since the team is so distributed. Please
> see the following for more information:
> http://owasp-development-guide.googlecode.com/files/development-guide-contributing.pdf
>
>
>
> Additional project controls can (and will) be added if necessary, but I’m
> trying to slow-roll such things, to give teams a chance to self-organize and
> take ownership of their sections and their efforts, and to carve out some
> time out of their schedules to work on this.
>
>
>
> E.g., I see for example some good work on OWASP-0800 based on SVN updates.
> I’d love to hear what’s the latest for this! Couple sentences, not a
> dissertation, although I am one who appreciates detail.
>
>
>
> Best,
>
>
>
> Mike B.
>
>
>
> *A postscript, less gentle:** DO NOT WORRY ABOUT “SPAMMING” THE LIST. I AM
> SPECIFICALLY ASKING YOU AS CONTRIBUTORS TO EMAIL IT WITH NEWS ABOUT YOUR
> GOOD WORKS AND TO USE THE LIST FOR DISCUSSIONS!! HOW YOU HANDLE SOMETHING IN
> ONE SECTION MAY NOT BE IMMEDIATELY OBVIOUS TO YOU HOW IT MAY BE RELEVANT TO
> SOMEONE ON ANOTHER SECTION, BUT SOMEONE WORKING ON THE OTHER SECTION MAY
> THEMSELVES SEE HOW YOUR GOOD WORK COULD HELP THEM OUT.*
>
>
>
>
>
> _______________________________________________
> Owasp-guide mailing list
> Owasp-guide at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-guide
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.owasp.org/pipermail/owasp-guide/attachments/20100311/fcaaa16c/attachment.html