Hello Daniel,
So Improving the unit tests before the actual porting is a must, duely
noted.
If only =3.3 is supported, all the activities HAVE to be ported to =3.3
as well.
Don't you think supporting 2.7+ for a while will enable a smoother
transition?
I also looked at the dependencies, telepathy
On Mar 9, 2014 7:23 PM, Ravi Kumar upma...@gmail.com wrote:
Hello Daniel,
So Improving the unit tests before the actual porting is a must, duely
noted.
If only =3.3 is supported, all the activities HAVE to be ported to =3.3
as well.
Don't you think supporting 2.7+ for a while will enable a
this release marks our feature freeze for 0.102. Now let's focus on bug
fixing!
It would be useful to see release notes for each release so as to know
what's changed, added and needs to be tested rather than a tarball
list dumped to the list.
Sources:
On 9 March 2014 11:02, Peter Robinson pbrobin...@gmail.com wrote:
this release marks our feature freeze for 0.102. Now let's focus on bug
fixing!
It would be useful to see release notes for each release so as to know
what's changed, added and needs to be tested rather than a tarball
list
On 9 March 2014 09:23, Ravi Kumar upma...@gmail.com wrote:
Hello Daniel,
So Improving the unit tests before the actual porting is a must, duely
noted.
If only =3.3 is supported, all the activities HAVE to be ported to =3.3
as well.
Don't you think supporting 2.7+ for a while will enable a
If I remember correctly Emil also agreed that the new framework should be
independent from telepathy at some point and even worked on it.
On 9 March 2014 06:45, Prasoon Shukla prasoon92.i...@gmail.com wrote:
Hi Sam. Sorry for the late response but I was occupied with academics.
Anyway, I
On 9 March 2014 04:07, Sebastian Silva sebast...@fuentelibre.org wrote:
Hello,
My machine is somewhat constrained in ram and diskspace so running Fedora
on a chroot was slow enough
that I decided to set *use_broot:false* on *prefs.json* with the
intention of running the latest sugar
We could port telepathy-python, it's a fairly small codebase.
I don't think it will be ported, the latest commit is four years old!
https://github.com/PabloCastellano/telepathy-python/tree/examples/src
But I didn't quite understand what exactly telepathy does.
So could you point me to some
Hi,
It sounds like the school server should be the node server.
Does this proposed implementation support python sugar activities?
Tony
On 03/09/2014 07:32 AM, sugar-devel-requ...@lists.sugarlabs.org wrote:
Message: 4
Date: Sun, 9 Mar 2014 12:12:56 +0100
From: Daniel
On 9 March 2014 12:50, Ravi Kumar upma...@gmail.com wrote:
We could port telepathy-python, it's a fairly small codebase.
I don't think it will be ported, the latest commit is four years old!
https://github.com/PabloCastellano/telepathy-python/tree/examples/src
It sounds like telepathy-python
In theory, yes. We could add support for the web socket based framework to
the python toolkit.
On 9 March 2014 13:33, Tony Anderson tony_ander...@usa.net wrote:
Hi,
It sounds like the school server should be the node server.
Does this proposed implementation support python sugar
/sugar-devel/attachments/20140309/2ac4/attachment.html
--
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
End of Sugar-devel Digest, Vol 65, Issue 32
If I remember correctly Emil also agreed that the new framework should be
independent from telepathy
It seems there were two separate threads of the same name:
1 - http://lists.sugarlabs.org/archive/sugar-devel/2014-January/046687.html
2 -
On 9 March 2014 17:53, Sebastian Silva sebast...@fuentelibre.org wrote:
Hi dear Sugar developers.
We have participated in the deployment in Peru of Sugar 0.94 (classic) for
XO1 and XO1.5. It will be ongoing in 2014 and hopefully we will tighten the
feedback circle and work closer with
Something I forgot to mention is that when testing activity startup you
really need to clean the kernel memory cache before each run, or you will
get inconsistent data.
sudo sh -c echo 3 /proc/sys/vm/drop_caches
On 9 March 2014 18:46, Daniel Narvaez dwnarv...@gmail.com wrote:
On 9 March 2014
this release marks our feature freeze for 0.102. Now let's focus on bug
fixing!
It would be useful to see release notes for each release so as to know
what's changed, added and needs to be tested rather than a tarball
list dumped to the list.
I agree, but at the moment I have no time to
The commit messages for our changes to Sugar core tend to be pretty
decent. If we grab those and put them into a wiki page, then we could
manually edit them into something more friendly to read once per
release cycle. I volunteer to do the editing.
Catching changes to the core activities is a bit
Just as a rough sketch of what pulling the commit messages would look
like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes
-walter
On Sun, Mar 9, 2014 at 4:37 PM, Walter Bender walter.ben...@gmail.com wrote:
The commit messages for our changes to Sugar core tend to be pretty
decent. If
Thanks Sebastian, will include it in the next version.
Gonzalo
On Sun, Mar 9, 2014 at 1:18 AM, Sebastian Silva
sebast...@fuentelibre.orgwrote:
Hi Gonzalo,
Thank you for breathing new life into Develop activity.
In order to try it out in sugar-build I did this little patch. Maybe it
can be
Then issues ocurred with gwebsockets. It persistently tried to use
python3.3, my system's default, instead of python2.7. Finally I found the
culprit, in
./out/sandbox/install/lib/python2.7/site-packages/osbuild/build.py I
replaced in line 190 one instance of python for python2.7 and it
On 9 March 2014 20:33, Peter Robinson pbrobin...@gmail.com wrote:
this release marks our feature freeze for 0.102. Now let's focus on
bug
fixing!
It would be useful to see release notes for each release so as to know
what's changed, added and needs to be tested rather than a tarball
On 9 March 2014 21:37, Walter Bender walter.ben...@gmail.com wrote:
The commit messages for our changes to Sugar core tend to be pretty
decent. If we grab those and put them into a wiki page, then we could
manually edit them into something more friendly to read once per
release cycle. I
On 10 March 2014 00:07, Gonzalo Odiard godi...@sugarlabs.org wrote:
Then issues ocurred with gwebsockets. It persistently tried to use
python3.3, my system's default, instead of python2.7. Finally I found the
culprit, in
./out/sandbox/install/lib/python2.7/site-packages/osbuild/build.py I
In the end, we need a summary to the end public, we can prepare it like in
the past,
based in the commit messages.
Gonzalo
On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
On 9 March 2014 22:31, Gaurav Parida gparid...@gmail.com wrote:
Keeping the commit messages,
I see.. :/
Gonzalo
On Sun, Mar 9, 2014 at 8:54 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
On 10 March 2014 00:46, Daniel Narvaez dwnarv...@gmail.com wrote:
On 10 March 2014 00:07, Gonzalo Odiard godi...@sugarlabs.org wrote:
Then issues ocurred with gwebsockets. It persistently tried
The thing is, I don't have time to do that manually for each unstable
release. We either need a volunteer to do it or a way to generate it
automatically from the log (which was the goal of my suggestion).
On 10 March 2014 00:56, Gonzalo Odiard godi...@sugarlabs.org wrote:
In the end, we need a
I am not thinking in doing it for every unstable release, just for 0.102.
I already did it for 0.100, I can volunteer to do it again in 0.102
Gonzalo
On Sun, Mar 9, 2014 at 8:58 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
The thing is, I don't have time to do that manually for each unstable
The discussion started because Peter would like to have release notes for
unstable releases. (Though he might be content with those being just the
git logs).
On 10 March 2014 01:01, Gonzalo Odiard godi...@sugarlabs.org wrote:
I am not thinking in doing it for every unstable release, just for
It didn't take me too long to pull together
http://wiki.sugarlabs.org/go/0.102/Notes and I am happy to do the same
again for the other unstable releases. We need to do some more work
for the stable release as per Gonzalo's comments.
-walter
On Sun, Mar 9, 2014 at 8:04 PM, Daniel Narvaez
Great! So I'll let you know when 0.101.4 is tagged.
On 10 March 2014 01:10, Walter Bender walter.ben...@gmail.com wrote:
It didn't take me too long to pull together
http://wiki.sugarlabs.org/go/0.102/Notes and I am happy to do the same
again for the other unstable releases. We need to do
All Arch Linux users I met usually solve this problem when developing
by using virtualenv.
2014-03-09 20:54 GMT-03:00 Daniel Narvaez dwnarv...@gmail.com:
On 10 March 2014 00:46, Daniel Narvaez dwnarv...@gmail.com wrote:
On 10 March 2014 00:07, Gonzalo Odiard godi...@sugarlabs.org wrote:
We just finished the review of the design issues the last week,
and we agreed in the general points.
I think we should make a effort to finalize the features already discussed,
and not include anything more.
Maybe we can discuss postpone feature freeze by one or two weeks more,
but of course this
@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Daniel Narvaez
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140309/2ac4/attachment.html
Oh interesting! osbuild is actually using a virtualenv. I suspect it
doesn't work because we are not activating it but just running the python
executable in the virtualenv. So osbuild is using the virtualenv python,
but the child processes are not. Now if I could remember why we are not
activating
Feel free to propose delaying feature freeze. The release was already a
week late, if we want more time to work on features, I tend to think the
final release should be pushed off accordingly too.
On 10 March 2014 01:21, Gonzalo Odiard godi...@sugarlabs.org wrote:
We just finished the review
For what it's worth it would be a -1 from me. I would be fine to delay a
bit to fix important bugs, but not to add more features, it seems to go
completely against the rationale of time based releases. But that's just my
opinion.
On 10 March 2014 01:34, Daniel Narvaez dwnarv...@gmail.com wrote:
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Daniel Narvaez
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140309/2ac4
On Sun, Mar 9, 2014 at 9:40 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
For what it's worth it would be a -1 from me. I would be fine to delay a
bit to fix important bugs, but not to add more features, it seems to go
completely against the rationale of time based releases. But that's just my
On 10 March 2014 01:48, Gonzalo Odiard godi...@sugarlabs.org wrote:
On Sun, Mar 9, 2014 at 9:40 PM, Daniel Narvaez dwnarv...@gmail.comwrote:
For what it's worth it would be a -1 from me. I would be fine to delay a
bit to fix important bugs, but not to add more features, it seems to go
El 09/03/14 06:32, Daniel Narvaez escribió:
Also, when building sugar, I had to manually create the directory
./out/install/etc/gconf/ or it would fail to install
Can I see the output? It seems like something we should fix.
Sure, I reproduced it easy enough. Thanks for the feedback.
El 09/03/14 06:32, Daniel Narvaez escribió:
Finally when building sugar-base I had to set up the environment
variable PYTHON=/usr/bin/python2.7 in order for it to build.
In sugar-toolkit-gtk3 we have
PYTHON=python2
AM_PATH_PYTHON
I don't remember why python2 instead of python2.7
El 09/03/14 06:32, Daniel Narvaez escribió:
It's unsupported because it's unlikely to work out-of-the-box. But if
anyone wants to try it on the latest version of a distro and do the
kind of analysis you have been doing, then it's very useful feedback,
because it's likely to find bugs, as we
42 matches
Mail list logo
