Package update
figaro - May 12, 2008 - 15:33
| Project: | Porter-Stemmer |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Description
Porterstemmer is in package group "Other". Attempting to align this with all other stemmer modules to have their own package called "Stemmer".
| Attachment | Size |
|---|---|
| porterstemmer.info_.patch | 417 bytes |
#1
Overview of proposed changes:
porterstemmer: http://drupal.org/node/257529
dutch stemmer: http://drupal.org/node/181947
german stemmer: http://drupal.org/node/257531
french stemmer is not upgraded to version 5 and has no info file.
#2
Having lots of collapsible fieldsets on the modules page seems like a bad idea to me. My believe is that most sites will only use this module or perhaps this module plus one other language. In that case the "Stemmer" group would be a group with only one or two items in it. That is a design anti-pattern to have groups that contain one or two items. The rule of thumb that I've heard and follow is that groups should be created, ideally, in a manner that contains between 7 and 12 items.
#3
Having its own namesake package is even worse than what you suggest. So that means: package="Other"
#4
Changing status to active.
#5
And back to "won't fix". This discussion is not worth it.
#6
The discussion is not worth it or the change is not worth it?
If you can find show me screenshots and/or a design rule that says we should do this, I'm all for it. But without that, this seems like a step backwards in usability to me and hence I'm against it.
#7
This issue is symptomatic of a larger problem. The inclusion of the package field is not being enforced as far as I am aware, let alone any standardisation, such that typos will lead to a different categorisation in the modules page. You can imagine what that does on a site with over 50 modules. It is a mess! And on a site with over 100 modules you will use Ctrl-F a lot. So keeping this issue on "won't fix" still a good idea, perhaps we should think about how modules will be categorised/packaged. Let's take an example from Case tracker as a start: all contributed modules have package = "Case tracker", which is very convenient.
#8
Yes, I think that makes sense for case tracker since there are several (maybe 5 or 10) modules which would commonly be used together with case tracker.
But for porterstemmer I don't think that's the case. More generally "Search" might be a good choice, but even that would only have 5-10 modules in the group in total and most sites would only have 1 out of those 10 installed.
I agree, the Package solution can also cause problems when used improperly, which I guess is true of a lot of things in Drupal.