[IAEP] ASLO

[Dave Crossland]

On 14 July 2016 at 07:13, Sam Parkinson <sam.parkinson3 at gmail.com> wrote:

> What do you mean?  ASLO is based on very old technology, which is going to
> get broken.
>
> 10/10 would love to improve ASLO.  I actually did an "ASLO2" effort a
> while ago, although that failed for reasons that are documented on my
> blog.  I would be up for using a AppStream and PackageKit based stack to
> reinvent the activity store experience though.
>

I think if ASLO can't be resuscitated, something VERY simple - a set of XO
files and a Jekyll-like simple HTML site that links to them - would best
replace it.


> Re Sugar using python2; a port to python3 was previously investigated as
> part of last years GSoC.  We can port it baring our telepathy-python
> dependency.  (FYI there has not been a commit for telepathy salut or gabble
> in the past 2 years.  Dead upstream?  Still, there are so many bugs that
> affect sugar.  10/10 would love to port collab to using something like
> Matrix.Org - the spec is *way* is more easy to understand than telepathy.
> Telepathy seems much more complex than Sugar needs - we don't need abstract
> multi-backend support.
>

I think we should not upgrade to python3 but javascript.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/iaep/attachments/20160714/a6b5915f/attachment.html>