title: How can i force meaningful checkin comments on Team Foundation?
body: <p>I have a team of developers that have a bad habit, they write <em>poor</em> checkin comments, which makes it a nightmare when we have to look at a file's history on team foundation. I have enabled the <strong>Changeset Comments Policy</strong>, so they can even leave a comment on their checkins (otherwise they wouldn't).</p>
  
  <p>We had a few discussions about work quality for the team, and they are fine with things to remind them to follow stabilished rules for the team, such as being forced to comment. The objective here is to make TFS warn them that they have to write something longer than "Fixed an issue" or "Updated", which they are fine to follow if enforced. I am in charge of the frameworks for our application, and i usually write messages to remind them of things, similar to how VS warns them for missing comments or broken code</p>
  
  <p>Now, i want to avoid that they simply comment a single word, or even a dot on their checkins. <strong>I want to force that at least 20 characters are written before they can checkin the changes</strong>. Is this possible? <strong>How can it be done?</strong></p>
  
  <p>We do not work with a build server or work items (we use <em>redmine</em> for tickets).</p>