TurnKey Linux Virtual Appliance Library

TKLPatch for OpenSIS

The OpenSIS community edition patch for TKL's LAMP stack 11.0(RC) Lucid is now attached below. Chelsea School student Jerel Moses really took lead on this one, with strong support from classmates Steven Robinson and Maurice Quarles.

Credentials:

User Root: Set on install

MySQL Root: Set on install

This one we chose not to bring to a fully configured state. This is in part because the installation process (on first access to http://$ipaddr/opensis) is very straightforward; but also, significantly, the same installation process asks for the school name and the start and stop dates of the academic year. If this isn't strong enough justification, we'll see about a new patch that will bring the appliance to a fully configured state and layout directions for the admin to change the school name and set the academic year calendar.

We really look forward to your feedback. We don't how this will go over since it's not in the repos, but in the interest of providing access to software that might be otherwise inaccessible to those who need it most, we've decided to post anyway (still with the hopes Alon and Liraz will choose to adopt - goes without saying).

Virtual appliances and an ISO will be available from http://9while9.com in the meantime.

Older: With the help of three Chelsea School students, a TKLPatch to turn LAMP Lucid 11.0(RC) into functional OpenSIS (community edition) appliance should be available this week. This is part of an endeavor to do all we can in the interest of a Ubuntu "School in a Box" server (click here for that thread).

The "community edition" of OpenSIS, at the very least is licensed as GPL v2.

OpenSIS identifies itself as a "student information system", but I've had a pretty thorough look at it, and based on my survey it appears to be a fairly comprehensive school management system. It's got almost everything; the only component I see missing is budget management. But that's not a common tool in school management systems, in my experience. It looks best suited for students who switch teachers through out the day - schools with periods or hours.

Jedmeister put together a nicely compehensive response to my initial inquiries about the viability of an OpenSIS patch; see his post here: http://www.turnkeylinux.org/forum/general/20101201/school-box-endeavors#comment-6053. He provides links to the resources he's reviewed. I can only add that #opensis on freenode does not seem to be a source of support. On my frequent visits I was consistently the only one in the room.

The home for OpenSIS is here: http://opensis.com/

Wikipedia has brief entry for it that describes its mission and competitors: http://en.wikipedia.org/wiki/OpenSIS

I drafted a working patch for it; I'm holding off until I squeeze all the pedagogy I can out of it. I'd like the submitted patch to be by the students rather than me.

Attached: 

Post to OpenSIS

This link is to a post a made to the OpenSIS forums seeking a collaborator to work with us to script an OpenSIS/Moodle integrated solution: http://os4ed.com/forum/viewtopic.php?f=3&t=679&p=1351#p1351


Liraz Siri's picture

Added to the build queue

From your description it sounds like OpenSIS would make a useful addition to the TurnKey library even as a standalone appliance without the Moodle integration discussed elsewhere. I've added it to the build queue and hope we'll manage to squeeze this into part 2 of the upcoming release. So much to do... :)
Liraz Siri's picture

Installing upstream software to user maintained paths

The patch seems to install OpenSIS to /usr/share, a filesystem location that is supposed to be maintained by the package management system. When you're installing software from an upstream zip or tarball archive, it's better to follow the Debian FHS and install the application to a user maintained directory such as /var/www or somewhere under /usr/local.

Liraz Siri's picture

Install web applications to the web root

For convenience, it's best to install the web application to the web root rather than a subpath (E.g., /opensis). That way even if you don't know about the path, you can just point your web browser to the IP address of the appliance and it will work.

Very Helpful Liraz

As I've commited to a mentorship in packaging and am preparing to start the research, small suggestions helpful tips like these are actually a significant help - beyond best practice for patches. I really appreciate the feedback.

With your suggestions in mind, should I go ahead and have the patch revised?

Rik


Post new comment

The content of this field is kept private and will not be shown publicly. If you have a Gravatar account, used to display your avatar.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <p> <span> <div> <h1> <h2> <h3> <h4> <h5> <h6> <img> <map> <area> <hr> <br> <br /> <ul> <ol> <li> <dl> <dt> <dd> <table> <tr> <td> <em> <b> <u> <i> <strong> <font> <del> <ins> <sub> <sup> <quote> <blockquote> <pre> <address> <code> <cite> <strike> <caption>

More information about formatting options

Leave this field empty. It's part of a security mechanism.
(Dear spammers: moderators are notified of all new posts. Spam is deleted immediately)