- 🇬🇧United Kingdom 2dareis2do
Looks like statistics module is being removed from 11.x unfortunately.
https://www.drupal.org/project/ideas/issues/3266457 🌱 [Policy] Deprecate Statistics module in D10 and move to contrib in D11 Fixed
- 🇺🇸United States tr Cascadia
Yeah, typical. Drupal core loses a feature because none of the core committers noticed the regression. But then when it is pointed out, there is push back to fixing it. In this case, the fix has been delayed for EIGHTEEN YEARS. Then the submodule gets removed from core, so there's no need to fix it. Thanks for wasting my time. No one remembers any more that we used to have this feature.
When I contributed patches for this issue, they were 100% compliant with the then-current Drupal standards. Those standards keep changing. If the patches had been committed 10 years ago, then this code would have organically evolved along with the rest of Drupal. But these patches keep getting judged by standards that DIDN'T EXIST when they were contributed, and when they are re-rolled they are neglected and rejected again.
If you want to encourage contribution to core, you're doing exactly the OPPOSITE of what you should.
I'm out. Clearly my contributions to this issue are not valued. A less patient person would have given up 10 years ago.
- 🇬🇧United Kingdom 2dareis2do
@tr I believe the statistics removal has been pushed back because it does not meet the criteria of being installed on less than 5% of sites.
To be fair there are a lot of issues that have built up over the years. I have some sympathy, largely due to the limited resources that seem to make up the 'core' drupal team, which if I understand correctly stands at around 20 people. This is only really possible due in part to the enormous good will of these people who give up their own time to try and move Drupal forward.
Why the core team is limited to just 20 people is beyond me?
That said, it is sad when the core team seem to neglect issues like this. Trying to get this and other features to work as they should take far too long and put developers off using Drupal.
Most businesses cannot function on the premise that an issue might be fixed in 18 years time. Usually they want things yesterday. This goes along way to explaining why many companies are turning their backs on Drupal when it takes so long to get things done and no amount of marketing spend will convince people otherwise.
This regression probably should have been resolved one way or another 18 years ago. IMO this and other issues in a similar state should be prioritised over and above new features such as project browser on that basis.
Thats said webform already has a project browser of sorts. I would like to seem them bring webform into core before building project browser.