Re: [Sugar-devel] GSOC proposal review for write activity

[James Cameron]

Thanks.

On Tue, Apr 02, 2019 at 10:33:00AM +0530, Ashish Aggarwal wrote:
> Hello Everyone ,
> My name is Ashish aggarwal and I am a B.Tech CSE student . I have attached my
> proposal for Write activity . Looking forward to getting reviews from mentors
> and community members . 
> Thanks and Regards
> [1]ashish aggarwal
> github - [2]ashish0910
> 
> References:
> 
> [1] http://ashishaggarwal.tech/
> [2] https://github.com/ashish0910



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

Re: [Sugar-devel] Activity

[James Cameron]

Thanks.  I've reviewed it.  You're welcome to modify it, but I've no
suggestions.

It is nice to see a proposal that isn't one of our prepared list of
project ideas.

On Tue, Apr 02, 2019 at 08:14:36AM +0530, kushagra nigam wrote:
> Dear Sir, 
> I'm waiting for a review of my proposal so that I can modify it before the
> final submission.
> Sincerely
> Kushagra Nigam
> [1]kushagra1...@gmail.com
> 
> On Sun, 31 Mar 2019 at 16:05, kushagra nigam <[2]kushagra1...@gmail.com> 
> wrote:
> 
> Dear Sir,
> Please find my draft proposal of new activity for the GSoC'19. Kindly
> review it and let me know if it requires any modification.
> Sincerely
> Kushagra Nigam
> [3]kushagra1...@gmail.com
> 
> On Wed, 27 Mar 2019 at 12:42, James Cameron <[4]qu...@laptop.org> wrote:
> 
> Yes, I have, thanks.
> 
> On Wed, Mar 27, 2019 at 10:22:24AM +0530, kushagra nigam wrote:
> > This is with reference to that GNOME cursor thing. I have created a
> pull
> > request [1][5]https://github.com/sugarlabs/sugar/pull/828. Kindly
> review it and
> > let me know if it needs any changes.
> >
> > Sincerely
> > Kushagra Nigam
> >
> > On Tue, 26 Mar 2019 at 02:59, James Cameron <[2][6]qu...@laptop.org>
> wrote:
> >
> >     Thanks.  Further discussion in pull request.
> >
> >     Please also read
> >     [3][7]https://github.com/sugarlabs/sugar-docs/blob/master/src/
> contributing.md
> >
> >     On Mon, Mar 25, 2019 at 04:36:34PM +0530, kushagra nigam wrote:
> >     > Dear Sir,
> >     >
> >     > You are indeed right! However after tinkering with the Sugar
> files, I got
> >     to
> >     > know that cursor theme of the instance Gio.Settings changes 
> the
> cursor
> >     theme of
> >     > the GNOME Desktop but does not affect the Default folder 
> (/usr/
> share/
> >     icons/
> >     > default) which contains the settings of the default cursor
> theme which
> >     you have
> >     > set. So changing the cursor theme to default in the function
> >     > _start_window_manager helps and works! 
> >     >
> >     > I started by taking a global variable of initial settings and
> then
> >     re-applying
> >     > those settings before the exit of Sugar. This was absolutely
> right but I
> >     > discovered/observed something easier later! :-)
> >     >
> >     > I have edited the main.py file and created a pull request.
> >     >
> >     > Sincerely
> >     > Kushagra Nigam
> >     > [1][4][8]kushagra1...@gmail.com
> >     >
> >     > On Mon, 25 Mar 2019 at 06:11, James Cameron <[2][5][9]
> qu...@laptop.org>
> >     wrote:
> >     >
> >     >     Yes, the Sugar cursor affects the GNOME desktop
> environment.
> >     >
> >     >     This is caused by
> >     >     [3][6][10]https://github.com/sugarlabs/sugar/blob/master/
> src/jarabe/
> >     main.py#L205
> >     >     where the GNOME desktop cursor theme is changed to the
> Sugar theme.
> >     >
> >     >     Workaround is to use gsettings to change cursor-theme in
> >     >     org.gnome.desktop.interface back to what it was.  Yes, you
> can use
> >     >     dconf to reset all settings, but that has many
> side-effects.
> >     >
> >     >     If this problem bothers anyone who wants to fix it, the 
> fix
> I'm
> >     >     interested in seeing is;
> >     >
> >     >     * read the value of cursor-theme before changing it in the
> >     >       _start_window_manager function,
> >     >
> >     >     * keep the Gio.Settings instance instead of deleting at 
> end
> of the
> >     >       _start_window_manager function,
> >     >
> >     >     * restore the old value in the _stop_window_manager
> function.
> >     >
> >     >     This should fix the problem for future users.
> >     >
> >     >     On Sat, Mar 23, 2019 at 11:28:34AM +0530, kushagra nigam
> wrote:
> >     >     > Subject : Help needed for the proposal
> >     >     > Dear Sir,
> >     >     >
> >     >     > Last day I was working with with the Sugar activities. I
> read the
> >     >     documentation
> >     >     > and setup the environment. I made this hello-world
> activity which
> >     was
> >     >     > instructed there and even used some of the artworks. I
> want to ask
> >     how
> >

[Sugar-devel] GSoC 2019: Call for proposals; Deadline approaching

[Rahul Bothra]

G'day

We have received a lot of amazing proposals for GSoC 2019 till now. For
those who are yet to share their proposals, please do so at the earliest,
so that you can get reviews from the project mentors in time.

