OWASP 2014 Project Handbook Appendix - Revision history

Mtesauro: Protected "OWASP 2014 Project Handbook Appendix": Significant content reorganization ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2017-02-15T04:41:55Z

Protected "OWASP 2014 Project Handbook Appendix": Significant content reorganization ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Kait Disney-Leugers: /* Project Sponsorship Operational Guidelines */

2014-02-20T21:35:44Z

‎Project Sponsorship Operational Guidelines

Kait Disney-Leugers: /* Project Sponsorship Operational Guidelines */

2014-02-20T21:34:55Z

‎Project Sponsorship Operational Guidelines

Kait Disney-Leugers: /* Project Sponsorship Operational Guidelines */

2014-02-20T21:34:08Z

‎Project Sponsorship Operational Guidelines

Kait Disney-Leugers: /* Project Sponsorship Operational Guidelines */

2014-02-20T21:33:28Z

‎Project Sponsorship Operational Guidelines

Kait Disney-Leugers: /* Project Spending Policy */

2014-02-20T21:30:39Z

‎Project Spending Policy

Kait Disney-Leugers: /* Grant Fund Spending Policy */

2014-02-20T21:28:58Z

‎Grant Fund Spending Policy

Kait Disney-Leugers: /* Grant Fund Spending Policy */

2014-02-20T21:28:20Z

‎Grant Fund Spending Policy

Kait Disney-Leugers: /* OWASP Project Donation Contract */

2014-02-20T21:27:34Z

‎OWASP Project Donation Contract

Kait Disney-Leugers: /* OWASP Project Donation Contract */

2014-02-20T21:26:13Z

‎OWASP Project Donation Contract

@@ Line 156: / Line 156: @@
 # Sponsor logos must NEVER be placed anywhere other than within the 'Acknowledgements' tab under the 'Project Sponsors' heading on the project wiki page.
 #Logos must be created using the following speciﬁcations for placement on the wiki page:
-*Resolution: 72dpi
+##Resolution: 72dpi
-*File Type:.PNG or .JPEG
+##File Type:.PNG or .JPEG
-*Size: No longer than 300 x 300 px
+##Size: No longer than 300 x 300 px
 # Sponsor logos on the product: All sponsor logos must be placed on a page/section/location that is separate from the content of the product. They must contain the company logo, their name, and their website url. The aim is to have a separate section on the product that clearly lists sponsor information. Template acknowledgement copy: “OWASP does not endorse vendors, but we would like to acknowledge the following contributions....”
 # Logos must be created using the following speciﬁcations for placement on the product:
-*Resolution: 300dpi
+##Resolution: 300dpi
-*File Type: .EPS
+##File Type: .EPS
-*Size: No smaller than 5in x 5in
+##Size: No smaller than 5in x 5in
 #All sponsorship logos will be placed on the project product and wiki page for one year or until the next major release. All legacy projects will be given one year to comply with these guidelines starting on January 01, 2014.
 #Logos must be sent to the OWASP Project Leader for inclusion on the OWASP Project wiki page and product. It is the responsibility of the Project Leader to make sure all of his/her project sponsors are properly represented on the OWASP Project wiki page and product.

@@ Line 156: / Line 156: @@
 # Sponsor logos must NEVER be placed anywhere other than within the 'Acknowledgements' tab under the 'Project Sponsors' heading on the project wiki page.
 #Logos must be created using the following speciﬁcations for placement on the wiki page:
-;Resolution: 72dpi
+*Resolution: 72dpi
-;File Type:.PNG or .JPEG
+*File Type:.PNG or .JPEG
-;Size: No longer than 300 x 300 px
+*Size: No longer than 300 x 300 px
 # Sponsor logos on the product: All sponsor logos must be placed on a page/section/location that is separate from the content of the product. They must contain the company logo, their name, and their website url. The aim is to have a separate section on the product that clearly lists sponsor information. Template acknowledgement copy: “OWASP does not endorse vendors, but we would like to acknowledge the following contributions....”
 # Logos must be created using the following speciﬁcations for placement on the product:
