Electronics & Programming

develissimo

Open Source electronics development and programming

  • You are not logged in.
  • Root
  • » PHP
  • » [PHP-DEV] [GSOC] Ideas? [RSS Feed]

#1 March 9, 2008 16:18:30

Hannes M.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PHP-DEV] [GSOC] Ideas?


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 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

http://wiki.php.net/gsoc/2008--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#2 March 9, 2008 18:04:11

Pierre J.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PHP-DEV] [GSOC] Ideas?


On Sun, Mar 9, 2008 at 4:17 PM, 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 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 seehttp://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,
--
Pierrehttp://blog.thepimp.net|http://www.libgd.org--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#3 March 10, 2008 01:03:22

Alan K.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PHP-DEV] [GSOC] Ideas?


I do think the wiki page needs some forwarding / segmenting.. etc.Who can/should contribute to it, (how it may not reflect the views ofthe php group..)Who 'owns' it in the end, and is going to delete proposals they thinkare a bit off-topic etc...Ideas from any .php net member relating to PHP extensions/core..Ideas for projects relating to documentation / PHP QA, supportinfrustructure.PEAR ideas...??Obviously what get's done really depends on the volunteers, and to somedegree finding a project that 'excites' someone... (now there's a realchallenge)..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 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

http://wiki.php.net/gsoc/2008--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#4 March 10, 2008 01:40:10

Pierre J.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PHP-DEV] [GSOC] Ideas?


HI Alan!

On Mon, Mar 10, 2008 at 1:02 AM, Alan Knowles <> wrote:
> 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...

I believe in self discipline. As long as RFC are in the proposal
phase, it can be marked as such, no harm (namespace rfc)

> Ideas from any .php net member relating to PHP extensions/core..

> Ideas for projects relating to documentation / PHP QA, support
> infrustructure.
>
> PEAR ideas...??

I don't think PEAR as a whole has a place there. PEAR has its own wiki
and is an independent project. The pear installer itself can certainly
be part of GSOC though (keeping the order of the three cases listed by
Lukas ealier).

> 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)..

Yes, that's the challenge. To find someone motivated enough and
willing to actually join the project is somehow hard. To find someone
who will disappear as soon as the gsoc is over is "easier" ;)

Cheers,
--
Pierrehttp://blog.thepimp.net|http://www.libgd.org--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

Board footer

Moderator control

Enjoy the 16th of December
PoweredBy

The Forums are managed by develissimo stuff members, if you find any issues or misplaced content please help us to fix it. Thank you! Tell us via Contact Options
Leave a Message
Welcome to Develissimo Live Support