Re: [Telepathy] ip4-address and ip6-address fields in telepathy-salut/telepathy-gabble

2013-03-28 Thread Guillaume Desmottes
Le jeudi 21 mars 2013 à 14:26 +0530, Ajay Garg a écrit :
 Hi all.
 
 I downloaded source-rpms for telepathy-salut-0.8.0, and
 telepathy-gabble-0.16.5, and after a quick grepping, realised that
 ip4-address/ip6-address fields is passed on as one of the
 buddy-properties in telepathy-salut, but the same does not happen in
 telepathy-gabble.
 
 
 Has there been any particular  reason for this? Or is it just that the
 need was never felt till date :P
 

I don't remember why we added these fields for OLPC. Is it still used by
Sugar these days? If it's not I'd be in favor of just removing them.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Server-devel] Gadget on XS

2009-04-13 Thread Guillaume Desmottes
Le vendredi 03 avril 2009 à 10:40 -0400, Dave Bauer a écrit :

 
 AHA! gadget.config.
 
 Can we add the startup and gadget.config to the README? 

I didn't realise this file was not documented, sorry for that.

I wrote some words about it in this patch:

http://git.collabora.co.uk/?p=user/cassidy/gadget;a=commitdiff;h=711fddfc4bdfad75582af776baa3beb532dea083

Could you review it please? Then I'll merge it to master.


thanks,


G.

___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] Gadget on XS

2009-04-01 Thread Guillaume Desmottes
Le mardi 31 mars 2009 à 13:45 -0400, Dave Bauer a écrit :
 Hi,
 
 I am trying to get gadget working on my XS at
 schoolserver.solutiongrove.com
 
 First I downloaded the source and built it, but I could not find any
 indication that gadget was installed. How can I tell if it is working?
 
 Next I tried the gadget package
 http://koji.fedoraproject.org/koji/taskinfo?taskID=1261886 RPM but it
 required ejabberd package. RPM says this is not installed. (I did
 install python-twisted which was another requirement of the RPM).
 
 Does anyoe have any advice on getting gadget working?

Basically you have to install the gadget service, launch it (it's a
separated process), modify your ejabberd.cfg as explained in the Gadget
README and then restart your ejabberd.

You can see if Gadget is working by looking at the XMPP traffic
exchanged between clients and the server.


G.

___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] Gadget on XS

2009-04-01 Thread Guillaume Desmottes
Le mercredi 01 avril 2009 à 12:45 +0200, Martin Langhoff a écrit :
 On Wed, Apr 1, 2009 at 12:36 PM, Guillaume Desmottes
  Basically you have to install the gadget service, launch it (it's a
  separated process), modify your ejabberd.cfg as explained in the Gadget
  README and then restart your ejabberd.
 
 I suspect he's done that already...
 
  You can see if Gadget is working by looking at the XMPP traffic
  exchanged between clients and the server.
 
 And as an end-user, what things work better / differently?

If you're using a recent Sugar it should request a view containing
random activities and buddies. So you should see people/activities in
your roster even if the shared roster is not configured.

 As an
 end-user-administrator, does it expose any info, stats, knobs, etc?

You can redirect Gadget log to a file. The Debian package write logs
to /var/log/gadget.log iirc; don't know for the RPM.


G.

___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] Gadget on XS

2009-04-01 Thread Guillaume Desmottes
Le mercredi 01 avril 2009 à 12:53 +0200, Martin Langhoff a écrit :
 On Wed, Apr 1, 2009 at 12:50 PM, Guillaume Desmottes
 guillaume.desmot...@collabora.co.uk wrote:
  If you're using a recent Sugar it should request a view containing
  random activities and buddies. So you should see people/activities in
  your roster even if the shared roster is not configured.
 
 Cool! And does it evolve (learn?) from random to people you've
 interacted with or something similar?

No, atm it's pure random. Gadget also supports contact and activity
search but Sugar doesn't have UI for it currently.

If user want to be able to always see a buddy, the right way is to add
him as a friend.


G.

___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] [Sugar-devel] Gadget on XS

2009-04-01 Thread Guillaume Desmottes
Le mercredi 01 avril 2009 à 14:14 +0200, Jonas Smedegaard a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On Wed, Apr 01, 2009 at 11:50:52AM +0100, Guillaume Desmottes wrote:
 Le mercredi 01 avril 2009 à 12:45 +0200, Martin Langhoff a écrit :
  On Wed, Apr 1, 2009 at 12:36 PM, Guillaume Desmottes
   Basically you have to install the gadget service, launch it (it's a 
   separated process), modify your ejabberd.cfg as explained in the 
   Gadget README and then restart your ejabberd.
  
  I suspect he's done that already...
  
   You can see if Gadget is working by looking at the XMPP traffic 
   exchanged between clients and the server.
  
  And as an end-user, what things work better / differently?
 
 If you're using a recent Sugar it should request a view containing 
 random activities and buddies. So you should see people/activities in 
 your roster even if the shared roster is not configured.
 
  As an
  end-user-administrator, does it expose any info, stats, knobs, etc?
 
 You can redirect Gadget log to a file. The Debian package write logs
 to /var/log/gadget.log iirc; don't know for the RPM.
 
 What Debian package? Gadget does not seem to be in Debian Sid. I'd be 
 happy to help maintain it officially for Debian if there is already a 
 Gadget package floating around unofficially.

See http://dev.laptop.org/git/projects/gadget/log/?h=debian


___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] [Sugar-devel] Gadget on XS

2009-04-01 Thread Guillaume Desmottes
Le mercredi 01 avril 2009 à 17:37 +0200, Jonas Smedegaard a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On Wed, Apr 01, 2009 at 10:18:37AM -0500, David Farning wrote:
 On Wed, Apr 1, 2009 at 9:47 AM, Jonas Smedegaard d...@jones.dk wrote:
  On Wed, Apr 01, 2009 at 03:22:12PM +0100, Guillaume Desmottes wrote:
 Le mercredi 01 avril 2009 à 14:14 +0200, Jonas Smedegaard a écrit :
  On Wed, Apr 01, 2009 at 11:50:52AM +0100, Guillaume Desmottes 
  wrote:
  The Debian package write logs to /var/log/gadget.log iirc;
 
  What Debian package? Gadget does not seem to be in Debian Sid. I'd 
  be happy to help maintain it officially for Debian if there is 
  already a Gadget package floating around unofficially.
 
 See http://dev.laptop.org/git/projects/gadget/log/?h=debian
 
  Above URL does not clarify if it is in Debian officially.
 
  If my questions are too silly to respond to with human words (as 
  opposed to just URLs), then I shall not bother you anymore with them.
 
 Please try to stay polite.
 
 Hi Guillaume (and everyone else),

Hi

(CCing Daf who is the author of this Debian package).

 Sorry for being rude.
 
 You mention a Debian package, and I wonder:
 
   1. Is it a Debian package of Gadget, ejabberd or something else?

The link I pasted you is a git branch of Gadget containing a 'debian'
directory used for the packaging.
These files are
http://dev.laptop.org/git/projects/gadget/tree/debian?h=debian


   2. If it is a Gadget package, is it targeted for Debian officially?

It could but has not been proposed to Debian yet.

   3. If yes, are you interested in help maintaining such package?
 
   4. If no, are you interested in helping maintain it officially?

Sure. Any help is welcome.

 Your brief response above seems to indicate that indeed it is a Gadget 
 package.
 
 I am still interested in clarification about questions 2, 3 and 4.
 
 If you answer with a URL, then I would appreciate that you also write 
 some human words too, as I believe (contrary to David, possibly) that it 
 can help avoid misunderstandings.

Sorry, I was quite busy when I replied to your mail.

Hope it's clearer now.


G.


___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] Fwd: [ejabberd] Fix or workaround for EJAB-731 - shared roster fails to show new user accts

2008-12-23 Thread Guillaume Desmottes
Le lundi 22 décembre 2008 à 13:54 -0200, Martin Langhoff a écrit :
 On Mon, Dec 22, 2008 at 9:30 AM, Guillaume Desmottes
 guillaume.desmot...@collabora.co.uk wrote:
   - Do we need this patch to interop with 8.2 correctly? What does it do?
 
  IIRC, this patch introduced new type of shared roster: @online@,
  @recent@ and @nea...@. Vanilla ejabberd only supports @a...@.
 
 Ah, so it's the old patch, reapplied. I'd like to learn more about
 it, are there any notes on how it works...anywhere? Who's the original
 author?

This patch was started by Rob and then finished/polished by P1. The
rational was to create new kind of shared roster groups that would be a
subset of @all@ to, hopefully, improve the scalability issues.


   - Have you tested vanilla ejabberd for the bugs reported in 
  EJAB-730/731?
 
  Yes. That's why I always mention @all@ instead of @online@ in the
  reports, but the problems were the same.
 
 Thanks for confirming...
 
  I think if things are working fine with this patch using the @all@
  shared roster, there is good chance that fixes @online@ as well.
 
 Ok. I'll try with @all@, and then see if I can merge...
 
 
 
 m


___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: Jabber client activity

2008-12-22 Thread Guillaume Desmottes
Le lundi 22 décembre 2008 à 10:52 +0100, Tomeu Vizoso a écrit :
 [adding sugar-devel as this is of interest also outside OLPC]
 
 On Sun, Dec 21, 2008 at 23:49, Mildred Ki'Lya ml.mildred...@gmail.com wrote:
  Hello everyone,
 
  I'm new here, and I came interested in the OLPC project because it's a
  wonderful computer, very well integrated, and I just had one via the
  European G1G1 project. And now, I thought I could contribute :)
 
  I wanted to know if there was any project of creating an activity that
  would be a jabber client. If so, could I help, where is it? And if not,
  perhaps I should start one.
 
 Actually, having Chat working as a regular IM client would be very
 interesting and may not be a very big project. The only missing piece
 is being able to add contacts to your roster other than through the
 mesh view.

Sugar *is* a jabber client, not only Chat but the whole sugar/sucrose.
Chat is used to chat (!) with your contacts, the mesh view is your buddy
list and VideoChat is suppose to be used for... audio/video chat.
The Telepathy framework offers you the possibility to split the
different features of your client (roster, chat, audio chat, logger,
etc) into different applications.

One big missing piece is the ability to add contacts by entering their
jid and UI to accept/decline friend requests. This is
https://dev.laptop.org/ticket/8841

Another one is the ability to run more than one account/connection. Main
problem here is the UI. How should we display that? Tabbed mesh views
maybe?