FYI, 9th April is the deadline to submit the proposal on the GSoC website,
and it's never good to wait till the last minute.

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

Re: [Sugar-devel] Activity

[kushagra nigam]

Dear Sir,
I'm waiting for a review of my proposal so that I can modify it before the
final submission.
Sincerely
Kushagra Nigam
kushagra1...@gmail.com

On Sun, 31 Mar 2019 at 16:05, kushagra nigam  wrote:

> Dear Sir,
> Please find my draft proposal of new activity for the GSoC'19. Kindly
> review it and let me know if it requires any modification.
> Sincerely
> Kushagra Nigam
> kushagra1...@gmail.com
>
> On Wed, 27 Mar 2019 at 12:42, James Cameron  wrote:
>
>> Yes, I have, thanks.
>>
>> On Wed, Mar 27, 2019 at 10:22:24AM +0530, kushagra nigam wrote:
>> > This is with reference to that GNOME cursor thing. I have created a pull
>> > request [1]https://github.com/sugarlabs/sugar/pull/828. Kindly review
>> it and
>> > let me know if it needs any changes.
>> >
>> > Sincerely
>> > Kushagra Nigam
>> >
>> > On Tue, 26 Mar 2019 at 02:59, James Cameron <[2]qu...@laptop.org>
>> wrote:
>> >
>> > Thanks.  Further discussion in pull request.
>> >
>> > Please also read
>> > [3]
>> https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md
>> >
>> > On Mon, Mar 25, 2019 at 04:36:34PM +0530, kushagra nigam wrote:
>> > > Dear Sir,
>> > >
>> > > You are indeed right! However after tinkering with the Sugar
>> files, I got
>> > to
>> > > know that cursor theme of the instance Gio.Settings changes the
>> cursor
>> > theme of
>> > > the GNOME Desktop but does not affect the Default folder
>> (/usr/share/
>> > icons/
>> > > default) which contains the settings of the default cursor theme
>> which
>> > you have
>> > > set. So changing the cursor theme to default in the function
>> > > _start_window_manager helps and works!
>> > >
>> > > I started by taking a global variable of initial settings and then
>> > re-applying
>> > > those settings before the exit of Sugar. This was absolutely
>> right but I
>> > > discovered/observed something easier later! :-)
>> > >
>> > > I have edited the main.py file and created a pull request.
>> > >
>> > > Sincerely
>> > > Kushagra Nigam
>> > > [1][4]kushagra1...@gmail.com
>> > >
>> > > On Mon, 25 Mar 2019 at 06:11, James Cameron <[2][5]
>> qu...@laptop.org>
>> > wrote:
>> > >
>> > > Yes, the Sugar cursor affects the GNOME desktop environment.
>> > >
>> > > This is caused by
>> > > [3][6]
>> https://github.com/sugarlabs/sugar/blob/master/src/jarabe/
>> > main.py#L205
>> > > where the GNOME desktop cursor theme is changed to the Sugar
>> theme.
>> > >
>> > > Workaround is to use gsettings to change cursor-theme in
>> > > org.gnome.desktop.interface back to what it was.  Yes, you
>> can use
>> > > dconf to reset all settings, but that has many side-effects.
>> > >
>> > > If this problem bothers anyone who wants to fix it, the fix
>> I'm
>> > > interested in seeing is;
>> > >
>> > > * read the value of cursor-theme before changing it in the
>> > >   _start_window_manager function,
>> > >
>> > > * keep the Gio.Settings instance instead of deleting at end
>> of the
>> > >   _start_window_manager function,
>> > >
>> > > * restore the old value in the _stop_window_manager function.
>> > >
>> > > This should fix the problem for future users.
>> > >
>> > > On Sat, Mar 23, 2019 at 11:28:34AM +0530, kushagra nigam
>> wrote:
>> > > > Subject : Help needed for the proposal
>> > > > Dear Sir,
>> > > >
>> > > > Last day I was working with with the Sugar activities. I
>> read the
>> > > documentation
>> > > > and setup the environment. I made this hello-world activity
>> which
>> > was
>> > > > instructed there and even used some of the artworks. I want
>> to ask
>> > how
>> > > should I
>> > > > proceed with the project? Should I make a layout on GTK+3
>> and push
>> > it
>> > > onto my
>> > > > github (But that'll take some time) or just writing a
>> detailed
>> > proposal
>> > > of how
>> > > > will I get along with the project every week would do the
>> job?
>> > Please
>> > > help me!!
>> > > >
>> > > > Secondly i discovered this issue:
>> > > > I have installed 'Sucrose' in my Ubuntu. Whenever I logout
>> and
>> > login with
>> > > the
>> > > > SUGAR environment, it is good. However when I log out from
>> SUGAR
>> > and come
>> > > back
>> > > > to Ubuntu, I still have that big cursor on my screen (The
>> sugar
>> > one),
>> > > that is
>> > > > the original cursor is replaced by the SUGAR one. Is this a
>> problem
>> > with
>> > > > everyone?
>> > > > A hack which I came up is to Reset the settings when you
>> come back
>> > to
>> > > Ubuntu (
>> > > > dconf 

Re: [Sugar-devel] GSoC proposal changes

[James Cameron]

Okay, thanks.

I'm not requiring any changes.  You're welcome to change it if you
like.

On Mon, Apr 01, 2019 at 02:07:42PM +0530, ANIKET MATHUR wrote:
> Thanks for answering and guiding.
> I am aware of the obstacles that I might face, also I am aware of
> the flexibility of the timeline that might change as the work
> proceeds.  My timeline is just an approximate idea of how long it
> might take to perform tasks in chronological order. To determine
> that I went through the previous work done on each task and the work
> remaining to be done, to make out approximate figures. I accept that
> the real difficulties are faced only once you start working, which
> might entirely alter my timeline. 
> 
> Also, I consider it as a possibility and accept it that I might have
> to work on things not mentioned in my proposal during the program,
> like porting other activities to TelepathyGlib, or other
> contributions to the source code essential at that time. I know this
> is how things work, rather than sticking to a timeline. 
> 
> Still, I am not clear about the changes that I have to make, because
> there is no such thing as a strict timeline. So do I have to keep my
> timeline the same and let my mentors guide me through the work that
> I have to do during the program itself? 
> 
> On Mon, Apr 1, 2019 at 12:50 PM James Cameron <[1]qu...@laptop.org> wrote:
> 
> On Sat, Mar 30, 2019 at 03:52:08PM +0530, aniket mathur wrote:
> > James wrote:
> > >  "your timeline has a queue of components in a set order; it is
> > > more likely you'll need to work on all components at once; that's
> > > how it seems to work for me."
> >
> > Suggestion given by @quozl for my timeline. Should I make my
> > timeline as a certain percent of work done on all components
> > together before phase evaluations? Need suggestions. Link to my
> > proposal.
> > [2]https://docs.google.com/document/d/
> 1uGwlzPMUG7Z_ZJEloORGc8tEiXs72qLurO-R7GlomsU
> 
> Thanks for asking.
> 
> No, I don't think a certain percentage could work; how would we
> measure?
> 
> Consider the varying purposes of a timeline;
> 
> 1.  so that we can see the weeks you'll be working,
> 
> 2.  so that you'll have something that can be assessed during
> evaluations, something that is working and 90% done by midterm,
> 
> 3.  so that we can see you've thought about the size of the
> work,
> 
> 4.  so that we can see if you have iterated into estimates of
> subtasks,
> 
> Also, the timeline is not going to be kept as-is; you and your
> mentors will adjust the timeline during the project.  When a
> timeline is not adjusted, that usually means mentors and student
> are not paying attention to the timeline.  In my experience an
> unadjusted timeline is a reliable sign of impending failure.
> 
> Implementation mistakes of working with timelines that I've seen
> are;
> 
> - stopping work when you've no idea how to proceed, and you have
> to ask questions of mentors, or other project teams; you must
> have something else to work on while you wait for an answer,
> 
> - not working on next week's tasks when something takes a
> shorter time than expected; the spare time should be used,
> 
> - moving on to a different task when a task is not finished; can
> be fatal to a project when there are task dependencies.
> 
> See also Google Summer of Code - Student Guide - Writing a
> proposal,
> [3]https://google.github.io/gsocguides/student/writing-a-proposal
> which does not talk about timelines.  There's an early paragraph
> about time management.
> 
> Now, your timeline seems to follow the "Project Task Checklist"
> in the idea.  We put that checklist there because those tasks
> have a somewhat forward dependency.  But there are some traps in
> using that checklist as a timeline.  Many of those tasks may
> stall for one reason or another outside your control.  Some of
> them are ill-defined; for example the port to TelepathyGLib is
> needed eventually for all activities, but only the Fructose set
> are to be ported by your project, so that suggests only the
> Fructose set and the Toolkit should be ported to TelepathyGLib.
> 
> So a good timeline will depend on planning of the tasks, and
> that may in turn depend on good estimates.  An invaluable input
> to estimating software effort is to try to use the software or
> cobble together a minimum viable prototype.  I know what sort of
> traps you would hit if you tried that.
> 
> --
> James Cameron
> [4]http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> [5]Sugar-devel@lists.sugarlabs.org
> [6]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] 
> https://docs.google.com/document/d/1uGwlzPMUG7Z_Z

[Sugar-devel] How to get started as a Sugar Labs developer [v6]

[James Cameron]

New to Sugar Labs?  Unlock these achievements.  Work from top to
bottom.

1.  Use Sugar or Sugarizer,

https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md

* by using Sugar or Sugarizer you will learn how it works, and
  what can be improved.

* mandatory,

2.  Read our Code of Conduct,

https://github.com/sugarlabs/sugar-docs/blob/master/src/CODE_OF_CONDUCT.md

* especially note the need to choose an appropriate forum, and
  remind others to do the same,

* mandatory,

3.  Join the developer mailing list,

https://lists.sugarlabs.org/listinfo/sugar-devel

* for asking questions and helping others,

* subscribe before posting,

* don't use digest mode if you plan to post messages or replies,
  as it breaks threads,

* try to keep discussions public; the default reply mode is
  private, use reply-all,

* mandatory,

4.  Get a GitHub account,

https://github.com/

* for reporting issues that you won't fix,

* for fixing problems in source code,

* recommended,

5.  Join the Sugar Labs GitHub organisation,

https://github.com/sugarlabs

* for regular source code contributors, and reviewers, by
  invitation, contact one of the existing members,

* helpful for mail notification of GitHub activity,

* optional,

6.  Join as a Member of Sugar Labs,

https://wiki.sugarlabs.org/go/Sugar_Labs/Members

* requires some contribution; code, documentation, translations,
  maintenance, running a Sugar deployment, or any other
  non-trivial activities which benefit Sugar Labs,

* reviewed by committee,

* optional,

7.  Get a wiki.sugarlabs.org account,

https://wiki.sugarlabs.org/

* needed for maintaining Wiki content,

* needed as part of moving Wiki content to GitHub,

* for subscribing to edit notifications.

* optional,

8.  Get an activities.sugarlabs.org account,

https://activities.sugarlabs.org/

* needed for releasing new versions of Sugar activities,

* optional,

9.  Get a shell.sugarlabs.org account,

https://wiki.sugarlabs.org/go/Service/shell#Requesting_a_shell_account

* requires a justification,

* also provides a @sugarlabs.org mail alias,

* for releasing new versions of Sugar components, test builds,
  or large data sets,

* for limited experimentation with non-root network services, such
  as bots or IRC proxies,

* optional,

10. Get a translate.sugarlabs.org account,

https://translate.sugarlabs.org/

* if you are bi- or multi-lingual, use your skills,

* especially if you can test Sugar activities and components, as
  this will inform your translations,

* optional,

11. Get a bugs.sugarlabs.org account,

https://bugs.sugarlabs.org/

* only if you must maintain old bug reports,

* new issues may be reported via GitHub,

* optional,

12. Join Sugar on Fedora live system mailing list,

https://lists.sugarlabs.org/listinfo/soas

* download, test, report bugs, fix bugs, package,

* share your experience with others who focus on this
  distribution,

* optional,

13. Join Sugar on Debian mailing lists,

https://github.com/sugarlabs/sugar/blob/master/docs/debian.md#packaging

* download, test, report bugs, fix bugs, package,

* share your experience with others who focus on this distribution,

* optional,

14. Join the Internet Relay Chat channel #sugar

irc://irc.freenode.net/#sugar

* for synchronous chat with others,

* requires registration with freenode.net,

* optional,

15. Join the Internet Relay Chat channel #sugar-meeting

irc://irc.freenode.net/#sugar-meeting
http://meeting.sugarlabs.org/

* for meetings, but keep your own transcripts and minutes,

* requires registration with freenode.net,

* optional,

16. Join Gitter

https://gitter.im/

* for chat with others,

* best is mailing list sugar-devel@ for topics of general interest,

* requires registration with one of several organisations,

* optional,

17. Maintain an Activity


https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer

* many learner focused activities (apps) need simple maintenance,

* adopt an activity you like as your focus.

Hope that helps!

See also "How to ask for directions",
http://lists.sugarlabs.org/archive/sugar-devel/2018-October/055788.html


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

Re: [Sugar-devel] Gsoc Proposal for "performance in musicblocks"

[James Cameron]

Thanks!

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

Re: [Sugar-devel] Regarding GSoC 2019

[James Cameron]

Welcome Roohan,

Good questions;

1.  not aware of any specific curriculum; we're a mix of nationalities
and our target audience is all; but you are welcome to make a
reference to a curriculum to back up a decision you've made,

2 (a).  sugar-devel@ subscription and participation is a minimum for
contributing to Sugar Labs, the others are optional; GitHub, IRC,
Gitter, Wiki, (that reminds me to repost my list),

2 (b).  treat the IRC nickname section as optional, and be prepared to
identify yourself by name when a group meeting is held; the template
was prepared when we expected mentors on IRC during this phase of
preparations, but mentors have not been available, so we have
de-emphasised IRC in other information, ... on the other hand, if you
haven't registered an IRC nickname on freenode.net, you may find
attending a group meeting difficult the first time you need to do it.

3. when you submit a draft proposal to sugar-devel@ or Google Summer
of Code, you can change it and submit a changed draft proposal; when
you are finished making any changes, you can submit the "Final PDF
Proposal" on Google Summer of Code web site,

Hope that helps.

On Tue, Apr 02, 2019 at 06:00:26AM +0530, Roohan wrote:
> Hello mentor/mentors,
> 
> I have been able to tackle myself most of the problems I have
> encountered till now, and I am brainstorming ideas for Sugarizer and
> writing the proposal at the same time.
> 
> I would love a little clarification on the following:
> 
> 1. I know that the "target age group" for Sugar/Sugarizer is around
> 6- 12 years of age.But, do I need to follow any  'specific
> curriculum'  while designing the activities? If so, I would like to
> know about the same.
> 
> 2. I am only using sugar-devel mailing list as a means of
> communication with the mentors and I am able to get my doubts
> cleared pretty much.Is it compulsory to be present in both : the
> mailing list & IRC ? I asked because there is blank in the proposal
> template asking for IRC nickname.
> 
> 3. Once I submit the proposal, will I be able to modify it later if
> I wanted to?
> 
> Thanking you
> 
> Roohan
> 

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

[Sugar-devel] Regarding GSoC 2019

[Roohan]

Hello mentor/mentors,

I have been able to tackle myself most of the problems I have encountered
till now, and I am brainstorming ideas for Sugarizer and writing the
proposal at the same time.

I would love a little clarification on the following:

1. I know that the "target age group" for Sugar/Sugarizer is around 6- 12
years of age.But, do I need to follow any  '*specific curriculum*'  while
designing the activities? If so, I would like to know about the same.

2. I am only using sugar-devel mailing list as a means of communication
with the mentors and I am able to get my doubts cleared pretty much.*Is it
compulsory to be present in both : the mailing list & IRC ? I asked because
there is blank in the proposal template asking for IRC nickname.*

3. Once I submit the proposal, will I be able to modify it later if I
wanted to?

Thanking you

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

Re: [Sugar-devel] GSoC Proposal : Sugar Dashboard

[James Cameron]

Thanks.  I've no feedback.

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

Re: [Sugar-devel] Gsoc Proposal for "performance in musicblocks"

[James Cameron]

Unfortunately, your document is protected.  "You need permission".

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

[Sugar-devel] Gsoc Proposal for "performance in musicblocks"

[Favour Kelvin]

Hello all,

I am Favour Kelvin, I have been contributing to music blocks for a while
now and want to work on "Performance In Musicblocks" as my GSOC 2019
project. Attached herewith is my proposal. Kindly review it and suggest any
changes.

  Proposal.pdf

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

Re: [Sugar-devel] [IAEP] April 19th workshop in Kano

[Patricia Escauriza]

Great, thanks!


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

El lun., 1 abr. 2019 a las 15:44, Walter Bender ()
escribió:

> I will ask Ahmed for his materials. I know he is also still looking for
> input.
>
> regards.
>
> -walter
>
> On Mon, Apr 1, 2019 at 3:20 PM Patricia Escauriza <
> pescaur...@paraguayeduca.org> wrote:
>
>> I'd like to do something like that in Paraguay, I would also appreciate
>> having the material and details.. regards!
>>
>> Patty
>>
>>
>> 
>>  Virus-free.
>> www.avast.com
>> 
>> <#m_-4738583439688204867_m_9168463907467690660_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> El dom., 31 mar. 2019 a las 2:02, Jaskirat Singh ()
>> escribió:
>>
>>> Looks great
>>>
>>> On Sun, 31 Mar 2019, 11:23 am Rishabh Thaney, 
>>> wrote:
>>>
 Sounds great!
 Can I please get the course material of the workshop? Would like to
 organise an event like this as well.

 Thanks!

 On Sat, Mar 30, 2019 at 7:59 PM Walter Bender 
 wrote:

> Please see the attached brochure.
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


 --
 Thanks & best regards
 Rishabh Thaney
 +91.999.909.3117
 rishabhtha...@gmail.com
 https://www.linkedin.com/in/rishabhthaney/

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

>>> ___
>>> IAEP -- It's An Education Project (not a laptop project!)
>>> i...@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/iaep
>>
>>
>>
>> --
>>
>>
>>
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
>


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

Re: [Sugar-devel] GSoC Proposal for "New Sugar Activity"

[James Cameron]

Thanks, interesting.  What child age range is the activity designed
for?  I've not yet encountered this science taught at an elementary
age range, but I'm not familiar with all countries.

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

[Sugar-devel] [GSoC'19] Project: Export Music Blocks code to JavaScript

[Mayank]

Hi everyone!
I’m joining a bit late in the game but here I go!
My name is Mayank and I am currently doing B.Tech from JIIT Noida. My
interests in-general are in Software Development, but there are so many
interesting areas out there that I want to explore! I have contributed to
open source projects, and have been part of many Open Source Communities in
Delhi-NCR.
I have looked over the GSoC project 'Export Music Blocks code to
JavaScript' and I am excited to learn and start! The learning curve is
really steep; it is a mighty challenge but I am confident in my skills in
JavaScript and the use of Python, and I do know how to use Version Control,
CI Testing.
I have deployed the project and exploring the code base of Music Blocks and
I don't find any beginner friendly bugs for the first-timer related to the
project. Can you guys help me with some basic bugs to start with?
I would love to continue contributing to SugarLabs in the future as I
totally loved the idea of One Laptop per Child and other Open Source
Projects of the SugarLabs.

Regards,
Mayank
https://gozmit.xyz
https://github.com/im-gozmit/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GSoC Proposal for "New Sugar Activity"

[Chihurumnaya Ibiam]

Hi Manan,

I like the idea but from your proposal you assumed that the student already
knows a bit about molecular biology and the activity aims to help them get
a better understanding of it.

As your proposal states that "the user inputs the PDB code", this is an
assumption that the student already has an idea about molecular biology.

What about a scenario where the student knows nothing about molecular
biology but wants to learn?

On Mon, Apr 1, 2019, 8:58 PM Manan Goel  wrote:

> Hi
> This is my proposal for a New Sugar Activity. Please take a look at it and
> tell me how I could improve it.
> Regards
> Manan Goel
> ___
> 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] Going Through Proposals

[James Cameron]

Perhaps it depends on why you are reading them.

For giving feedback to students as a contributor or member of Sugar
Labs, keep the mailing list messages until you've answered, or use the
mailing list archives if you've lost the messages;

http://lists.sugarlabs.org/archive/sugar-devel/

For the time period between 10th April and 2nd May, the organisation
slot request and project selection, mentors will use the Google Summer
of Code link to the "Final PDF Proposals";

https://summerofcode.withgoogle.com/dashboard/proposals/shared/

I think the above is sufficient.  I don't like adding a Wiki, or
GitHub repository because;

1.  it is unfair on students who have already submitted a proposal, as
we will have moved the goal posts,

2.  it puts proposals now in three places instead of two, making it
harder for students and others to keep these places synchronised.

3.  it isn't mentioned in Google Summer of Code guide to writing a
proposal.  https://google.github.io/gsocguides/student/writing-a-proposal

However, if we have a volunteer to collate all this, and
cross-reference it, and keep it up to date, we can't stop them.  But
requiring the students to do it is not right, as I said above.

On Mon, Apr 01, 2019 at 10:37:01PM +0530, kushagra nigam wrote:
> How about you create a repository with folders (project wise) and ask everyone
> of us to put a pull request of proposals accordingly. You can review the draft
> proposals, comment upon them, and then merge it. 
> 
> On Mon, 1 Apr 2019 at 21:54, Vipul Gupta <[1]vipulgupta2...@gmail.com> wrote:
> 
> The GSoC GitHub page could keep good track of proposal links. Each
> contributor can open an issue with a link to their proposal, so everyone 
> in
> the community can check it out.  
> 
> Cordially, 
> Vipul Gupta 
> [2]Mixster | [3]Github
> 
> On Mon, Apr 1, 2019 at 8:59 PM Sumit Srivastava 
> <[4]sumitsrisu...@gmail.com
> > wrote:
> 
> I propose we should make a wiki.
> 
> We had it in the past, we should do it again.
> 
> On Mon, 1 Apr 2019, 7:36 pm Vaibhav Aren, <[5]vaibhavda...@gmail.com>
> wrote:
> 
> Is there a way to check the proposals on the project wise basis?
> When I Go through mailing list it is very difficult to keep a 
> track
> and reply to the applicant or is going through sugar-devel 
> archives
> the only way?
> 
> Vaibhav Aren
> ___
> Sugar-devel mailing list
> [6]Sugar-devel@lists.sugarlabs.org
> [7]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> ___
> Sugar-devel mailing list
> [8]Sugar-devel@lists.sugarlabs.org
> [9]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> ___
> Sugar-devel mailing list
> [10]Sugar-devel@lists.sugarlabs.org
> [11]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:vipulgupta2...@gmail.com
> [2] https://mixstersite.wordpress.com/
> [3] https://github.com/vipulgupta2048
> [4] mailto:sumitsrisu...@gmail.com
> [5] mailto:vaibhavda...@gmail.com
> [6] mailto:Sugar-devel@lists.sugarlabs.org
> [7] http://lists.sugarlabs.org/listinfo/sugar-devel
> [8] mailto:Sugar-devel@lists.sugarlabs.org
> [9] http://lists.sugarlabs.org/listinfo/sugar-devel
> [10] mailto:Sugar-devel@lists.sugarlabs.org
> [11] http://lists.sugarlabs.org/listinfo/sugar-devel

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


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

Re: [Sugar-devel] [IAEP] April 19th workshop in Kano

[Walter Bender]

I will ask Ahmed for his materials. I know he is also still looking for
input.

regards.

-walter

On Mon, Apr 1, 2019 at 3:20 PM Patricia Escauriza <
pescaur...@paraguayeduca.org> wrote:

> I'd like to do something like that in Paraguay, I would also appreciate
> having the material and details.. regards!
>
> Patty
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_9168463907467690660_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> El dom., 31 mar. 2019 a las 2:02, Jaskirat Singh ()
> escribió:
>
>> Looks great
>>
>> On Sun, 31 Mar 2019, 11:23 am Rishabh Thaney, 
>> wrote:
>>
>>> Sounds great!
>>> Can I please get the course material of the workshop? Would like to
>>> organise an event like this as well.
>>>
>>> Thanks!
>>>
>>> On Sat, Mar 30, 2019 at 7:59 PM Walter Bender 
>>> wrote:
>>>
 Please see the attached brochure.

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

>>>
>>>
>>> --
>>> Thanks & best regards
>>> Rishabh Thaney
>>> +91.999.909.3117
>>> rishabhtha...@gmail.com
>>> https://www.linkedin.com/in/rishabhthaney/
>>>
>>> ___
>>> Sugar-devel mailing list
>>> Sugar-devel@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>> ___
>> IAEP -- It's An Education Project (not a laptop project!)
>> i...@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/iaep
>
>
>
> --
>
>
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


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

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

Re: [Sugar-devel] [IAEP] April 19th workshop in Kano

[Patricia Escauriza]

I'd like to do something like that in Paraguay, I would also appreciate
having the material and details.. regards!

Patty


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

El dom., 31 mar. 2019 a las 2:02, Jaskirat Singh ()
escribió:

> Looks great
>
> On Sun, 31 Mar 2019, 11:23 am Rishabh Thaney, 
> wrote:
>
>> Sounds great!
>> Can I please get the course material of the workshop? Would like to
>> organise an event like this as well.
>>
>> Thanks!
>>
>> On Sat, Mar 30, 2019 at 7:59 PM Walter Bender 
>> wrote:
>>
>>> Please see the attached brochure.
>>>
>>> --
>>> Walter Bender
>>> Sugar Labs
>>> http://www.sugarlabs.org
>>> 
>>> ___
>>> Sugar-devel mailing list
>>> Sugar-devel@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>
>>
>> --
>> Thanks & best regards
>> Rishabh Thaney
>> +91.999.909.3117
>> rishabhtha...@gmail.com
>> https://www.linkedin.com/in/rishabhthaney/
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
> ___
> IAEP -- It's An Education Project (not a laptop project!)
> i...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep



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

[Sugar-devel] suggestions regarding idea and further guidance

[paul hunter]

hi,

I have a following idea which i discussed with Mr. Walter, with his
recommendation I post it here kindly pose your opinions.


*Ideology*: Introducing young students to the problem solving experience
visually though interactive simulations and games.

*Methodology*: The workflow of this application can be distributed in the
following manner:

   1. Initially the plan is to introduce student to the basic concepts of
   programmatic expressions through interactive games, an example of this can
   be found in the doodle released by Google at their 50th Anniversary
   .
   2. The only difference is the ability to carry out the process, we could
   use hand expressions for kids.
   3. Gradually the problem statements can be increased as per the
   education level of the child.



*Outcome*: Children will be more aware and mindful while solving their day
to day problems in a better way.



Though I believe that this task may be challenging to carry out, but with
the guidance of appropriate mentors and with full devotion I believe we can
carry this out.



Looking forward for your intuitive suggestions and further guidance.



Regards

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

Re: [Sugar-devel] Going Through Proposals

[kushagra nigam]

How about you create a repository with folders (project wise) and ask
everyone of us to put a pull request of proposals accordingly. You can
review the draft proposals, comment upon them, and then merge it.

On Mon, 1 Apr 2019 at 21:54, Vipul Gupta  wrote:

> The GSoC GitHub page could keep good track of proposal links. Each
> contributor can open an issue with a link to their proposal, so everyone in
> the community can check it out.
>
> Cordially,
> Vipul Gupta
> Mixster  | Github
> 
>
>
> On Mon, Apr 1, 2019 at 8:59 PM Sumit Srivastava 
> wrote:
>
>> I propose we should make a wiki.
>>
>> We had it in the past, we should do it again.
>>
>> On Mon, 1 Apr 2019, 7:36 pm Vaibhav Aren,  wrote:
>>
>>> Is there a way to check the proposals on the project wise basis?
>>> When I Go through mailing list it is very difficult to keep a track and
>>> reply to the applicant or is going through sugar-devel archives the only
>>> way?
>>>
>>> Vaibhav Aren
>>> ___
>>> 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
>>
> ___
> 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] GSoC Proposal : Sugar Dashboard

