Metaflask - A repository to organize the Flask ecosystem

by killahpriest • 12 years ago

115 10 12 years ago

This is a very welcome development in the Flask world. It seems that Armin Ronacher (mitsuhiko) found himself in a situation where things outside of open-source projects started demanding more of his time [0] while issues and PRs started accumulating on Flask, Flask-SQLAlchemy etc. You can't really blame him for being overwhelmed by it, and thankfully, in the past day some progress has been made [1] and maintainers are being selected.

[0] http://lucumr.pocoo.org/2013/11/28/emotional-programming/

[1] https://github.com/mitsuhiko/flask-sqlalchemy/issues/197#iss...

pekk• 12 years ago

It's only a polite fiction that things outside of open-source projects overwhelmed him. Your link itself says that he doesn't want to work on his open source Python projects because of Python 3 taking his motivation.

pyre3• 12 years ago

Whether you are accepted as member or not is arbitrary and the decision is made in an even more arbitrary process by the members of Metaflask. Rejections can be challenged by flamewars on the closed issue.

keypusher• 12 years ago

GuitHub repo is an interesting way to structure a government, will be curious to see how this plays out.

pyre3• 12 years ago

Why not? Reminds me a bit of the way that CPAN is setup (author files, filesystem-based layout, etc).

Walkman• 12 years ago

The guy should set up a Github organization and use one repo for every project. Organizations can have members also, and one project is not cluttered with another one's issues.

pyre3• 12 years ago

I'm not sure you understand. This repository is just a directory containing metadata; basically just a listing of Flask extensions, and their stewardship / author information. There is no intention to pull all Flask extensions into a single monolithic repository.

Think of it as CTAN / CPAN / PyPI / etc specifically for Flask extensions, minus the distribution angle.

collyw• 12 years ago

Can I assume they play nicely together if they are listed, or should I stick with Django for that sort of thing?

Metaflask - A repository to organize the Flask ecosystem

Related Stories