Once this is done, you'll be able to use your normal IM accounts on
Sugar and be able to chat with them using Chat, send them files using
journal object sharing and call them with VideoChat.

Actually, as Sugar is using Telepathy, it's much more than a Jabber
client. By being a real Telepathy client, it could become a IRC, MSN,
SIP (or whatever protocol) client!
I talked about that during one of my Sugarcamp conf:
http://people.collabora.co.uk/~cassidy/talks/sugar-camp-futur-of-collab.pdf

We'll be happy to help any contributor interested in working on this.
Just come and say hi on #sugar or #telepathy.
But *please*, let's not waste time and resources on implementing a gajim
or pidgin activity. We already have an existing flexible and performant
IM framework; we just need to integrate it properly in Sugar to offer a
rocking user experience.


G.

 I think the idea is to add a palette option somewhere that allows you
 to type or paste a contact ID so it will appear in your friends view.
 Then you would get presence notification, the ability to chat and
 transfer files, and with some extra work, a/v conversations.
 
 If someone would like to jump on this challenge, it's there waiting for you!


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Server-devel] Fwd: [ejabberd] Fix or workaround for EJAB-731 - shared roster fails to show new user accts

2008-12-22 Thread Guillaume Desmottes
Le samedi 20 décembre 2008 à 18:13 -0200, Martin Langhoff a écrit :
 Hi Guillaume,
 
Hi Martin,

 Badlop has posted a new patch that I want to test. It conflicts with a
 patch you've introduced to our build,
 recent_online_and_rearby_groups_updated.diff -- two questions
 
  - Do we need this patch to interop with 8.2 correctly? What does it do?

IIRC, this patch introduced new type of shared roster: @online@,
@recent@ and @nea...@. Vanilla ejabberd only supports @a...@.

  - Have you tested vanilla ejabberd for the bugs reported in EJAB-730/731?

Yes. That's why I always mention @all@ instead of @online@ in the
reports, but the problems were the same.

 In the short term, I'm building an rpm to test here - with lop's
 patch, and without yours. Have made any attempt at a merge - but can
 try if you tell me it's needed. (Not that I know much erlang or
 ejabberd internals, but getting there. Help welcome.)
 

I think if things are working fine with this patch using the @all@
shared roster, there is good chance that fixes @online@ as well.


G.

 cheers,
 
 
 m
 
 -- Forwarded message --
 From: Martin Langhoff martin.langh...@gmail.com
 Date: Sat, Dec 20, 2008 at 6:09 PM
 Subject: Re: [ejabberd] Fix or workaround for EJAB-731 - shared roster
 fails to show new user accts
 To: ejabb...@jabber.ru
 
 
 On Sat, Dec 20, 2008 at 11:20 AM, Martin Langhoff
 martin.langh...@gmail.com wrote:
  - is there an altrnative workaround, something to force ejabberd to
  re-scan its list of users without a restart?
 
  Yes, check
  https://support.process-one.net/browse/EJAB-731
  That new patch for ejabberd 2.0.2 fixes this and other problems
  related to Shared Roster. There is a comment at the bottom of the page
  with explanation of the changes.
 
  If you try the patch, please tell me if all seems to work correctly.
 
  Right - following that discussion, you are saying that the patch that
  fixed EJAB-71 should fix it, correct? But we are seeing the problem on
 
 I misread initially - thinking of the discussion in EJAB-730, that
 points to EJAB-71. I've now seen the new patch and I've built a new
 rpm with it. Will be testing tomorrow or Monday.
 
 cheers,
 
 
 
 m
 --
  martin.langh...@gmail.com
  mar...@laptop.org -- School Server Architect
  - ask interesting questions
  - don't get distracted with shiny stuff  - working code first
  - http://wiki.laptop.org/go/User:Martinlanghoff
 
 
 

___
Server-devel mailing list
server-de...@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: Debugging tips for presence over Telepathy/Gabble?

2008-12-17 Thread Guillaume Desmottes
Le mardi 16 décembre 2008 à 12:19 -0200, Martin Langhoff a écrit :
 Looking for Telepathy/Gabble hints...
 
 With the new ejabberd in 0.5 (2.0.1 + Collabora's patches) people have
 reported very unreliable Network View listings. The problem seems to
 be that everyone disappears after a short while, and if you leave it
 for a few hs, everyone reappears.
 
 The thread starting with this message has quite a bit of good info -
 including the fact that the problem is visible with standard xmpp
 clients too -
 http://lists.laptop.org/pipermail/server-devel/2008-December/002658.html
 
 I am starting to work on reproducing it here, with a small number of
 XOs. Haven't worked on this area before -- so I am looking for good
 hints on this from people who've been doing this lots ;-)

env variables GABBLE_DEBUG=all and LM_DEBUG=net would give you debug
info and XMPP stanzas exchanged.

Few months ago I filled shared roster bug on ejabberd BTS. Maybe you are
hitting one of these issue?
https://support.process-one.net/browse/EJAB-730
https://support.process-one.net/browse/EJAB-731
https://support.process-one.net/browse/EJAB-732


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Server-devel] Debugging tips for presence over Telepathy/Gabble?

2008-12-17 Thread Guillaume Desmottes
Le mardi 16 décembre 2008 à 12:19 -0200, Martin Langhoff a écrit :
 Looking for Telepathy/Gabble hints...
 
 With the new ejabberd in 0.5 (2.0.1 + Collabora's patches) people have
 reported very unreliable Network View listings. The problem seems to
 be that everyone disappears after a short while, and if you leave it
 for a few hs, everyone reappears.
 
 The thread starting with this message has quite a bit of good info -
 including the fact that the problem is visible with standard xmpp
 clients too -
 http://lists.laptop.org/pipermail/server-devel/2008-December/002658.html
 
 I am starting to work on reproducing it here, with a small number of
 XOs. Haven't worked on this area before -- so I am looking for good
 hints on this from people who've been doing this lots ;-)

env variables GABBLE_DEBUG=all and LM_DEBUG=net would give you debug
info and XMPP stanzas exchanged.

Few months ago I filled shared roster bug on ejabberd BTS. Maybe you are
hitting one of these issue?
https://support.process-one.net/browse/EJAB-730
https://support.process-one.net/browse/EJAB-731
https://support.process-one.net/browse/EJAB-732


G.

___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Telepathy] ANNOUNCE: telepathy-gabble 0.7.17

2008-12-15 Thread Guillaume Desmottes
Le lundi 15 décembre 2008 à 11:09 +0100, Peter Robinson a écrit :
  F-10 doesn't have dbus-glib 0.78, only 0.76 so I can't add this to
  joyride yet. Do we want an OLPC-4 branch for dbus-glib to handle this?
 
  I think we can wait that the updated package reach F-10.
 
  Collabora, is this relevant to OLPC? If not, we can hold off on
  packaging this for now, but if we need it we must make the above
  happen...
 
  No, that shouldn't be a problem.
 
 BTW I noticed this changelog entry in the rawhide version of
 telepathy-salut Enable OLPC support code. It is not used unless a
 client explicitely requests them. would this mean that the forks
 aren't required when this gets pushed to the F-10 packages?

Actually Gabble doesn't have a --enable-olpc option (only Salut has
one). I removed it from jhbuild's moduleset.

But I'm afraid we still need the fork for the Rainbow workaround.


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Server-devel] ejabberd tests with old and new TLS code

2008-11-24 Thread Guillaume Desmottes
Le samedi 22 novembre 2008 à 13:17 +1300, Douglas Bagnall a écrit :
 Actually hyperactivity does create fake activities, though I am not
 sure to what extent it really shares them. Hopefully someone from
 Collabora can explain it better (I'm interested too).

Yes, it does. Fake activities are created, joined used and left
randomly.


G.

___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] Mini ejabberd workplan notes...

2008-11-20 Thread Guillaume Desmottes
Le mercredi 19 novembre 2008 à 18:54 +1300, Douglas Bagnall a écrit :
 The other day Martin wrote:
 
   - Trying the SSL patch on the ejabberd version we use. P1 people say
  that the patch is ok to backport so...
... and of course load testing it to witness the magic decrease in
  memory, and how ssl compress is still in use.
 
 Patched version is here:
 http://dev.laptop.org/git?p=users/dbagnall/ejabberd-rpm.git
 
 It's too early to say anything about the memory but I've set it up to
 have a night of horribly difficult tests.
 
 I hope to soon rebase ejabberd off 2.0.2.


Would be good as Gadget requires at least this version to work properly.


G.
 

___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: Anyone set up a client/server application using stream tubes?

2008-10-27 Thread Guillaume Desmottes
Le vendredi 24 octobre 2008 à 14:18 +, Faisal Anwar a écrit :
 Hi All,
 
 I'm trying to document some more stuff related to Stream Tubes for the
 sugar almanac (http://wiki.laptop.org/go/Sugar_Almanac) and wanted to
 set up some examples related to the different types of client/server
 arrangments that can be supported by the sugar.network package.
 However, I've been having some trouble getting a client/server
 application up an running on a stream tube through threading. Has
 anyone else tried this and could you point me to some example code? 
 
 One example of what I would like to be able to do: create a
 continuously running http server on one XO that can send files to
 requests from a client XO. I have created a server that can do this
 once, but when I try to get it to repeatedly listen for client
 requests, I am not able to get things working. 
 
 Any help would be greatly appreciated!


Hi,

AFAIK, Read is currently the only OLPC activity using stream tubes but
the tube code is not OLPC specific at all; it just use the Telepathy
API.
You can find some doc about tubes in the Telepathy specification [1].
The most examplary codes are probably in telepathy-python/examples/.
You'll find some scripts demoing stream and D-Bus tubes.


G.


[1]
http://telepathy.freedesktop.org/spec.html#org.freedesktop.Telepathy.Channel.Type.Tubes


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Server-devel] ejabberd-xs package

2008-10-27 Thread Guillaume Desmottes
Le vendredi 24 octobre 2008 à 10:48 +1300, Douglas Bagnall a écrit :
 I've made an ejabberd-xs package from a slightly modified version of
 Collabora's ejabberd-rpm XS branch.  The git is here
 
 http://dev.laptop.org/git?p=users/dbagnall/ejabberd-rpm.git;a=summary
 
 and the RPM here:
 
 http://xs-dev.laptop.org/xsrepos/testing/olpc/9/i386/ejabberd-xs-2.0.1-11.fc9.olpc.i386.rpm
 
 
 The reasoning behind ejabberd-xs was developed in the thread starting
 here:
 
 http://lists.laptop.org/pipermail/server-devel/2008-October/002303.html
 
 To summarise, unless we do this, new ejabberd packages from Fedora are
 likely to clobber our XS specific changes.  The only significant
 change, apart form the name, is that ejabberd-xs 2.0.1 conflicts with
 any ejabberd, and obsoletes ejabberd versions up to 2.0.2.
 

