[meta] Create a D7 "version" of Kit

Problem/Motivation

Various changes between Drupal 6 and Drupal 7 render the Drupal 7 version of the Kit Feature Specification out of date.

Proposed resolution

Probably the easiest and most understandable route here would be to follow standard Drupal git practice:

• Branch the current code as 6.x-1.x.
• Empty out the master branch, leaving a README.txt pointer.
• Branch the 6.x-1.x branch to 7.x-1.x.
• Make the minimal changes that are needed for 7.x compliance.

That way, with minimal work, we get quickly a usable 7.x version. Any significant changes can then go into a 2.x branch.

Remaining tasks

Aside from the branching, separate issues will be opened for each larger bit of updating needed.

• #777850: Update standard set of theme regions for D7.
• #1738616: Review and update restricted user permission list for D7.
• #1738624: Review and update restricted variable list for D7.

Original report by Greyside

Time marches on, and so do web-standards and core expectations. Issues like #777850: Update standard set of theme regions for D7 need a new version of the Kit spec. The question becomes how best to do that.

I propose branching the current spec from master as 1.x, and continuing to use master to define a 2.x version of the specification. Doing so will require an intention to never add code to this project, so purpose the naming-scheme should retain Drupal versions... 6.x-1.x