Hi Martin,<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I agree, and we are saying the same thing.<br><br>1. I do think that an archival system is necessary for a long run. I remember Ivan mentioning that an incremental backup, and auto archiving is on its way, but that might take a while?<br>
<br>2. If ID management and SSO is working, that will be perfect ! The reason i brought up auto log in was because I was hoping to get something running by April. I was thinking maybe use js/php script to store uid/passwd locally and pass it to the server (moodle) to authenticate with its auth db. Is it any good?<br>
<br>3. I will try get ideas for Nepal server from moodles working on K12, :) that is a good ideas. <br><br>4. UI, everything you have said on it is perfect for us.<br><br>best,<br><font color="#888888">Sulochan</font><div>
<div></div><div class="Wj3C7c"><br><br><br><div class="gmail_quote">
On Jan 27, 2008 6:40 AM, Martin Langhoff <<a href="mailto:martin.langhoff@gmail.com" target="_blank">martin.langhoff@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Jan 27, 2008 5:08 AM, sulochan acharya <<a href="mailto:sulochan@gmail.com" target="_blank">sulochan@gmail.com</a>> wrote:<br>> I just want to add to Bryan's email about our plans for the school server in<br>
> Nepal, and how we might wanna manage content so that it is easier for kids<br>
> to use the XO with the server.<br><br>Hi Sulo,<br><br>I think your ideas match the overall plan for things. Some notes below...<br><br><br>> On Moodle:<br>> ><br>> > I am just thinking out loud. These might be really bad ideas.<br>
> ><br>> > 1. Authentication : Can we use a client side script to secure autologin so<br>> that<br>> > kids dont have to remember login info. The login should take kids to<br>> > whatever (predefined) course they are enrolled in. No front page, no<br>
> > selecting etc. This login info should be tied to the XO.? How big a<br>> > concern is security ?<br><br>Yes - Ivan has said that the XO will identify itself to the server via<br>OpenID somehow, which would provide the SSO you want. If OpenID is too<br>
hard, and there's an easier way to do it, I will be happy to use it --<br>but I need to get some more info from Ivan as master of all things<br>Bitfrost (which is the security scheme XOs use).<br><br>> > 2. Really simplify the UI. Use feature like Chat, Workshop, Database<br>
> > and maybe assignments and thats it. More modules, more confusing it<br>> > is.<br><br>Yes! - have you seen my notes on the wiki? In short<br><br> - a theme that follows Sugar's HIGs and look-and-feel where possible<br>
- non-essential modules disabled<br> - replace Moodle's chat with facility to invoke the XOs chat<br><br>> > 3. Create groups and separate them and make other groups invisible,<br>> > and tie each user to whatever group they fall under. Like grade 2 will<br>
> > only view Group 2 and work within it.<br><br>Yes. Here we have an interesting case -- course/group management (who<br>is in which course/group) can be done in Moodle, as there are good UIs<br>and APIs to manage that. So it will be in Moodle, and may be that the<br>
XO "reads" that info too for other purposes.<br><br>> > 4. Question: How do we let students save their documents in the server<br>> > (not as a part of moodle, but something done outside moodle)? Something<br>
> that is tied to the journal would be perfect. Can<br>> > moodle handle something like this? Some sort of archiving that will<br>> > let students easily save and retrieve files? I guess we should be able<br>
> > to write a custom web page to do this and access it from within<br>> > moodle.<br>> Maybe even a Puttyssh or ssh with a GUI ?<br><br>The intention is to have the students always save locally on the XO,<br>
and have a backup script run regularly (rsync over ssh?) to copy the<br>docs to the XS. IIRC there's been some progress on this, if you search<br>server-devel@ archives. I do not think that the students need to be<br>
aware of file storage in the XS (except for uploading a file to moodle<br>or other webapps, for example). The main purpose of the backup is to<br>recover the data in case the XO is broken/stolen. Further down the<br>road we may want to extend it into an archive so that kids can keep<br>
old stuff on the XS, and only current stuff in the XO, but that will<br>need a UI.<br><br>cheers,<br><font color="#888888"><br><br><br>martin<br></font></blockquote></div><br>
</div></div></blockquote></div><br>