Naturally, the key is volunteer activity by the community. As always
identify the non-working activities, identify common problems which can
be handled such as conversion to GTK3, and anyone who wants take that
on. For testers and reviewers, get help from out users. If we set up a
'help' path
Thanks for clarifying; I'd misunderstood
On Wed, Jan 23, 2019, 7:29 PM James Cameron No, thanks! What my time can accomplish was given only as an
> indication of the size of the solved part of the overall problem.
>
> OLPC continues to pay me to work on our education solution, which
>
No, thanks! What my time can accomplish was given only as an
indication of the size of the solved part of the overall problem.
OLPC continues to pay me to work on our education solution, which
includes Sugar and these activities. The rest of my time is already
sold.
On Wed, Jan 23, 2019 at
First, what are the numbers: extrapolating from this N=1 sample, how many
activities can be maintained by a very experienced python and Sugar developer?
Regards
Martin
> On Jan 23, 2019, at 07:27, Dave Crossland wrote:
>
> James, are you soliciting SL pay you as a contractor to fix
James, are you soliciting SL pay you as a contractor to fix Activities not
on the list?
On Wed, Jan 23, 2019, 1:15 AM James Cameron Nice idea, but hasn't happened yet, and I don't expect it to ever
> happen without scaling up the number of testers and fixers.
>
> We just don't have enough people
My naive view is that if we seriously undertake the task, others will join.
As an example, now that we have Sugar on Ubuntu 18.04, we could easily
install every activity on a laptop and test in Sugar by launching to see
if it shows the opening screen or gives 'failed to start'. In the latter
Nice idea, but hasn't happened yet, and I don't expect it to ever
happen without scaling up the number of testers and fixers.
We just don't have enough people paying attention.
How would you propose that attention be purchased? Sugar Labs has
$95k we could spend. You've seen from the list what
My original point was that as a community we should view the activities
on ASLO as a corpus to be treasured and protected. No activity can be
either abandoned or orphaned. It is the responsibility of the community.
When a change 'upstream' breaks an activity or set of activities, the
problem
On Tue, Jan 22, 2019 at 09:54:08PM -0500, Walter Bender wrote:
>
> On Tue, Jan 22, 2019 at 9:13 PM James Cameron <[1]qu...@laptop.org> wrote:
>
> On Tue, Jan 22, 2019 at 01:29:56PM -0500, Devin Ulibarri wrote:
> > Hi,
> >
> > This was my experience:
> >
> > • I came
On Tue, Jan 22, 2019 at 9:13 PM James Cameron wrote:
> On Tue, Jan 22, 2019 at 01:29:56PM -0500, Devin Ulibarri wrote:
> > Hi,
> >
> > This was my experience:
> >
> > • I came into SugarLabs community at the time that this migration was
> > beginning to happen.
> > • I started a GH
On Tue, Jan 22, 2019 at 01:29:56PM -0500, Devin Ulibarri wrote:
> Hi,
>
> This was my experience:
>
> • I came into SugarLabs community at the time that this migration was
> beginning to happen.
> • I started a GH account because that is where I was told the software was
> being
Hi,
This was my experience:
* I came into SugarLabs community at the time that this migration was
beginning to happen.
* I started a GH account because that is where I was told the software was
being maintained.
* I have continued to "go with the flow" and work via GH although I have come
to
Walter,
I will try. I am moving on Feb 3 to Palawan. I'll try to get to it then.
My principal concern re GSOC is to define projects with manageable scope
- many of the past projects ended undelivered.
Tony
On 1/21/19 3:10 PM, Walter Bender wrote:
On Mon, Jan 21, 2019 at 3:44 AM James
On Mon, Jan 21, 2019 at 3:44 AM James Cameron wrote:
> Fascinating, I never thought the move to GitHub was ever going to
> achieve all that. It was to enable a shutdown of the unmaintained
> gitorious instance at git.sugarlabs.org. Which still hasn't happened
> because it is still useful, in
Hi, James
This is a disagreement with Walter from day one. ASLO is a means to
maintain the library of Sugar activities in use for nearly a decade.
Introducing gitHub created an obstacle for our users as contributors.
Another disagreement I have with Walter is the concept of replacing
ASLO.
Fascinating, I never thought the move to GitHub was ever going to
achieve all that. It was to enable a shutdown of the unmaintained
gitorious instance at git.sugarlabs.org. Which still hasn't happened
because it is still useful, in turn because this community hasn't the
time to do the necessary
While it is marvelous to see some actual attention to the Sugar
activities, this approach is the direct opposite of the logic behind the
move of the activities to gitHub. This is a return to the G1G1 model in
which individuals develop, contribute and own activities. There can be
no abandoned
I am actively maintaining Music Blocks and Turtle Blocks JS.
I just haven't had the bandwidth to do much beyond that of late. That said,
I am happy to kibbutz on any of the activities which I used to maintain.
On Fri, Jan 18, 2019 at 3:11 AM Rahul Bothra wrote:
> I am maintaining CowBulls and
I noticed Dimensions fell off the list. I will take that one on as I think
it is of real value.
-walter
On Sun, Jan 20, 2019 at 8:44 AM James Cameron wrote:
> Thanks. So the list looks like;
>
> # Walter Bender
>
> * Music Blocks,
> * Turtle Blocks JS,
>
> # Rahul Bothra
>
> * CowBulls,
> *
Thanks. So the list looks like;
# Walter Bender
* Music Blocks,
* Turtle Blocks JS,
# Rahul Bothra
* CowBulls,
* Flappy,
* Cedit,
* Polari,
# James Cameron
* Abacus,
* Browse (master),
* Browse (fedora 18 - webkit - v157.x),
* Calculator,
* Chart,
* Chat,
* Clock,
* Develop,
* Distance,
*
I am maintaining CowBulls and Flappy.
I can take up cedit and Polari
On Fri, Jan 18, 2019 at 12:53 PM James Cameron wrote:
> Once we had a list of abandoned activities, where the maintainer is
> missing in action, not doing testing or releasing.
>
> Now, I propose the inverse; a list of
Once we had a list of abandoned activities, where the maintainer is
missing in action, not doing testing or releasing.
Now, I propose the inverse; a list of activities with a maintainer
testing and releasing. It will be easier to maintain that list.
For myself, each of the Fructose activities,
22 matches
Mail list logo