[Jaskirat Singh]

Great. It looks good

On Mon, 1 Apr 2019, 9:11 pm Hrishi Patel,  wrote:

> Hello,
> I have attached my proposal for GSoC 2019 for the Sugar Dashboard project.
> Please provide valuable feedback, I would keep improving my proposal.
> Thank you!
> ___
> 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] Going Through Proposals

[Jaskirat Singh]

Mentors on the GSOC dashboard has access to all the proposals at one place.

On Mon, 1 Apr 2019, 8:59 pm Sumit Srivastava, 
wrote:

> I propose we should make a wiki.
>
> We had it in the past, we should do it again.
>
> On Mon, 1 Apr 2019, 7:36 pm Vaibhav Aren,  wrote:
>
>> Is there a way to check the proposals on the project wise basis?
>> When I Go through mailing list it is very difficult to keep a track and
>> reply to the applicant or is going through sugar-devel archives the only
>> way?
>>
>> Vaibhav Aren
>> ___
>> 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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Going Through Proposals

[Vipul Gupta]

The GSoC GitHub page could keep good track of proposal links. Each
contributor can open an issue with a link to their proposal, so everyone in
the community can check it out.

Cordially,
Vipul Gupta
Mixster  | Github



On Mon, Apr 1, 2019 at 8:59 PM Sumit Srivastava 
wrote:

