Re: [Sugar-devel] [ASLO] Log activity

2012-04-09 Thread Gonzalo Odiard 
I have updated the info in the ASLO page.

Gonzalo

On Mon, Apr 9, 2012 at 8:36 PM, James Cameron  wrote:

> On Mon, Apr 09, 2012 at 04:23:55PM -0700, Thomas C Gilliard wrote:
> > Only 0.82 compatible log activity:
> >
> > http://wiki.laptop.org/go/Log
> > (Not on ASLO)
> >
> > log-7.xo  (G1G1)
>
> I disagree.  The OLPC OS release 8.2.0 which bundled Sugar 0.82.1 lists
> log-16 as the base version.
>
> http://wiki.laptop.org/go/Activities/G1G1/8.2
> http://dev.laptop.org/~erikos/bundles/0.82.1/Log-16.xo
>
> > "The releases with which this version of the activity has been tested.
> 8.2.0
> > (767) "
> > http://activities.sugarlabs.org/en-US/sugar/addons/versions/4056 only
> goes to
> > 0.84
>
> I agree.
>
> Won't fix.  To use Log with Sugar 0.82, please use Log-16.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Clock #3394

2012-04-09 Thread Gary Martin 
Hi Manuel,

On 9 Apr 2012, at 19:10, Manuel Quiñones wrote:

> El día 9 de abril de 2012 13:59, Gary Martin
>  escribió:
>> Hi Manuel,
>> 
>> On 9 Apr 2012, at 17:25, Manuel Quiñones wrote:
>> 
>>> Hi Gary,
>>> 
>>> have you found time to take a look at this issue? "Clock activity
>>> draws off the screen".  Rafael and I have some patches pending.
>> 
>> When I last tested your patch I found it just drew a blank grey canvas on 
>> 11.3.1 and past releases of Sugar. I am not yet ready to start forking the 
>> activities I maintain for the GKT3 move (as I'm still not too happy with the 
>> use of dotted version numbers if I can avoid them – seriously thinking of 
>> ignoring dotted releases for now and just int +10 when I fork).
> 
> Oh, good to know.  So I will test the patch in 11.3.1 and see what's
> happening.  Thanks!

Fab. When I tested, I assumed the patch caused the whole clock to be being 
drawn off screen for 11.3.1 and previous.

> This is not for the GTK3 move, the issue appeared in olpc's builds for
> 12.1.0, in current Clock code.
> 
>> I also don't have no tickets on http://bugs.sugarlabs.org/ticket/3394 for a 
>> patches or two you emailed to the list (your patch for Cairo was at least 
>> one of them, might be one other). I know the core team use the patchwork 
>> website and email for landing things in sugar shell, but it seems pretty 
>> useless for activity developers to find/review patches. Any chance you could 
>> open some bugs.sl.org tickets for the patches you'd still like to see land?
> 
> Right, I will open tickets for the Cairo port and the dragging hands
> feature.  However, I would like to see the fix for #3394 landed first,
> as it is a regression, I'm giving more priority to that.

+1 I like the dragging hands feature but would like to raise several issues:

1) on an XO 1.75 it runs like a sloth (>5sec per UI frame update!), but that 
might be the patch for Cairo and poor gfx acceleration in the current XO-1.75 
dev release.

2) Would love to see some visual clock face change when activating the feature, 
ideally large round circle buttons at the end of each clock hand for easy and 
obvious dragging (also provides us a large hit target for touch screen devices).

3) Did we get any pedagogical feedback regarding the hands rotating in lock 
step with time (aka drag the hour hand and see the min and sec hands whiz 
around), vs. allowing each hand to be set arbitrarily? 

> And I don't
> mind to hold the Cairo port until I fix the text sizes.  Will open
> tickets to track them.

Fab thanks!

> 
>>> Or may I request co-maintainership?
>> 
>> Sure, however I'd rather get the above items sorted before you start to land 
>> patches and make releases, or I'm more likely to just hand it over and stop 
>> work on it myself ;)
> 
> OK, we have to be careful while co-maintaining, pair reviewing or at
> least testing so we don't loose code quality, maybe Rafael can help me
> with Clock.

