Hi Edward,
I have not included the case of multiple schools interacting together.
This is focused on the first step which covers scale, network config and
basic collaboration within a single school.
I created a new page called collaboration requirements phase 2 linked
from 9.1.0 page:
http
Hi Martin,
OK, I can use RFC style language instead of my must and should
definitions if that helps us communicate better. I'm not up to full RFC
format but I can try to get as close as needed.
I don't see must/should/nice to have defined in this link:
ftp://ftp.isi.edu/in-notes/rfc2223.txt
On Mon, Aug 4, 2008 at 15:43, Greg Smith [EMAIL PROTECTED] wrote:
Hi Martin,
OK, I can use RFC style language instead of my must and should
definitions if that helps us communicate better. I'm not up to full RFC
format but I can try to get as close as needed.
I don't see must/should/nice to
On Tue, Aug 5, 2008 at 1:35 AM, Greg Smith [EMAIL PROTECTED] wrote:
I have not included the case of multiple schools interacting together.
This is focused on the first step which covers scale, network config and
basic collaboration within a single school.
To expand on this -- I had not seen
n Fri, Aug 1, 2008 at 2:16 AM, Greg Smith [EMAIL PROTECTED] wrote:
First Michael:
This feels very similar to an RFC.
GS - Its not meant to be an RFC
I think Michael was just suggesting a time-saving device: you defined
should, must, etc, and there's a common standard for that kind of
On Wed, Jul 30, 2008 at 2:21 PM, Greg Smith [EMAIL PROTECTED] wrote:
Hi All,
I wrote up some collaboration requirements to help get us to a
definition of collaboration support that teachers can use in schools.
Thanks. It is not clear to me whether you mean to include the case of
children
On Thu, Jul 31, 2008 at 03:47:19AM +0100, Gary C Martin wrote:
On 31 Jul 2008, at 01:07, Michael Stone wrote:
On Wed, Jul 30, 2008 at 05:21:34PM -0400, Greg Smith wrote:
It was well promoted and teachers on the sur list have
repeatedly asked for a definition of how to use it successfully.
On Wed, Jul 30, 2008 at 10:32:47PM -0400, Polychronis Ypodimatopoulos wrote:
Dear Greg and Michael,
It seems to me that we spend more time discussing things, instead of
implementing them.
...
Even if you pick one randomly you are guaranteed to scale by a whole
order of magnitude better
Hi All,
Thanks a lot for all the comments.
I tie up a single response and I edit the requirement as needed. Let me
know if I don't respond to something you think needs further discussion.
I put the updated version in the wiki 9.1.0 Collaboration requirements
section: http://wiki.laptop.org/go
Hi All,
I wrote up some collaboration requirements to help get us to a
definition of collaboration support that teachers can use in schools.
This is my first somewhat rigorous requirements definition for OLPC so
comments on style as well as substance are welcome.
I will take one round
On Wed, Jul 30, 2008 at 05:21:34PM -0400, Greg Smith wrote:
This is my first somewhat rigorous requirements definition for OLPC so
comments on style as well as substance are welcome.
This feels very similar to an RFC. Take a look at RFC 2223 Instructions
to RFC Authors and think about whether you
Dear Greg and Michael,
It seems to me that we spend more time discussing things, instead of
implementing them. The issue of scalability in large ad-hoc networks has
been around for more than a decade and some pretty descent research
results have been out there for several years now. Even if
On 31 Jul 2008, at 01:07, Michael Stone wrote:
On Wed, Jul 30, 2008 at 05:21:34PM -0400, Greg Smith wrote:
It was well promoted and teachers on the sur list have
repeatedly asked for a definition of how to use it successfully.
Insofar as we make no use of our own collaborative technology as
Dear Pol, Greg and Michael,
There is so much going on here that it's difficult to approach.
I mostly second Michael's comments. Though Greg obviously took a lot
of his time to put these goals together, I think we are missing the
target. It's good to have goals such as 40 XOs being able to chat
14 matches
Mail list logo