Btw, it would be good to rebase to 2.0.2 as some point as we'll need
this version for Gadget.

G.



___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] ejabberd shared roster config

2008-10-27 Thread Guillaume Desmottes
Le vendredi 24 octobre 2008 à 16:41 +0200, Morgan Collett a écrit :
 I've been playing around with setting up ejabberd seeing that Debian
 and Intrepid ship with the shared roster patches:
 http://wiki.laptop.org/go/Installing_ejabberd/deb
 
 I managed to hack up the shared roster with a minimum of things that
 could go wrong, by using:
 
 sudo ejabberdctl srg-create Online your.host.name Online Online users Online
 sudo ejabberdctl srg-user-add @online  Online your.host.name
 
 This doesn't work immediately as it creates @online @ nothing
 instead of @online@ - but it does populate @online@ into the web
 interface, so you just need to log in and submit the form with no
 changes under shared roster groups. Then it correctly sets @[EMAIL PROTECTED]
 
 Anyone have a simpler way to do this?

Yes.
As explained on [1], we have a patch allowing to define the roster in
ejabberd's conf file and to create it using a command.
I don't know if this patch is included in the Debian pkg though.


G.

[1] https://dev.laptop.org/ticket/5310#comment:11


___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel


[ANNOUNCE] Gadget 0.0.2 released

2008-10-17 Thread Guillaume Desmottes
The Monster Lake release.

Highlights:

  - Support for constraining activity search results.
  - Various bug fixes.
  - Adds load simulation tools for testing purposes.
  - Support for multi criteria search.


Tarballs: http://dev.laptop.org/pub/gadget/



G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: VideoChat is working now - hooray!

2008-10-13 Thread Guillaume Desmottes
Le dimanche 12 octobre 2008 à 19:11 +1100, Pia Waugh a écrit :
 Hi all,
 
 We now have Videochat v9 which works. This is a great thing that will help
 children connect, and in particular help with remote support for children.
 It could assist with eHealth, remote education, speech therapy and any
 number of useful functions.
 
 Anyway, it also needs more hacking, so anyone interested in helping should
 have a play and get involved. Currently it only does basic video
 conferencing between 2 laptops but the vision (as it states on the webpage)
 is for whiteboard functionality and more.
 
 Anyway, thought there would probably be a few of you for whom this would be
 useful :)
 
 Download and information:
 
   http://wiki.laptop.org/go/Video_Chat


This code as not been merged to VideChat upstream [1]. Please provide a
git repo with your branch so I'll be able to easily review and merge
it. :)


G.

[1] https://dev.laptop.org/git?p=projects/video-chat-activity;a=summary


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Server-devel] ejabberd sysconfig patch

2008-10-13 Thread Guillaume Desmottes
Le lundi 13 octobre 2008 à 13:44 +1300, Douglas Bagnall a écrit :
 This patch to Collabora's OLPC ejabberd-rpm package makes
 /etc/init.d/ejabberd look for (and, if possible, incorporate)
 /etc/sysconfig/ejabberd.  Two options can be set there:
 
  - CONFIG_FILE gives an alternative to /etc/ejabberd/ejabberd.cfg
  - ULIMIT_MAX_FILES sets the number of open files (using ulimit -n).
 
 The latter is useful to anyone running a popular ejabberd server (you
 have to do this, one way or another), while the config redirection
 decouples the OLPC specific configuration from the ejabberd package.
 

Thanks for the patch. I applied it on my XS branch.
Unfortunately, I wasn't able to use git-am, so I re-recorded your patch.
Suggestion welcome :)

$ cat /tmp/ejabberd-sysconfig.patch | git-am 
Patch does not have a valid e-mail address.

 Peter: would you consider taking this upstream?  It would make life
 easier for OLPC (which we need) and no doubt for others too.
 
 Collabora people: I've been using the XS git branch.  If I understand
 correctly, without the specialised ejabberd.cfg, the only patch we
 have over Fedora is recent_online_and_nearby_groups_updated.diff:
 
 http://git.collabora.co.uk/?p=user/cassidy/ejabberd-rpm;a=blob;f=recent_online_and_nearby_groups_updated.diff;h=7138ad4a1a55dace867b76c683163dfc71d9f4d3
 
 and if that gets absorbed or obsoleted, then we could be back on the
 F-9 rpm?

recent_online_and_nearby_groups_updated.diff is the only patch we apply
on upstream code (to support the @online@ shared roster).

You can easily see the modifications I did on the F9 package by browsing
the repo:
http://git.collabora.co.uk/?p=user/cassidy/ejabberd-rpm;a=shortlog;h=refs/heads/XS
and looking at the commits after Import F-9 package:


automatically generate a .pem file on installation if one doesn't
exist
I think this patch has been merged to the Fedora package.


add ejabberd.cfg from xs-config
Install XS specific ejabberd.cfg instead of the default one

This patch is to use directly XS's configuration file so users which
want to deploy their own ejabberd but are not running a XS have the
right configuration.


Import patch from https://bugzilla.redhat.com/show_bug.cgi?id=452326
fixing quote bug in ejabberdctl
Didn't check if it has been merged to the F9 package (if it didn't, it
should be).

ejabberd.cfg: add mod_ctlextra to the modules list
This patch is needed ton add more commands to mod_ctlextra.


 Or should I be looking at the push-groups or patch-extra
 branches, and this is a futile idea?

These 2 branches are an attempt to make creation of the shared roster
easier (see #5310).
The push-groups is probably the way to got. With it, user can create
the shared roster using this command ejabberdctl vhost host
push-groups and so doesn't have to deal with the web interface anymore.

I rebased this branch on top of the current XS.



G.


___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel


Re: hyperactivity limits

2008-10-02 Thread Guillaume Desmottes
Le jeudi 02 octobre 2008 à 19:28 +1300, Douglas Bagnall a écrit :
 I wrote:
 

Hi Douglas,


  It is not completely satisfactory: I don't have the resources to test
  up to 3000 active users which I believe is an important target.
 
 Just to clarify this: it was actually client resources I ran out of,
 not the server (though that must have been getting close to melt
 down).
 
 I used hyperactivity, but could only maintain about 250 connections
 from each instance.  Guillaume: you mentioned somewhere that you had
 worked on a Gabble bug relating to hyperactivity, so I tried a git
 snapshot and got a recurring trace back with this punchline:


Yeah, I discovered some vicious Gabble bugs when using hyperactivity.
One of my fix [1] wasn't merged yet. I will ask to Daf to review it.

 dbus.exceptions.DBusException:
 org.freedesktop.Telepathy.Errors.NotImplemented: \
  Unknown property BuddyGadgetAvailable on org.laptop.Telepathy.Gadget

Sorry about that, I forgot to push my patch after the API change. Please
update your hyperactivity with [2].

 Do I need to replace other stuff than just Gabble?  Or should I not
 bother yet? Is 250 connections in the order that you get?  Perhaps my
 hyperactivity has issues all of its own.

I also observed issues when running too much connections on the same
Gabble instance (IIRC around 250 connections as you). I'll continue to
test and try to fix more of them.

For now, you can run multi instances of Gabble and hyperactivity.
Hyperactivity doesn't support multi instances yet, so you'll have to
make a full copy of it for each instance (don't forget to erase your
accounts directory to create new ones). I should fix that too.


G.


[1] http://monkey.collabora.co.uk/telepathy-gabble_fix-tube/
[2]
https://dev.laptop.org/git?p=users/guillaume/hyperactivity/.git;a=summary




___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: testing ejabberd

2008-09-24 Thread Guillaume Desmottes
Le mercredi 24 septembre 2008 à 16:29 +1200, Douglas Bagnall a écrit :
 Guillaume,
 
  Would be helpful if you could upload Gabble log somewhere. Before
  starting hyperactivity, launch Gabble manually like this:
  GABBLE_PERSIST=1 GABBLE_LOGFILE=/tmp/gabble.log GABBLE_DEBUG=all
  LM_DEBUG=net /usr/lib/telepathy/telepathy-gabble
 
 Thanks.  That was enough for me to sort it out -- the problem was
 caused by ejabberd restricting the number of registrations per IP
 address.  Adding {registration_timeout, infinity}. to ejabberd.cfg
 fixed it.
 
 I've put the log at http://halo.gen.nz/gabble-wired-connection-1.log
 but only in case you are curious.
 
 I've tested up to about 350 users from various machines at various
 activity rates.  Collaboration continues to work while ejabberd is
 under this load, while its memory use grows to around 160MB.  I'll
 report on this in more detail soon.


Oh right, I already observed this problem too. I added [1] explanations
in hyperactivity's README so hopefully you should be the last person
confused by this problem. :)


G.

[1]
https://dev.laptop.org/git?p=users/guillaume/hyperactivity/.git;a=commitdiff;h=e50d399881b823cad51edcc5525d53a972968459


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: testing ejabberd

