pear:gsoc:2009
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
pear:gsoc:2009 [2009/03/10 20:34] – dufuz | pear:gsoc:2009 [2009/03/10 21:07] – add PEAR CI idea ashnazg | ||
---|---|---|---|
Line 14: | Line 14: | ||
===== PHP_CodeSniffer XSS and SQL security analyzer ===== | ===== PHP_CodeSniffer XSS and SQL security analyzer ===== | ||
- | //Possible mentor: [[davidc@php.net|David Coallier]]// | + | //Possible mentor: [[davidc@php.net|David Coallier]], [[mp@manuel-pichler.de|Manuel Pichler]]// |
Implement a Cross Side Scripting and SQL Injection security analyzer to find security threats in your " | Implement a Cross Side Scripting and SQL Injection security analyzer to find security threats in your " | ||
Line 83: | Line 83: | ||
===== Extensible source code highlighter ===== | ===== Extensible source code highlighter ===== | ||
- | //Possible mentor: | + | //Possible mentor: |
The basic scope of this component is highlighting source code of various programming languages. It is limited to common text based one dimensional programming languages, not designed to also work for esoteric languages. Several existing syntax highlighters already can directly generate HTML syntax highlights, but this is not feasible for all applications. | The basic scope of this component is highlighting source code of various programming languages. It is limited to common text based one dimensional programming languages, not designed to also work for esoteric languages. Several existing syntax highlighters already can directly generate HTML syntax highlights, but this is not feasible for all applications. | ||
- | The approach basically works by using common EBNFs for the definition of the syntax of the scanned programming language, simplification of the resulting AST using sorts and then visiting the simplified AST into different output formats, like HTML or a line based token stream. A more detailed requirements document can be found here: http:// | + | The approach basically works by using common |
====Deliverables==== | ====Deliverables==== | ||
Line 106: | Line 106: | ||
//Possible mentors: Helgi, Brett// | //Possible mentors: Helgi, Brett// | ||
- | This will involve working on Pyrus which is the next generation PEAR installer. | + | This will involve working on Pyrus installer |
PHP 5.3+, namespaces and all the goodies that come with PHP 5.3 | PHP 5.3+, namespaces and all the goodies that come with PHP 5.3 | ||
+ | |||
+ | This includes writing good chunks of the installer from scratches, write extensive unit tests, design APIs and still make it work with existing channels and packages. | ||
+ | This will require very good understanding of PHP, XML and other technologies a like. | ||
+ | |||
+ | |||
+ | ===== PEAR CI ===== | ||
+ | //Possible mentors: // | ||
+ | |||
+ | A proof-of-concept for a " | ||
+ | - runs builds against multiple PHP versions across multiple OSs (via VMs if necessary) | ||
+ | - aggregates build results from all sources, even remote ones | ||
+ | |||
+ | ====Deliverables==== | ||
+ | |||
+ | ===Midterm=== | ||
+ | A working CI instance executing builds on multiple PHP versions locally | ||
+ | ===Final=== | ||
+ | Backend processing pulls/ | ||
+ | |||
+ | The additional code/ | ||
+ | |||
+ | PEAR can benefit by the proof instance being retained after completion. |
pear/gsoc/2009.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1