On Sat, Jun 15, 2013 at 6:42 PM, Daniel Narvaez wrote:
> Cool. I'd say it's in then... Added a feature page
>
> https://github.com/sugarlabs/roadmap/issues/9
Thanks for being open to this. The implementation is ready for review.
https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/11
https://git
Cool. I'd say it's in then... Added a feature page
https://github.com/sugarlabs/roadmap/issues/9
On 13 June 2013 01:42, Manuel Quiñones wrote:
> 2013/6/12 Daniel Narvaez :
> > On 12 June 2013 22:19, Daniel Drake wrote:
> >>
> >> On Wed, Jun 12, 2013 at 2:10 PM, Daniel Narvaez
> >> wrote:
> >
On Thursday, 13 June 2013, Ajay Garg wrote:
> Daniel,
>
> what you say makes sense for small-but-critical patches (like it happens
> in the linux-kernel world, where there is rarely a patch more than 10 lines
> long. Moreover, the linux-kernel code is cleanly segregated into different
> modules, s
Daniel,
what you say makes sense for small-but-critical patches (like it happens in
the linux-kernel world, where there is rarely a patch more than 10 lines
long. Moreover, the linux-kernel code is cleanly segregated into different
modules, so there are rarely clashes in people's work, as far as t
On 13 June 2013 11:33, Jerry Vonau wrote:
> cc'ing Ajay
>
> On 13 June 2013 00:56, James Cameron wrote:
>
>> On Thu, Jun 13, 2013 at 01:54:24AM -0300, Gonzalo Odiard wrote:
>> > Yes, but somebody should provide patches, and do any change needed
>> > when the maintainers do the review, to be sure
On 13 June 2013 07:56, James Cameron wrote:
> On Thu, Jun 13, 2013 at 01:54:24AM -0300, Gonzalo Odiard wrote:
> > Yes, but somebody should provide patches, and do any change needed
> > when the maintainers do the review, to be sure we have the quality
> > needed upstream.
>
> Maintainers could do
cc'ing Ajay
On 13 June 2013 00:56, James Cameron wrote:
> On Thu, Jun 13, 2013 at 01:54:24AM -0300, Gonzalo Odiard wrote:
> > Yes, but somebody should provide patches, and do any change needed
> > when the maintainers do the review, to be sure we have the quality
> > needed upstream.
>
> Maintai
On Thu, Jun 13, 2013 at 01:54:24AM -0300, Gonzalo Odiard wrote:
> Yes, but somebody should provide patches, and do any change needed
> when the maintainers do the review, to be sure we have the quality
> needed upstream.
Maintainers could do this themselves if they wanted to.
I'd caution against
> FWIW, 3g modem[1], and 3g sharing[2] both work in Dextrose4, perhaps you
> could look to see how AC implemented their version.
>
> 1. http://wiki.sugarlabs.org/go/Features/3G_Support
> 2. http://wiki.sugarlabs.org/go/Features/3G_Support/Share
>
> Jerry
>
Yes, but somebody should provide patches
On 12 June 2013 15:10, Daniel Narvaez wrote:
> Hi,
>
> we are going to code freeze on Sep 4, and that's when it would also
> probably make sense to branch master. Which is a bit later than you would
> like to land it.
>
> Though I wonder if we should consider this feature for 0.100 since
>
> * T
2013/6/12 Daniel Narvaez :
> On 12 June 2013 22:19, Daniel Drake wrote:
>>
>> On Wed, Jun 12, 2013 at 2:10 PM, Daniel Narvaez
>> wrote:
>> > Hi,
>> >
>> > we are going to code freeze on Sep 4, and that's when it would also
>> > probably
>> > make sense to branch master. Which is a bit later than
On 12 June 2013 22:19, Daniel Drake wrote:
> On Wed, Jun 12, 2013 at 2:10 PM, Daniel Narvaez
> wrote:
> > Hi,
> >
> > we are going to code freeze on Sep 4, and that's when it would also
> probably
> > make sense to branch master. Which is a bit later than you would like to
> > land it.
> > Thou
On Wed, Jun 12, 2013 at 2:10 PM, Daniel Narvaez wrote:
> Hi,
>
> we are going to code freeze on Sep 4, and that's when it would also probably
> make sense to branch master. Which is a bit later than you would like to
> land it.
> Though I wonder if we should consider this feature for 0.100 since
Hi,
we are going to code freeze on Sep 4, and that's when it would also
probably make sense to branch master. Which is a bit later than you would
like to land it.
Though I wonder if we should consider this feature for 0.100 since
* There is still a considerable amount of time left. Freeze dates
Tue, 11 Jun 2013 16:42:11 -0600
> From: Daniel Drake
> To: Sugar Devel
> Subject: [Sugar-devel] [FEATURE] Automatic activity updates
> Message-ID:
> py8p...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> Over the last few month
+1
Very nice idea and very good analysis of drawbacks of the old updates
process.
Lionel.
--
Message: 3
Date: Tue, 11 Jun 2013 16:42:11 -0600
From: Daniel Drake
To: Sugar Devel
Subject: [Sugar-devel] [FEATURE] Automatic activity updates
Message-ID
+1 providing the back-end supports proxies. I recall the native updater
in sugar didn't in the past, haven't tested lately.
Jerry
On Tue, 2013-06-11 at 16:42 -0600, Daniel Drake wrote:
> Hi,
>
> Over the last few months I have been slowly developing a much needed
> field feature, the final piec
+1 to the idea :)
2013/6/11 Daniel Drake
> Hi,
>
> Over the last few months I have been slowly developing a much needed
> field feature, the final piece in the "automatic system upgrade"
> puzzle. Now I am getting close, I would like to open the
> formalities...
>
> http://wiki.sugarlabs.org/go
Hi,
Over the last few months I have been slowly developing a much needed
field feature, the final piece in the "automatic system upgrade"
puzzle. Now I am getting close, I would like to open the
formalities...
http://wiki.sugarlabs.org/go/Features/Automatic_activity_updates
At this point I've it
19 matches
Mail list logo