2008-09-23 Thread Guillaume Desmottes
Le mardi 23 septembre 2008 à 18:22 +1200, Douglas Bagnall a écrit :
 hi
 
 I'm having some trouble using hyperactivity to test ejabberd.
 Hyperactivity always ends up looping over unsuccessful accounts,
 producing output like this:
 
 can't connect hyperactivity-ac4ec2e2-892e-11dd-a4b7-0017c40d34e4. Remove it
 have to create 1 accounts
 create 
 accounts/gabble/schoolserver.dell.xs.laptop.org/hyperactivity-ac9cecec-892e-11dd-a4b7-0017c40d34e4.account
 can't connect hyperactivity-ac6d40aa-892e-11dd-a4b7-0017c40d34e4. Remove it
 have to create 1 accounts
 create 
 accounts/gabble/schoolserver.dell.xs.laptop.org/hyperactivity-acb4ce02-892e-11dd-a4b7-0017c40d34e4.account
 can't connect hyperactivity-ac85168a-892e-11dd-a4b7-0017c40d34e4. Remove it
 
 What ejabberd says of each of these is something like:
 
 I(0.258.0:ejabberd_listener:112) : (#Port0.464) Accepted
 connection {{0,0,0,0,0,65535,44050,2588},33012} -
 {{0,0,0,0,0,65535,44050,1},5222}
 
 This would make simple sense if hyperactivity didn't succeed every now
 or then.  These usable accounts build up over time, so hyperactivity
 ends up starting with a few of them.  So in the sea of unsuccessful
 creations there is every now and then a line like:
 
 client hyperactivity-c3e52044-88f3-11dd-a913-0017c40d34e4: -- change
 current activity
 
 Although that has no server-side correspondent. The anomalous messages
 on the server side are:
 
 =INFO REPORT 2008-09-23 01:15:34 ===
 I(0.386.0:ejabberd_c2s:478) :
 ({socket_state,gen_tcp,#Port0.451,0.385.0}) Failed legacy
 authentication for
 [EMAIL PROTECTED]/Telepathy
 
 =INFO REPORT 2008-09-23 01:15:34 ===
 I(0.388.0:ejabberd_c2s:438) :
 ({socket_state,gen_tcp,#Port0.453,0.387.0}) Accepted legacy
 authentication for
 [EMAIL PROTECTED]/Telepathy
 
 =INFO REPORT 2008-09-23 01:15:34 ===
 I(0.388.0:mod_shared_roster:640) : user_available for
 hyperactivity-c3e52044-88f3-11dd-a913-0017c40d34e4 @
 schoolserver.dell.xs.laptop.org (1 resources)
 
 [ ... millions of the 'Accepted connection' messages, then ... ]
 
 =INFO REPORT 2008-09-23 01:15:54 ===
 I(0.388.0:ejabberd_c2s:1290) :
 ({socket_state,gen_tcp,#Port0.453,0.387.0}) Close session for
 [EMAIL PROTECTED]/Telepathy
 
 =INFO REPORT 2008-09-23 01:15:54 ===
 I(0.388.0:mod_shared_roster:679) : unset_presence for
 hyperactivity-c3e52044-88f3-11dd-a913-0017c40d34e4 @
 schoolserver.dell.xs.laptop.org / Telepathy - [] (0 resources)
 
 
 Has somebody seen this before?  What am I doing wrong?
 


Would be helpful if you could upload Gabble log somewhere. Before
starting hyperactivity, launch Gabble manually like this:
GABBLE_PERSIST=1 GABBLE_LOGFILE=/tmp/gabble.log GABBLE_DEBUG=all
LM_DEBUG=net /usr/lib/telepathy/telepathy-gabble

(Gabble path can change depending on your distro).
You should have logs in /tmp/gabble.log


G.



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Videochat - any status?

2008-09-11 Thread Guillaume Desmottes
Le jeudi 11 septembre 2008 à 14:21 +1000, Pia Waugh a écrit :
 Hi all,
 
 I have a great need for the video chat application to use for remote speech
 pathology and other services to remote communities through chat. Does anyone
 know the status of this project:
 
   http://wiki.laptop.org/go/Video_Chat
 
 It looks like nothing has happened with it for several months. If there is
 anyone leading this, could they post a status of the project?


Few months ago I posted this mail [1] explaining the current status of
VideoChat. The situation didn't evolve since but I guess it should still
be basically usable.


G.


[1] http://lists.laptop.org/pipermail/devel/2008-April/013227.html

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Server-devel] Update ejabberd package

2008-09-10 Thread Guillaume Desmottes
Le mercredi 10 septembre 2008 à 11:14 +1200, Martin Langhoff a écrit :
 On Wed, Sep 10, 2008 at 1:28 AM, Guillaume Desmottes
 [EMAIL PROTECTED] wrote:
  As mentioned few weeks ago, I created an updated version of the ejabberd
  XS package.
 
 Excellent. I'll give it a spin asap, now that the F9 based XS is in
 better shape.

Cool!

  This package still suffers shared roster bugs but after lot of tests
  they appear to be upstream problems and should not be a regression
  comparing to the current package.
 
  I think it would be worth to consider inclusion of this new package to
  XS for wider testing.
 
 Can you give me a bit of info on how much you've tested it internally.
 Also, I'll be looking for hints on how to use Daf's new testing tools
 effectively... (any links, clues...?)

Didn't test it that much yet as Daf is still working on the test tools.
I just moved to our Cambridge office so I'll be able to help Sjoerd and
Daf on the test bed.
I'll let you know as soon we have test results.

FYI, I'm working on #5310 and hope to have a package creating
automatically the shared roster soon.


G.


___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] Update ejabberd package

2008-09-10 Thread Guillaume Desmottes
Le mercredi 10 septembre 2008 à 14:44 +0100, Guillaume Desmottes a
écrit :
 FYI, I'm working on #5310 and hope to have a package creating
 automatically the shared roster soon.

I hacked a ejabberd module and we are now able to create the shared
roster using 2 commands. Problem is, we can't execute them as RPM post
install commands (see http://dev.laptop.org/ticket/5310#comment:10 for
details).

So, maybe we could provide a script creating the shared roster once the
server name has been configured in ejabberd.cfg? That would make
configuration lot easier for users as they won't have to deal with the
web interface anymore.

Thoughts?


G.


___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: #7893 -- Presence service gets confused.

2008-08-22 Thread Guillaume Desmottes
Le jeudi 21 août 2008 à 13:56 -0400, Michael Stone a écrit :
 Folks,
 
 #7893 was recently upgraded to release-blocker status since it is
 reported to afflict the Neighborhood view independent of the use of
 Gabble or Salut and since no reasonable workarounds are known.

This bug is about a simple mesh configuration without server, so only
Salut is involved, not Gabble.

 Please help investigate.
 
 Collabora folks -- what debugging would you like independent testers to
 be turning on?

telepathy-salut (with debugging on) and PS log on each XO's. When mesh
views is not synced with reality anymore, the output of avahi-browse
--all could be useful to check which services are still known.
A tcpdump log capturing all the network traffic during the test could be
nice too.



G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: ejabberd XS package questions

2008-08-21 Thread Guillaume Desmottes
Le mercredi 20 août 2008 à 11:15 -0400, John Watlington a écrit :
 This has been previously discussed on this list.
 On Fedora, ejabberdctl requires the erlang nodename as the first  
 argument:
 ejabberdctl ejabberd register admin hostname passwd
 
 This is documented at:
 http://wiki.laptop.org/go/XS_Configuration_Management#Small_School. 
 2FHome_School

I tried to launch ejabberdctl with the node argument, but that doesn't
change anything.

I got this error when trying to change the domain name as explained on
the wiki:

[EMAIL PROTECTED] ~]# /etc/sysconfig/olpc-scripts/domain_config
schoolserver.cbg.collabora.co.uk random.xs.laptop.org
Changing from random.xs.laptop.org to schoolserver.cbg.collabora.co.uk
find: /fsroot.olpc/etc/sysconfig/olpc-scripts/domain_config.d/: No such
file or directory

Btw, which version of xs-config and xs-pkgs should be installed? I had
to remove them when I desinstalled ejabberd during my tests then I
reinstalled these 2 packages using yum. The installed versions are
xs-config-0.2.5-6 and xs-pkgs-0.3.0-1.

Thanks for your help.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: ejabberd XS package questions

2008-08-21 Thread Guillaume Desmottes
Le jeudi 21 août 2008 à 12:27 +0200, Guillaume Desmottes a écrit :
 Le mercredi 20 août 2008 à 11:15 -0400, John Watlington a écrit :
  This has been previously discussed on this list.
  On Fedora, ejabberdctl requires the erlang nodename as the first  
  argument:
  ejabberdctl ejabberd register admin hostname passwd
  
  This is documented at:
  http://wiki.laptop.org/go/XS_Configuration_Management#Small_School. 
  2FHome_School
 
 I tried to launch ejabberdctl with the node argument, but that doesn't
 change anything.

After lot of tests, I finally found the problem. It was a known but
unfixed test in the Fedora package.
I fixed it in this commit:
http://git.collabora.co.uk/?p=user/cassidy/ejabberd-rpm;a=commitdiff;h=3ff84e7a25c2ca98d338bac3cc6d9d0996f30c07


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: ejabberd XS package questions

2008-08-20 Thread Guillaume Desmottes
Le mercredi 20 août 2008 à 10:17 +1200, Martin Langhoff a écrit :
 On Tue, Aug 19, 2008 at 11:56 PM, Guillaume Desmottes
 [EMAIL PROTECTED] wrote:
  I'm working on the ejabberd package for the XS. We'd like to provide an
  updated package based on ejabberd 2.0.1 which just work once is
  installed. The goal is of course to simplify as much as possible the
  deployment of ejabberd servers for schools and community users.
 
 Good goals, though there's a tricky aspect in that we don't know the
 domain name at install time, and AFAIK ejabberd doesn't like the
 domain being changed after the DB has been setup.
 
 Following that, my intention is to automate the setup steps that need
 to take place once the fqdn has been set.

Humm good point. Don't know how exactly ejabberd handles that.

  My current package is hosted in this git repo:
  http://git.collabora.co.uk/?p=user/cassidy/ejabberd-rpm;a=shortlog;h=refs/heads/XS
 
 Great.
 
  Here is few points I'd like to discuss:
 
  - Where are hosted XS packages source? I guess my ejabberd package
  should belong here.
 
 xs-dev. Have you got an acct there? If not, send me and Henry Hardy
 your public keys and we'll set things up.
 

No, will send you my key.

  - /etc/ejabberd/ejabberd.pem is not installed by current XS package but
  xs-config provide it. Recently, the Fedora's devel package was updated
  to generate this file at the package installation (#5834). I integrated
  this change in my package so we'll probably have to drop ejabberd.pem
  from xs-config.
 
 Yes. I've seen your .pem generation, and I think it's a good idea. As
 soon as we clear your new pkg for installation I'll remove the .pem
 file from xs-config.

Cool!

  - Same question about ejabberd.cfg which is currently overridden by
  xs-config. The XS package should directly provide the right conf file I
  guess.
 
 Your package should provide a default cfg. xs-config will have scripts
 that will override it (I'm changing how that works at the moment to
 make it saner) with a config file that is specific to the XS.

I patched my package to provide xs-config's ejabberd.cfg instead of the
default upstream one.
See
http://git.collabora.co.uk/?p=user/cassidy/ejabberd-rpm;a=commitdiff;h=509b8a26ead28a2ab4957cc907ddaa926c8524f4
http://git.collabora.co.uk/?p=user/cassidy/ejabberd-rpm;a=commitdiff;h=faaeb9797461b244b06fadbe526d079723eb46c2


 A couple of questions WRT your package:
 
  - How is it different from the one in F9? New/added files? Patched files?

As you can see on
http://git.collabora.co.uk/?p=user/cassidy/ejabberd-rpm;a=shortlog;h=refs/heads/XS
all the changes are *after* the Import F-9 package commit:
- This patch  recent_online_and_nearby_groups_updated.diff
- Generation of the PEP file
- The new ejabberd.cfg


  - Can we make it so that it is _only_ additional files? If so, then
 we could make it into a package that depends on F9's ejabberd.

I'm afraid no as we need to patch ejabberd code
(recent_online_and_nearby_groups_updated.diff). Maybe for 9.1.0 as we
plan to remove the shared roster hack and use Gadget instead.


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: ejabberd XS package questions

2008-08-20 Thread Guillaume Desmottes
Le mardi 19 août 2008 à 13:56 +0200, Guillaume Desmottes a écrit :
 Hi,
 
 I'm working on the ejabberd package for the XS. We'd like to provide an
 updated package based on ejabberd 2.0.1 which just work once is
 installed. The goal is of course to simplify as much as possible the
 deployment of ejabberd servers for schools and community users.
 
 My current package is hosted in this git repo:
 http://git.collabora.co.uk/?p=user/cassidy/ejabberd-rpm;a=shortlog;h=refs/heads/XS
 
 Here is few points I'd like to discuss:

I'm facing a problem with my current package, I'm unable to register the
admin user using ejabberdctl.
I use ejabberdctl register admin hostname password as explained on
http://wiki.laptop.org/go/Ejabberd_Configuration#Configuration but
ejabberdctl silently fail (it just displays the usage message).
The same command does work on my own ejabberd installation.

Did you previously notice similar issues?


Thanks,


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


ejabberd XS package questions

2008-08-19 Thread Guillaume Desmottes
Hi,

I'm working on the ejabberd package for the XS. We'd like to provide an
updated package based on ejabberd 2.0.1 which just work once is
installed. The goal is of course to simplify as much as possible the
deployment of ejabberd servers for schools and community users.

My current package is hosted in this git repo:
http://git.collabora.co.uk/?p=user/cassidy/ejabberd-rpm;a=shortlog;h=refs/heads/XS

Here is few points I'd like to discuss:

- Where are hosted XS packages source? I guess my ejabberd package
should belong here.

- /etc/ejabberd/ejabberd.pem is not installed by current XS package but
xs-config provide it. Recently, the Fedora's devel package was updated
to generate this file at the package installation (#5834). I integrated
this change in my package so we'll probably have to drop ejabberd.pem
from xs-config.

- Same question about ejabberd.cfg which is currently overridden by
xs-config. The XS package should directly provide the right conf file I
guess.


Thanks


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [sugar] How do I connect to a Jabber server ?

2008-08-05 Thread Guillaume Desmottes
Le mardi 05 août 2008 à 12:24 +0100, Gary C Martin a écrit :
 On 5 Aug 2008, at 09:46, Morgan Collett wrote:
 
  The xochat.org jabber server is the one I seem to reliably attach to
  for my XO testing, though I'd love to see an official developer  
  jabber
  server, so as not to pester real G1G1 users with my tests, and so we
  can 'eat our own dogfood' in a dev environment**. Connecting to a
  remote jabber server is currently the way to see and share with other
  remote users*** in the neighborhood.
 
  ** perhaps Sugar Labs could run such an environment?
 
  Collabora run a server which is the default setting for jhbuild:
  olpc.collabora.co.uk
 
 That's good to hear re-confirmed, but I've not seen any buddies/ 
 activities shared on olpc.collabora.co.uk for weeks/months. I'd just  
 assumed your server was always borked by lots of connections, or in  
 some unstable dev status, so I had switched over to xochat.org which  
 always seems to respond and have buddies showing.
 
 Using your recent nc olpc.collabora.co.uk 5222 trick I can now see  
 olpc.collabora.co.uk is responding with some xml just fine. So, is no  
 one else using it, or should I do some debugging? Are you running a  
 dev version of a jabber server that's doing something different?

olpc.collabora.co.uk was recently reinstalled to a new ejabberd server
in order to test Gadget. The shared roster hack was removed which
improve stability but doesn't automatically display all the connected
buddies anymore. Gadget should solve that, I plan to merge it at the
beginning of the 9.1.0 cycle.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Collaboration Bug Triage Notes

2008-08-04 Thread Guillaume Desmottes
Le vendredi 01 août 2008 à 17:43 -0400, Greg Smith a écrit :
 Hi All,
 

Hi,


 Also:
 I recorded this URL but forgot what it refers to :-( 
 http://64.233.183.104/search?q=cache:Z1ajb0I4Aj8J:wiki.laptop.org/go/XMPP_Extensions+olpc+shared+rosterhl=cyct=clnkcd=1

This is a page explaining the XMPP server configuration we are currently
using and specially the shared roster hack (and why that's a bad thing).

 I need to review an e-mail which Guillaume posted recently on 
 collaboration status. Sorry I lost that :-( can you resend?

Sure. http://lists.laptop.org/pipermail/sugar/2008-July/007407.html

 We're on again Monday at 10AM US ET on freenode.net #olpc-meeting. 
 Picking up the same query from the top. Please add any other critical 
 collaboration bugs to the list ASAP

See you later.

 Thanks a lot to the collabora team for their time and patience getting 
 me up to speed.
 

You're welcome.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Network, neighborhood view, and the emulator.

2008-08-04 Thread Guillaume Desmottes
Le samedi 02 août 2008 à 15:18 -0400, Ton van Overbeek a écrit :
 On 8/2/08, Alejandro Fernandez [EMAIL PROTECTED] wrote:
  Hi All,
is it possible to browse the neighborhood witn the OLPC emulator (on
   qemu) to discover other XOs and emulated XOs? (over a wi-fi network)
My first attempt showed me an empty neighborhood view on the
   emulated XO altough the real XOs could see each other. The real XOs
   did not see the emulated XOs.
   Regards,
   Casco
 
 
 Works if you can connect to a working jabber server. All real and
 emulated XOs connected to the jabber server show up in the
 neighborhood on both the emulated and real XOs.
 Meshing does not work on emulated XOs.

You can also connect your XO's and emulators to the same access point
and use serverless collaboration (telepathy-salut).
That just doesn't work if your XO's are connected in simple mesh.



G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: SMS messaging

2008-07-25 Thread Guillaume Desmottes
Le jeudi 24 juillet 2008 à 09:59 +0200, Guillaume Desmottes a écrit :
 The plan with Gadget is to allow user to request random buddies (and
 activities) or perform search based on different criteria. As you can
 see on [1], currently only search based on buddy properties is
 implemented but we plan to add alias search soon (maybe next week if you
 really need it).


I implemented search by alias using Gadget.

The gadget branch is not merged yet and the Gabble one is
http://monkey.collabora.co.uk/telepathy-gabble-gadget/

See
http://people.collabora.co.uk/~cassidy/spec-olpc-gadget.html#org.laptop.Telepathy.Gadget
 for the API.


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: SMS messaging

2008-07-24 Thread Guillaume Desmottes
Le mercredi 23 juillet 2008 à 12:38 -0400, Ankur Verma a écrit :
 
 I can run a bash/python script upon the reception of the message with
 the message parameters.  This makes it flexible enough to call any
 application.
 

Then I think you should write a Python application which connect to the
jabber server, find the buddy and send him the message.

As a start I suggest you to take a look on the Telepathy spec [1] and
telepathy-python examples.


G.


[1] http://telepathy.freedesktop.org/spec.html



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: SMS messaging

2008-07-24 Thread Guillaume Desmottes
Le jeudi 24 juillet 2008 à 03:36 -0400, Ankur Verma a écrit :
 
 As per our earlier discussion, the method at present is to use
 roster.py, which you are planning to remove in the next versions.

Humm not really. Using the roster is and will always be a sane way to
find contacts. But, as you can guess, it assumes that the contact is in
your roster.
Currently this is a sane assumption because of the shared roster hack.
But when we'll drop it, that won't be true anymore.

 As roster.py also uses Telepathy to get the nicks of XO who have
 subscribed or are friends, are there any alternative functions which I
 can use to fetch the list of XOs? I am ready to look more into
 telepathy specs, but I am curious to know the answer.

The plan with Gadget is to allow user to request random buddies (and
activities) or perform search based on different criteria. As you can
see on [1], currently only search based on buddy properties is
implemented but we plan to add alias search soon (maybe next week if you
really need it).

So for now, I suggest you to use a server with the shared roster hack or
manually subscribe your SMS user with a test buddy for your tests.
So you could test most of the part of your app and just change it to use
alias search later.


G.

[1]
http://people.collabora.co.uk/~cassidy/spec-olpc-gadget.html#org.laptop.Telepathy.Gadget
 


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: SMS messaging

2008-07-23 Thread Guillaume Desmottes
Le mardi 22 juillet 2008 à 18:36 -0400, Ankur Verma a écrit :
 
 Message is in the format Nick_Name:Message. Though its true that
 Nicknames are not unique across a school, but it is the only way to
 specify XO in a user-friendly manner. 
 
 If XO is not currently connected, a SMS autoreply will be sent
 indicating XO is not present in the mesh. One of the use cases would
 be when parents want to know about their child's presence in the
 school considering every XO in school is connected!

Ok, then I think the Telepathy based client connected to the jabber
server could be a good solution. In which language is written your
application?


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: SMS messaging

2008-07-22 Thread Guillaume Desmottes
Le mardi 22 juillet 2008 à 09:18 -0400, Ankur Verma a écrit :
 
 Hi Guillaume,
 
 Thank you for your message.
 
 Though it is an external application, but its intended to be run on
 server (Application has similarities with server implementation like
 it runs Apache)
 
 
 A) If that's an external application, then you have to connect
 to the
 jabber server as any client/XO. You'll be able to see all the
 connected
 XO's that are in your jabber roster. Currently we are using an
 ugly hack
 called shared roster meaning you'll see all the connected
 XO's but we
 plan to drop it soon.
 A solution could be to use Gadget [1] but we currently don't
 have API to
 search for buddies based on their alias (that's probably
 something
 useful to have so we could consider to add one).
 Another solution would be for each buddies to subscribe to
 your
 application (as a Friend) if they are interested about
 receiving SMS
 messages but that's not very convenient IMHO.
 
 The idea of having the API to search for buddies based on their nicks
 and forwarding message to them seems good.

Be aware that with this solution, you won't find the XO if he's not
currently connected. How do you plan to handle such case?


 One of the solution to forward message can be a XMPP message, though I
 am not sure how to implement this. Can you think of any alternatives?

If you use Telepathy, sending a XMPP message to the contact will be
trivial.


 B) A server plugin. You'll be able to use the server API (and
 so be able
 to know which buddies are connected, etc) but you'll be depend
 on a
 server implementation and your app will have to run on the
 same box as
 the server.
 
 Server API doesn't let us know about the nicks of  current buddies
 that are connected. As Wad meant to say, Jabber IDs are available
 which are not human readable and they cannot be mapped to nicks at
 present. 

I have no idea how plugin's API work but I guess you should be able to
access to most of the server's model, including the alias.


G.



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Video Chat

2008-07-16 Thread Guillaume Desmottes
Le mardi 15 juillet 2008 à 19:39 -0400, Ricardo Carrano a écrit :
 Hey!


Hi,


 I am trying to install the Video Chat activity, in order to check #7511.
 
 Following instructions in:
 http://lists.laptop.org/pipermail/devel/2008-April/013227.html
 
 Fetching the rpms from:
 http://people.collabora.co.uk/~cassidy/olpc-video-chat/
 
 All the rpms installs ok but the last which fails on dependency for
 libtelepathy-glib.so.0.
 Where can I get this lib? I tried some obvious things, like yum
 install libtelepathy, but it didn't help.


Humm this is weird. Which build are you using? Could you check what rpm
-qa | telepathy returns ?



G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Video Chat

2008-07-16 Thread Guillaume Desmottes
Le mercredi 16 juillet 2008 à 09:31 -0300, Ricardo Carrano a écrit :
  I am trying to install the Video Chat activity, in order to check #7511.
 
  Following instructions in:
  http://lists.laptop.org/pipermail/devel/2008-April/013227.html
 
  Fetching the rpms from:
  http://people.collabora.co.uk/~cassidy/olpc-video-chat/
 
  All the rpms installs ok but the last which fails on dependency for
  libtelepathy-glib.so.0.
  Where can I get this lib? I tried some obvious things, like yum
  install libtelepathy, but it didn't help.
 
 
  Humm this is weird. Which build are you using? Could you check what rpm
  -qa | telepathy returns ?
 
 
 It is candidate-708:
 
 telepathy-gabble-0.7.1-0.8.olpc2
 telepathy-salut-0.2.3-1.olpc2
 telepathy-filesystem-0.0.1-2.fc7
 telepathy-glib-0.6.1-1.olpc2


This version is too old. telepathy-stream-engine requires at least
telepathy-glib 0.7.6.
You should try using Joyride.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [SURVEY] builders, how do you build? what do you build?

2008-07-01 Thread Guillaume Desmottes
Le vendredi 27 juin 2008 à 17:23 -0400, Erik Garrison a écrit :
 Developers, specifically those running build systems,
 
 Many of us are confused about the software flows inherent in the daily
 build processes which are occuring at OLPC.  I would like to conduct a
 simple survey of all people building software for OLPC so that all of us
 can better understand the sources of the software running on the XO and
 XS without individually hassling the responsible parties every time we
 have generic questions about their build processes.
 
 Builders, please describe your local build network:
 
 0) Who are you and who do you directly work for?

Guillaume Desmottes, working for Collabora Ltd.

 1) What do you build?

The Telepathy Stack: telepathy-gabble, telepathy-glib, telepathy-salut,
telepathy-stream-engine
The Farsight Stack (used for the video-chat activity): farsight,
gstreamer-plugins-farsight, libjingle

and sugar-presence-service.

 2) Where does it come from? / Who directly provides you with source code?

Most of the time I package mine own new releases (as I'm upstream of the
presence-service, Gabble and Salut) or include a patch I just wrote to
fix some issue.

I also occasionally package latest stable releases of the rest of the
stack when I need one new feature or I know it improves general
stability.

 3) Where does the output of your build process go?  / Who handles the
 immediate output of your builds?

Directly to Koji.

 4) Where specifically is it built? (I want server names and/or
 descriptions, where security is a concern please share them with me
 privately.)

My builds are submitted from teach.laptop.org to Koji.

 5) What build systems do you use to build software?  Please briefly
 describe their operation or provide a link to documentation or source
 code which does.

