Linux Driver Verification

At the moment the user can write any imaginable sequence of letters, digits and signs in field Tags. Although it is very flexible sooner or later it leads to so great variety of tags that they become almost useless (different tags can mean the same cases as well as the same tags can be used for completely different cases).

Actually the users from a particular group gradually elaborate some common tags and it will be very useful to suggest the user to select one of the common tags prior to create the new one. Using some classification of tags can simplify markup process even more. For instance, the user can select some first-level class (e.g. this false alarm is due to incomplete environment model), then some second-level class (e.g. a timer function isn't called) and so on.

As a workaround I encourage the users to manually select one of existing tags and to create new tags as seldom as possible. For instance, one can use saved form data (to clean up it one can follow steps like these).