OWASP Java File I O Security Project - Health Check

[Claudia Casanovas]

Hello Project Leader:

We have recently have done a Health Check on your project accordance with Project Process work flow.

We have the following findings:Currently has a google code repository which is expired this year and needs to be moved to github or any other repository that you decide.  No updates have been made to the  wiki page since August 2014.

Wiki page: https://www.owasp.org/index.php/OWASP_Java_File_I_O_Security_Project

google code: https://code.google.com/archive/p/owasp-java-fileio/

Unfortunately at this time the project will added to the  OWASP Archived Projects of the OWASP Project Inventory and marked as in-active.

Please Note: At the time your project becomes active again, the OWASP Foundation will allocate a $500 budget amount to help you and your project continue its OWASP activities.  Additional funding needs can be requested on the OWASP wiki site under funding.

If you have any updates or a different repository, please advise at your earliest convenience. 

--

Claudia Aviles-Casanovas

Project Coordinator

Phone:973-288-1697

[August Detlefsen]

Hi Claudia, 

The project was actually exported to GitHub some time ago: https://github.com/augustd/owasp-java-fileio

I have updated the OWASP wiki to reflect the new URL. 

The code compiles, and all tests pass. Thus I consider this project to essentially done -it has achieved its original goal of providing a File I/O security library that is separate from ESAPI and has no dependencies. Other than sorely needing documentation, what else is needed in order to un-archive this project? 

Thanks,

August 

[Claudia Casanovas]

Hello Project Review Team,

Please advise of next steps and decision on adding the project back to the OWASP Inventory List.

Updates from Project Leader:

https://github.com/augustd/owasp-java-fileiohttps://www.owasp.org/index.php?title=OWASP_Java_File_I_O_Security_Project&action=history

Thank you 

Claudia Casanovas