I am only working with the schoolbell application, but I would like
to share my point of view on the matter. If possible, keep releasing
a "bare-bones" solution to the public and then publish the patches
made for the different schools, with reasonable documentation of what
has been done.
This way early adopters are given the choice of:
a) using the bare-bones system as is
b) implement the patches to get an existing, school specific, solution
c) follow the instrucions in order to create a new school specific
implementation
Where option c) might gereate new school specific solutions available
for users to use.
The biggest hurdle in software development is understanding all the
quirks of the system. Starting with a bare bones solution and then
exploring patches/custom add-ons is a lot more appealing than having
to dive in to "the complete package, bugs and all...". I've seen this
from both ends.
Regards Sebastian
_______________________________________________
Schooltool mailing list
[email protected]
http://lists.schooltool.org/mailman/listinfo/schooltool