OK full privileges:

  http://git.sugarlabs.org/clock/mainline/committerships

Regards,
--G

> Thank you very much,
> 
>> Regards,
>> --Gary
>> 
>>> Greetings,
>>> 
>>> --
>>> .. manuq ..
>> 
> 
> 
> 
> -- 
> .. manuq ..

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [ASLO] SugarGame problem

2012-04-09 Thread Rafael Ortiz 
On Mon, Apr 9, 2012 at 4:41 PM, Alan Jhonn Aguiar Schwyn <
alan...@hotmail.com> wrote:

>
> Hi,
>
> I try to change the OlpcGames for SugarGame in some activities..
>
> The problem is with this:
>
> Traceback (most recent call last):
>   File "/home/alan/Activities/ConozcoAmerica.activity/sugargame/event.py",
> line 209, in _mousemove_cb
> self._post(evt)
>   File
> "/home/alan/Activities/ConozcoAymerica.activity/sugargame/event.py", line
> 243, in _post
> raise e
> pygame.error: video system not initialized
>
> What is the cause of this error?
>
> Regards!
>
>


> Alan
>
> Why you want to change olpcgames for sugargames ?


Cheers-

> ___
> ASLO mailing list
> a...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/aslo
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] [ASLO] Release Pilas-1

2012-04-09 Thread Sugar Labs Activities 
Activity Homepage:
http://activities.sugarlabs.org/addon/4484

Sugar Platform:
0.90 - 0.94

Download Now:
http://activities.sugarlabs.org/downloads/file/27588/pilas-1.xo

Release notes:
First release!  Made during SugarCamp Junín 2011, Argentina.

Pilas is an engine for making videogames in an easy way.

It's oriented to people that are learning to code videogames and that want to 
achive interesting and fun result very quickly.

For more information about Pilas: http://www.pilas-engine.com.ar/



Sugar Labs Activities
http://activities.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [ASLO] Log activity

2012-04-09 Thread James Cameron 
On Mon, Apr 09, 2012 at 04:23:55PM -0700, Thomas C Gilliard wrote:
> Only 0.82 compatible log activity:
> 
> http://wiki.laptop.org/go/Log
> (Not on ASLO)
> 
> log-7.xo  (G1G1)

I disagree.  The OLPC OS release 8.2.0 which bundled Sugar 0.82.1 lists
log-16 as the base version.

http://wiki.laptop.org/go/Activities/G1G1/8.2
http://dev.laptop.org/~erikos/bundles/0.82.1/Log-16.xo

> "The releases with which this version of the activity has been tested. 8.2.0
> (767) "
> http://activities.sugarlabs.org/en-US/sugar/addons/versions/4056 only goes to
> 0.84

I agree.

Won't fix.  To use Log with Sugar 0.82, please use Log-16.

-- 
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [ASLO] Log activity

2012-04-09 Thread Thomas C Gilliard 

Only 0.82 compatible log activity:

http://wiki.laptop.org/go/Log
(Not on ASLO)

log-7.xo  (G1G1)

"Okay, Log-7 bundle has been posted. wade 
 16:56, 21 May 2008 (EDT) "


"The releases with which this version of the activity has been tested. 
8.2.0 (767) "
http://activities.sugarlabs.org/en-US/sugar/addons/versions/4056 only 
goes to 0.84


On 04/09/2012 03:31 PM, Alan Jhonn Aguiar Schwyn wrote:


Hi,

The Log activity not works in Sugar 0.82.

Can update the page?

http://activities.sugarlabs.org/en-US/sugar/addon/4056

Regards!

Alan

PD: you will change it or fill a ticket?


___
ASLO mailing list
a...@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/aslo
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Log activity

2012-04-09 Thread Alan Jhonn Aguiar Schwyn 


Yes... A problem of libraries:
ImportError   Traceback (most recent call last)
/usr/bin/sugar-activity in () 19 from sugar.activity import main
 20 ---> 21 main.main()global main.main =   
   22  23 
