Projects/Reports/2014-17-01 - Revision history

Samantha Groves at 07:03, 21 January 2014

2014-01-21T07:03:28Z

Samantha Groves at 07:02, 21 January 2014

2014-01-21T07:02:31Z

Samantha Groves at 21:11, 20 January 2014

2014-01-20T21:11:15Z

Samantha Groves at 07:34, 18 January 2014

2014-01-18T07:34:56Z

Samantha Groves at 07:31, 18 January 2014

2014-01-18T07:31:46Z

Samantha Groves at 07:17, 18 January 2014

2014-01-18T07:17:07Z

Samantha Groves at 07:07, 18 January 2014

2014-01-18T07:07:17Z

Samantha Groves at 06:51, 18 January 2014

2014-01-18T06:51:49Z

Samantha Groves at 06:47, 18 January 2014

2014-01-18T06:47:50Z

Samantha Groves at 06:30, 18 January 2014

2014-01-18T06:30:54Z

@@ Line 217: / Line 217: @@
 Hello Leaders,
-I just wanted to give a big thank you to all of you who responded to my request for comments and ideas for the OWASP Projects 2014 Operational Goals. I have made some adjustments based on your responses, and I have now finalized the goals for the year. Here they are below:
+I just wanted to give a big thank you to all of you who responded to my request for comments and ideas for the OWASP Projects 2014 Operational Goals. I have made some adjustments based on your responses, and I now have a final draft of the goals for the year. Here they are below:
 --------------------------------------

@@ Line 269: / Line 269: @@
 '''GRANTS & PROJECT FUNDRAISING'''
-'''Primary Goal:''' Generate $50,000 USD in funding for OWASP related activities through grants, and raise necessary funds to run OWASP Projects and related programs.
+'''Primary Goal:''' Generate $50,000 USD in funding for OWASP related activities through grants, and raise funds for OWASP Projects.
 '''Subgoal 1:''' Identify grants that can fund current or potential OWASP Foundation programs.
@@ Line 275: / Line 275: @@
 * Create a submission calendar for upcoming grant opportunities and submissions.
 * Recruit an assistant to help with grant applications.
-* Begin grant writing and submission process for 2014.
+* More public announcements of grant opportunities, and more grant writing resources for Project Leaders.
 '''Subgoal 2:''' Raise enough funds for 2014 Project Summit.
-* Raise approximately $50,000 USD in seed funding (either in funds or barter and trade) for the project summit.
+* Raise approximately $50,000 USD (estimate) in seed funding (either in funds or barter and trade) for the project summit.
-'''Subgoal 4:''' Raise funds for Women in AppSec
+'''Subgoal 3:''' Raise funds for Women in AppSec
 * Aim is to run the Women in AppSec Program at all 4 Global AppSec conferences.
-* Raise $18,000 USD in sponsorship and donations for the program.
+* Raise $10,000 USD in sponsorship and donations for the program.
 --------------------------------------

@@ Line 279: / Line 279: @@
 '''Subgoal 2:''' Raise enough funds for 2014 Project Summit.
-* Raise approximatley $50,000 USD in seed funding (either in funds or barter and trade) for the project summit.
+* Raise approximately $50,000 USD in seed funding (either in funds or barter and trade) for the project summit.
-* Raise approximatley $100,000 USD in sponsorships to put together the projects summit. (Depending on how much is needed. This is an estimate based on past summit costs)
+* Raise approximately $100,000 USD in sponsorships to put together the projects summit. (Depending on how much is needed. This is an estimate based on past summit costs)
 '''Subgoal 3:''' Identify grants that can fund current OWASP Projects. Raise $50,000 USD for OWASP Projects.

@@ Line 70: / Line 70: @@
 **Patrick Calder, Design Foundry Owner, put together the original flyer.
 **However, we need to update the contend due to the new Corporate Membership model.
-**The content needed to be updated.
+**I spent some time reading the new information, and consolidating it into a brief statement about each membership option.
-**I spent some time reading the information, and consolidating it into a brief statement about each membership option.
+**Then, I re-created the design with new content.
 **It is the first draft, but I am glad I was able to get a good start on this project today.
@@ Line 79: / Line 78: @@
 **I am still waiting on the outcome reports from some of the project leaders that participated in the summit.
 **The rest of the content is complete, but I would like to get this report done as soon as possible.
 **I hope to finalize it by next week, Friday.

@@ Line 55: / Line 55: @@
 *'''Grants and Project Fundraising Goals'''
