benselme/flask-makotemplates — pull request #3 by AnIrishDuck (2012-07-10 19:50:25+00:00)
Title: Rename; Make extension compliant with guidelines for new Flask extensions.

Flask has a detailed list of [requirements for templates](http://flask.pocoo.org/docs/extensiondev/#approved-extensions). These changesets fix the extension so that it's compliant with numbers 0-10 on that page. Additionally, the module has been moved and renamed to conform with the current recommend [naming practice for modules](http://flask.pocoo.org/docs/extensiondev/#extension-import-transition).

Aside from these changes, I've renamed the module from flask-makotemplates to flask-mako. "flask-mako" is shorter and still conveys the intended purpose of the extension. It's also consistent with current approved extensions. Finally, we can combine the flask and mako logos directly to have a [new spiffy logo](https://github.com/AnIrishDuck/flask-mako/raw/c30e66cf2dd0a15bbbccebb088932c21dec1378b/docs/_static/flask-mako.png) that visually combines both project's logos. I have added you as an owner of the [flask-mako PyPI listing](http://pypi.python.org/pypi?:action=display&name=Flask-Mako) so that you can upload future changes to PyPI under that name.

Naturally, the extension name change will require some repository shuffling to work. What I'd recommend you do is:
* Fork benselme/flask-makotemplates to benselme/flask-mako
* Add a notice to benselme/flask-makotemplates indicating that it is an older development version of the current extension repository (like I did in [my old extension repository](https://github.com/AnIrishDuck/flask-mako-legacy)).
* Update your [pull request to flask](https://github.com/mitsuhiko/flask/pull/543) to point to your new "benselme/flask-mako" repository.

I see this as the best course of action because your old extension will retain its google ranking, new users will be directly pointed to the best repository, and we could then work from a common code base.