-;Resolution: 300dpi
+*Resolution: 300dpi
-;File Type: .EPS
+*File Type: .EPS
-;Size: No smaller than 5in x 5in
+*Size: No smaller than 5in x 5in
 #All sponsorship logos will be placed on the project product and wiki page for one year or until the next major release. All legacy projects will be given one year to comply with these guidelines starting on January 01, 2014.
 #Logos must be sent to the OWASP Project Leader for inclusion on the OWASP Project wiki page and product. It is the responsibility of the Project Leader to make sure all of his/her project sponsors are properly represented on the OWASP Project wiki page and product.

@@ Line 156: / Line 156: @@
 # Sponsor logos must NEVER be placed anywhere other than within the 'Acknowledgements' tab under the 'Project Sponsors' heading on the project wiki page.
 #Logos must be created using the following speciﬁcations for placement on the wiki page:
-Resolution: 72dpi
+;Resolution: 72dpi
-File Type:.PNG or .JPEG
+;File Type:.PNG or .JPEG
-Size: No longer than 300 x 300 px
+;Size: No longer than 300 x 300 px
 # Sponsor logos on the product: All sponsor logos must be placed on a page/section/location that is separate from the content of the product. They must contain the company logo, their name, and their website url. The aim is to have a separate section on the product that clearly lists sponsor information. Template acknowledgement copy: “OWASP does not endorse vendors, but we would like to acknowledge the following contributions....”
 # Logos must be created using the following speciﬁcations for placement on the product:
-Resolution: 300dpi
+;Resolution: 300dpi
-File Type: .EPS
+;File Type: .EPS
-Size: No smaller than 5in x 5in
+;Size: No smaller than 5in x 5in
 #All sponsorship logos will be placed on the project product and wiki page for one year or until the next major release. All legacy projects will be given one year to comply with these guidelines starting on January 01, 2014.
 #Logos must be sent to the OWASP Project Leader for inclusion on the OWASP Project wiki page and product. It is the responsibility of the Project Leader to make sure all of his/her project sponsors are properly represented on the OWASP Project wiki page and product.

@@ Line 149: / Line 149: @@
 '''GUIDELINES'''
-# Any company or individual can donate funds to a project in exchange for the placement of one sponsorship
+# Any company or individual can donate funds to a project in exchange for the placement of one sponsorship logo on the OWASP project page and product they have sponsored.
-logo on the OWASP project page and product they have sponsored.
+# There is no limit or minimum amount that a company or individual can give in funds to an OWASP Project. However, the minimum amount required to have a company logo on the OWASP Project wiki page and product is $1000 USD.
 # Sponsors that donate less than $1000 USD will have their company name, and website url added to the project wiki page and product. No logo will be placed for donations below this amount.
-# There is no limit or minimum amount that a company or individual can give in funds to an OWASP Project.
+# A sponsor can choose to donate to the overall OWASP Projects budget. If the sponsor chooses to donate to the overall Projects budget, then one logo of their choosing will be placed on the OWASP Projects wiki page under the 'Sponsors' tab. The minimum amount required to have their company logo on the OWASP Project page is $1000 USD.
-However, the minimum amount required to have a company logo on the OWASP Project wiki page and product is
+# If a sponsor is donating funds to a speciﬁc project, then the logo must be placed in the 'Acknowledgements' tab under the 'Project Sponsors' heading using the new OWASP Projects wiki template.
-$1000 USD.
+# Sponsor logos must NEVER be placed anywhere other than within the 'Acknowledgements' tab under the 'Project Sponsors' heading on the project wiki page.
 #Logos must be created using the following speciﬁcations for placement on the wiki page:
 Resolution: 72dpi
 File Type:.PNG or .JPEG
 Size: No longer than 300 x 300 px
 # Sponsor logos on the product: All sponsor logos must be placed on a page/section/location that is separate from the content of the product. They must contain the company logo, their name, and their website url. The aim is to have a separate section on the product that clearly lists sponsor information. Template acknowledgement copy: “OWASP does not endorse vendors, but we would like to acknowledge the following contributions....”
 # Logos must be created using the following speciﬁcations for placement on the product:
 Resolution: 300dpi
 File Type: .EPS
 Size: No smaller than 5in x 5in
 #All sponsorship logos will be placed on the project product and wiki page for one year or until the next major release. All legacy projects will be given one year to comply with these guidelines starting on January 01, 2014.
