Re: [PHP-DOC] GSoC 2012
Philips, Just about the editor, we can add this to the TODO list who can interest some developers : Porting the editor to ExtJs 4. Actually, the editor use ExtJs 3 and porting to ExtJs4 is a hard task. Best, Yannick 2012/2/27 Philip Olson > > On Feb 24, 2012, at 11:30 AM, Daniel Brown wrote: > > > On Wed, Feb 22, 2012 at 15:42, Philip Olson wrote: > >> > >> Hello everyone, > >> > >> Agreed, that we can't add 'Add PHP examples to the PHP documentation' > >> as a project for the GSoC. Now, we can do this ourselves of course > >> (and probably should) but this thread is specific to the GSoC. > >> > >> But, perhaps a project could exist that's specific to using PHP > >> extensions. Nothing obvious comes to mind, but a group of smaller > >> projects involving extensions may or may not work. Some creativity > >> would be required to make that work for/with us. > >> > >> So it feels like Adam and Daniel would make a good team for > >> administrating this, and having co-admins is allowed via the GSoC > >> app. I believe both Hannes and Marcus performed this task the last > >> time we did this. > >> > >> Also, we already have the following mailing list: > >> > >> Mail: php-g...@lists.php.net > >> News: http://news.php.net/php.gsoc > >> > >> And as Adam alluded to, our GSoC (and related) situation is outdated. > >> For example: > >> > >> https://wiki.php.net/gsoc > > > >So before this gets overlooked or derailed, is there enough > > general interest to participate again this year, or will it just > > fizzle out before we even apply like it did in 2010 and last year? > > Isn't it your job to generate interest? :) An early php.net news > entry should help, one that also asks for additional ideas and > proposals. > > Regards, > Philip >
Re: [PHP-DOC] GSoC 2012
On Mon, Feb 27, 2012 at 14:09, Philip Olson wrote: > > Isn't it your job to generate interest? :) An early php.net news > entry should help, one that also asks for additional ideas and > proposals. It would be if I were, indeed, involved. So far, the only times it's been mentioned are when I volunteered and when you suggested Adam and I could co-chair. Then the discussion died entirely. -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] GSoC 2012
On Feb 24, 2012, at 11:30 AM, Daniel Brown wrote: > On Wed, Feb 22, 2012 at 15:42, Philip Olson wrote: >> >> Hello everyone, >> >> Agreed, that we can't add 'Add PHP examples to the PHP documentation' >> as a project for the GSoC. Now, we can do this ourselves of course >> (and probably should) but this thread is specific to the GSoC. >> >> But, perhaps a project could exist that's specific to using PHP >> extensions. Nothing obvious comes to mind, but a group of smaller >> projects involving extensions may or may not work. Some creativity >> would be required to make that work for/with us. >> >> So it feels like Adam and Daniel would make a good team for >> administrating this, and having co-admins is allowed via the GSoC >> app. I believe both Hannes and Marcus performed this task the last >> time we did this. >> >> Also, we already have the following mailing list: >> >> Mail: php-g...@lists.php.net >> News: http://news.php.net/php.gsoc >> >> And as Adam alluded to, our GSoC (and related) situation is outdated. >> For example: >> >> https://wiki.php.net/gsoc > >So before this gets overlooked or derailed, is there enough > general interest to participate again this year, or will it just > fizzle out before we even apply like it did in 2010 and last year? Isn't it your job to generate interest? :) An early php.net news entry should help, one that also asks for additional ideas and proposals. Regards, Philip
Re: [PHP-DOC] GSoC 2012
On Wed, Feb 22, 2012 at 15:42, Philip Olson wrote: > > Hello everyone, > > Agreed, that we can't add 'Add PHP examples to the PHP documentation' > as a project for the GSoC. Now, we can do this ourselves of course > (and probably should) but this thread is specific to the GSoC. > > But, perhaps a project could exist that's specific to using PHP > extensions. Nothing obvious comes to mind, but a group of smaller > projects involving extensions may or may not work. Some creativity > would be required to make that work for/with us. > > So it feels like Adam and Daniel would make a good team for > administrating this, and having co-admins is allowed via the GSoC > app. I believe both Hannes and Marcus performed this task the last > time we did this. > > Also, we already have the following mailing list: > > Mail: php-g...@lists.php.net > News: http://news.php.net/php.gsoc > > And as Adam alluded to, our GSoC (and related) situation is outdated. > For example: > > https://wiki.php.net/gsoc So before this gets overlooked or derailed, is there enough general interest to participate again this year, or will it just fizzle out before we even apply like it did in 2010 and last year? -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] GSoC 2012
On Thu, Feb 23, 2012 at 12:08 AM, Daniel Brown wrote: > Unfortunately, it's blocked in the Sandwich Islands and American > Samoa (that part's actually true). And Germany :(
Re: [PHP-DOC] GSoC 2012
On Wed, Feb 22, 2012 at 15:42, Philip Olson wrote: > > So it feels like Adam and Daniel would make a good team for > administrating this, and having co-admins is allowed via the GSoC > app. I believe both Hannes and Marcus performed this task the last > time we did this. > > And as Adam alluded to, our GSoC (and related) situation is outdated. > For example: > > https://wiki.php.net/gsoc To take the first step, I've successfully brought us up to speed with the smoothest, most professional, most uber-awesome video presentation anyone could ever do in eternity: http://links.parasane.net/lxoi Unfortunately, it's blocked in the Sandwich Islands and American Samoa (that part's actually true). -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] GSoC 2012
On Feb 22, 2012, at 9:08 AM, Daniel Brown wrote: > On Wed, Feb 22, 2012 at 08:46, Klaus Silveira wrote: >> There are many parts of the documentation that could use clear examples in >> *code*, specially extensions like SSH and LDAP. > >I can't say with absolute certainty that it's still the same, but > in the past, documentation was explicitly prohibited as a project. > >And, a quick look shows that hasn't changed: > > > http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#documentation Hello everyone, Agreed, that we can't add 'Add PHP examples to the PHP documentation' as a project for the GSoC. Now, we can do this ourselves of course (and probably should) but this thread is specific to the GSoC. But, perhaps a project could exist that's specific to using PHP extensions. Nothing obvious comes to mind, but a group of smaller projects involving extensions may or may not work. Some creativity would be required to make that work for/with us. So it feels like Adam and Daniel would make a good team for administrating this, and having co-admins is allowed via the GSoC app. I believe both Hannes and Marcus performed this task the last time we did this. Also, we already have the following mailing list: Mail: php-g...@lists.php.net News: http://news.php.net/php.gsoc And as Adam alluded to, our GSoC (and related) situation is outdated. For example: https://wiki.php.net/gsoc Regards, Philip
Re: [PHP-DOC] GSoC 2012
On Wed, Feb 22, 2012 at 08:46, Klaus Silveira wrote: > There are many parts of the documentation that could use clear examples in > *code*, specially extensions like SSH and LDAP. I can't say with absolute certainty that it's still the same, but in the past, documentation was explicitly prohibited as a project. And, a quick look shows that hasn't changed: http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#documentation -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] GSoC 2012
There are many parts of the documentation that could use clear examples in *code*, specially extensions like SSH and LDAP. On Wed, Feb 22, 2012 at 11:43 AM, Derick Rethans wrote: > On Wed, 22 Feb 2012, Klaus Silveira wrote: > > > What about the documentation itself, guys? The tools sure need help, but > > the documentation could benefit from a code rush. > > It's called Google Summer of *Code*. > > Derick >
Re: [PHP-DOC] GSoC 2012
On Wed, 22 Feb 2012, Klaus Silveira wrote: > What about the documentation itself, guys? The tools sure need help, but > the documentation could benefit from a code rush. It's called Google Summer of *Code*. Derick
Re: [PHP-DOC] GSoC 2012
What about the documentation itself, guys? The tools sure need help, but the documentation could benefit from a code rush. On Wed, Feb 22, 2012 at 9:09 AM, Alexander Moskaliov wrote: > Hello! > > 2012/2/22 Philip Olson : > > - Online Editor > >- Possible mentors: Alexander, Yannick > Sorry, but I can't be mentor for some personal reasons(such as my bad > english, wedding, move in new home, etc.) =) > Try ask Yannick. > -- Klaus Silveira (011) 8564-2492 www.klaussilveira.com
Re: [PHP-DOC] GSoC 2012
Hello! 2012/2/22 Philip Olson : > - Online Editor > - Possible mentors: Alexander, Yannick Sorry, but I can't be mentor for some personal reasons(such as my bad english, wedding, move in new home, etc.) =) Try ask Yannick.
Re: [PHP-DOC] GSoC 2012
On 02/21/2012 06:50 PM, Philip Olson wrote: > Hello doc geeks, > > I'm not sure if PHP will join the GSoC[1] effort this year, but regardless > it's worth coming up with worthy tasks. We've had great success with PhD > in the past, so here are a few rough ideas: > > - PhD > - Possible mentors: Hannes, Moacir > - What: Renders DocBook > - Related links: > - 2010 proposal: http://docbook.xmlpress.net/tiki-index.php?page=PhD > - Old TODO: https://wiki.php.net/doc/todo/phd > - Source: http://svn.php.net/viewvc/phd/trunk/ > - TODO: * > > - Online Editor > - Possible mentors: Alexander, Yannick > - What: Web-based DocBook editor > - Related links: > - TODO: > http://git.php.net/?p=web/doc-editor.git;a=blob_plain;f=TODO;hb=HEAD > - Site: https://edit.php.net/ > - Source: http://git.php.net/?p=web/doc-editor.git > - TODO: * > > - Docweb > - Possible mentors: Hannes, Philip, anyone > - What: Tool for helping manage the PHP documentation > - Related links: > - Site: http://doc.php.net/ > - Source: http://git.php.net/?p=web/doc.git > - TODO: > - We barely use this site, so could we change this? > - Integrate more doc-base/scripts/ stuff? > > If we want to join the GSoC then I'm guessing we'll need to lead the charge. > Please speak up if you're willing to administrate the GSoC for the entire > PHP project. One to add to the list. Gearman worker support in php-fpm that I brought up in 2010 but never got to myself. See this thread: http://www.serverphorums.com/read.php?7,161054 I'll volunteer to mentor this one myself. Like I explained in the thread, it may not actually need to be Gearman-specific. It is simple enough for userspace PHP code to register themselves with gearmand, so if we go that route this is becomes about adding multiple worker pools support to fpm and being able to indicate that these pools aren't actually FastCGI workers. By not making them Gearman-specific they would be useful for managing beanstalkd workers and custom libevent, ZeroMQ and whatever else people are writing these days that need robust process management. For people already running nginx+php-fpm for their web serving needs, this would reduce the number of moving parts and make it easier to manage. There are a bunch of efficiencies I can think of that would come from centralizing this process management in one place. -Rasmus
Re: [PHP-DOC] GSoC 2012
On 22 February 2012 10:50, Philip Olson wrote: > If we want to join the GSoC then I'm guessing we'll need to lead the charge. > Please speak up if you're willing to administrate the GSoC for the entire > PHP project. I did put my hand up for that on IRC a week or two back, so I'm still fine with that if need be. > Also, here's the general ideas page for the PHP project: > - http://wiki.php.net/ideas Some of this is pretty out of date (referring to the FPM patch as a patch, for instance), so the first step is going to be pruning back the list to what still makes sense. We've basically got about two weeks to whip this into shape, gather new ideas, find mentors, et cetera. Adam
Re: [PHP-DOC] GSoC 2012
On Feb 21, 2012 9:51 PM, "Philip Olson" wrote: > > Hello doc geeks, > > I'm not sure if PHP will join the GSoC[1] effort this year, but regardless > it's worth coming up with worthy tasks. We've had great success with PhD > in the past, so here are a few rough ideas: > > - PhD >- Possible mentors: Hannes, Moacir >- What: Renders DocBook >- Related links: > - 2010 proposal: http://docbook.xmlpress.net/tiki-index.php?page=PhD > - Old TODO: https://wiki.php.net/doc/todo/phd > - Source: http://svn.php.net/viewvc/phd/trunk/ >- TODO: * > > - Online Editor >- Possible mentors: Alexander, Yannick >- What: Web-based DocBook editor >- Related links: > - TODO: http://git.php.net/?p=web/doc-editor.git;a=blob_plain;f=TODO;hb=HEAD > - Site: https://edit.php.net/ > - Source: http://git.php.net/?p=web/doc-editor.git >- TODO: * > > - Docweb >- Possible mentors: Hannes, Philip, anyone >- What: Tool for helping manage the PHP documentation >- Related links: > - Site: http://doc.php.net/ > - Source: http://git.php.net/?p=web/doc.git >- TODO: > - We barely use this site, so could we change this? > - Integrate more doc-base/scripts/ stuff? > > If we want to join the GSoC then I'm guessing we'll need to lead the charge. > Please speak up if you're willing to administrate the GSoC for the entire > PHP project. > > Also, here's the general ideas page for the PHP project: > - http://wiki.php.net/ideas > > Regards, > Philip > > [1] http://www.google-melange.com/gsoc/homepage/google/gsoc2012 Incidentally, I was going to send a similar message tomorrow, volunteering to oversee the entire PHP involvement through from start to finish, applications, reviews, et al. I'd love to see the success we've had in the years we've done it, as well as increasing the retention of the participants as permanent committers. I wanted to check in with folks on IRC tomorrow morning to gauge their interest as well, since it would not only be the docs, but core and subprojects (if any) as well.