No idea :)



Hope that help,


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: OLPC config in salut in F9?

2008-06-27 Thread Guillaume Desmottes
Le jeudi 26 juin 2008 à 17:23 -0400, Michael Stone a écrit :
 On Thu, Jun 26, 2008 at 05:01:04PM +0200, Morgan Collett wrote:
  I asked Dennis about branching salut, and he recommended we try keep
  everything in F-9 if possible. Is it feasible to put the rainbow
  specific patches in such that they are enabled with a runtime option,
  if built with --enable-olpc?
 
 Could you put up a link to the OLPC-specific patches?

Gabble patches:
https://dev.laptop.org/git?p=sugar-jhbuild;a=blob_plain;f=config/modulesets/patches/telepathy-gabble-chmod-unix-socket.patch;hb=HEAD
https://dev.laptop.org/git?p=sugar-jhbuild;a=blob_plain;f=config/modulesets/patches/telepathy-gabble-olpc-no-dbus-uid-check.patch;hb=HEAD

And the same patches for Salut:
https://dev.laptop.org/git?p=sugar-jhbuild;a=blob;f=config/modulesets/patches/telepathy-salut-olpc-no-dbus-uid-check.patch;h=d876cd80c1251e5d5abdc27709a4df132387181c;hb=HEAD
https://dev.laptop.org/git?p=sugar-jhbuild;a=blob;f=config/modulesets/patches/telepathy-salut-chmod-unix-socket.patch;h=5d36941d1faf84015fc4357f03926995fae1626c;hb=HEAD