-#All sponsorship logos will be placed on the project product and wiki page for one year or until the next major
+#Logos must be sent to the OWASP Project Leader for inclusion on the OWASP Project wiki page and product. It is the responsibility of the Project Leader to make sure all of his/her project sponsors are properly represented on the OWASP Project wiki page and product.
-release. All legacy projects will be given one year to comply with these guidelines starting on January 01, 2014.
+#All additional contributors get their name, email address, company name (if desired), and a link to one external website (no logo). No logos should be added for individuals who only contribute time, or for any other sort of contribution.
 # Project Sponsorship Rejection: A Project Leader can decide to accept sponsorships or not, but this must be across the board. In essence, a Project Leader must agree to accept all sponsors, or he/she must agree to deny all sponsorship support. However, if a Project Leader wants to reject a speciﬁc sponsor (not across the board) then an exception will have to be requested from the Board of Directors.
-#Logos must be sent to the OWASP Project Leader for inclusion on the OWASP Project wiki page and product.
+# If a Project Leader fails to follow these guidelines, the OWASP Projects Manager will notify the Project Leader of the infringement. If the infringement continues, the Project Leader may face the removal of all Project Leader privileges until further notice.

@@ Line 130: / Line 130: @@
 '''GUIDELINES'''
-#OWASP Project funds are to be spent on project related expenses ONLY. If your project has more than one
+#OWASP Project funds are to be spent on project related expenses ONLY. If your project has more than one Project Leader, then all Project Leaders must agree to the expense before the purchase.
-Project Leader, then all Project Leaders must agree to the expense before the purchase.
+#Before a purchase is made, the Project Leader must make sure that his/her project actually has the funds to cover the purchase. The easiest way to do this is to communicate your purchase needs to the OWASP Projects Manager, or you can look at the running funds list provided by the Foundation.
 #Project expenses exceeding $500 USD must be communicated to the OWASP Projects Manager before the purchase.
-#Before a purchase is made, the Project Leader must make sure that his/her project actually has the funds to
+#All project expenses will be managed via a reimbursement process. Once a purchase is made, the purchaser must submit a reimbursement request using our reimbursement form. Note: A receipt is required for the reimbursement process to be successful.
-cover the purchase. The easiest way to do this is to communicate your purchase needs to the OWASP Projects
+#Appropriate Project Expenses encompass the following: Graphic Design; Technical Contractor; Web Design; Printing; Software Purchase; Hardware Purchase; Intern Stipends; Team Travel Expenses (for project related work ONLY); Venue Hire (project related work only); Food and Drink (if used to meet with other Project Leaders, contributors, OWASP staff, or an OWASP related function); Project Contractor. Please check with the OWASP Projects Manager before you move forward with a purchase if your expense falls outside of the items listed above.
-Manager, or you can look at the running funds list provided by the Foundation.
+#All OWASP Projects are started with the understanding that they will be volunteer run, and they must remain volunteer run.
 #In the event that a project’s Leaders decide they would like to hire a contractor to work on a particular aspect of the project, then the Project Leaders must manage the recruitment and payment on a task/work assignment basis. Contractors must be paid upon satisfactory completion of the task/work assignment. Additionally, the OWASP Projects Manager must be be informed that project funds will be used to hire a contractor for project development.
-#Project expenses exceeding $500 USD must be communicated to the OWASP Projects Manager before the
+#Hiring Project Leaders as Contractors: If a project’s Leaders decide to hire another Leader as a contractor for a project task/work assignment, then the OWASP Projects Manager must be informed before work begins. Leaders must demonstrate to the OWASP PM that they have searched for 3rd party contractors, before the decision was reached to hire the Project Leader(s) as contractors.The contracted Leader(s) will be paid upon satisfactory completion of the work.
-purchase.
+#As of Jan 01, 2014, OWASP will add a disclaimer to the donation page which states that the Foundation reserves the right to reallocate funds to the general Foundation income account. For all money received for projects prior to Jan 1st - OWASP will make best efforts to contact donors in respect to their donor intent before reallocating funds in the instance of inactive projects.
 ===Project Sponsorship Operational Guidelines===

