Anonymous user
GSoC 2013: Difference between revisions
→Modernize the OpenHatch Django codebase
imported>Paulproteus No edit summary |
imported>Paulproteus |
||
Line 28:
Right now, the OpenHatch codebase can be described as a tangled mess of the best Django practices we could pick up in 2009. Do you want to learn about refactoring by trying it with a real codebase?
We do have high test coverage. That will help you dramatically if you want to take on this task! That is, the test coverage is what will keep you sane.
If you're excited about code quality, over the summer, here is kind of thing we'd
Make a diagram of our circular imports, and then propose a plan to decrease how circular they are. (You can use tools like http://chadaustin.me/2009/05/visualizing-python-import-dependencies/ to visualize the import dependencies.) Then, in small patches, move (or remove) code to simplify the import chain.
In the second half of the summer, we recommend reading through the custom code we have, and consider if a Django reusable app can replace it. I expect that in a large number of the cases, you can find external code to replace most of the OpenHatch app. (-:
Additionally, if you are excited about Django's new class-based views, you could consider porting the OpenHatch views to be class-based.
| |||