G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: OLPC config in salut in F9?

2008-06-26 Thread Guillaume Desmottes
Le jeudi 26 juin 2008 à 17:23 +0200, Morgan Collett a écrit :
 On Thu, Jun 26, 2008 at 17:03, Guillaume Desmottes
 [EMAIL PROTECTED] wrote:
  Le jeudi 26 juin 2008 à 17:01 +0200, Morgan Collett a écrit :
  On Wed, Jun 25, 2008 at 12:01, Guillaume Desmottes
  [EMAIL PROTECTED] wrote:
   Le mardi 24 juin 2008 à 17:36 -0700, Brian Pepple a écrit :
   On Wed, 2008-06-25 at 01:12 +0200, Morgan Collett wrote:
Can we enable the OLPC-specific patches and config in telepathy-salut
in F-9? We're rebasing OLPC builds on F-9 and it would be good to work
in the F-9 branch and not need to fork.
  
   Does it make sense to have these patches in F9? I'm on vacation right
   now, so I don't really have time to look at the patches.  If it makes
   sense to have these in F9 in addition to OLPC, I don't have a problem
   with you doing enabling it.
  
   Not really. These patches are ugly OLPC specific workarounds due to XO
   security model (Rainbow).
   Building Salut with --enable-olpc doesn't hurt though (Debian does).
 
  I asked Dennis about branching salut, and he recommended we try keep
  everything in F-9 if possible. Is it feasible to put the rainbow
  specific patches in such that they are enabled with a runtime option,
  if built with --enable-olpc?
 
  Then it would be build time option and F9 users will have the patch
  applied anyway (which is not really a good idea).
 
 Can we make it a runtime option?


We certainly don't want to add a CM parameter for this. We could
eventually check an env variable but I'm not convince that's a so good
idea as these workarounds are very very hackish.

Sjoerd, Daf: Thoughts?


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: journal object transfer for 8.2

2008-06-10 Thread Guillaume Desmottes
Le lundi 09 juin 2008 à 16:12 -0400, Michael Stone a écrit :
 Tomeu,
 
  have heard occasional requests to implement the sending and sharing of
  journal entries.
 
 It's a desirable feature but, from my perspective, it's much lower in
 immediate priority than work which brings the sugar UI revision into a
 releasable condition and which polish the existing work by closing
 several of the 379 tickets assigned to component 'sugar':
 
   
 http://dev.laptop.org/query?status=assignedstatus=newstatus=reopenedcomponent=sugarorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=component
 
  So the questions are: is this a feature we should deliver for the 8.2
  release? 
 
 In my opinion, no. 
 
 Do you think differently?


The new (work in progress) Telepathy file transfer specification should
be able to nicely implement object transfer. But I doubt we'll have an
implementation ready for 8.2.

Could be a cool feature for the next release cycle though.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: New, more realistic multi-hop network testbed

2008-06-09 Thread Guillaume Desmottes
Le dimanche 08 juin 2008 à 12:11 -0400, Michail Bletsas a écrit :
   b) collabora did some work to abstract out avahi, in theory the
  groundwork is present for a cerebro backend. 
 That's more like wishful thinking at this point. We need to push more
 on that end. 
 