> I propose we should make a wiki.
>
> We had it in the past, we should do it again.
>
> On Mon, 1 Apr 2019, 7:36 pm Vaibhav Aren,  wrote:
>
>> Is there a way to check the proposals on the project wise basis?
>> When I Go through mailing list it is very difficult to keep a track and
>> reply to the applicant or is going through sugar-devel archives the only
>> way?
>>
>> Vaibhav Aren
>> ___
>> 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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Going Through Proposals

[Sumit Srivastava]

I propose we should make a wiki.

We had it in the past, we should do it again.

On Mon, 1 Apr 2019, 7:36 pm Vaibhav Aren,  wrote:

> Is there a way to check the proposals on the project wise basis?
> When I Go through mailing list it is very difficult to keep a track and
> reply to the applicant or is going through sugar-devel archives the only
> way?
>
> Vaibhav Aren
> ___
> 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

[Sugar-devel] Going Through Proposals

[Vaibhav Aren]

Is there a way to check the proposals on the project wise basis?
When I Go through mailing list it is very difficult to keep a track and
reply to the applicant or is going through sugar-devel archives the only
way?

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

Re: [Sugar-devel] GSoC proposal changes

[ANIKET MATHUR]

Thanks for answering and guiding.
I am aware of the obstacles that I might face, also I am aware of the
flexibility of the timeline that might change as the work proceeds.
My timeline is just an approximate idea of how long it might take to
perform tasks in chronological order. To determine that I went through the
previous work done on each task and the work remaining to be done, to make
out approximate figures. I accept that the real difficulties are faced only
once you start working, which might entirely alter my timeline.

