Infrastructure for the i18n group

Seems like we have not communicated the infrastructure we use to create and test the actual code changes properly, as we get questions about the process frequently.

• Development Seed sponsors a subversion repository, where some people already have accounts to commit changes. The server is open for anonymous checkouts, so anyone can try out our changes as we go along. The web interface is at http://svn3.cvsdude.com/vvc/devseed/i18n/?root=sandbox There we have a temporary fork of Drupal, which we periodically sync with Drupal 6-dev. We already use some of the fruits of the 6-dev branch, like the url() and l() related changes, and we build on the new menu code. Since what is in the repository is a full Drupal, you can try it out, set up, test and benchmark. Use this subversion root: http://svn3.cvsdude.com/devseed/sandbox/i18n/
• Every commit to this subversion space ends up on the internationalization at devseeddev.com mailing list, which has a public archive and is open for participation. You can subscribe or view the archives on the web interface. This list is intended to be for code level discussions involving the i18n for core project (and is definitely not a support or discussion channel for any existing contrib modules).
• As we go along, we document our changes and the reasons behind them. Expect some documents to come the next days about the development sprint we recently had. Our final goal is to get Drupal 6-dev ready to accommodate i18n related needs, and for this to work, we need to create smaller patches out of the repository we work on now, once some implementation seems to be feasible to get into Drupal core. Until changes get into the official Drupal 6-dev, we are more than open for your suggestions, benchmark showing that there are better ways to do the implementation, etc. (This is also possible after patches get into Drupal 6-dev, but then you need to persuade the core maintainers).