<div class="gmail_quote">On Wed, Oct 29, 2008 at 9:20 AM, Tomeu Vizoso <<a href="mailto:tomeu@tomeuvizoso.net">tomeu@tomeuvizoso.net</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Wed, Oct 29, 2008 at 2:52 PM, Benjamin M. Schwartz <<a href="mailto:bmschwar@fas.harvard.edu">bmschwar@fas.harvard.edu</a>> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Tomeu Vizoso wrote: >> I have stopped work on the DS and Journal because OLPC is apparently >> funding the development of a replacement for them > > Really? Well, it's at least apparent because both Scott and Erik have mentioned in public that they are working on their own replacements. OLPC management hasn't told me to stop working on the journal, but I don't see how I could keep working on it without risking to lose even more of my time. I asked Scott if he could say by Nov 17 if he thought that he would be able to ship his journal in 0.84 and he seemed to agree. I didn't got a single comment from OLPC engineers when I asked them about my DS replacement, so I guess it wasn't considered a worth possibility by them. >> We could easily hack the DS in 0.83 to return D-Bus strings for >> standard properties that are known (or rather, expected) to contain >> textual data, but introducing this inconsistency in the API may not be >> such a good idea. > > OK. What happens to Journal entries with non-Ascii titles? D-Bus strings are UTF-8 encoded, so that wouldn't be a problem. Regards, </blockquote></div>Ben, Would you be willing to continue your work on the data store in closer collaboration with Sugar Labs? A few day ago there was a emotional appeal from OLPC about how to 'build trust with the community.'  It would seem to me that communicating clearly with outside developers would be the first step in building  trust. thanks david