Community map/email lists

[tekelsey at gmail.com]

(sj as per request am sending to library list, though it seems like it would make sense to have a list for infrastructure/documentation. I understand about having a lot of lists, but on the flip side, less consolidation will make it harder for people to find archived info - and it would not seem to lead to a relative increase in emails. At one point I suggested to kim that I could draft a suggested community taxonomy, and she seemed to think it helpful. This could be used to presuppose email lists, and the etiquette for launch could be to send a "meta" email announcement to all lists when a new list is there.

Then if you like I could make an email alias that would be subscribed to all lists, so that staff could send a broadcast if needed.)

--------

Anne,

I don't know if it exists, prolly needs a tree structure nav, wondering if you would feel ok about adding a small section on Documentation page of "Documentation requests and ideas" and then a bullet on an org chart / community map. If it doesn't exist it should, at least as a framework, so people can at least learn about the staff, inasmuch as appropriate and not covered on laptop.org, and vise versa, so staff could see various projects, contacts and so on.

For example, even if they are used simply to feed people to the wiki, communities and small groups will form in big spaces spontaneously, such as Yahoo, Myspace, facebook, and google groups. They've already started forming, and it will probably be helpful to staff to have an easy way of seeing what's up if they need to.

what triggered this is the email below. It was interesting to learn about this person.

It may also be helpful for us to note and eventually try to find someone to help make a wiki welcome kit, like even down to the kid level. That's the whole point of this thing, so there should also be a wiki for kids, or at least a wiki section.

-----Original Message-----

From:  "Danny Clark" <danny at laptop.org>
Subj:  Re: [laptop.org #1581] StopWatch activity
Date:  Wed Nov 14, 2007 5:03 pm
Size:  1K
To:  bens at alum.mit.edu; access at laptop.org
cc:  OLPC Developer's List <devel at lists.laptop.org>

So it doesn't look like there is consensus on this yet - Mako - since
you seem to be following this (and I'm at a conference), could you
ping me when you think consensus has been reached?

Thanks,
-- 
Daniel Clark # Sys Admin, One Laptop per Child
# http://laptop.org  # http://opensysadmin.com
# http://planyp.us/djbclark # http://dclark.us


On Nov 14, 2007 4:35 PM, Benjamin M. Schwartz <bmschwar at fas.harvard.edu> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hal Murray wrote:
> >> Obsessive accuracy.
> > What's your version of "Obsessive"?  Seconds?  Milliseconds?  Microseconds?
> I have no desire to do better than 0.01s.  Human reaction times are an order of
> magnitude slower than that anyway.
> What I meant is, I have done everything I could think of to maximize accuracy,
> and this is obvious in the way the code is structured.  For example, the first
> instruction in each user-interface callback records the event time, before any
> processing is done, to minimize computation delay.
>
> > Are you assuming that the clocks on various XOs are synchronized?  If so, how
> > well?
> No.  Upon joining, a new member asks everyone else what time they think it is.
> The algorithm assumes that the network delay is the same in each direction.
> Whoever responds first "wins", because this computer experienced the least
> network+scheduling delay, and so the assumption is most likely to be true.
> Experimentally, this works very well with two nodes on a mesh; that's about all
> I can test at the moment.
>
> A more sophisticated synchronization algorithm would be appreciated, but I did
> not know how to make NTP work:
> 1. From python
> 2. As a highly restricted non-root user
> 3. Over Tubes
> 4. In a way that is resilient to the sudden disappearance of any member of the
> group.
>
> TamTam developers: I would like to know how you do synchronization.  I looked
> through your git repository, but I couldn't find any C source for it.
>

--- message truncated ---