Hi,
On Thu, May 17, 2018 at 3:11 AM, James Cameron wrote:
> As you may have seen in my post in the last hour, forks of software
> dilute maintainership, and everyone is worse off.
> As part of porting to Python 3, we need to port to TelepathyGLib as
> well. This is because
At the cited meeting, I was prepared to update the status of activities
on ASLO and github. However, there was
no interest.
A quick summary: There are 514 activities divided into three groups:
83 which have the current version from github installed on aslo
Thanks for working on this.
As you may have seen in my post in the last hour, forks of software
dilute maintainership, and everyone is worse off.
As part of porting to Python 3, we need to port to TelepathyGLib as
well. This is because there is no maintained static binding of
Telepathy for
On Wed, May 16, 2018 at 5:09 PM James Cameron wrote:
> On Wed, May 16, 2018 at 10:27:59PM +0200, Lionel Laské wrote:
> > Hi all,
> >
> > I've read on a recent sugar-meeting questions regarding Sugarizer
> > packaging.
> > Because I've just released version 1.0,
>
> Thanks for
On Wed, May 16, 2018 at 10:27:59PM +0200, Lionel Laské wrote:
> Hi all,
>
> I've read on a recent sugar-meeting questions regarding Sugarizer
> packaging.
> Because I've just released version 1.0,
Thanks for the reminder; I've rebased the Sugar Labs clone of your
Sugarizer repository.
> I think
Hi all,
I've read on a recent sugar-meeting [1] questions regarding Sugarizer
packaging.
Because I've just released version 1.0, I think it's the right time to
build a Sugarizer FAQ.
I'm answering below on questions asked during this meeting but I will be
please to add to this future FAQ all
Hi,
I started understanding how Telepathy and DBus work, and porting our code
to use their PyGI bindings instead of static bindings, and it looks like a
big task.
Also, GitHub search gives 72 results
https://github.com/search?p=5=org%3Asugarlabs+%22from+telepathy%22=Code=%E2%9C%93
for instances
7 matches
Mail list logo