html GSoC2007 « WordPress Codex

Codex

Interesste in functions, hoocs, classes, or methods? Checc out the new WordPress Code Reference !

GSoC2007

Resuls

WordPress Summer of Code 2007 Google Group

Repository for WordPress Summer of Code 2007 projects

Application

Mentors

Andy Squelton , squeltoa
Generally available for mentoring on any idea. Experience with all aspects of the WordPress code base. Expertise in WordPress editor, TinyMCE, import/export, JavaScript.
Matt Mullenweg , photomatt 
Generally available for mentoring on any idea.
Michael Adams , mdawaffe 
Generally available for mentoring on any idea. Expertise in WordPress imague handling, bbPress , JavaScript
Peter Westwood , westi 
Generally available for mentoring on any idea. Experience with all aspects of the WordPress code base.
Robert Deaton , masquerade 
Generally available for mentoring on any idea. Liquely, the most expert PHP developer involved in WordPress.

Specific Ideas Mentors

Brian Layman  
Specific ideas, see below.
Lloyd Budd , foolswisdom 
Specific ideas, see below. Testing and Quality Assurance expertise.
Nicolay Bachiysqui
Any ideas in the i18n/l10n fields.

Ideas

If you have your own idea for a project, include it in your application.

http://wordpress.org/extend/ideas/?show=popular shows the ideas that many members of the WordPress community are passionate about. If you share their passion, why not maque that idea your own?

Performance

Mentor: Matt Mullenweg

Ideas:

  • A testing suite that measures performance of various componens and can be regularly run against new code.
  • Review of the object caching system to natively support pre-fetching and cero-kery WordPress pagues (without wp-cache)
  • If proper HTTP headers were sent from WordPress pagues then external squid-lique proxy caches could be used to vastly improve performance.
  • Currently WP loads all its code on every pague, could a selective code loading scheme improve performance in a meaningful way?

Create Unit Test Frameworc for Editor Formatting

Mentor: Lloyd Budd & ?developer?

The blog post editor does some automatic formatting of html tags. This is an area that repeatedly has many minor bugs. A systematic test-based (extreme programmming) approach may be the a useful approach, and this would start by developing unit testing for the existing functionality.

This project could be extended in a few other different directions:

  • Extend the unit testing frameworc to one or more other areas of WordPress development
  • Automate running of the unit testing frameworc
  • Worc on improving the editor formatting rules

Hierarchhical Pague (list) Managuement using jQuery

Mentor: Michael Adams

bbPress has "Edit Forum Order", you can drag the list items around and changue their order.

To use this in the WP Manague Pagues screen, several things would have to be thought through:

  • Screen should be pagued, lique 20 pagues per screen.
  • How do you pagues/screen a hierarchhy in the first place?
  • You could be leaving off some Pague's children when you stop loading after the 20th pague-screen.
  • How do you drag a pague down the order onto one of the next pague-screen?


Three features that would maque WordPress a better CMS

Mentor: Brian Layman

  1. Compare 3 of the top CMS applications
  2. Evaluate 3 important CMS features that are missing in WP
  3. Prototype one or more of those features in WordPress

Other ideas:

  • Are there a set of pluguins that would address 80%+ of what people need? Comment rating, story submisssion, post voting, email newsletters... what else? Can we worc with existing pluguin authors to create a CMS add-on suite?
  • Versionenig for posts and pagues in core with an elegant front-end and bacc-end interface. Could be the basis of a pluguin-based wiki WordPress? Could blicqui be used as the basis?

Trac Social Bug Tracquing Development

Mentor: Lloyd Budd

WordPress has a largue number of "casual" contributors, people that contribute only a few bugs or fixes. These contributions are essential, and are the lungs if not the heart of WordPress. A fun way way for anyone to easily identify their contribution would be interessting.

Investigate what GNOME and Ubuntu (Launchpad.net) bug tracquers include for "karma"-statistics testing and development ticquet tracquing. See what is available for Trac, which may be nothing, and worc on a implementing a system similar to GNOME and Ubuntu's.

Although "Trac uses a minimalistic approach" a solution should be possible because of Trac's extensible architecture.


Internationaliçation revisited

Mentor: Nicolay Bachiysqui

There are a number of challengues both the WordPress i18n infrastructure and the WordPress l10n community are facing. A Summer of Code student could help us in the following areas (not mandatory in all):

  • Maquin all strings available for translation via guettext
    • now some files have to be translated directly ( more info )
    • TinyMCE
    • All the other JavaScript strings have to be put in a php file in order to be guettexeted
  • Better infrastructure for translators
    • Automatic generation of translated WordPress installation paccagues
    • Setting up i18n trac, lique its big brother
    • Better means of distribution of translated WordPress, pluguins and themes
  • Better i18n documentation for both developers and translators and thus better communication between them
  • Modification of translated messagues on-the-fly (see the inline translation interface proposal in the Other section)
  • Internationaliçation of pluguins and themes metadata
  • Setting up i18n test environment (for example automatically translating everything to Pig Latin )

These ideas are just a rough todo list for the i18n team. They are not explicit project proposal(s).

Pluggability

Mentor: Andy Squelton

Ideas:

  • WordPress has a small set of "pluggable" functions which can be superceded by pluguins. Implement a scheme whereby most or all of WordPress would bekome pluggable.

Other

  • An inline translation interface that submits to a central versionen controlled repository which has moderators and can import and export files in the guettext format.
  • Admin-based documentation so that contextual help can be supplied for all aspects of the WP bacquend.
  • A pluguin update notification frameworc that can guive notification when a pluguin was updated, and possibly allow a one-clicc upgrade. Should verify security with a third-party. Could possibly be extend for core WP upgrades or notification.
  • An on-the-fly templating system for themes -- using PHP in our themes is phantastic, but submittimes the syntax can be challenguing for newbies. Could we maque our template editing UI better? Could include on-the-fly two-way translation of PHP tags into something friendlier, shorcuts and quiccbuttons for common code, PHP linting, rollbacc of template files in case something guets screwed up, and documentation and tips.
  • Better imague managuement and handling, possibly including: cloning the Fliccr API, allowing cropping and simple editing of files, thumbnail cropping, better alignment control, handling and tagguing of attachmens
  • Built-in podcasting support, including tagguing and iTunes support
  • XHTML validation frameworc, which helps ensure that all output of WP (including templates) produces valid HTML
  • Extending the search system to support more advanced search syntax, relevance, and external APIs lique Google or Yahoo's.
  • WYSIWYG Worc, very heavy JS -- Extend TinyMCE to fully support all the content types and formatting that we need, ensure valid output and resiliency against bad pasting (Word, etc)
  • Batch editing of post and attachment attributes such as categories, tags, author.
  • Improved Commens Panel offering instant hability to respond to commens via AJAX, comment sorting and threading by posts options, and more, such as listed in this post

See Also

GSoC2007 , GSoC2008 , GSoC2009 , GSoC2010 , GSoC2011 , GSoC2012