Also, I consider it as a possibility and accept it that I might have to
work on things not mentioned in my proposal during the program, like
porting other activities to TelepathyGlib, or other contributions to the
source code essential at that time. I know this is how things work, rather
than sticking to a timeline.

Still, I am not clear about the changes that I have to make, because there
is no such thing as a strict timeline. So do I have to keep my timeline
the same and let my mentors guide me through the work that I have to do
during the program itself?

On Mon, Apr 1, 2019 at 12:50 PM James Cameron  wrote:

> On Sat, Mar 30, 2019 at 03:52:08PM +0530, aniket mathur wrote:
> > James wrote:
> > >  "your timeline has a queue of components in a set order; it is
> > > more likely you'll need to work on all components at once; that's
> > > how it seems to work for me."
> >
> > Suggestion given by @quozl for my timeline. Should I make my
> > timeline as a certain percent of work done on all components
> > together before phase evaluations? Need suggestions. Link to my
> > proposal.
> >
> https://docs.google.com/document/d/1uGwlzPMUG7Z_ZJEloORGc8tEiXs72qLurO-R7GlomsU
>
> Thanks for asking.
>
> No, I don't think a certain percentage could work; how would we
> measure?
>
> Consider the varying purposes of a timeline;
>
> 1.  so that we can see the weeks you'll be working,
>
> 2.  so that you'll have something that can be assessed during
> evaluations, something that is working and 90% done by midterm,
>
> 3.  so that we can see you've thought about the size of the work,
>
> 4.  so that we can see if you have iterated into estimates of
> subtasks,
>
> Also, the timeline is not going to be kept as-is; you and your mentors
> will adjust the timeline during the project.  When a timeline is not
> adjusted, that usually means mentors and student are not paying
> attention to the timeline.  In my experience an unadjusted timeline is
> a reliable sign of impending failure.
>
> Implementation mistakes of working with timelines that I've seen are;
>
> - stopping work when you've no idea how to proceed, and you have to
>   ask questions of mentors, or other project teams; you must have
>   something else to work on while you wait for an answer,
>
> - not working on next week's tasks when something takes a shorter time
>   than expected; the spare time should be used,
>
> - moving on to a different task when a task is not finished; can be
>   fatal to a project when there are task dependencies.
>
> See also Google Summer of Code - Student Guide - Writing a proposal,
> https://google.github.io/gsocguides/student/writing-a-proposal which
> does not talk about timelines.  There's an early paragraph about time
> management.
>
> Now, your timeline seems to follow the "Project Task Checklist" in the
> idea.  We put that checklist there because those tasks have a somewhat
> forward dependency.  But there are some traps in using that checklist
> as a timeline.  Many of those tasks may stall for one reason or
> another outside your control.  Some of them are ill-defined; for
> example the port to TelepathyGLib is needed eventually for all
> activities, but only the Fructose set are to be ported by your
> project, so that suggests only the Fructose set and the Toolkit should
> be ported to TelepathyGLib.
>
> So a good timeline will depend on planning of the tasks, and that may
> in turn depend on good estimates.  An invaluable input to estimating
> software effort is to try to use the software or cobble together a
> minimum viable prototype.  I know what sort of traps you would hit if
> you tried that.
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> 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] GSoC proposal changes