Latest Salut release has a new Avahi abstraction layer (see #6658).
It's still unclear if Cerebro should be integrated as an Salut backend
or in its own connection manager though.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [sw-eco] Keyboard Support for Haiti Ethiopia - OLPC 8.1.1 bugfix release

2008-05-22 Thread Guillaume Desmottes
Le mercredi 21 mai 2008 à 19:47 +0100, Dafydd Harries a écrit :
 I'll try and find out which Telepathy fixes might be worth pushing into an
 USR. Looking at changelogs, I see at least one bug:
 
 http://en.pastebin.ca/1025092
 

Yeah having the fix for
http://bugs.freedesktop.org/show_bug.cgi?id=14343 would be good.

The fix of #6883 could be worth to ship too.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: New network scripts/tools for testing

2008-05-12 Thread Guillaume Desmottes
Le samedi 10 mai 2008 à 00:44 -0400, Giannis Galanis a écrit :
 The past couple of weeks I have been working on developing several
 Network testing scripts,
 that make testing a more pleasant experience!
 

Awesome!
I'm sure this will make debugging of PS/Telepathy issues a lot easier.

Thanks a lot


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Internet wide chat

2008-04-24 Thread Guillaume Desmottes
Le lundi 21 avril 2008 à 10:55 +0200, Bernie Innocenti a écrit :
  - how could a kid talk with his parents or teachers who are using
a normal computer
 

FYI, I did some packaging work and resurrected the video-chat activity.
I was able to videocall my 2 XO's and to call one XO using Empathy from
my desktop.

The UI is still awful and we need to solve some issues (#1627,#6301) to
properly integrate audio/video calls in sugar, but that's a start.

If you want to test it, you have to install the bundle and packages from
http://people.collabora.co.uk/~cassidy/olpc-video-chat/ on a Joyride
install in that order:
- gsm
- libjingle
- gstreamer-ffmpeg
- gstreamer-plugins-farsight
- farsight
- telepathy-stream-engine
- VideoChat


sugar-install-bundle is currently broken in Joyride. That should be
fixed soon.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Joyride

2008-04-24 Thread Guillaume Desmottes
Le mercredi 23 avril 2008 à 19:31 -0400, Benjamin M. Schwartz a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Benjamin M. Schwartz wrote:
 | Simon Schampijer wrote:
 | | Chris Ball wrote:
 | | Hi,
 | |
 | | Can anybody suggest a relatively functional Joyride with the new UI
 | | ?  I'm at the end of a think pipe, and probably won't have time to
 | | download a second image if the first is marginal...
 | |
 | | 1896 ?
 | |
 | | The new Journal design landed in 1895, and there were many sugar changes
 | | in 1894.  I think 1892 is a decent bet.
 | |
 | | - Chris.
 | |
 | | 1895 has latest journal which has some changes for the new UI as well -
 | | I run it here fine.
 |
 | In 1896, I am consistently unable to open Write.  Everything else seems to
 | work.  I guess I don't recommend 1896, for that reason.   I don't know
 | when this bug was introduced.
 
 As usual, I spoke too soon.  The only activity that works under 1896 is
 Terminal.  Everything else dies without producing any logfiles.  It
 appears that this is due to the presence-service change in 1896.
 

The only change is this new presence-service is
https://dev.laptop.org/git?p=projects/presence-service;a=commitdiff;h=507e53d55d2f0767f35777e2db40abd654605f08

It shouldn't affect activities launching.

G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Joyride

2008-04-24 Thread Guillaume Desmottes
Le mercredi 23 avril 2008 à 19:31 -0400, Benjamin M. Schwartz a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Benjamin M. Schwartz wrote:
 | Simon Schampijer wrote:
 | | Chris Ball wrote:
 | | Hi,
 | |
 | | Can anybody suggest a relatively functional Joyride with the new UI
 | | ?  I'm at the end of a think pipe, and probably won't have time to
 | | download a second image if the first is marginal...
 | |
 | | 1896 ?
 | |
 | | The new Journal design landed in 1895, and there were many sugar changes
 | | in 1894.  I think 1892 is a decent bet.
 | |
 | | - Chris.
 | |
 | | 1895 has latest journal which has some changes for the new UI as well -
 | | I run it here fine.
 |
 | In 1896, I am consistently unable to open Write.  Everything else seems to
 | work.  I guess I don't recommend 1896, for that reason.   I don't know
 | when this bug was introduced.
 
 As usual, I spoke too soon.  The only activity that works under 1896 is
 Terminal.  Everything else dies without producing any logfiles.  It
 appears that this is due to the presence-service change in 1896.
 

Write does work for me with 1896 (as the few others activities I tried).

G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Document sharing issues

2008-04-22 Thread Guillaume Desmottes
Le lundi 21 avril 2008 à 10:24 -0500, James Simmons a écrit :
 2).  Downloading a document is very slow.  I distribute View Slides 
 files on an Apache server, using the Browse activity to copy same to the 
 Journal.  This takes under a minute even for a large file (over 15mb).  
 Then I share the document with another instance of Sugar on the same 
 box.  *That* is agonizingly slow.  I know the two instances are not 
 communicating directly, but it still seems like there is a lot of 
 overhead going on.  Can I do anything about this?

Were you using Gabble or Salut? Currently Gabble stream tubes still send
their data through the jabber server making transfer really slow. I'm
working on implementing real p2p instead (#4047).
Salut doesn't have this problem though as it already uses TCP
connections.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Internet wide chat

2008-04-22 Thread Guillaume Desmottes
Le lundi 21 avril 2008 à 10:55 +0200, Bernie Innocenti a écrit :
  - how could they make kids from Ankara and Istanbul chat together
 
  - how could a kid talk with his parents or teachers who are using
a normal computer
 

We use XMPP/Jabber when the laptop is connected to a schoolserver. So
basically all we need to do to allow this is:
- Enable communications between jabber server
- Add a way in Sugar to add not OLPC contact as Friend, initiate chats
with them, etc.
- Modify Chat to properly handle 1-1 chats and not OLPC activities muc
(#6298)

It's more an UI and privacy issue than a technical problem, really.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Internet wide chat

2008-04-22 Thread Guillaume Desmottes
Le lundi 21 avril 2008 à 11:54 -0400, Chris Ball a écrit :
 Hi,
 
  - They asked if video chat is possible.  I recall someone was
 working on it months ago.  What is the current status?
 
 We need two things:  a codec that we can encode and decode in real-time
 (the demo from 2006 used h.263) and a transport layer -- I think we have
 a UDP transport for Salut, but not for Gabble, so video chat would be on
 the local mesh only.
 

No. Gabble already implements Jingle audio/video (as gtalk). Transport
is done using UDP-ICE. Last year I wrote a simple (and ugly :) video
chat activity who was using this.

 It would be worth someone checking out the Theora team's latest
 optimizations, which might make Theora solve the codec problem.

Right. As said we need a good free encoder as H263 has legal issues.

So, if we want to have full audio/video support on XO's we have to:
a) Solve this legal codec issue and make farsight work with the chosen
free codec
b) Implement audio/video in Salut
c) Have a proper video chat activity integrated in sugar (#1627, #6301)
d) Profit :)


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Document sharing issues

2008-04-22 Thread Guillaume Desmottes
Le mardi 22 avril 2008 à 04:26 -0400, Polychronis Ypodimatopoulos a
écrit :
 Guillaume Desmottes wrote:
  Le lundi 21 avril 2008 à 10:24 -0500, James Simmons a écrit :

  2).  Downloading a document is very slow.  I distribute View Slides 
  files on an Apache server, using the Browse activity to copy same to the 
  Journal.  This takes under a minute even for a large file (over 15mb).  
  Then I share the document with another instance of Sugar on the same 
  box.  *That* is agonizingly slow.  I know the two instances are not 
  communicating directly, but it still seems like there is a lot of 
  overhead going on.  Can I do anything about this?
  
 
  Were you using Gabble or Salut? Currently Gabble stream tubes still send
  their data through the jabber server making transfer really slow. I'm
  working on implementing real p2p instead (#4047).
  Salut doesn't have this problem though as it already uses TCP
  connections.

 Can you elaborate more on this? Isn't TCP the underlying mechanism for 
 Gabble also? How is Salut more efficient?

Gabble uses one TCP connection to the jabber server and when you connect
to a stream tube, all the data are send using this connection. This is
very inefficient because all the data are encoded into base64 XML
stanzas and go trough the server (the traffic inside a stream tube can
potentially be really big).
What we need to do is to establish a *new* TCP connection between the 2
peers of the tube. So data won't have to be encoded to base64 and won't
go trough the server anymore. But that's not an easy task as peers can
potentially be behind a NAT. So we have to use NAT traversal magic using
Jingle, ICE and stuffs as we do for audio/video calls.

Salut doesn't have this problem as peers are on the same network and so
can directly talk to each other.


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: list of laptops connected to jabber

2008-04-22 Thread Guillaume Desmottes
Le lundi 21 avril 2008 à 10:05 +0200, Guillaume Desmottes a écrit :
 Le samedi 19 avril 2008 à 22:18 +0300, Giannis Galanis a écrit :
  In the testbed in peabody, the list of peers seen from the server is
  usually a superset of what we see from each individual mesh view.
  
 
 Could be related to: #6883 #6884 #6888
 
  It would be very useful if we could get the list shown by the analyze
  activity, but from the console.
  
  I believe it would easy to do that from the telepathy-gabble logs. For
  every new arrival or departure there must a specific entry.
  
 
 Actually there are different levels for this:
 - Contacts know as online by Gabble
 - OLPC Buddy in the PS
 - Buddy displayed by sugar in the mesh view
 
 And of course, bugs can occur in each level.
 telepathy-gabble.log gives us enough information to track the first
 level (but not easy to read as log can be a mess). presence-service.log
 for the second. And currently the only way to check 3 is to manually
 count buddies.
 
 I agree with you, more helper would be welcome to debug these kinds of
 bugs.


I wrote a simple script listing all the buddies known by the PS. See
https://dev.laptop.org/ticket/6918

Maybe we should ship it with images?


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: list of laptops connected to jabber

2008-04-21 Thread Guillaume Desmottes
Le samedi 19 avril 2008 à 22:18 +0300, Giannis Galanis a écrit :
 In the testbed in peabody, the list of peers seen from the server is
 usually a superset of what we see from each individual mesh view.
 

Could be related to: #6883 #6884 #6888

 It would be very useful if we could get the list shown by the analyze
 activity, but from the console.
 
 I believe it would easy to do that from the telepathy-gabble logs. For
 every new arrival or departure there must a specific entry.
 

Actually there are different levels for this:
- Contacts know as online by Gabble
- OLPC Buddy in the PS
- Buddy displayed by sugar in the mesh view

And of course, bugs can occur in each level.
telepathy-gabble.log gives us enough information to track the first
level (but not easy to read as log can be a mess). presence-service.log
for the second. And currently the only way to check 3 is to manually
count buddies.

I agree with you, more helper would be welcome to debug these kinds of
bugs.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: How to use Salut?

2008-04-16 Thread Guillaume Desmottes
Le mardi 15 avril 2008 à 20:32 +0200, Morgan Collett a écrit :
 A very quick test for which one is running is: ps ax |grep telepathy
 - if it shows telepathy-gabble, you're on a jabber server. If it shows
 telepathy-salut, you're on salut. If it shows neither, then something
 made salut crash - please log a ticket and attach logs if you have
 them enabled[0]. If it shows both gabble and salut, also log a ticket
 against presence-service with presenceservice.log.
 

... and the needed footnote :)

[0] http://wiki.laptop.org/go/Telepathy-debug


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


/home is full on dev.laptop.org

2008-04-15 Thread Guillaume Desmottes
Hi,

Don't know what the right person to inform but /home is full on
dev.laptop.org, making git push impossible.

[EMAIL PROTECTED]:~$ df -h
FilesystemSize  Used Avail Use% Mounted on
/dev/cciss/c0d0p5 9.2G  3.5G  5.7G  39% /
varrun2.4G   88K  2.4G   1% /var/run
varlock   2.4G 0  2.4G   0% /var/lock
udev  2.4G   56K  2.4G   1% /dev
devshm2.4G 0  2.4G   0% /dev/shm
/dev/cciss/c0d0p6 1.1T  1.1T 0 100% /home
/dev/cciss/c0d0p3 957M   34M  924M   4% /tmp
/dev/cciss/c0d0p2 957M  309M  649M  33% /var/log