/usr/lib/python2.5/site-packages/sugar/activity/main.py in main()101 
class_name = splitted_module[1]102 --> 103 module = 
__import__(module_name)module = undefinedglobal 
__import__ = undefinedmodule_name = 'logviewer'104 for comp in 
module_name.split('.')[1:]:105 module = getattr(module, comp)
/home/olpc/Activities/Log.activity/logviewer.py in () 26 import 
pango 27 import gobject---> 28 import gioglobal gio = undefined 
29  30 from sugar.activity import activity
ImportError: No module named gio



> Date: Tue, 10 Apr 2012 08:42:50 +1000
> From: qu...@laptop.org
> To: sugar-devel@lists.sugarlabs.org
> Subject: Re: [Sugar-devel] Log activity
> 
> I have contributed to Log in the past.
> 
> I would prefer to find out what the problem is and fix it so that it
> remains compatible with 0.82.
> 
> Can you describe the nature of the failure?
> 
> -- 
> James Cameron
> http://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
  ___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Log activity

2012-04-09 Thread James Cameron 
I have contributed to Log in the past.

I would prefer to find out what the problem is and fix it so that it
remains compatible with 0.82.

Can you describe the nature of the failure?

-- 
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Log activity

2012-04-09 Thread Alan Jhonn Aguiar Schwyn 


Hi,
The Log activity not works in Sugar 0.82.
Can update the page?
http://activities.sugarlabs.org/en-US/sugar/addon/4056
Regards!
Alan
PD: you will change it or fill a ticket?
  ___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] SugarGame problem

2012-04-09 Thread Alan Jhonn Aguiar Schwyn 


Hi,
I try to change the OlpcGames for SugarGame in some activities..
The problem is with this:
Traceback (most recent call last):  File 
"/home/alan/Activities/ConozcoAmerica.activity/sugargame/event.py", line 209, 
in _mousemove_cbself._post(evt)  File 
"/home/alan/Activities/ConozcoAmerica.activity/sugargame/event.py", line 243, 
in _postraise epygame.error: video system not initialized
What is the cause of this error?
Regards!
Alan  ___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Clock #3394

2012-04-09 Thread Rafael Ortiz 
2012/4/9 Manuel Quiñones 

> El día 9 de abril de 2012 13:59, Gary Martin
>  escribió:
> > Hi Manuel,
> >
> > On 9 Apr 2012, at 17:25, Manuel Quiñones wrote:
> >
> >> Hi Gary,
> >>
> >> have you found time to take a look at this issue? "Clock activity
> >> draws off the screen".  Rafael and I have some patches pending.
> >
> > When I last tested your patch I found it just drew a blank grey canvas
> on 11.3.1 and past releases of Sugar. I am not yet ready to start forking
> the activities I maintain for the GKT3 move (as I'm still not too happy
> with the use of dotted version numbers if I can avoid them – seriously
> thinking of ignoring dotted releases for now and just int +10 when I fork).
>
> Oh, good to know.  So I will test the patch in 11.3.1 and see what's
> happening.  Thanks!
>
> This is not for the GTK3 move, the issue appeared in olpc's builds for
> 12.1.0, in current Clock code.
>
> > I also don't have no tickets on http://bugs.sugarlabs.org/ticket/3394for a 
> > patches or two you emailed to the list (your patch for Cairo was at
> least one of them, might be one other). I know the core team use the
> patchwork website and email for landing things in sugar shell, but it seems
> pretty useless for activity developers to find/review patches. Any chance
> you could open some bugs.sl.org tickets for the patches you'd still like
> to see land?
>
> Right, I will open tickets for the Cairo port and the dragging hands
> feature.  However, I would like to see the fix for #3394 landed first,
> as it is a regression, I'm giving more priority to that.  And I don't
> mind to hold the Cairo port until I fix the text sizes.  Will open
> tickets to track them.
>
> >> Or may I request co-maintainership?
> >
> > Sure, however I'd rather get the above items sorted before you start to
> land patches and make releases, or I'm more likely to just hand it over and
> stop work on it myself ;)
>
> OK, we have to be careful while co-maintaining, pair reviewing or at
> least testing so we don't loose code quality, maybe Rafael can help me
> with Clock.
>
> +1.


> Thank you very much,
>
> > Regards,
> > --Gary
> >
> >> Greetings,
> >>
> >> --
> >> .. manuq ..
> >
>
>
>
> --
> .. manuq ..
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Activity Team] Wiki guidance for adopting orphaned Activities / Activity co-maintainer

