What package to use in footnotes.info ("Input filters")? Affects grouping in Admin panel.

Are there many module using this very exact package name?
If so, then yes: it would make sense to use it, too.
If not, then it's better to leave it in 'others'.

On the other hand, how many contrib input filter modules do the average web site have?
The 'others' group might feel a bit cluttered if we have many modules, but it's even worse to have as many categories as contrib modules (i.e. each module in their own 'group').

I checked. Two filter modules I regularly use, Code Filter module and quote module, are both listed in 'other' (i.e. there is no explicit package definition).

I guess the most logical think to do is to leave the footnotes filter where it currently is. It does not make sense to have a separate category when most users would only have in average 1 or 2 modules within that category.

I let hingo make the final decision. I personally vote 'wont fix' or even better 'by design'.

Without much deliberation I'm all for categorisation and "Input filters" seems to be what footnotes is.

Pancho, can you give us some background info (like a link) to what the available categories are? Mostly to convince beginner that you're idea is good, but I do agree that in order to "formally choose" a category it would be nice if we knew more about the category system and what the available categories are.

(Finally: Beginner's comments probably make sense from a usability standpoint, but I think this is the wrong context for that discussion. If all other contrib modules are going to be categorised too, there is not particular desire for footnotes to be left alone in 'Other')

hingo, are your subscribed to the dev list?

This issue was discussed a few months back (around D5 release time), and the consensus was that contrib modules shouldn't be on their own within a category.
Categories were meant for large sets of modules that work together, like the dozens of CCK modules, project*, ecommerce, etc, which are large modules coming with a sizeable set of 'contrib' modules often used together.

Now, if all the input filter modules decided to use the same category, that would be one thing... but still: how many input filter modules does one need? 1~3 in average, which is a bit on the low end to create a category.

Check the discussion in the dev list archive.

But at the end, I don't need being convinced. It's your module and I am happy if you make the final decision :)

Hi Hingo, hi beginner,

There is in fact no such thing as a standardized list of module categories. All we have is some kind of de-facto standards, which we may support or not.
From my point of view it makes a lot of sense to group modules together, even if the category is used only by two or three modules in a standard install. Site admins using some thirty or more modules (which is not that crazy) are happy about any structure on this cluttered page.

You can see a listing with mostly filters at http://drupal.org/project/Modules/category/63

In my projects I'm regularly using some of:
* Footnotes
* Spamspan (already in group "Input filters")
* Typogrify (already in group "Input filters")
* Filter Default (convinced to use group "Input filters")
* Smart Line Break Converter (issue has been filed)
* Quote (issue has been filed)
* Code filter (issue has been filed)

Another input filter module already using the group "Input filters" is Collapsible Text.

Regards, Pancho

@Beginner: Heh, no unfortunately I'm not able to follow anything development related on drupal.org, that's why I'm totally dependent on you! (And the collaboration is working well, thanks a lot.)

@Pancho: I understand the concept you are proposing and I'm convinced it is a good idea. What I get from this conversation is that

1. Contributed modules are being categorised
2. A category "Input filters" makes sense, there are several (some dozens?) contributed modules that would fit such a category
3. The process of categorisation is un-coordinated (as is typical for an Open Source community)
4. I'm not very well involved in the Drupal community and discussions on the dev list. (I maintain the footnotes module maybe 3-4 times a year. Unix philosophy of doing one simple thing well has been helpful here.) In addition my "trusted lieutenant" if you will wasn't immediately enthusiastic about the proposal.

Conclusion: Since I'm passive in the Drupal community in general, it makes sense to be a "passive follower" here too. I think your idea is good, but I don't want to be among the first ones to jump into such category. When more modules have categorised themselves into "Input filters", I'll join them.

Does this sounds like it makes sense?

@Pancho,

How did your efforts to categorize filter modules succeed? Can you provide updated statistics whether there is consensus in the Drupal community about putting filters in an "Input Filters" package?

I checked out all contributed modules from HEAD. I could only grep 4 modules which would be using "package = Input filters". I conclude that "Other" is still the way to go.