We have several tags that are variants on and . I don't see these categories being useful, as the questions are already grouped by their subject (the program being customized/modified), while user expertise in customization qua customization doesn't make sense.

At first I considered a rename/merge to until I saw the above issue. If there was demonstrated need, we could have a , but I don't see a pertinent use case for . If you disagree, at the very least we should merge the configure/customise tags into one.

1 Answer 1


configure, customise, and customize will now all merge to

  • Do you think the combined tag will be useful? It currently looks like a hodgepodge of things that more have to do with settings than necessarily configuration files (and are better covered in other tags)
    – wolf
    Commented Oct 2, 2016 at 14:54
  • Configuration in general is messy. I think it's best we don't encourage the use of several different and poorly defined tags though. We should encourage people to tag the application/area they want to configure as well.
    – Lewis Goddard Mod
    Commented Oct 2, 2016 at 14:57
  • All right, but raising the possibility of just deleting it outright
    – wolf
    Commented Oct 2, 2016 at 15:00
  • I'm not sure there is a way for me to quickly delete a tag.
    – Lewis Goddard Mod
    Commented Oct 2, 2016 at 15:33
  • 1
    Probably worth merging configuration with settings too—they overlap in scope (unless you think that requires another discussion)
    – wolf
    Commented Oct 17, 2016 at 21:05

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .