[Sugar-devel] [SoaS] Etoys in RC4 SoaS-v7 does not start when jabber is connected. ( f17 release is imminent )

[Peter Robinson]

On Mon, May 28, 2012 at 5:49 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>
> On 28.05.2012, at 18:19, Peter Robinson wrote:
>
>> On Mon, May 28, 2012 at 5:05 PM, Walter Bender <walter.bender at gmail.com> wrote:
>>> On Mon, May 28, 2012 at 10:57 AM, Peter Robinson <pbrobinson at gmail.com> wrote:
>>>> On Mon, May 28, 2012 at 3:30 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>>>>>
>>>>> On 28.05.2012, at 15:52, Peter Robinson wrote:
>>>>>
>>>>>> On Mon, May 28, 2012 at 2:50 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>>>>>>> SoaS still has the old Etoys version (4.1). Etoys 5 was released along with Sugar 0.96. It is more robust wrt presence service failures.
>>>>>>
>>>>>> it also still needs the sugar-presence-service package which has been obsolete for a long
>>>>>> time.
>>>>>
>>>>>
>>>>> Etoys 5 is no worse than previous versions in that respect. On the contrary, it deals better with presence service deterioration.
>>>>>
>>>>> Re-implementing the presence service takes time, I'm on my own, can't make it happen soon.
>>>>
>>>> I think it's been over 2 years, I might just drop eToys from the build
>>>> because it always causes random issues.
>>>
>>> Peter,
>>>
>>> I urge you to not drop Etoys. It is one of the most powerful learning
>>> tools we offer. Sugar is greatly diminished without it. Are there open
>>> tickets on these random issues?
>>
>> Well it would be nice if the developers actively participated and
>> tested in the process. We've had these issues on going for as long as
>> I can remember and they never get the attention that they need for
>> "one of the most powerful learning tools we offer" and mostly just
>> causes me pain.
>>
>> It's not too late to fix for the core SoaS v7 release so it gives
>> people 6 months to actively improve the situation for the next
>> release.
>>
>> Peter
>
>
> I, too, hope you threaten to drop Etoys just to illustrate your frustration.
>
> What else can we do besides fixing issues and hoping you package the result? That's our take on trying to "actively improve the situation".
>
> Again, Etoys 5 starts fine, Etoys 4.1 not. But we cannot really test distro stuff if it has not been packaged yet.

The last release I remember seeing was an RC (don't remember if it was
RC1 or 2) and I had issues and never got back to it and if I must have
missed the final release. Ultimately it would be nice if the
developers of their Activities checked and tested and emailed the SoaS
list if they have issues or the new versions have been missed. We have
nightly builds right through the dev process and various
Alpha/Beta/RCs etc in the lead up to final for testing. I can't test
everything and I'm not fallible and the process we use has clearly
defined [1] development schedule to know when fixes need to be in by.

> Regarding the locale directory layout: I did not find a ticket in any of the trackers, neither upstream nor at sugarlabs or olpc. What would make the packaging easier for you?

To use the same layout that is used by everything else so we can use
the standard distro tools to deal with them. Probably the best package
to look at is TurtleArt.

Peter

[1] https://fedoraproject.org/wiki/Releases/17/Schedule