I've just seen that patches are supposed to be against the trunk. No problem, I can do that, but I'd love to hear beforehand if the patch stands a chance to be merged at all. Thanks!
--------------------------------------------------------------------------------
I love the feature idea but we will need to have the patch apply to trunk and also to have some tests (especially for ApplicationHelper). Would you mind updating the patch?

Also the screencast was great. It really made it easy to see what functionality was included.
--------------------------------------------------------------------------------
I've applied the patch (with routes adapted) against the mirror on Github and added "Index by category" and "Pages without category" to the featureset. Furthermore, I've written a bunch of tests as well.

http://github.com/svoop/redmine/tree/master

Shall I create a patch against the current master or do a pull request on Github?
--------------------------------------------------------------------------------
Here are the changes against upstream master as of today.
--------------------------------------------------------------------------------
Sven has asked me to take a look at this patch. Assigning to myself as a reminder.
--------------------------------------------------------------------------------
I'm trying to clean up my contributions to a few projects before I loose the overview. This patch is several months now, do you see a chance to apply it any time soon? Or is there anything I can do to make this more likely to happen such as rebasing on Github or creating a new patch against the current trunk?
--------------------------------------------------------------------------------
I've forked anew on Github and added the wiki page categories feature again. (Rebasing caused a funky issue I couldn't resolve.)

Please DON'T use the above patch, it has a bug which is fixed in this new commit on Github:

http://github.com/svoop/redmine/commit/e06a07e0f004e2f826687e1d10611a5162eef4f2
--------------------------------------------------------------------------------
I did a quick review of the patch (included) and the feature looks good. A concern I have is storing the categories as a delimited string on a wiki page. It makes querying for the categories harder (e.g. SQL LIKE) and requires the code to do a bunch of string processing to split and join them each time they are used. What if we use a full database model to store the Wiki categories and associte them with the wiki pages themselves?
--------------------------------------------------------------------------------
-1.
I find very odd the way to assign a category to a page.
A proper Tag model should be used and extended to tickets, forums...
See #480, #2897
--------------------------------------------------------------------------------
Instead, we'd better review the existing Tagging plugins for Rails app to choose one.
--------------------------------------------------------------------------------
Fair point, Jean-Philippe. I'm used to Mediawiki, so I took the approach from there which may or may not be a fit for Redmine. (However, I would have preferred to get opinions before doing the extra work, after all, it was easy to see from the screencast. Don't particularly like to code into the wastebin.)

Never mind, is there a particular tagging plugin you have in mind?
--------------------------------------------------------------------------------
I've only used tagging once so far (with the acts-as-taggable-on plugin). From a UI point of view, would it be better to edit the tags on the "edit wiki page" view or directly in the sidebar?

By the way, I guess the reason why Mediawiki sets the page category (or tag) in the content itself is to include the page category (or tag) in the history.

--------------------------------------------------------------------------------
I'll do an alternative implementation based on tagging. The tags will be displayed in the show view sidebar and can be edited in the edit view. (A future enhancement could be AJAX editing directly in the sidebar.)

I favour acts_as_taggable_on (as it's the only one I have used so far). Any other suggestions for the tagging plugin?

http://return42.blogspot.com/2009/07/many-ways-to-tag-taggables.html

--------------------------------------------------------------------------------