Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36068
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain akbkhome.com designates 202.81.246.113 as permitted sender)
Message-ID: <47D47AA0.8010001@akbkhome.com>
Date: Mon, 10 Mar 2008 08:02:40 +0800
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: Hannes Magnusson <hannes.magnusson@gmail.com>
CC: PHP Development <internals@lists.php.net>
References: <7f3ed2c30803090817l7986fcb8x72c4ad44e78b891e@mail.gmail.com>
In-Reply-To: <7f3ed2c30803090817l7986fcb8x72c4ad44e78b891e@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [GSOC] Ideas?
From: alan@akbkhome.com (Alan Knowles)

I do think the wiki page needs some forwarding / segmenting.. etc.
Who can/should contribute to it, (how it may not reflect the views of 
the php group..)
Who 'owns' it in the end, and is going to delete proposals they think 
are a bit off-topic etc...

Ideas from any .php net member relating to PHP extensions/core..

Ideas for projects relating to documentation / PHP QA, support 
infrustructure.

PEAR ideas...??

Obviously what get's done really depends on the volunteers, and to some 
degree finding a project that 'excites' someone... (now there's a real 
challenge)..

Regards
Alan


Hannes Magnusson 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.
>
>
> Couple of ideas I'd love the see implemented:
>
> New bugtracker for all the *.php.net projects (one-tracker-rules-them-all).
>  - Feature requests for specific extensions/module/class/component
>  - Documentation bug for specific extension/module/class/component
>  - "Milestones"
>  - When a FR is closed then its automatically classified as
> documentation problem
>  - When a commit contains "bug#n" the commit message and links to the
> changed files (diffs) are automatically added to the report
>  - Possibility to reply to reports (add comment, change status) via email
>  - Notification system (i.e. "watch this report") which sends email to
> people watching that report on changes
>  - Monthly reminders to reporters of reports with status
> "feedback"/"no feedback"
>  - No #%"#$& signup required to file reports
>  - Possibility to attach files (patch/phpt)
>  - Developer authentication against CVS (fallback to pear/peclweb) accounts
>  - Support for openid (i.e. users with openid don't have to fill out a
> completely unreadable CAPTCHA)
>
>
> PhD:
>  - PDF format support
>  - CHM format support
>  - man format support
>  - PEAR/Gtk "themes"
>  - Create a true indexer
>  - Implement the rest of the standard Docbook elements+attributes
>  - Implement default "themes" for all formats
>  - Support for dbhtml processing instructions
>
> Random other ideas (most probably too small):
>  - openid extension
>  - 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
>  - reST to html/docbook parser
>  - translation tool allowing users to suggest better translations
> ...
>
> So, what do you guys think? Have any ideas?
>
> -Hannes
>
> [1] http://wiki.php.net/gsoc/2008
>
>