Every XO in the world shows up on mesh view / need a jabber server for each school

[kimquirk]

Build 513/514

When you connect to the internet through an Access point or through school server mesh, you will see every XO that is currently connected in the world since there is only one Jabber service.

We need to figure out how to provide a jabber server for each school and make sure that the XO knows its local school jabber address.

[kimquirk]

Changing ownership to Scott and milestone to Trial-2

[wenmi01]

Replying to kimquirk:

Build 513/514 When you connect to the internet through an Access point or through school server mesh, you will see every XO that is currently connected in the world since there is only one Jabber service. We need to figure out how to provide a jabber server for each school and make sure that the XO knows its local school jabber address.

---

I think it is good to see everyone in the world, but there must be a way to separate the view to a certain network. It is good for collaborating with other developers for testing.

[jg]

c_scott reports the jabber server is working on the school server.

Sugar/the presence server should start trying to use the local school server jabber server.

2214 should be reassigned, as well -- the jabber server is set up, but sugar is not using it needs a sugar hacker (or a collabora person) to tell why

[morgs]

The jabber server is hardcoded to olpc.collabora.co.uk in the presence-service code. We need a way to preconfigure the XOs in some way with a server name before we can change the hardcoding.

[smcv]

As discussed last Wednesday, we need some sort of commissioning process (activation?) to hand us a server name somehow. It could be as simple as writing the server name into "/security/xmpp-server", but we need to be fed that information from some external source. Once the people responsible for activation have a version that places the server name in a known location, they should let us know what that location is and we can start using it in PS.

[dcbw]

Here's the plan, just need somebody to implement. The machines will ship with _no_ jabber server by default. We need to make sure Sugar + PS don't blow up when they don't get a jabber server. The registration bits will write the correct jabber server to ~/.sugar/default/config. Next time sugar + PS start, they will continue as they do right now. So we just need to ensure that thinks don't puke when there is a blank "Server" field in the config

[morgs]

telepathy-gabble does raise an exception if it tries to connect with a blank server field. I don't think that causes any side effects though as it can't run in that condition anyway.

[dcbw]

Fixes push to PS and sugar.

[jg]

Are they in 541? Or next build?

[morgs]

This went into 542. As a side effect, build 542 does not connect to the olpc.collabora.co.uk server - server must be set manually in .sugar/default/config

[jg]

This should be set by the registration script (registering a machine with a school server), now in the build as well.

That needs to be documented.

Once there is a wiki page, *and* I have it in the release notes, we can close this.