Note: Patch Spotlight is deprecated. All initiatives should be catalogued now under sub-pages of http://drupal.org/community-initiatives/drupal-core.
Eliminate required modules
Drupal currently ships with a large number of required modules: modules that must be enabled for a site to operate correctly, and cannot be turned off. What's telling is that many of these modules were not previously required (for example, Node module). These are signs of unnecessary tight coupling. All functionality provided by modules should be optional for Drupal's operation. Functionality that is required should be moved to underlying core APIs and sensible default values, with modules providing optional configuration UI.
Read moreMenu needs to be torn apart
1. Router system with access control.
1. Tabs with access control.
1. Menu links
These three have little to do in common and yet we keep them together. I separated the two access controls because it's not always the same and while most of the time it's a permission for paths, it's almost never a permission for tabs. Tab work is at http://drupal.org/node/484234 .
Menu links should be simply saved from install files and not generated from router.
-----------
"saved from install files" -> how do you imagine that? hook_install()
Read more
Only variables should be passed by reference
As you know if you've fiddled with PHP's error_reporting setting, Drupal 7 is not yet E_STRICT compliant. E_STRICT compliance is a good idea for forward compatibility (PHP 5.3 and 6.0) and also helpful for servers that already log E_STRICT errors.
Read moreDrupal Code +Test Sprint Beginners Guide
Last updated by greggles on Wed, 2010-03-31 16:06
THIS WIKI PAGE IS A WORK IN PROGRESS
In helping with LA Drupal's D7 Code+Test Sprint event, I noticed there's some easy points that help newbies feel progressive. There are many ways to help at a Code+Test sprint, and here are the ways that helped us in Los Angeles.
- Make sure you have a Drupal.org account, with "Contributor links" turned on in your profile. This will expose a sidebar block linking to areas of interest for contributors. For example: "Patches to review (D7)" is what most people click on to find patches needing review.
A critical look at the implementation of Plugin Manager - Underlying issues and possible solutions
I have been harboring some growing concerns about the direction of the plugin manager integration proposals for Drupal core almost since their inception, but have not been able to make an informed opinion on the subject until I had properly reviewed the proposed system on a much deeper scale.
While my impressions of the project and the current implementation are fairly negative, I have aimed to frame my criticisms in a positive constructive manner because I believe that the goals of the project are worthwhile, and that for a large section of users this could be a very flexible and usable solution.
Unfortunately a lot of my concerns have been well founded, and I believe that the implementation of this system needs to be taken in a different direction for it to be able to succeed in its goals, while not negatively affecting projects like Aegir, Open Atrium and many other ‘serious developers’.
Read more
Authenticated User Caching Thoughts From Another CMS
I just wanted to share some technical information about a very different caching scheme, in hopes that someone would be able to make use of the information for Drupal.
Read more
Total Drupal administration revamp
This is actually very very closely related to Redesign /admin as well as Re-work top-level admin categories. I don't want to pollute both issues with the following findings. If you are interested in reworking Drupal's administrative structure and top-level categories, you want to read on.
[01:22] * tha_sun gathered awesome usability insights from a newbie Drupal user after lengthy discussions.
[01:22] * tha_sun will incorporate that knowledge in admin menu 3.x.
[01:24] <dmitrig01> tha_sun: that being?
Which way for comments in Drupal 7?
No one likes to play with comment.module, it's long neglected, manages to just about keep up with its basic tasks OK (making it not so broken as to invite a flood of patches), but singularly fails when you want to do anything clever with it due to fairly fundamental architecutural issues (making it a pain to write patches for). But core standards are improving, and it can only limp along for so long.
Read moreCore 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
Read moreDatabase 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)
Read moreD7 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)
Read moreNext generation Wysiwyg API: Edit like a rock star!
smk-ka and me worked on the next generation of Wysiwyg API today. Stunning results! Which are still compatible with D6 and D5.
Read moreAnnouncing Wysiwyg API - major milestone
I took the time to rewrite the Wysiwyg (Editor) module into a generic API over the weekend. So the primary concerns about TinyMCE-specific code all over the module are eliminated now. Also, you might have noticed, that I have added an example integration for FCKeditor already - which of course is rather a proof of concept than a fully-fledged integration (and it works cleanly 8).
So Wysiwyg has become a real API finally.
Read moreremoving $op from hooks api
Last updated by Anonymous on Sat, 2008-09-27 09:18
motivation comes from lots of places, good discussion on the dev list here.
i've started a patch to remove $op from hook_user (Code Needs Review).
any comments on whether this is likely to make D7?
Read moreQuality Assurance-related core patches
Last updated by birdmanx35 on Wed, 2009-01-28 15:41
(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)
Read moreKiller feature-enablers
Last updated by keith.smith on Fri, 2008-12-26 17:55
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.
Read moreLanguages & translation related
Last updated by Gábor Hojtsy on Wed, 2008-11-26 10:16
¿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
Read moreImproved DX (Developer Experience)
Last updated by amitaibu on Wed, 2009-01-07 14:26
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"
Read morePerformance-related core patches
Last updated by webchick on Sat, 2009-01-31 18:35
(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)
Read more