[Sugar-devel] [IAEP] Sugar Digest 2012-11-30

[Walter Bender]

I'll make it into eight separate tasks...

On Fri, Nov 30, 2012 at 5:16 PM, James Simmons <nicestep at gmail.com> wrote:
> Walter,
>
> This was my write-up:
>
> http://wiki.sugarlabs.org/go/GoogleCodeIn2012/MYOSA
>
> I had eight sub-tasks in there, which included proposals for new chapters
> and a couple of suggestions for the existing chapters, mostly involving GTK3
> porting.  I thought giving students the option of making their own chapters
> would be a better incentive than the necessary drudgery of updating the
> existing ones, which I can take on myself.  Since we are still shipping the
> old GTK the existing book still works.  We could leave well enough alone and
> add a chapter on migrating to GTK3 plus create new entries in the Git
> repository with the code samples migrated.  I don't see updating individual
> chapters as attractive tasks, and I don't think a student would either.
>
> I was more concerned that the Melange only shows this as one big task rather
> than eight.
>
> Again, if it turns out that GCI comes and goes and nobody chooses to work on
> this I'll still work with anyone who wants to add a chapter to the book, on
> his (or her) own terms, and buy them a printed copy of the book and ship it
> to where they live.  That person will also get his picture on the back cover
> and any other inducement I can reasonably offer.
>
> James Simmons
>
>
> On Fri, Nov 30, 2012 at 2:54 PM, Walter Bender <walter.bender at gmail.com>
> wrote:
>>
>> Perhaps we could break the editing update into chapters.
>>
>> -walter
>>
>> On Fri, Nov 30, 2012 at 3:44 PM, James Simmons <nicestep at gmail.com> wrote:
>> > I am wondering if I did the best possible job setting up my tasks for
>> > the
>> > Google code-in.  Judging from
>> >
>> > http://www.google-melange.com/gci/dashboard/google/gci2012#all_org_tasks
>> >
>> > it looks like lots of small tasks are most attractive to potential
>> > students.
>> > I wrote up a little page explaining some possible improvements, each one
>> > of
>> > which could be considered a task, but on Melange it looks like updating
>> > the
>> > book is considered one big task.  So I'm wondering if that needs to be
>> > changed and how to go about it.
>> >
>> > Whether it as part of the Google code-in or not, I hope to work with the
>> > Python Joven and others like them to make an improved version of MYOSA
>> > and
>> > give them a shot at literary immortality.  It isn't fair for me to keep
>> > all
>> > of it for myself.
>> >
>> > James Simmons
>> >
>> >> 2. Google Code-In [3] began on Monday. We have 22 mentors [4], 40
>> >> students [5], and 79 out of 132 tasks already completed [6]. (More
>> >> tasks are coming on-line soon.) The contest runs for 6 weeks, so it is
>> >> not too late to sign up as a mentor [7] and to recruit students to
>> >> participate [8]. Some highlights include new tutorials for Turtle Art,
>> >> using Sugar in a Virtual Machine, and using Sugar on a Stick; a new
>> >> feature: load a background image on the home screen; and numerous
>> >> patches in support of internationalization. Some of the usual suspects
>> >> are making their usual outstanding contributions, while some new
>> >> talent is also emerging. Thanks to everyone (mentors, students, and
>> >> Google) for participating.
>> >
>> >
>> >>
>> >> [6]
>> >>
>> >> http://www.google-melange.com/gci/dashboard/google/gci2012#all_org_tasks
>> >
>> >
>>
>>
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.org
>
>



-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org