← Older revision	Revision as of 04:41, 15 February 2017
(No difference)

@@ Line 116: / Line 116: @@
 '''GUIDELINES'''
 #All grant applications submitted to a grant awarding body on behalf of an OWASP Project must be submitted to the OWASP Projects Manager for approval before they are submitted to the grant awarding organization.
-#All grant funds awarded to an OWASP Project must be spent in accordance to the project plan and budget
+#All grant funds awarded to an OWASP Project must be spent in accordance to the project plan and budget submitted to the OWASP Projects Manager, and the grant awarding organization, prior to the award of the funds.
 #All expenses to be made using grant awarded funds must be pre-approved by the OWASP Projects Manager.
-#Awarded grant funds may not be used, re-allocated, or given away to any other initiative or OWASP Project for
+#Awarded grant funds may not be used, re-allocated, or given away to any other initiative or OWASP Project for any reason.
-any reason.
+#It is the Project Leader’s responsibility to make sure he/she is working with the OWASP Projects Manager to manage grant related expenses and spending.
-#It is the Project Leader’s responsibility to make sure he/she is working with the OWASP Projects Manager to
+#It is the Project Leader’s responsibility to make sure they are delivering the product outlined in the grant proposal using the funding made available by the grant awarding body.
-manage grant related expenses and spending.
+#In the event that the awarded project terminates its activities, the OWASP Projects Manager will notify the sponsor or grant awarding organization, and inform them of the cease of activity. The grant awarding organization can then decide to either take back the funds, or donate them to another project, to the general OWASP Project fund, or to another part of the OWASP organization that accepts sponsorships.
 ===Project Spending Policy===

@@ Line 96: / Line 96: @@
 You and the Foundation hereby accept and agree to the following terms and conditions:
-# The donation of your project means that you agree to hand over all past, present and future contributions of
+# The donation of your project means that you agree to hand over all past, present and future contributions of source code and documentation to the Foundation, however submitted to the Foundation, excluding any submissions that are conspicuously marked or otherwise designated in writing by You.
-source code and documentation to the Foundation, however submitted to the Foundation, excluding any
+# You hereby grant to the Foundation a non-exclusive, irrevocable, worldwide, no-charge, transferable copyright license to use, execute, prepare derivative works of, and distribute (internally and externally, in object code and, if included in your Contributions, source code form) your Contributions. Except for the rights granted to the Foundation in this paragraph, You reserve all right, title and interest in and to your Contributions. OWASP will always release a free and open version of anything we distribute that includes your Contributions.
-submissions that are conspicuously marked or otherwise designated in writing by You.
+# You may continue to be involved in the donated project, but you may no withdraw your project from the OWASP Foundation once the project donation process has been completed. The project donation process is complete once the Foundation receives as signed version of this form from you.
-# You hereby grant to the Foundation a non-exclusive, irrevocable, worldwide, no-charge, transferable copyright
+# You represent that you are legally entitled to grant the above license. If your employer(s) have rights to intellectual property that you create, you represent that you have received permission to make the Contributions on behalf of that employer, or that your employer has waived such rights for your Contributions to the Foundation.
-license to use, execute, prepare derivative works of, and distribute (internally and externally, in object code and, if
+# You represent that, except as disclosed in your Project Donation submission(s), each of your Contributions is your original creation. You represent that your Contribution submission(s) include complete details of any license or other restriction (including, but not limited to, related patents and trademarks) associated with any part of your Contribution(s) (including a copy of any applicable license agreement). You agree to notify the Foundation of any facts or circumstances of which you become aware that would make Your representations in this Agreement inaccurate in any respect.
-included in your Contributions, source code form) your Contributions. Except for the rights granted to the
+# You are not expected to provide support for your Contributions, except to the extent you desire to provide support. You may provide support for free, for a fee, or not at all. Your Contributions are provided as-is, with all faults defects and errors, and without warranty of any kind (either express or implied) including, without limitation, any implied warranty of merchantability and ﬁtness for a particular purpose and any warranty of non-infringement.
 Please sign: __________________________________ Date: ________________