Skip to content
This repository has been archived by the owner on Dec 17, 2019. It is now read-only.
This repository has been archived by the owner on Dec 17, 2019. It is now read-only.

Consider breaking up django-badger into simpler apps #156

Open
lmorchard opened this issue Mar 5, 2013 · 0 comments
Open

Consider breaking up django-badger into simpler apps #156

lmorchard opened this issue Mar 5, 2013 · 0 comments
Labels

Comments

@lmorchard
Copy link
Contributor

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
  • OBI JSON representations of badges & awards
  • 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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant