[Owasp-board] Open Topics & Archives for future boards

Josh Sokol josh.sokol at owasp.org
Wed May 7 13:47:43 UTC 2014


I like the idea of tracking ongoing issues in a living document.  I added a
new column to track an "Owner" as well because simply tracking issues is
not enough.  We need people who are actually going to follow up and
champion them through to completion.

~josh


On Wed, May 7, 2014 at 7:11 AM, Tom Brennan - proactiveRISK <
tomb at proactiverisk.com> wrote:

> Happy to support use of google docs as a platform.  To others points
> raised prior in new tech, the use case should be explained and demonstrated.
>
> Leading by example here will help acceptance in the community to apply
> downstream to chapters and projects too
>
> Not the only way... But the preferred way.
>
>
> On May 7, 2014, at 12:37 AM, Jim Manico <jim.manico at owasp.org> wrote:
>
> So this would basically be the "public OWASP-board dashboard".
>
> I like it. Let's do it. This is helpful in being more transparent to the
> community.
>
> +1
>
> - Jim
>
> On 5/6/14, 11:35 PM, Michael Coates wrote:
>
>     Board,
>
>  In my opinion, the number of open board topics is growing and items are
> getting neglected and handled at a slower pace than optimal. Let me state
> that I don't believe this is from a lack of interest or diligence by the
> board. Instead I think these reasons are the cause:
>
>  1. No central catalog of open issues
>  2. Reliance on discussion through email leads to threads getting buried
> in people's in boxes
>  3. No central document repository
>
>  I suggest that we create a catalog of all activity items by the board.
> This can live in a google doc that we link to every board meeting.
>
>  Here is an initial page as an example.
> https://docs.google.com/a/owasp.org/document/d/1PqOUKc59ZRT80FrX1z69CVbyfYVcbZFgzlJ0EzOFTRU/edit
>
>
>  I think this will be beneficial since we can keep things very clear about
> what topics are open and need attention. This will also be a running log of
> topics discussed with links to artifacts/documents/discussion.
>
> This is an investment in "bookkeeping" but I think it's worth it.
>
>  Thoughts?
>
> --
> Michael Coates
> @_mwc
>
>
>
> _______________________________________________
> Owasp-board mailing listOwasp-board at lists.owasp.orghttps://lists.owasp.org/mailman/listinfo/owasp-board
>
>
> _______________________________________________
> Owasp-board mailing list
> Owasp-board at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-board
>
>
> WARNING: E-mail transmission cannot be guaranteed to be secure or
> error-free as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses. The sender therefore does
> not accept liability for any errors or omissions in the contents of this
> message, which arise as a result of e-mail transmission. No employee or
> agent is authorized to conclude any binding agreement on behalf of
> proactiveRISK with another party by email.
>
>
> _______________________________________________
> Owasp-board mailing list
> Owasp-board at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-board
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-board/attachments/20140507/e3c2b03d/attachment-0001.html>


More information about the Owasp-board mailing list