orbit-oss/flask
4
4
Fork 2
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Updated PyCon 2012 Sprint (markdown)

rduplain 2012-03-11 12:50:08 -07:00
parent 46464f98c3
commit b9cdc1e186
1 changed files with 66 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

67
PyCon-2012-Sprint.md

@ -1 +1,66 @@
I'm writing this right now, will be up by lunch Sunday. -Ron
Participating
-------------
My name is Ron, and I'm running the Flask sprint at PyCon 2012.
All experience levels welcome (seriously!). Location TBD. Channel: #pocoo on freenode IRC. http://flask.pocoo.org/community/irc/ -- Committers will be present at the sprint, to integrate anything you can contribute. :-)
Windows
-------
Add IIS deployment documentation. Expand documentation for Windows.
The Quickstart
--------------
Review the current quickstart to evaluate the user experience. Any overhaul, or just some updates? Add a deployment quickstart, to help new users feel as though they accomplished something by deploying an application and not just listening on a local port. Heroku is an option here. All of this *might* mean that we split up the quick start into multiple pages.
Work through Issue Trackers
---------------------------
Look for open issues and comment, close, and fix. Ask questions if anything is unclear, in person at the sprint or directly on the issue.
Go through http://feedback.flask.pocoo.org/unhappy and either create issues (if verified) in the bug tracker or fix the documentation directly. You can get the feedback as JSON if that helps (http://feedback.flask.pocoo.org/faq).
See these issue trackers:
* https://github.com/mitsuhiko/flask/issues
* https://github.com/mitsuhiko/jinja2/issues
* https://github.com/mitsuhiko/werkzeug/issues
Extensions
----------
At it's core, Flask itself isn't changing much. But there are plenty of extensions which could use attention, and other ideas out there to build new extensions. We also need to update the extension registry and approve extensions.
Make sure *all* extensions which you can find are in the registry driving this page: http://flask.pocoo.org/extensions/ -- note that extensions which are alpha are sometimes in the registry, but not listed. I (Ron) will show you how to work with the registry; it's a .py file.
Review these extensions, https://github.com/mitsuhiko/flask/issues?labels=extension+review -- We list extensions with clear APIs and some starter documentation. We approve extensions which meet these requirements: http://flask.pocoo.org/docs/extensiondev/#approved-extensions
Give love to any of the extensions on which I (Ron) am a maintainer:
* Flask-Celery
* Flask-CouchDB
* Flask-Mail
* Flask-SQLAlchemy
* Flask-Script
* Flask-Solr (unreleased)
* Flask-Testing
* Flask-Uploads
* Flask-WTF
Build a Web Application for Continuous Integration / Buildbot
-------------------------------------------------------------
We have a dedicated build server called flaskbot which is configured with buildbot. No one uses it. It has too much data, and we could use Buildbot's JSON APIs to build very useful views of the state of the Flask core and *all* of the Flask extensions.
Ideas
-----
Idea: Build URLs across Flask instances.