Drupal Association members fund grants that make connections all over the world.
Drupal core is not maintainable anymore. Too much cruft. Too many half-baked features that no one actually maintains. This causes the following issues:
- Some core features compete directly with better solutions in contrib, so people don't use them or they do and their expectations aren't met.
- Having a large number of features in core means that any refactoring often has to touch a lot of code (including ones trying to decouple things).
- Several core contributors are getting burned out fixing things that 1. they don't use themselves 2. They don't believe many other people use either), especially in the context of what is currently a very, very high bug fixing workload.
- Define heuristics/criteria for deciding which features actually belong in core, this is happening in the issue.
- Start applying those heuristics to specific features in core to see how they apply - this is being done in separate issues and in 'lists' posted to this issue. Please do that only in the context of developing the heuristics, kill vs. keep is not that helpful.
- Find maintainers for features in core that are unmaintained or poorly unmaintained, but which meet the criteria for "things that belong in core". Make sure there's a plan somewhere to fix bugs in those features or bring them up to date. Set deadlines for some of this and actively look for people.
Drupal core is not maintainable anymore. Too much cruft. Too many half-baked features that no one actually maintains.
here's only one way to get it back under control: Rip out everything that does not have to be in core.
Attached patch removes the most obvious cruft, to be maintained in contrib by folks who care, and can be pulled back into a Drupal product:
However, several core component maintainers already mentioned that the following other components are equally not maintained in core, and thus should also be moved into contrib:
Removal of these is not included in the patch yet.
A separate discussion is going to be required regarding Node, Comment, and Taxonomy.
Update: while issues are not a democracy, someone is trying to maintain a tally of opinions expressed in this issue at https://docs.google.com/spreadsheet/ccc?key=0AjtNrWLTvACJdEJicFIwVXVoT1F... which give a summary of the actual consensus on what should or shouldn't be removed.