Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36065
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.169 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=Kjv38Fg+8dCQc8aX6vrsu7ql9XgcFxiVcdEQhlEpz/BgsenYmkGS6YIN5uGJnuqcVY20RuQHmZTFx53e5dZQjdBGioEL9D0uEfkuBoAqSBGsUWi5jYD4y92sVEfSf3IUz2fUiKnlkeftzPHu4U8KoaY2xaWyKvFieqqK6bS8/ZA=
Message-ID: <7f3ed2c30803090817l7986fcb8x72c4ad44e78b891e@mail.gmail.com>
Date: Sun, 9 Mar 2008 16:17:51 +0100
To: "PHP Development" <internals@lists.php.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [GSOC] Ideas?
From: hannes.magnusson@gmail.com ("Hannes Magnusson")

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