gsoc:2009:ideas

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
gsoc:2009 [2009/03/30 23:47] – pbiggargsoc:2009:ideas [2011/04/06 10:59] – external edit 127.0.0.1
Line 5: Line 5:
 Before you submit your proposal, you are encouraged to contact the possible mentors for the project you are applying. If the project hasn't any mentor assigned or if you are submiting an off-list project, please contact one of our [[http://php.net/mailing-lists.php|mailing lists]] to discuss the proposal before submiting it. Before you submit your proposal, you are encouraged to contact the possible mentors for the project you are applying. If the project hasn't any mentor assigned or if you are submiting an off-list project, please contact one of our [[http://php.net/mailing-lists.php|mailing lists]] to discuss the proposal before submiting it.
  
-Priority will be given to proposals that are directly related to the PHP Project, this includes PECL. [[http://pear.php.net|PEAR]] has it's own ideas page over [[pear/gsoc/2009|here]]. If we have any spare slots then we will consider non PHP Project proposals.+Priority will be given to proposals that are directly related to the PHP Project, this includes PECL. [[http://pear.php.net|PEAR]] has it's own ideas page over [[gsoc:pear:gsoc:2009|here]]. If we have any spare slots then we will consider non PHP Project proposals.
  
 If your project is to be written in PHP, please make sure you read the [[http://pear.php.net/manual/en/standards.php|PEAR Coding Standards]] when applying. If your project is to be written in PHP, please make sure you read the [[http://pear.php.net/manual/en/standards.php|PEAR Coding Standards]] when applying.
Line 91: Line 91:
 //Possible mentors: [[bjori@php.net|Hannes Magnusson]] // //Possible mentors: [[bjori@php.net|Hannes Magnusson]] //
  
-[[doc:PhD]] is the tool that renders the DocBook based documentation for both the PHP Manual and PEAR Manual. It uses XMLReader to read the XML, so it has many obvious drawbacks but XMLReader is also the reason why it's so blazing fast.+[[doc:phd]] is the tool that renders the DocBook based documentation for both the PHP Manual and PEAR Manual. It uses XMLReader to read the XML, so it has many obvious drawbacks but XMLReader is also the reason why it's so blazing fast.
  
 Today PhD is PHP.net centric, meaning it contains several "rules" and "workarounds" that are only applicable to PHP.net. The project goals: Today PhD is PHP.net centric, meaning it contains several "rules" and "workarounds" that are only applicable to PHP.net. The project goals:
Line 100: Line 100:
 For questions and thoughts please join the #php.doc IRC channel on EFnet and/or write the PHP Documentation list at phpdoc@lists.php.net For questions and thoughts please join the #php.doc IRC channel on EFnet and/or write the PHP Documentation list at phpdoc@lists.php.net
  
-===== Xdebug path-base code-coverage analysis ==== +===== Xdebug: Support for Path Coverage ===== 
-//Possible mentors: [[derick@php.net|Derick Rethans]] //+//Possible mentors: [[derick@php.net|Derick Rethans]], [[sebastian@php.net|Sebastian Bergmann]]//
  
-[[http://xdebug.org|Xdebug]] is a tool for debugging, analyzing and profiling PHP applications. One of its features is analyzing which code has been executed in a function. At the moment this only happens with a line-based resolution. This project is about extending this to analyze which code *paths* are being covered in functions. This project idea requires C-skills, and you will get very intimate with the PHP internals. Feel free to drop by in either #php.pecl or #xdebug on EFnet (and look for Derick) if you have any questions.+[[http://xdebug.org|Xdebug]] is a tool for debugging, analyzing and profiling PHP applications. One of its features is analyzing which code has been executed in a function. At the moment this only happens with a line-based resolution. This project is about extending this to analyze which code *paths* are being covered in functions and methods. This project idea requires C-skills, and you will get very intimate with the PHP internals. Feel free to drop by in either #php.pecl or #xdebug on Freenode (and look for Derick) if you have any questions.
  
-===== Xdebug remote debugging support for watch expressions ====+===== Xdebug: Remote Debugging Support for Watch Expressions ====
 //Possible mentors: [[derick@php.net|Derick Rethans]] // //Possible mentors: [[derick@php.net|Derick Rethans]] //
  
Line 143: Line 143:
 Work has started on an online editor for the PHP Manual. The student would help get this tool up and running for live use at php.net. The tool performs the following actions: Work has started on an online editor for the PHP Manual. The student would help get this tool up and running for live use at php.net. The tool performs the following actions:
  
-  * Allows CVS users to make and commit changes+  * Allows SVN users to make and commit changes
   * Allow anybody to create patches, which are sent to a patch queue for developers review   * Allow anybody to create patches, which are sent to a patch queue for developers review
   * Works with all translations   * Works with all translations
Line 149: Line 149:
 Resources of interest: Resources of interest:
  
-  * Demo: http://ytorres.dyndns.org:81/doc-editor/ (user: cvsread pass: phpfi)+  * Demo: http://doc.php.net/editor/
   * Videos showing use: http://tmp.cweiske.de/phpeditor-videos/   * Videos showing use: http://tmp.cweiske.de/phpeditor-videos/
-  * The source in CVS: http://cvs.php.net/viewvc.cgi/doc-editor/ +  * The source in SVN: http://svn.php.net/viewvc/web/doc-editor/ 
-  * TODO: http://cvs.php.net/viewvc.cgi/doc-editor/TODO?view=log+  * TODO: http://svn.php.net/viewvc/web/doc-editor/trunk/TODO?view=markup
  
  
gsoc/2009/ideas.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1

Page Tools