Remove inheritance from PolyModel in Answer and Linkable model. Replace PolyModel inheritance with base.ModelWithFieldAttributes.
A little explanation why we are trying to get rid of PolyModel. We decided to use PolyModel in order to get support for model inheritance in App Engine, however as we know this was a hacky workaround which added inheritance_line property to each model. Recent commits which added Linkable model caused our data viewer in admin console to show only one model "Linkable" since all of the classes inherited from it. Basically datastore viewer was useless plus we had a really big mess in datastore since everything was of one kind (Linkable). It's almost like creating one huge table in SQL database. Upcoming commits will eliminate all usage of PolyModel and finally remove PolyModel from our repository. We are still using inheritance however this doesn't modify how models are saved in data store so basically it's like copy and paste of properties from parent models.
Patch by: Pawel Solyga, Sverre Rabbelier
TEMPLATE NAMESPACES
Templates are placed in a "namespace" subdirectory in the templates directory,
since the templates directory will be added to the Django templates search
path. This allows other packages to extend existing templates without "hiding"
the original template. For example, a template in another Melange application
can extend a template in the SoC framework like this:
{% extends 'soc/some_existing_template.html' %}
without "hiding" the some_existing_template.html for other uses, even if the
derived template is also named some_existing_template.html.
So, please do not put any templates in this soc/templates directory, but only
place them in the soc/templates/soc "namespace" subdirectory.
Different Melange applications should also follow this pattern, to promote
sharing of templates between applications as well. For exmample, the GSoC
Melange application should place its templates in gsoc/templates/gsoc.
MODEL/VIEW TEMPLATE NAMING
View templates are usually named some_view.html for a corresponding someView()
function and SomeViewForm form class. Since SomeView is likely to be a common
View name for multiple Models, Model-specific templates should be placed in
soc/<model>/<view> sub-directories.