2012-04-09 Thread Manuel Quiñones 
El día 9 de abril de 2012 13:41, Gonzalo Odiard  escribió:
> Ok. We need try encourage co-maintainership,
> and see case by case.

As I said in the Clock thread, we have to be careful while
co-maintaining, hold the patch until someone ACKs or at least tests
it, so we keep improving.  I mean, don't make this a shortcut for
getting code landed, don't skip reviewing phase.

Cheers,

-- 
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Clock #3394

2012-04-09 Thread Manuel Quiñones 
El día 9 de abril de 2012 13:59, Gary Martin
 escribió:
> Hi Manuel,
>
> On 9 Apr 2012, at 17:25, Manuel Quiñones wrote:
>
>> Hi Gary,
>>
>> have you found time to take a look at this issue? "Clock activity
>> draws off the screen".  Rafael and I have some patches pending.
>
> When I last tested your patch I found it just drew a blank grey canvas on 
> 11.3.1 and past releases of Sugar. I am not yet ready to start forking the 
> activities I maintain for the GKT3 move (as I'm still not too happy with the 
> use of dotted version numbers if I can avoid them – seriously thinking of 
> ignoring dotted releases for now and just int +10 when I fork).

Oh, good to know.  So I will test the patch in 11.3.1 and see what's
happening.  Thanks!

This is not for the GTK3 move, the issue appeared in olpc's builds for
12.1.0, in current Clock code.

> I also don't have no tickets on http://bugs.sugarlabs.org/ticket/3394 for a 
> patches or two you emailed to the list (your patch for Cairo was at least one 
> of them, might be one other). I know the core team use the patchwork website 
> and email for landing things in sugar shell, but it seems pretty useless for 
> activity developers to find/review patches. Any chance you could open some 
> bugs.sl.org tickets for the patches you'd still like to see land?

Right, I will open tickets for the Cairo port and the dragging hands
feature.  However, I would like to see the fix for #3394 landed first,
as it is a regression, I'm giving more priority to that.  And I don't
mind to hold the Cairo port until I fix the text sizes.  Will open
tickets to track them.

>> Or may I request co-maintainership?
>
> Sure, however I'd rather get the above items sorted before you start to land 
> patches and make releases, or I'm more likely to just hand it over and stop 
> work on it myself ;)

OK, we have to be careful while co-maintaining, pair reviewing or at
least testing so we don't loose code quality, maybe Rafael can help me
with Clock.

Thank you very much,

> Regards,
> --Gary
>
>> Greetings,
>>
>> --
>> .. manuq ..
>



-- 
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Clock #3394

2012-04-09 Thread Rafael Ortiz 
2012/4/9 Gary Martin 

> Hi Manuel,
>
> On 9 Apr 2012, at 17:25, Manuel Quiñones wrote:
>
> > Hi Gary,
> >
> > have you found time to take a look at this issue? "Clock activity
> > draws off the screen".  Rafael and I have some patches pending.
>
> When I last tested your patch I found it just drew a blank grey canvas on
> 11.3.1 and past releases of Sugar. I am not yet ready to start forking the
> activities I maintain for the GKT3 move (as I'm still not too happy with
> the use of dotted version numbers if I can avoid them – seriously thinking
> of ignoring dotted releases for now and just int +10 when I fork).
>
> I also don't have no tickets on http://bugs.sugarlabs.org/ticket/3394 for
> a patches or two you emailed to the list (your patch for Cairo was at least
> one of them, might be one other). I know the core team use the patchwork
> website and email for landing things in sugar shell, but it seems pretty
> useless for activity developers to find/review patches. Any chance you
> could open some bugs.sl.org tickets for the patches you'd still like to
> see land?
>
> > Or may I request co-maintainership?
>
> Sure, however I'd rather get the above items sorted before you start to
> land patches and make releases, or I'm more likely to just hand it over and
> stop work on it myself ;)
>
> Regards,
> --Gary
>
>
Yep, in my case I've not sent my patch because Manu's patches are not
applied yet, these patches
fixed some mayor issues and I don't want to work with the actual clock code
that has still the aforementioned issues.

