HI all,
Right now we're trying to settle on a new set of development proposals
for POV. One thing I'm contemplating is the future of SchoolBell.
We've rearranged the SchoolTool source tree to be more modular, and
with a few week's work we'll be able to build new SchoolBells from the
current SchoolTool source tree, which means that we won't have to fix
bugs in two places, and it will be fairly easy to keep the two in
sync.
On the other hand, time is short and there are many pressing things to
work on to have SchoolTool ready for testing in the fall, and that's
the top priority. A few weeks spent on SchoolBell is a few weeks not
spent on, say, fixing SchoolTool's access control. In that context,
SchoolBell feels like a ball and chain slowing down the rest of the
project.
I would feel much better about spending time and money on SchoolBell
if someone from the community would volunteer to step up and help
maintain it going forward. This would require some technical (Python)
skills, but not necessarily a lot of programming. More just tracking
SchoolTool development, testing SchoolBell builds from the development
branch, fixing the bugs which will inevitably crop up along the way,
sorting out dependencies, and generally advocating for keeping
SchoolBell working.
No decisions have been made at this point, but I'd like some feedback.
--Tom
_______________________________________________
Schooltool mailing list
[email protected]
http://lists.schooltool.org/mailman/listinfo/schooltool
