-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Home
This is an ad-hoc list of ideas, todos, etc. It's used by the core Mezzanine team to collaborate. It should not be taken as a roadmap. Things on here may be terrible ideas that are thrown out.
The current changelog is automatically generated from commit messages. It's terrible. Many commit messages are poorly written (I think requiring perfect commit messages would be too much of a hindrance for contributions), and don't reflect the correct granularity of changes, as one change may be represented by many commits (again, I think asking contributors to correct this is too high a bar). Moving forward is easy. We just create a changelog file and update it as we go, categorising each line as a feature, fix, or removal (are there other types?). The hard part is going back through 5 years worth of commits and writing a manual changelog for what's already been done. This doesn't have to be perfect, but I think it would need to happen.
This would be an enormous win for the flexibility of Mezzanine. The basic idea is that any model (particularly Page, BlogPost, Cartridge's Product) could be swapped, the same way the User model can be swapped in Django. This would enable the flakey EXTRA_MODEL_FIELDS setting to be removed. See: https://github.com/stephenmcd/mezzanine/issues/1160
WIP underway - https://github.com/stephenmcd/mezzanine/issues/1250
This should also involve reviewing our default settings.py, comparing it to Django's template project's settings.py, and bring them into line as much as possible.
This is a matter of integrating https://github.com/alexhill/TinyMezzCE4 into Mezzanine.