For people writing db drivers (like http://drupal.org/project/oracle), I think we should probably create a new project type of 'database driver' so they don't have to get jumbled in with modules or themes. I'm not sure how this will work with the redesign. Thoughts?

Comments

dww’s picture

dww
we/he/they
commented

How DB drivers are we talking about? 1? 3?

Seems a little wonky to have an entirely new project type just for these. What about cache backend implementations? They don't all have to be modules. In theory, just a new copy of cache.inc and a variable in settings.php. In D7, what about new #391340: Job queue API implementations? All you need for that is your own class and a variable. It seems like there are a *lot* of these that could be floating around. Do we want to handle all of these separately, too? I think not.

But, I don't really know what to call these. "Extensions" is too vague. "Handlers" isn't officially adopted as core terminology (yet). Seems like we really need to think bigger about this problem before we add a new project type for this.

See also: #322626: META: Package and version non-modules for download

Niklas Fiekas’s picture

Niklas Fiekas commented

Subscribe.

tvn’s picture

tvn commented
Status: Active » Closed (won't fix)

Closing old issues. Please re-open if needed.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Closed (won't fix) » Active

This is still valid.

mlhess’s picture

mlhess commented
Issue summary: View changes
Status: Active » Closed (won't fix)

I don't think it makes sense to have an entire subproject type (module, theme, distro) for database drivers. Feel free to reopen if you still disagree.