G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [sugar] Automatic transfer/update of activities on the mesh (Was: Sharing behavior in the core Read activity)

2008-03-26 Thread Guillaume Desmottes
Le mardi 25 mars 2008 à 16:02 -0400, Benjamin M. Schwartz a écrit :
 This works, and will work for the proposed case.  For the future, I see
 file transfer as precisely the sort of thing that should be handled
 internally to Telepathy.  Perhaps Telepathy should implement XEP-0234
 (file transfer)[2] or even XEP-0214 (file sharing)[3].
 

We have a draft of spec for file transfer (but it will be probably
modified) and a Salut branch implementing it. So that's definitely
something that could be done at some point.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Cerebro performance

2008-03-07 Thread Guillaume Desmottes

Le vendredi 07 mars 2008 à 02:29 -0500, Michael Stone a écrit :
 RPMS and better developer documentation will probably appear tomorrow,
 as soon as Polychronis and I manage to cut a release.
 
 As for the 'sugar/telepathy' help: the plan is to fill in the stub
 'telepathy-cerebro' Telepathy ConnectionManager, then to implement a
 cerebro_plugin in the Sugar Presence Service. This will get us a working
 mesh view. Then comes Tubes. :)
 

No, the plan is to implement a Cerebro backend in Salut. I filed #6658
to track this work.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: FWD: Bonjour Problem

2008-03-05 Thread Guillaume Desmottes

That's a know bug (https://dev.laptop.org/ticket/6298) Currently Chat
activity can't talk with the not OLPC world.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: New update.1 build 696

2008-03-05 Thread Guillaume Desmottes

Le mercredi 05 mars 2008 à 09:28 +0200, Morgan Collett a écrit :
 C. Scott Ananian wrote:
  On Tue, Mar 4, 2008 at 10:46 PM, Build Announcer v2 [EMAIL PROTECTED] 
  wrote:
  http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build696
   Changes in build 696 from build: 695
   -sugar-presence-service 0.75.2-1.olpc2
   +sugar-presence-service 0.75.1-1.olpc2
  
  Don't we need the school-server-detection bits in s-p-s 0.75.2? (trac
  #6299).  The suggestion in the trac bug is that we need to include the
  newer Pippy, not revert s-p-s.  Unless the sugar developers plan to
  fix trac #6299 in some other way?
 
 Last I heard this wasn't actually tested yet with a real schoolserver,
 and Daf and Guillaume were going to change the patch in some way, so
 from my perspective it's not ready for Update.1. Dennis said it was only
 tagged into build 695 for the tests last week - so it can still be
 tested as-is with that build.


According to our tests, this patch seems to work pretty well but we are
still a bit unsure about Salut restarting after 2 minutes if Gabble
didn't connect.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: new plugin in the Presence Service

2008-02-27 Thread Guillaume Desmottes

Le mercredi 27 février 2008 à 16:22 -0500, Rene De Santiago a écrit :
 Robert and all,
 
 I would appreciate a clarification in the following issues:
 
 Currently how does the Presence Service and Telepathy-Salut  
 communicate with each other?  Is it through the PS DBus API 
 (http://wiki.laptop.org/go/Presence_Service_DBus_API)? 

No, Telepathy connection managers (as Gabble and Salut) communicates to
the Presence Service using the Telepathy API:
http://telepathy.freedesktop.org/spec.html

My understanding is that this API is the interface between the  
 sugar environment, activities, etc., and Presence Service; is this  
 correct?
 
Yeah, the PS API is between the Presence Service and Sugar/Activities.

 In re-factoring  Salut to use a Cerebro DBus service instead of Avahi,  
 what are the things that we must watch out for in order to avoid  
 breaking PS?

What we need to do is to abstract mDNS/avahi in Salut and then provide
an implementation of it using Cerebro.
The Telepathy API won't change so PS shouldn't have to be modified.

 I hope my questions are clear,
 Rene De Santiago


Hope that helps,


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Preparing the XOs for next week's test

2008-02-25 Thread Guillaume Desmottes

Le samedi 23 février 2008 à 08:13 -0500, Walter Bender a écrit :
 Read sharing is a critical feature. Please do test it.
 

Would be good to consider to include my fix for #6540 then. It's waiting
review and merge from a Read developer.


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: telepathy - request for guidance

2008-02-21 Thread Guillaume Desmottes

Le mercredi 20 février 2008 à 17:09 -0500, Mikus Grinbergs a écrit :
  Could be a loudmouth bug. Could you provide telepathy-gabble log with
  LM_DEBUG=net defined please?
 
 I was already using that definition, and earlier posted the ending 
 part of my telepathy-gabble.log.  Just in case you need it, here is 
 the beginning of that log (constant string deleted from each line):
 


Could be a Gabble or Loudmouth bug. Could you open a ticket on 
http://dev.laptop.org/ , assign it to telepathy-gabble,
explain your problem and attach your log file please?

Thanks,


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: telepathy - request for guidance

2008-02-20 Thread Guillaume Desmottes

Le mercredi 20 février 2008 à 00:37 -0500, Mikus Grinbergs a écrit :
 | ** ERROR **: file lm-connection.c: line 364 
 (_lm_connection_succeeded): asserti
 | on failed: (source != NULL)
 | aborting...
 
 That to me implies I am now getting through my proxy.  The last two 
 (ERROR) lines occur only when I have specified olpc.collabora.co.uk 
 as my jabber server - they don't show in the log when I try a local 
 jabber server.
 

Could be a loudmouth bug. Could you provide telepathy-gabble log with
LM_DEBUG=net defined please?
See http://wiki.laptop.org/go/Telepathy-debug about how define this env
variable.


 p.s.  [Other modules besides server_plugin.py have different 
 _get_account_info() methods -- I gather despite the common name, 
 each method's scope applies only within its containing module.]
 

Yeah only the one in server_plugin.py manage the Gabble connection, so
don't touch the others



G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Connection Managers and Presence Service

2008-02-18 Thread Guillaume Desmottes

Le vendredi 15 février 2008 à 14:35 -0500, Rene De Santiago a écrit :
 I've been looking at how to implement a new communication manager that  
 communicates with the OLPC presence service and I'm still trying to  
 make sense out of parts involved there, like DBus, the presence  
 service and the existing plugins (linklocal_plugin.py and  
 server_plugin.py).

As you said, these 2 plugins are a simple glue between the PS and 2
Telepathy connection manager.
linklocal_plugin is used with telepathy-salut, the XMPP linklocal CM and
server_plugin.py with telepathy-gabble, the XMPP/Jabber CM.


 Can someone provide more insight on the role of the above plugins? It  
 seems that they act as glue between the presence service and the  
 connection managers implemented in C.  The OLPC wiki also provides a  
 list of methods for the Presence Service DBus, what are the plugins  
 that interact between the Connection Managers and the Presence Service  
 to satisfy these methods.  Furthermore, the DBus documentation talks  
 about bindings that can be use to interface with it, are the plugins  
 mentioned above (linklocal_plugin.py and server_plugin.py) these  
 bindings or are they somewhere else?
 
 Also, is there any documentation about the interface between the  
 Connection Managers and the activities?  The OLPC wiki only provides a  
 brief document about the methods.
 
 Any insight would be appreciated.

You can find some documentation on the OLPC wiki:
http://wiki.laptop.org/go/Category:Telepathy

You'll also be interested in the Telepathy D-Bus specification:
http://telepathy.freedesktop.org/spec.html and
http://people.collabora.co.uk/~cassidy/spec-olpc.html for the OLPC
specific interfaces.


What do you want to do exactly?



G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: multilingual googletalk

2008-01-28 Thread Guillaume Desmottes

Le vendredi 25 janvier 2008 à 13:29 -0600, Todd Kelsey a écrit :
 Hi - you may already know about this but evidently as of mid december
 you can now invite chat bots into googletalk, in order to have instant
 messaging conversations with people in different languages. (widget
 version also supports group chat).
 

Don't know how these bots work but the Chat activity is already using
XMPP/Jabber when XO's are connected to Internet. So there is no need to
create yet another chat activity.



G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: New joyride build 1591

2008-01-28 Thread Guillaume Desmottes

Le samedi 26 janvier 2008 à 05:38 +, [EMAIL PROTECTED] a écrit :
 On Fri, 25 Jan 2008, Build Announcer v2 wrote:
 
  http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1591
 
  Changes in build 1591 from build: 1590
 
 this build appears to break WEP (I upgraded from build 689)
 

That's probably this bug: http://dev.laptop.org/ticket/5485


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: WPA not working after upgrade to Joyride 1430.

2007-12-17 Thread Guillaume Desmottes

Le dimanche 16 décembre 2007 à 23:03 -0500, Marcus Leech a écrit :
 I was running Joyride 1407, but upgraded to 1430.  WPA appears to no
 longer function.  I know that WPA broke around 1416, but
   I guess I assumed that it would have been fixed.  But perhaps not?

That's a known bug. See http://dev.laptop.org/ticket/5485


G.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: New ship.2 build 647

2007-11-30 Thread Guillaume Desmottes

Le vendredi 30 novembre 2007 à 04:44 -0500, C. Scott Ananian a écrit :
 We believe this build also fixes our linksys WDS interoperability
 problems, and seems to be able to connect to more access points.
 

Still doesn't work for me: http://dev.laptop.org/ticket/4858#comment:13



G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Journal and Tubes Minutes from 9/18/07

2007-11-17 Thread Guillaume Desmottes

Le mardi 18 septembre 2007 à 21:41 +0200, J.M. Maurer a écrit :
* Bug 2463, when the initiator of a shared activity leaves,
  others can no longer join, even though it looks like they can
  from the neighborhood mesh view. 
* If we had fully understood this bug earlier, it would
  have been good to shut down the activity when the
  initiator left, and then figure out a better solution
  for FRS. The way it works now is just really confusing
  and will cause complaints and support calls. The
  longer term solution needs to allow another laptop to
  advertise the shared activity if the first one leaves.
 
 Ah, so then I can't test this one https://dev.laptop.org/ticket/3445 in
 sugar while implementing support for it in AbiCollab, is that correct?
 Saves me a lot of time knowing that :)
 

Yes and No.
#2463 is only when using Salut (link-local), there is no problem with
Gabble as there is a server where the muc is stored.


G.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel