A little while ago, I merged django-badger-multiplayer into django-badger, because there were some weird hacks needed to keep the two apart. Now, django-badger combines a lot of things in one big app:
basic views & models for badges & awards
views to allow users to manage & award their own badges
deferred awards with claim codes and email addresses (ie. invitations)
claim code label printing
progress tracking models
nomination models & view
Maybe django-badger should be stripped back down to the bare basics, and I should find a way to split most of the above off into "addon" apps without nasty hacks.
Some of these features might more properly belong elevated into badges.mozilla.org and not a reusable Django app at all. (eg. like claim code label printing) Or, maybe even something like claim codes could be spun off into its own not-badge-specific Django app.
A little while ago, I merged django-badger-multiplayer into django-badger, because there were some weird hacks needed to keep the two apart. Now, django-badger combines a lot of things in one big app:
Maybe django-badger should be stripped back down to the bare basics, and I should find a way to split most of the above off into "addon" apps without nasty hacks.
Some of these features might more properly belong elevated into badges.mozilla.org and not a reusable Django app at all. (eg. like claim code label printing) Or, maybe even something like claim codes could be spun off into its own not-badge-specific Django app.