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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
