I went through the blog post and topics in 3.1 RFC forum to compile an updated progress report on 3.1 Ascraeus.
Below, "merged" means the feature is in develop branch and effectively finished. "Patch in progress" means there is a complete or incomplete patch either in the ticket or in the RFC topic. Complete patches are complete according to patch submitters. These patches need to be reviewed, and if no issues are raised can be merged as is. Incomplete patches are those where either the submitter stated that additional work is needed or "complete" patches that were reviewed and comments or objections raised. "RFC only" means either there is no code attached to either the ticket or the RFC topic, or there is code which is potentially relevant but not in a form of patch for the particular RFC; in other words, essentially work on these RFCs has not started.
Merged:
- Coding Guideline Modifications RFC Ticket
- Autoloading & Class Naming Convention RFC Ticket
- Improved Page Titles RFC Ticket
- Request Class RFC Ticket
- Resume support for attachments / HTTP range support RFC Ticket
- Rename MSNM to WLM RFC Ticket
- Normalise internet protocol version 6 addresses RFC Ticket
- Modular Cron RFC Ticket
- HTML5 Doctype RFC Ticket
- Enhanced Team Page RFC Ticket
- Link global announcements to forums RFC Ticket
- Attachments Management RFC Ticket
- Improved template engine RFC Ticket
- Extensions RFC Ticket
- Inclusion of jQuery RFC Ticket
- Optionally use jQuery from Google RFC Ticket
- No db storage of themes and stylesheets RFC Ticket
- Support for X-Accel-Redirect and X-Sendfile headers for attachment downloads Ticket
- Avatar improvements, Gravatar RFC Ticket
Status: v1 rejected - waiting for v2 from ckwalsh with better factoring - SQLite 3.0+ Support RFC Ticket
Status: patch attached to RFC topic, needs to be turned into a proper git branch; some discussion going on in RFC topic pertaining to the patch - Updated BBcode engine RFC Ticket
Status: partial implementation - discussion is in RFC topic - implementation needs to be finished - Switch to PHP timezone handling RFC Ticket
Status: partial patch in RFC topic - needs to be finished - General Hook Architecture RFC Ticket
Status: incomplete patch exists - stalled? - I am working on an alternative implementation - Improve User Pruning feature RFC Ticket
Status: unreviewed patch on github - linked to ticket - Cleaning up the ACP UI RFC Ticket
Status: unmerged patch in tracker - needs to be reviewed and merged - HipHop for PHP compatibility RFC Ticket
Status: patch submitted - some comments in the RFC topic
- Soft Delete RFC Ticket
- Migrations (UMIL) RFC Ticket Data Providers RFC
- Changing IP banning to use "longest prefix matching" RFC Ticket
- Ability to delete auto login keys RFC Ticket
- Authentication Plugin Refactoring, User Integration & OpenID RFC Ticket
- Session Backend Abstraction (memcache support) RFC Ticket
- Search Backend Refactoring RFC Ticket
- Pre-Compile Template Includes RFC
- Overridable imageset and theme paths for CDNs RFC
- Simple message API RFC Ticket
- MOD Installer RFC Ticket
As you can see, there are several features which have been implemented and need to be reviewed. While patch merging is done by phpBB developers anyone can review submitted patches and provide comments. Of course, for RFCs that do not have a complete implementation everyone is welcome to contribute code as well.
