Google Summer of Code View as Markdown

Google are running the Summer of Code again this year, and Dan Brown
and I have tentatively agreed to act as organisation administrators if
we can get an application together. We have a week from today to
apply, but before we can, we need updated ideas. Our old ideas list is
at https://wiki.php.net/ideas — if we can get this cleaned up and
updated, then I can turn it into a single ideas page for our
application.

It has just been pointed out to me by Philip that the ideas page was a
general ideas page rather than GSoC specific ideas — my apologies for
missing that. The projects where I said "maybe not for GSoC" are
obviously not intended for GSoC. :)

Adam

I'd be willing to be a mentor.

-----Original Message-----
From: adam@adamharvey.name [mailto:adam@adamharvey.name] On Behalf Of Adam Harvey
Sent: Thursday, March 01, 2012 8:00 PM
To: PHP internals
Subject: [PHP-DEV] Google Summer of Code

Hi all,

Google are running the Summer of Code again this year, and Dan Brown and I have tentatively agreed to act as organisation administrators if we can get an application together. We have a week from today to apply, but before we can, we need updated ideas. Our old ideas list is at https://wiki.php.net/ideas — if we can get this cleaned up and updated, then I can turn it into a single ideas page for our application.

Here's a summary of what's there at the moment, the suggested mentors (if your name is on this list, an indication of whether the idea is still valid and whether you'd still be interested in mentoring would be appreciated), and any thoughts I have on whether they're still viable ideas. Updates welcome — new ideas very very welcome.

• Automatic Code Checker (suggested mentor: Nuno Lopes): still sounds like a good idea to me.

• Bugs Update (Philip Olson): this seems really thin for a whole project. Are there other improvements currently pending that could turn this into a broader refresh of the bug tracker?

• PHP/PECL Build Bot (Elizabeth Smith): sounds good, if we can get hardware to support it.

• Zend Bytecode to LLVM Converter (Nuno Lopes): sounds good.

• Abstract Extension API and Dependency Interface (Brian Shire, Andrei
  Zmievski): sounds good.

• CGI/FastCGI SAPI Improvement (Dmitry Stogov): pretty sure the merge of FPM has made this moot.

• Get Involved - Writing it (Philip Olson): I think the GSoC prohibition on documentation projects would prevent this.

• PHP-GTK documentation (no mentor): as above.

• Integrated Code Coverage of C and PHP Code (Sebastian Bergmann): sounds good.

• Patch Server (no mentor): could this link in with the Build Bot project above?

• PHP Authentication System (??): this is three years old — may still be relevant, but the page itself would need a serious update.

• New Mirror Management System (Daniel Brown): not sure if this is relevant — systems guys? Daniel?

• php.net search improvements (??): sounds good.

• PHP.net search SQLite wrapper (??): probably should be rolled into the previous project.

• run-tests.php improvements (Zoe Slattery, Stefan Priebsch): sounds good; I'd be prepared to mentor this if we needed to find a new mentor, having just done a bit of exploratory work on this myself of late.

• Revamping user comments at php.net (Philip Olson): might also be a bit thin as written, but it depends on where it goes.

Remember, we're not limited to ideas on our ideas page (students can also suggest ideas, and often do), but having a strong ideas page will greatly enhance our chances of being accepted, particularly in light of having missed the last couple of GSoCs.

As I said, both updates to the existing list and new ideas would be very welcome, either here or on the aforementioned Wiki page.

Thanks,

Adam

• New Mirror Management System (Daniel Brown): not sure if this is
  relevant — systems guys? Daniel?

No, the system I had been drafting was mainly to fix a few issues

and introduce some new features to make mirror management easier. In
the intervening years, I've done the majority of what I'd set out to
do (but didn't rewrite it as the original project scope would've
done). So this is no longer relevant; I'll remove it today.

• Revamping user comments at php.net (Philip Olson): might also be a
  bit thin as written, but it depends on where it goes.

From discussions I've seen over the years on the official GSOC

list, this may be wrapped into the blanket rejection on documentation.

--
</Daniel P. Brown>
Dedicated Servers, Cloud and Cloud Hybrid Solutions, VPS, Hosting
(866-) 725-4321
http://www.parasane.net/