The current objects in Pinax aren't set in stone and I'd really like
Pinax-LMS to help drive the next generation of those.
I think the way to do that is to start off with new, concrete models
and only abstract later. In some cases we can reuse apps or at least
code snippets, but I would rather see a clean concrete implementation
of various pieces of an LMS and then use that to drive what goes back
in to Pinax core.
This is actually the approach I've been thinking about for a lot of
domains:
2 or 3 LMS-related project instances --> common Pinax-LMS code -->
core Pinax code
I think the key is to start with a few different small learning-
related projects that we can prototype pretty quickly and then work on
refining and abstracting.
For example, one of my own interests in this is for my flashcard site,
Quisition. It's completely focus on the individual at the moment but
I've had numerous requests from teachers wanting to set up flashcard
packs specifically for their class and manage which users are students
in that class, which flashcards are available to that class and then
see various reports on how students in that class are going with
various flashcards.
It's an extremely simple example and a long way from a full LMS, but
it has some of the key pieces and I would like to have small successes
as we build up to bigger systems.
James