-**
+**This week, I worked on putting together the goals and milestones for grants and project fundraising.
 *'''ESAPI Hackathon'''
-**Kevin kindly updated me on the status of the Hackathon this week.
+**There are only 3 days left until the end of the ESAPI Hackathon!
 **The aim of the Hackathon is to encourage contributions to the ESAPI Project in several key areas.
 **There will be 1st, 2nd, 3rd, and 4th place prizes awarded to the best 4 contributions.
@@ Line 67: / Line 67: @@
 *'''Membership Flyer'''
-**Kevin kindly updated me on the status of the Hackathon this week.
+**I worked on putting together the OWASP Membership flyer today for a few hours.
-**Unfortunately, they have not had too many submissions.
+**Patrick Calder, Design Foundry Owner, put together the original flyer.
 *'''2013 Project Summit Report Update'''
-**Kevin kindly updated me on the status of the Hackathon this week.
+**This has been quite a hassle to finish.
-**Unfortunately, they have not had too many submissions.
+**I am still waiting on the outcome reports from some of the project leaders that participated in the summit.
 *'''Daily Project based queries and requests'''

@@ Line 42: / Line 42: @@
 *'''2014 Goals for OWASP Projects'''
-**Last week I put together the 2014 Goals and Milestones I think are important for us to accomplish for OWASP Projects.
+**About two weeks ago, I put together the 2014 Goals and Milestones I think are important for us to accomplish for OWASP Projects.
 **The blog post can be found here: [http://owasp.blogspot.com/2014/01/2014-operational-goals-for-owasp.html OWASP Projects 2014 Goals]
 **The aim was to share these goals with our OWASP community members and Leaders and gather feedback.
-**I want these goals to be 'our' goals, not just my goals.
+**I have now finalized the goals thanks to the feedback I received from our OWASP Project Leaders.
-**I hope to finalize these by next week, and start working on them by the end of January.
+**You can find the final list of the goals in the Announcements section of this report.
 *'''Women in AppSec at AppSec APAC 2014'''
-**I am happy to report that four (4) OWASP Project talks were accepted for the AppSec APAC 2014 conference.
+**I am happy to report that the AppSec APAC 2014 planning team has decided to move forward with Women in AppSec for the conference.
-**[https://www.owasp.org/index.php/AppSecAsiaPac2014#tab=SPEAKERS AppSec APAC 2014 Talks and Trainings].
+**I am now in the process of putting together all of the documentation and marketing materials they will need to translate into Japanese.
-**I am thrilled that the selection team chose so many OWASP Projects.
+**I am also working on a logistics plan for running the Call for Entries.
-**I spoke to the planning team about having Women in AppSec at the conference again this week, as well.
+**I hope to start fundraising for the award come next week.
 *'''Grants and Project Fundraising Goals'''
-**I am sad to report that Kait's internship with OWASP has come to an end today.
+**
 *'''ESAPI Hackathon'''

@@ Line 48: / Line 48: @@
 **I hope to finalize these by next week, and start working on them by the end of January.
-*'''Apple Developer Program'''
+*'''Women in AppSec at AppSec APAC 2014'''
 **I am happy to report that four (4) OWASP Project talks were accepted for the AppSec APAC 2014 conference.
 **[https://www.owasp.org/index.php/AppSecAsiaPac2014#tab=SPEAKERS AppSec APAC 2014 Talks and Trainings].
@@ Line 64: / Line 56: @@
 **I hope they agree to have the program run at the conference.
-*'''RFPs for Code Review Guide'''
+*'''Grants and Project Fundraising Goals'''
 **I am sad to report that Kait's internship with OWASP has come to an end today.
 **It was a true pleasure having Kait as part of our team.
@@ Line 88: / Line 72: @@
 **The Hackathon ends January 20th 2014.
 **For more information, visit the [https://www.owasp.org/index.php/Projects/ESAPI_Hackathon Guidelines page] or e-mail Chris, Kevin, or me directly.
 *'''Daily Project based queries and requests'''

@@ Line 225: / Line 225: @@
 Hello Leaders,
-I am posting these here to give all of our OWASP Project Leaders an opportunity to review and comment. I would like to know if you think these are the right items we should be focusing on at the foundation level. Is this what you want to see from OWASP Projects in 2014? If so, great! If not, what would you like me to focus on? Now is your chance to let me know. It is up to you, and what your needs are. Please either post a comment here, or e-mail me directly at Samantha.Groves@owasp.org. I would like to get our goals finalized by next week Wednesday.
+I just wanted to give a bit thank you to all of those who responded to my request for comments and ideas for the OWASP Projects 2014 Operational Goals. I have made some adjustments based on your responses, and I have now finalized the goals for the year. Here they are below:
 --------------------------------------
 '''Primary Goal:''' Continue to evolve the OWASP Projects Infrastructure by developing operational systems that facilitate Leader participation and innovation.
@@ Line 238: / Line 240: @@
 * Continue to produce weekly and quarterly information reports.
 * Organize a monthly webinar about an OWASP Project.
-* Continue to produce stories, announcements, and content for our monthly Connector.
+* Produce more substantial software security/projects articles for our quarterly Connector.
 * Migrate all of the Project wiki pages to the new template
 * Facilitate project page compliance with new Sponsorship Guidelines.
@@ Line 245: / Line 246: @@
 * Develop marketing and communications pieces that promote: Benefits of Having an OWASP Project; How to start a project; Project Lifecycle; and Review Process.
 * Have one Project Leader meeting a month.
 * Facilitate OWASP contributions to the Apple Developer Program.
 * Identify & promote cross-project collaboration to move clusters of projects forward, with e.g. work groups that work on a certain domain.
-* Start a task force of people with spare cycles that can help projects that need extra man-power of are falling behind in delivery of new releases (especially the flag ship projects).
+* Start a task force of people with spare cycles that can help projects that need extra man-power of are falling behind in delivery of new releases (especially the flag ship projects)
 * Ask project leaders to create & give project related training or contribute to the OWASP trainings.
 '''Subgoal 2:''' Bring more Project Leaders together in 2014.
@@ Line 255: / Line 257: @@
 * Plan a Project Summit Event in 2014
 * Work on developing Project Leader Workshop module that can be given when I am not present.
-−
 '''Subgoal 3:''' Solidify the Projects Review Process.
@@ Line 273: / Line 275: @@
 * Develop an implementation plan.
 --------------------------------------

@@ Line 178: / Line 178: @@
 ==Message from OWASP ESAPI Project Leaders, Kevin Wall & Chris Schmidt==
-'''ESAPI Hackathon / Bug Bash Contest: Only 10 days left to contribute for a chance to win!'''
+'''Only 3 Days left for a chance to win!'''
-Our very own OWASP ESAPI Project Leaders, Chris Schmidt and Kevin Wall, are hosting the OWASP ESAPI Hackathon starting on Friday, December 20th 2013 and ending on Monday, January 20th 2014. The aim of the ESAPI Hackathon is to encourage contributors to Implement modular security controls, fix existing bugs, provide reference implementations, and improve user documentation.
+Our very own OWASP ESAPI Project Leaders, Chris Schmidt and Kevin Wall, are hosting the OWASP ESAPI Hackathon which ends on Monday, January 20th 2014. The aim of the ESAPI Hackathon is to encourage contributors to Implement modular security controls, fix existing bugs, provide reference implementations, and improve user documentation.
 Each participant will be evaluated by four judges, and prizes will be awarded to those who provide the most valuable contribution to the project. Here are the list of prizes:
@@ Line 200: / Line 200: @@
 Hello Leaders,
-The OWASP Technical Advisors and I are in the process of reviewing our projects, and we would like to ask for your assistance with this assessment. We would like to ask that you take a bit of time to fill in a short survey that we will use to assess the Usability and Value of each project to its users and the community.
+We are still in need of more survey results. We would like to ask that you take a bit of time to fill in a short survey that we will use to assess the Usability and Value of each project to its users and the community.
 You can find the assessment survey here: [https://docs.google.com/a/owasp.org/forms/d/1K2fXppFhAuuus34J5zpafFUw7dWyAXT0_v5sH6OsnHY/viewform Project Usability and Value Assessment]
@@ Line 213: / Line 213: @@
 *[https://www.owasp.org/index.php/OWASP_Project_Inventory#Flagship_Projects All OWASP Flagship Projects]
-Please note that this is only one part of the full assessment for each project. The more responses we can get for each project, the better. Please only complete the assessment if you are familiar with the project, or if you have time to familiarize yourself with the project. We would like to get these survey results by the end of next week: '''Friday, January 17th 2014.'''
+Please note that this is only one part of the full assessment for each project. The more responses we can get for each project, the better. Please only complete the assessment if you are familiar with the project, or if you have time to familiarize yourself with the project. Thank you to those of you who have submitted your responses. Your assistance is very much appreciated.
 Please reach out to me if you have any questions.