Re: [GSOC] Ideas?
| From: | Pierre Joye | Date: | Sun, 09 Mar 2008 17:03:29 +0000 |
| Subject: | Re: [GSOC] Ideas? | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-36066@lists.php.net to get a copy of this message | ||
On Sun, Mar 9, 2008 at 4:17 PM, Hannes Magnusson
<hannes.magnusson@gmail.com> wrote:
> Hi all
>
> We should probably discuss some ideas for Google Summer of Code this year.
> I see people have already added few to the wiki page[1] which is great
> and all but wikis aren't for discussions..
>
> The plan as I see it:
> Discuss ideas. Draft them up on the wiki. Move them to php.net/ideas
> when they are solid enough.
I don't really see a point to move them there. wiki.php.net/gsoc/2008
is just fine. One can create sub pages to complete a proposal.
> New bugtracker for all the *.php.net projects (one-tracker-rules-them-all).
What's up with Jani's work?
> Random other ideas (most probably too small):
> - openid extension
I'm not sure it is a good idea to bring the relatively small API into
an extension. The slow and complex part is already possible with
openssl (Dmitry's patch).
> - threaded run-tests.php and graphical stats
> - mirror-test bot rewrite
> - automatically run relevant tests on new commit (i.e commits to
> ext/foo triggers test run for ext/foo/tests)
> - daily/weekly buildfailure mails to internals@ (win/linux/solaris/bsd/mac/..)
> - doxygen-to-phpdoc/docbook
> - user-submitted-coverage to gcov
Something like what is done with ctest (cmake's test tool) would rock.
I can provide links if there is an interest (or see http://cmake.org)
> - reST to html/docbook parser
I somehow have doubts about reST now that we have a wiki. Too much
formats will bring more confusions than really helping to write docs,
specs or RFC.
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org