Improvements to core
Note: Patch Spotlight is deprecated. All initiatives should be catalogued now under sub-pages of http://drupal.org/community-initiatives/drupal-core.
Killer feature-enablers
These patches enable some of our "killer" Drupal 7 features. Great patches for a Drupal hero(ine) out there to review. This section is reserved for patches that enable Dries' Drupal 7 hit list.
- Input format widget (critical UX improvement for input formats)
- Integrate Diff into core
- Add token functionality to core
- Battleplan for node access
See also the dedicated page about status, progress, and summary of Wysiwyg support in Drupal core.
OMG WTF BBQ
This is a list of core issues that are seriously, seriously broken. Looking to become the next Drupal hero(ine)? Help fix these.
See also: All critical bugs
Performance-related core patches
(Note: I have moved the contents of this node to a sub-page of the http://drupal.org/community-initiatives/drupal-core section: http://drupal.org/node/367257 - webchick)
Improved DX (Developer Experience)
These patches clean up really annoying API things or otherwise make Drupal development more of a joy. If you spend lots of time staring at code, check out some of these patches.
- Unify and rewrite module_rebuild_cache() and system_theme_data()
- Standardize static caching
- New variable defaults to improve performance and help developers
- Data API: first steps
- Blocks system refactoring
- API clean-up: Array-itize file_scan_directory()'s parameters
- Fix the pluggable mail system framework
See also: All patches marked "DX"
Quality Assurance-related core patches
(Note: I have moved the contents of this node to a sub-page of the http://drupal.org/community-initiatives/drupal-core section: http://drupal.org/node/365527 - birdmanx35)
Core taxonomy patches
Taxonomy module is undergoing an overhaul at the moment. This is happening in multiple small to medium-sized patches which will be tracked here as far as possible, otherwise check the taxonomy issue queue
D7 file system wish list (moved)
(Note: I have moved the contents of this node to a sub-page of the http://drupal.org/community-initiatives/drupal-core section: http://drupal.org/node/361854 - webchick)
Quick UX review please:
Please review active core usability issues, specifically:
- Filter for permissions page
- Allow more users to see the node admin page
- Make "approval queue" the default page for comment
- Improve usability of "Select all" feature
- Book module workflow improvements
- Breadcrumbs are only taken from one menu
- Move "Read more" link to the end of the nodes teaser
See also: All usability issues in the queue
Theme system improvements
Here are theme system improvements or CSS/XHTML items in the queue that could use the eyes of designer/themer-types.
- Allow customizing themes from the UI
- Add $classes to hook templates
- Refactor page (and node) rendering
- Allow Inline CSS in drupal_add_css
- Allow external CSS in drupal_add_css
- Allof CSS files to be altered (hook_css_alter)
- Add numeric weight to drupal_add_css
See also: All theme-related patches
Documentation-related core patches (moved)
(Note: I have moved the contents of this node to a sub-page of the http://drupal.org/community-initiatives/drupal-core section: http://drupal.org/node/363007 - webchick)
JavaScript improvements (moved)
(Note: I have moved the contents of this node to a sub-page of the http://drupal.org/community-initiatives/drupal-core section: http://drupal.org/node/362430 - webchick)
Languages & translation related
¿Hablas español? Parlez-vous français? You can help with these patches that are translation-related.
- Improve translation string search and editing interface
- locale_inc_callback() is a thing of the past
- Re-split locale module (depends on the locale_inc_callback() patch)
See also: All translation-related issues
Database spotlight (moved)
(Note: I have moved the contents of this node to a sub-page of the http://drupal.org/community-initiatives/drupal-core section: http://drupal.org/node/361858 - webchick)
Aggregator rework
Patch review FAQs
What do I do if I find a bug while testing a patch?
Try to reproduce the bug on a 'clean' copy of Drupal HEAD. For patches without database changes, you can "reverse" apply a patch to remove it:
patch -p0 -R < patchfile.patchFor patches that make changes to the database, you'll need a clean checkout elsewhere to compare against.
Check to see if the bug manifests itself without the patch. And note: don't forget to re-apply afterwards:
patch -p0 < patchfile.patchIf not, it's usually safe to assume it's caused by the current patch. Mark the issue "code needs work" and describe in detail what you experienced and how the developer can re-produce the steps.
If so, then there is a deeper problem with core... see if someone has already reported a bug on it by searching the issue queue. If not, feel free to file a bug.
General patch reviewing tips
Here is a list of general resources for applying and testing patches.
- HOW TO: Set up a test environment to help review patches: First thing's first: get a development environment setup to perform your testing. This requires a CVS checkout (not a CVS account!), a web environment with Apache, MySQL, and PHP, and the 'diff' and 'patch' utilities. More specific information can be found at the following pages:
- HOW TO: Apply Patches: This is where the action starts. For visual learners, there is also Video: Applying Patches to Drupal Core
- Tips for reviewing patches: Some best practice guidelines on what makes up a good patch review.
- HOWTO: Benchmark Drupal code: Some changes are extensive and require performance benchmarking in order to make it into core. Learn more about it here.
- There is also a Reviewers group, a group of folks dedicated to doing patch reviews who would be happy to answer your questions!