+1 to Manu as co-maint.



> Greetings,
> >
> > --
> > .. manuq ..
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Clock #3394

2012-04-09 Thread Gary Martin 
Hi Manuel,

On 9 Apr 2012, at 17:25, Manuel Quiñones wrote:

> Hi Gary,
> 
> have you found time to take a look at this issue? "Clock activity
> draws off the screen".  Rafael and I have some patches pending.

When I last tested your patch I found it just drew a blank grey canvas on 
11.3.1 and past releases of Sugar. I am not yet ready to start forking the 
activities I maintain for the GKT3 move (as I'm still not too happy with the 
use of dotted version numbers if I can avoid them – seriously thinking of 
ignoring dotted releases for now and just int +10 when I fork).

I also don't have no tickets on http://bugs.sugarlabs.org/ticket/3394 for a 
patches or two you emailed to the list (your patch for Cairo was at least one 
of them, might be one other). I know the core team use the patchwork website 
and email for landing things in sugar shell, but it seems pretty useless for 
activity developers to find/review patches. Any chance you could open some 
bugs.sl.org tickets for the patches you'd still like to see land?

> Or may I request co-maintainership?

Sure, however I'd rather get the above items sorted before you start to land 
patches and make releases, or I'm more likely to just hand it over and stop 
work on it myself ;)

Regards,
--Gary

> Greetings,
> 
> -- 
> .. manuq ..

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Activity Team] Wiki guidance for adopting orphaned Activities / Activity co-maintainer

2012-04-09 Thread Gonzalo Odiard 
Ok. We need try encourage co-maintainership,
and see case by case.

Gonzalo

On Mon, Apr 9, 2012 at 1:31 PM, Gary Martin wrote:

> Hi Gonzalo,
>
> On 9 Apr 2012, at 05:07, Gonzalo Odiard wrote:
>
> > IMHO, seven days is not enough time to take a decision.
> > We can promise reply in seven days, and specially in the case of a new
> maintainer,
> > help him to be involved.
> > I am thinking in the case of Labyrinth, and trying to no repeat the same
> error.
>
> I think Labyrinth and myself as maintainer/developer was the original vat
> of boiling oil this all started with. I strongly disagreed with the design
> and a patch a deployment was shouting for landing but didn't have the
> bandwidth to write/present my version, after a week or so of me not getting
> time to spend on it, I had received a bunch of impatient emails, at which
> point I'd had enough of the inbox hassle and other tasks needing work, so I
> just handed over maintainership to get them off my back.
>
> Any way, yes I agree 7 days is not long enough for the complicated cases
> (e.g. deployment with potentially part time staff, or staff away on
> holiday), but in these cases (hopefully not too frequent) the Activity Team
> decision in that time can be 'no' while we further try to contact the
> maintainer for some given duration of time. We would just be acting as a
> cushion between potential forks (there is nothing stopping anyone form
> forking an Activity on day one and ignoring the existing maintainer), and
> hopefully have a little more history/knowledge with regard to an Activity
> and its maintainer vs. the new requestor.
>
> The primary reason for this FAQ entry is that Bernie seemed to think it
> was an issue from his experience with a past deployment, we/he can now
> point people to the FAQ if this comes up again. Ideally the push towards
> co-maintainers means that someone else can make a call on landing (or not)
> a patch if the lead maintainer is out of contact for a while.
>
> Regards,
> --Gary
>
> > Gonzalo
> >
> > On Thu, Apr 5, 2012 at 1:05 PM, Gary C Martin <
> garycmar...@googlemail.com> wrote:
> > Hi folks,
> >
> > This is a quick tentative shot a providing some FAQ guidance on the wiki
> for adopting orphaned Activities, or becoming an Activity co-maintainer.
> Nothing too dramatic or rocket-science but the conversation came up on IRC
> today with bernie and cjl so here it is:
> >
> >
> http://wiki.sugarlabs.org/go/Activity_Team/FAQ#How_do_I_adopt_an_orphaned_Activity.2C_or_become_an_Activity_co-maintainer
> >
> > Shout if you disagree! :)
> >
> > Regards,
> > --Gary
> >
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Activity Team] Wiki guidance for adopting orphaned Activities / Activity co-maintainer