[James Cameron]

On Sat, Mar 30, 2019 at 03:52:08PM +0530, aniket mathur wrote:
> James wrote:
> >  "your timeline has a queue of components in a set order; it is
> > more likely you'll need to work on all components at once; that's
> > how it seems to work for me."
> 
> Suggestion given by @quozl for my timeline. Should I make my
> timeline as a certain percent of work done on all components
> together before phase evaluations? Need suggestions. Link to my
> proposal.
> https://docs.google.com/document/d/1uGwlzPMUG7Z_ZJEloORGc8tEiXs72qLurO-R7GlomsU

Thanks for asking.

No, I don't think a certain percentage could work; how would we
measure?

Consider the varying purposes of a timeline;

1.  so that we can see the weeks you'll be working,

2.  so that you'll have something that can be assessed during
evaluations, something that is working and 90% done by midterm,

3.  so that we can see you've thought about the size of the work,

4.  so that we can see if you have iterated into estimates of
subtasks,

Also, the timeline is not going to be kept as-is; you and your mentors
will adjust the timeline during the project.  When a timeline is not
adjusted, that usually means mentors and student are not paying
attention to the timeline.  In my experience an unadjusted timeline is
a reliable sign of impending failure.

Implementation mistakes of working with timelines that I've seen are;

- stopping work when you've no idea how to proceed, and you have to
  ask questions of mentors, or other project teams; you must have
  something else to work on while you wait for an answer,

- not working on next week's tasks when something takes a shorter time
  than expected; the spare time should be used,

- moving on to a different task when a task is not finished; can be
  fatal to a project when there are task dependencies.

See also Google Summer of Code - Student Guide - Writing a proposal,
https://google.github.io/gsocguides/student/writing-a-proposal which
does not talk about timelines.  There's an early paragraph about time
management.

Now, your timeline seems to follow the "Project Task Checklist" in the
idea.  We put that checklist there because those tasks have a somewhat
forward dependency.  But there are some traps in using that checklist
as a timeline.  Many of those tasks may stall for one reason or
another outside your control.  Some of them are ill-defined; for
example the port to TelepathyGLib is needed eventually for all
activities, but only the Fructose set are to be ported by your
project, so that suggests only the Fructose set and the Toolkit should
be ported to TelepathyGLib.

So a good timeline will depend on planning of the tasks, and that may
in turn depend on good estimates.  An invaluable input to estimating
software effort is to try to use the software or cobble together a
minimum viable prototype.  I know what sort of traps you would hit if
you tried that.

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