Default tags vocabulary

I also think this should have some default terms, like "Drupal" and perhaps another which could be tagged onto an automatically created first node.

Also, here is the "advanced user" issue: #261882: 'Minimum' install profile. (also subscribe).

-1 on first post. A lot of packages do this and you have to go in and delete the sucker. I personally get annoyed and offended that a package creates published content that I did not approve and without any choice in the matter. It makes me wonder if they had to do that because there's a foreach() bug in the code which manifests itself when there's no content. Don't laugh.

I also take issue with Drupal being in any default vocabulary. Some of us are building sites that aren't about Drupal, hard as it may be to believe.

However one of the first things I've done on several sites was import a list of general conversational tag terms that it took me a long time to compile. Don't even know if the xml taxonomy import/export module is still around these days, but maybe this should be an issue for that module to provide an example file with an editable and generally useful starting vocabulary. It would be very useful indeed having things like autos, music, computers, love, war, weather - and the other top 200 or so conversational topics covered out of the box or with one extra download.

The problem doing it in core is then translations are required and you'll also never get folks to agree on what should be on the list by default.

@macgirvin - Did you write this before reading the Advanced user profile issue? That issue addresses the problem of having to delete these if you are an "advanced user" because you choose an installation path where they don't get created. And let's ignore my comment about using "Drupal" in the vocabulary and focus on whether we should have a term in it by default or not. We can decide on the word later.

Should we have a default taxonomy?
Should we have one or more default terms in that taxonomy?

I agree with Catch and think the answer to both questions is yes and that we should have one or a very few terms in the taxonomy.

Correct - I wrote here before seeing the other topic. That addresses the issue. I'm all in favor of a default taxonomy, and I'd like to see more than one or two terms in it. My default category list is around 150 terms. But I'm also not looking forward to the endless debate about what terms should go in by default and whether it belongs in core at all.

We could spend months on whether or not to include the s-e-x tag. Many will feel it is a mandatory topic of conversation, and an equal number will be opposed to having the word appear on their website and soiling their pristine reputation.

Seems reasonable. What are you going to call the default tags vocabulary? :p

tags.

Works for me.

I'd support a default tags vocabulary for articles.

Patch applies cleanly. Have not tested functionality.

I think this looks good. Too bad we can't set this up using a clean taxonomy module API ...

Working fine!

I've committed this to CVS HEAD. Let's keep working on the minimum profile as well. Thanks catch.

Sorry. I've been away for a while trying to make a living.

I'm leaving this fixed but putting it in my tracker until I can make a patch to implement:

- // Create a default tags vocabulary for articles.
- $description = st('Tags are used to group your articles into different categories.');
- $help = st('Enter a comma separated list of words.');

+ // Create a default vocabulary named "Tags", applied by default to article content types.
+ $description = st('Tags group articles by category.');
+ $help = st('Enter a comma-separated list of words.');

Can I make the catch's patch slightly wordier? Please?

(This just slightly rewords some descriptions and comments.)

Good one. Rerolled against HEAD, absolutely no changes, no credit please.

Committed to CVS HEAD. Thanks for the quick follow-up.