2012-04-09 Thread Gary Martin 
Hi Gonzalo,

On 9 Apr 2012, at 05:07, Gonzalo Odiard wrote:

> IMHO, seven days is not enough time to take a decision.
> We can promise reply in seven days, and specially in the case of a new 
> maintainer,
> help him to be involved.
> I am thinking in the case of Labyrinth, and trying to no repeat the same 
> error.

I think Labyrinth and myself as maintainer/developer was the original vat of 
boiling oil this all started with. I strongly disagreed with the design and a 
patch a deployment was shouting for landing but didn't have the bandwidth to 
write/present my version, after a week or so of me not getting time to spend on 
it, I had received a bunch of impatient emails, at which point I'd had enough 
of the inbox hassle and other tasks needing work, so I just handed over 
maintainership to get them off my back.

Any way, yes I agree 7 days is not long enough for the complicated cases (e.g. 
deployment with potentially part time staff, or staff away on holiday), but in 
these cases (hopefully not too frequent) the Activity Team decision in that 
time can be 'no' while we further try to contact the maintainer for some given 
duration of time. We would just be acting as a cushion between potential forks 
(there is nothing stopping anyone form forking an Activity on day one and 
ignoring the existing maintainer), and hopefully have a little more 
history/knowledge with regard to an Activity and its maintainer vs. the new 
requestor.

The primary reason for this FAQ entry is that Bernie seemed to think it was an 
issue from his experience with a past deployment, we/he can now point people to 
the FAQ if this comes up again. Ideally the push towards co-maintainers means 
that someone else can make a call on landing (or not) a patch if the lead 
maintainer is out of contact for a while.

Regards,
--Gary

> Gonzalo
> 
> On Thu, Apr 5, 2012 at 1:05 PM, Gary C Martin  
> wrote:
> Hi folks,
> 
> This is a quick tentative shot a providing some FAQ guidance on the wiki for 
> adopting orphaned Activities, or becoming an Activity co-maintainer. Nothing 
> too dramatic or rocket-science but the conversation came up on IRC today with 
> bernie and cjl so here it is:
> 
> http://wiki.sugarlabs.org/go/Activity_Team/FAQ#How_do_I_adopt_an_orphaned_Activity.2C_or_become_an_Activity_co-maintainer
> 
> Shout if you disagree! :)
> 
> Regards,
> --Gary
> 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Clock #3394

2012-04-09 Thread Manuel Quiñones 
Hi Gary,

have you found time to take a look at this issue? "Clock activity
draws off the screen".  Rafael and I have some patches pending.

Or may I request co-maintainership?

Greetings,

-- 
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SWEETS] Easy repository managing; Wiki rehashing

2012-04-09 Thread Thomas C Gilliard 

Install to HD tests:

http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution/Testing

On 04/09/2012 04:56 AM, Aleksey Lim wrote:

On Sat, Apr 07, 2012 at 11:44:56PM +, Aleksey Lim wrote:

Hi all!


To reflect on the fact that Sweets Distribution is a part of Harmonic
Distribution effort[1], Wiki was tuned. So, it doesn't say only about
Ubuntu (Harmonic Distribution is distro agnostic[2]).

The another thing is suggesting using sweets-distribution utility to
easy managing Sweets Distribution repositories. For example to attach
Factory repository on clean system:

 wget http://download.sugarlabs.org/packages/sweets-distribution.sh
 sudo sweets-distribution.sh select Factory

After getting feedback, sweets-distribution.sh was simplified to make it
simple installer. So, the command:

 wget ftp://download.sugarlabs.org/packages/sweets-distribution.sh
 sudo sh sweets-distribution.sh

will just install "sweets" package to have "sweets-distribution" command
in the system.


More information:

 
http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution#Installation

The previous tips were moved to:

 
http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution/Manual_Installation


[1] http://wiki.sugarlabs.org/go/Platform_Team/Harmonic_Distribution/Software
[2] 
http://wiki.sugarlabs.org/go/Platform_Team/Harmonic_Distribution/Supported_platforms

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SWEETS] Easy repository managing; Wiki rehashing

