Port Token to Drupal 7

It's kind of premature to discuss this. There's still a chance token will be part of core for Drupal 7. If not, though, it is very easy to "port" token for the most part, so it will be ready the day that Drupal 7 ships.

I agree that is too early to port a module to Drupal 7, as there could be some changes in the Drupal API; in example, it seems that Drupal 7 is going to use a new hook that would allow a module to call variable_get() (or a similar function) without to pass the default value for the Drupal variable.

I'd like to finish up Submitted By too. There are only 6 weeks to code freeze; has anything been decided or even started yet?

The HEAD of token's code in CVS is a 7.x compatible version of the module that is similar to what is proposed in #113614: Add centralized token/placeholder substitution to core for core.

I think the chances of getting token into core are quite good, so you can simply apply the latest patch from #113614: Add centralized token/placeholder substitution to core to your 7.x installation and work from there.

I think there's still a very valid case for having a Token D7 version.
1. There is no UI or token browser for the core tokens. I think token in D7 should provide a token listing that can be re-used by other modules, and a token autocompletion that could be used in textfields and textareas.
2. There are some tokens that were supported by token in D6 but not ported to D7. Tokens like menupath, bookpath, etc. If there are any other missing or important tokens, they should be added in a D7 token port.

We have a release now for Token D7, and issues filed for all the major things we want done. I'm going to mark this as fixed.