User talk:Sj/Archive2007: Difference between revisions

From OLPC
Jump to navigation Jump to search
Line 18: Line 18:
== A question ==
== A question ==
Is there a preliminary list of [[new features]] I can review somewhere? From my point of view, getting a better idea of the [[Journal]], and more generally: how content will be deployed. For example can our software tie into the depolyment mechanism. So content that has been downloaded and is displayed in our software can reference other content that the student hasn't downloaded yet. --Scott C.
Is there a preliminary list of [[new features]] I can review somewhere? From my point of view, getting a better idea of the [[Journal]], and more generally: how content will be deployed. For example can our software tie into the depolyment mechanism. So content that has been downloaded and is displayed in our software can reference other content that the student hasn't downloaded yet. --Scott C.
: How would you want to reference software on the network that hasn't yet been downloaded? There will be visibility of content on the mesh and server, at least via an index with basic metadata about the files. [[User:Sj|Sj]] [[User talk:Sj|<font color="fc9"><small>talk</small></font>]] 19:48, 10 December 2006 (EST)
:


== Notes ==
== Notes ==

Revision as of 00:48, 11 December 2006

You may talk to me here, but check my status to see whether I'm around. See my userpage for other ways to contact me if you need something in a hurry (email is best for anything not urgent). Sj

Hey

Hey- Thanks for your help, it's refreshing to have some collaboration.

I'd like to talk to you more about the include tags you mentioned before. Those could prove to be quite useful.

Also, I like what you've done with the sidebar. Portions of it may or may not be temporary depending on how we decide to set up the front page. Walter and I had discussed setting it up like the main page of fr.wikipedia.org. I really like the organization going on there. Everything is right at your fingertips, and it's still very navigable. I had a different approach than what they had though (I think)- My idea is to modularize the page into elements (or blocks, or cells, or whatever you want to call them). Say we categorize the entire wiki into a dozen super categories. Each category would have it's own template (or page, or whatever). That way the main page can be just an index of what blocks are included instead of a bunch of ugly html. Am I discovering something that's already in use? Is this a good/bad/superlative idea? Let me know what you think. Thanks! --Aburton 18:39, 26 June 2006 (EDT)

OLPCities

I received your comments. Thanks. OLPCities is an open project. Everybody (some anonimous...) can help, create content etc. etc. We hope that, in the future, we can use the MIT(?) OLPC server (I believe that there are one available) to upload all the material. Our server can be not good enought if we have a big trafic (we are optimist...). --Americo , 19 September 2006

refactoring love

content page ideas on my user page. Phoebe 01:22, 12 October 2006 (EDT)

A question

Is there a preliminary list of new features I can review somewhere? From my point of view, getting a better idea of the Journal, and more generally: how content will be deployed. For example can our software tie into the depolyment mechanism. So content that has been downloaded and is displayed in our software can reference other content that the student hasn't downloaded yet. --Scott C.

How would you want to reference software on the network that hasn't yet been downloaded? There will be visibility of content on the mesh and server, at least via an index with basic metadata about the files. Sj talk 19:48, 10 December 2006 (EST)

Notes

Local copies of text with push updates, changes when others change. Personal wikis with small groups/clusters. Synch of pages across wikis. Diffs pushed to email servers, pulled down to rev control.

Songbird, etc for exposing, sharing music. Post-v6 IP sharing. Version and data problems... doing away with net file systems.