2012-04-09 Thread Aleksey Lim 
On Mon, Apr 09, 2012 at 10:39:03AM -0300, Esteban Bordón wrote:
> Hi Aleksey,
> 
> Have you planned to add sweets distribution in 12.04 repos?

As far as it will be released. This is due to the design decisions in
Open Build System, Sweets Distribution is being built on.

> I'm trying in Ubuntu 12.04 and I getting the error:
> 
> $ sweets-distribution status
> Traceback (most recent call last):
>   File "/usr/bin/sweets-distribution", line 26, in 
> from sweets_distribution import env, util, printf
> ImportError: No module named sweets_distribution

Exactly this error is minor (sweets package installed sweets_distribution
module for different Python version) but a after fixing it, the rest of
non-noarch packages might not work on 12.04.

-- 
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SWEETS] Easy repository managing; Wiki rehashing

2012-04-09 Thread Esteban Bordón 
Hi Aleksey,

Have you planned to add sweets distribution in 12.04 repos?
I'm trying in Ubuntu 12.04 and I getting the error:

$ sweets-distribution status
Traceback (most recent call last):
  File "/usr/bin/sweets-distribution", line 26, in 
from sweets_distribution import env, util, printf
ImportError: No module named sweets_distribution


2012/4/9 Aleksey Lim 

> On Sat, Apr 07, 2012 at 11:44:56PM +, Aleksey Lim wrote:
> > Hi all!
> >
> >
> > To reflect on the fact that Sweets Distribution is a part of Harmonic
> > Distribution effort[1], Wiki was tuned. So, it doesn't say only about
> > Ubuntu (Harmonic Distribution is distro agnostic[2]).
> >
> > The another thing is suggesting using sweets-distribution utility to
> > easy managing Sweets Distribution repositories. For example to attach
> > Factory repository on clean system:
> >
> > wget http://download.sugarlabs.org/packages/sweets-distribution.sh
> > sudo sweets-distribution.sh select Factory
>
> After getting feedback, sweets-distribution.sh was simplified to make it
> simple installer. So, the command:
>
>wget ftp://download.sugarlabs.org/packages/sweets-distribution.sh
>sudo sh sweets-distribution.sh
>
> will just install "sweets" package to have "sweets-distribution" command
> in the system.
>
> > More information:
> >
> >
> http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution#Installation
> >
> > The previous tips were moved to:
> >
> >
> http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution/Manual_Installation
> >
> >
> > [1]
> http://wiki.sugarlabs.org/go/Platform_Team/Harmonic_Distribution/Software
> > [2]
> http://wiki.sugarlabs.org/go/Platform_Team/Harmonic_Distribution/Supported_platforms
>
> --
> Aleksey
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SWEETS] Easy repository managing; Wiki rehashing

2012-04-09 Thread Aleksey Lim 
On Sat, Apr 07, 2012 at 11:44:56PM +, Aleksey Lim wrote:
> Hi all!
> 
> 
> To reflect on the fact that Sweets Distribution is a part of Harmonic
> Distribution effort[1], Wiki was tuned. So, it doesn't say only about
> Ubuntu (Harmonic Distribution is distro agnostic[2]).
> 
> The another thing is suggesting using sweets-distribution utility to
> easy managing Sweets Distribution repositories. For example to attach
> Factory repository on clean system:
> 
> wget http://download.sugarlabs.org/packages/sweets-distribution.sh
> sudo sweets-distribution.sh select Factory

After getting feedback, sweets-distribution.sh was simplified to make it
simple installer. So, the command:

wget ftp://download.sugarlabs.org/packages/sweets-distribution.sh
sudo sh sweets-distribution.sh

will just install "sweets" package to have "sweets-distribution" command
in the system.

> More information:
> 
> 
> http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution#Installation
> 
> The previous tips were moved to:
> 
> 
> http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution/Manual_Installation
> 
> 
> [1] http://wiki.sugarlabs.org/go/Platform_Team/Harmonic_Distribution/Software
> [2] 
> http://wiki.sugarlabs.org/go/Platform_Team/Harmonic_Distribution/Supported_platforms

-- 
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel