Re: [Sugar-devel] happy birthday Sugar Labs

[ANIKET MATHUR]

拾拾拾

On Fri, 15 May, 2020, 7:20 pm Vaibhav Aren,  wrote:

> ^_^
>
> On Fri, May 15, 2020 at 6:07 PM Walter Bender 
> wrote:
>
>> :)
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal Review Request

[ANIKET MATHUR]

Hii Ayush nawal,

Though I am not one of the mentors for Sugar Labs this year,  but as a
general information Google has updated the timeline , you must have
received a mail for that, please make that changes in your proposal.

For technical guidance, wait for other mentors they will review your
proposal soon :-)

Thanks,
Regards,
Aniket

On Sat, 21 Mar, 2020, 10:13 pm ayush nawal,  wrote:

> G'day,
>
> Sharing my project proposal for Improve and Maintain 25 Sugar Activities.
>
> Followed the Sugar Labs template on GitHub and posted the proposal on
> GSoC's dashboard too.
>
> Requesting for a review.  Any suggestions will be helpful.
>
> Thanks and regards
> Ayush
> ___
> 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] Sugar Labs has been accepted into GSoC 2020

[ANIKET MATHUR]

Great! Congratulations 

On Thu, 20 Feb, 2020, 10:37 pm Walter Bender, 
wrote:

> Details to follow.
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.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] Regarding Stand at FOSDEM [1-2 February]

[ANIKET MATHUR]

G'day everyone,
Being an active contributor to Sugar Labs for almost a year and an
open-source enthusiast, it would be a great opportunity for me to
participate in FOSDEM from Sugar Labs.
I would love to know how I can make it happen. What is expected from me and
what help can I get from Sugar Labs?

Thanks,
Regards,
Aniket Mathur

On Wed, Dec 4, 2019 at 12:23 PM James Cameron  wrote:

> Hello Shubhika,
>
> Sugar Labs has roughly $85 to $90k USD in cash, with most income
> arising from Google Summer of Code and Google Code-in.  The oversight
> board is responsible for allocating the cash, and we have tended to
> focus on things that have a clear return on investment.
>
> So funding would depend on what you plan to do for Sugar Labs, based
> largely on what you have previously done for Sugar Labs.
>
> However, you can certainly get involved in conferences, design,
> coding, and fixing without funding.
>
> On Wed, Dec 04, 2019 at 12:09:29PM +0530, Shubhika Bhardwaj wrote:
> > Hi everyone!
> > I am Shubhika Bhardwaj. I am been a part of the SugarLabs community for a
> > while.I am begining my journey in open source.
> >
> > Can the students contributers from the SugarLabs participate in FOSDEM?
> >
> > Is there a scholarship or travel reimbursement for FOSDEM?
>
> > ___
> > 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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Request for Wiki Account

[ANIKET MATHUR]

G'day Utkarsh

Please write an email to "syst...@lists.sugarlabs.org" requesting a new
wiki account with a username of your choice and an email address.
Then sign in with that account to edit the page.

On Sat, Nov 2, 2019 at 5:25 PM Utkarsh Raj Singh 
wrote:

> Greetings,
>
> I wanted to extend my candidature for Mentorship at GCI 2019 with
> Sugarlabs. I have been a long term contributor with the Sugarizer Project,
> and looking forward to the opportunity to help new members and make the
> community stronger in the GCI.
>
> I can help with Coding, Testing, Research and Documentation. Can you
> please guide to the further steps ? How do I get the access to Wiki and add
> my name ?
>
> Regards,
> Utkarsh Raj Singh
> ___
> 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] [IAEP] Google Code-in 2019

[ANIKET MATHUR]

Thanks, I just sent an email to syst...@lists.sugarlabs.org, requesting a
new account :-)

On Sat, Nov 2, 2019 at 2:26 AM Sumit Srivastava 
wrote:

> Yes, Aniket!
>
> On Sat, Nov 2, 2019, 2:19 AM ANIKET MATHUR  wrote:
>
>> G'day everyone,
>>
>> I wish to mentor GCI 2019 for Sugar Labs. I have a query about how to add
>> my name to the mentor list on the wiki page,
>> do I need a Sugar Labs wiki account for that?
>>
>> Thanks!
>>
>> On Wed, Oct 30, 2019 at 9:23 PM Euan Ong  wrote:
>>
>>> Dear Walter,
>>>
>>> Great to see Sugar Labs has been accepted for GCI 2019 :) I'd definitely
>>> be interested in mentoring this year.
>>>
>>> Best regards,
>>> Euan
>>>
>>> On Thu, 10 Oct 2019 at 22:56, Walter Bender 
>>> wrote:
>>>
>>>> I've begun putting together our application to GCI 2019. And I have
>>>> created a page in the wiki with background information [2]
>>>>
>>>> If you are interested in mentoring, please let me know (and add your
>>>> name to the list at the bottom of the wiki page.). Please indicate what
>>>> areas you wish to help with (coding, design, research, documentation, and
>>>> QA) and relevant experience in the Sugar Labs community.
>>>>
>>>> Looking forward to GCI.
>>>>
>>>> regards.
>>>>
>>>> -walter
>>>>
>>>> [1] https://codein.withgoogle.com/
>>>> [2] https://wiki.sugarlabs.org/go/Google_Code_In_2019
>>>>
>>>> --
>>>> Walter Bender
>>>> Sugar Labs
>>>> http://www.sugarlabs.org
>>>> <http://www.sugarlabs.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
>>>
>> ___
>> 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

Re: [Sugar-devel] Google Code-in 2019

[ANIKET MATHUR]

G'day everyone,

I wish to mentor GCI 2019 for Sugar Labs. I have a query about how to add
my name to the mentor list on the wiki page,
do I need a Sugar Labs wiki account for that?

Thanks!

On Wed, Oct 30, 2019 at 9:23 PM Euan Ong  wrote:

> Dear Walter,
>
> Great to see Sugar Labs has been accepted for GCI 2019 :) I'd definitely
> be interested in mentoring this year.
>
> Best regards,
> Euan
>
> On Thu, 10 Oct 2019 at 22:56, Walter Bender 
> wrote:
>
>> I've begun putting together our application to GCI 2019. And I have
>> created a page in the wiki with background information [2]
>>
>> If you are interested in mentoring, please let me know (and add your name
>> to the list at the bottom of the wiki page.). Please indicate what areas
>> you wish to help with (coding, design, research, documentation, and QA) and
>> relevant experience in the Sugar Labs community.
>>
>> Looking forward to GCI.
>>
>> regards.
>>
>> -walter
>>
>> [1] https://codein.withgoogle.com/
>> [2] https://wiki.sugarlabs.org/go/Google_Code_In_2019
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GCI 2019

[ANIKET MATHUR]

Congrats, that's great

On Tue, 29 Oct 2019, 10:42 pm Amaan Iqbal,  wrote:

> Amazing!
> Congratulations to us!
>
> On Oct 29, 2019 10:39 PM, "Jaskirat Singh"  wrote:
>
>> Awesome.
>>
>> On Tue, 29 Oct 2019, 10:37 pm Walter Bender, 
>> wrote:
>>
>>> Sugar Labs has been selected as a Google Code-in 2019 mentor
>>> organization.
>>> I'll send some details this evening.
>>>
>>> regards.
>>>
>>> -walter
>>>
>>> --
>>> Walter Bender
>>> Sugar Labs
>>> http://www.sugarlabs.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
>>
>> ___
> 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] [IAEP] Google Code-in 2019

[ANIKET MATHUR]

Hello everyone,

I am Aniket Mathur, an undergraduate student at the Indian Institute of
Technology, Roorkee.

I would like to be a mentor for Google Code-in 2019 for Sugar Labs, and
interested in areas of coding and documentation. I am contributing to Sugar
Labs since December 2018,
I was also a GSoC participant for Sugar Labs with Port to Python 3 project
this year. Now looking forward to contribute as a mentor.

Link <http://aniketmathur.me/assets/documents/resume.pdf> to my resume.

Thanks,
Regards
Aniket Mathur



On Fri, Oct 11, 2019 at 8:46 PM Samson Goddy  wrote:

> Excited to hear that we are applying this year. I am interested to be a
> mentor this year.
>
>
> Regards
>
> On Fri, Oct 11, 2019 at 4:12 PM Samson Goddy 
> wrote:
>
>> Excited to hear that we are applying this year. I am interested to be a
>> mentor this year.
>>
>>
>> Regards
>>
>> On Fri, Oct 11, 2019 at 3:04 PM Rishabh Thaney 
>> wrote:
>>
>>> Awesome!
>>> Was looking forward to this, would love to mentor again
>>>
>>> On Fri, 11 Oct 2019 at 7:31 PM, Arnav Mandal 
>>> wrote:
>>>
>>>> Hello everyone!
>>>>
>>>> I hope you all are doing well. I would love to mentor sugar labs for
>>>> GCI'19.
>>>>
>>>> As a brief introduction of myself, I am a final year student from
>>>> India. I was a GSoC'19 student with AboutCode. I have worked with Amazon
>>>> and Directi as well as a software developer.
>>>> I have been a part of organizations such as Fossasia, JgraphT and
>>>> Coala. From the past few months, I have been regularly taking part in the
>>>> Sugar Labs discussion.
>>>>
>>>> Please let me know how to start contributing to Sugar Labs as a mentor
>>>> for GCI'19.
>>>>
>>>> Regards,
>>>> Arnav Mandal
>>>>
>>>>
>>>> On Fri, Oct 11, 2019 at 7:19 PM Vaibhav Aren 
>>>> wrote:
>>>>
>>>>> +1. I am excited to mentor again.
>>>>> Did someone export last year's tasks?
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Oct 11, 2019 at 3:36 AM Sumit Srivastava <
>>>>> sumitsrisu...@gmail.com> wrote:
>>>>>
>>>>>> Yay! All the best to everyone involved with the ambitious mission of
>>>>>> Sugar Labs!
>>>>>>
>>>>>> Regards
>>>>>> Sumit
>>>>>>
>>>>>> On Fri, Oct 11, 2019, 3:25 AM Walter Bender 
>>>>>> wrote:
>>>>>>
>>>>>>> I've begun putting together our application to GCI 2019. And I have
>>>>>>> created a page in the wiki with background information [2]
>>>>>>>
>>>>>>> If you are interested in mentoring, please let me know (and add your
>>>>>>> name to the list at the bottom of the wiki page.). Please indicate what
>>>>>>> areas you wish to help with (coding, design, research, documentation, 
>>>>>>> and
>>>>>>> QA) and relevant experience in the Sugar Labs community.
>>>>>>>
>>>>>>> Looking forward to GCI.
>>>>>>>
>>>>>>> regards.
>>>>>>>
>>>>>>> -walter
>>>>>>>
>>>>>>> [1] https://codein.withgoogle.com/
>>>>>>> [2] https://wiki.sugarlabs.org/go/Google_Code_In_2019
>>>>>>>
>>>>>>> --
>>>>>>> Walter Bender
>>>>>>> Sugar Labs
>>>>>>> http://www.sugarlabs.org
>>>>>>> <http://www.sugarlabs.org>
>>>>>>> ___
>>>>>>> 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 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
>>>>
>>> --
>>> Thanks & best regards
>>> Rishabh Thaney
>>> +91.999.909.3117
>>> rishabhtha...@gmail.com
>>> https://www.linkedin.com/in/rishabhthaney/
>>>
>>> ___
>>> IAEP -- It's An Education Project (not a laptop project!)
>>> i...@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/iaep
>>>
>>
>>
>> --
>> ---
>> Oversight Board Member at Sugar Labs
>>
>
>
> --
>
> Samson Goddy
>
> Twitter: https://twitter.com/samson_goddy
> Email: samsongo...@sugarlabs.org
> samsongo...@gmail.com
>
> Website: https://samsongoddy.me/  <https://www.sugarlabs.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] GCI 2019 Announced

[ANIKET MATHUR]

Awesome! Great to hear it.


On Tue, 24 Sep 2019, 10:11 pm Rishabh Thaney, 
wrote:

> Awesome, glad to hear the news!
>
> On Tue, 24 Sep 2019 at 2:43 AM, Walter Bender 
> wrote:
>
>>
>>
>> On Mon, Sep 23, 2019 at 4:35 PM Freddie N 
>> wrote:
>>
>>> Hi everyone,
>>>
>>> Google Code-In 2019 has now been officially announced running from 2nd
>>> December to 23rd January.
>>>
>>
>> Orgs can begin applying on Oct. 10.
>>
>>>
>>> Read more here:
>>> https://opensource.googleblog.com/2019/09/google-code-in-2019-is-right-around_23.html
>>>
>>> The dates are even later this year.
>>>
>>> It has been very successful at encouraging open source within Sugar Labs
>>> for many years with contributors still around from the first year we
>>> entered.
>>>
>>> Freddie
>>> ___
>>> 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
>>
> --
> 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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Google Code-in-2019

[ANIKET MATHUR]

G'day everyone,

I am Aniket, an undergraduate at IIT Roorkee, I had my GSoC with Sugar Labs
and contributing to the organisation since December 2018.

I would like to be a mentor for Google Code-in 2019 for Sugar Labs. It
would be great if I get this opportunity.

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

Re: [Sugar-devel] could be a nice opportunity for Sugar

[ANIKET MATHUR]

Seems awesome!

On Tue, 3 Sep 2019, 11:05 am Samson Goddy,  wrote:

> Great. Exciting news.
>
> On Tue, Sep 3, 2019, 1:56 AM Walter Bender 
> wrote:
>
>>
>> https://www.aboutchromebooks.com/news/crostini-linux-for-chromebooks-distro-menu-debian-fedora-ubuntu/
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] New User

[ANIKET MATHUR]

Welcome. Also, please have a look at our guide

for contributing.

On Thu, Aug 15, 2019 at 7:46 AM James Cameron  wrote:

> Welcome.  What do you think of Sugar?
>
> On Wed, Aug 14, 2019 at 08:27:31PM +0530, amey bhosle wrote:
> > Hello I am new to this community how can I start contribute to this
> > organization.
>
> --
> 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] Error on running sugar-activity

[ANIKET MATHUR]

Swarup, what is the order of installation you followed for datastore, sugar
and sugar-toolkit?

I am not much sure about it but it might be related.

Thanks.

On Wed, 31 Jul 2019, 3:55 pm James Cameron,  wrote:

> The datastore process failed.  Look in datastore.log for more
> information.
>
> Datastore is started by Sugar through D-Bus API, and would normally
> continue operating until Sugar is stopped.  If it fails before an
> activity is started, then the activity call through the D-Bus API will
> restart the datastore.  The traceback you pasted shows this has
> happened, and then the datastore failed again.
>
> Check the D-Bus service file created by the datastore source.  It may
> refer to the wrong path for the binary.
>
> On Wed, Jul 31, 2019 at 10:21:48AM +0530, Swarup N wrote:
> > Hi,
> > I setup Sugar 0.114 via the Native method on a new laptop. On running
> > sugar-activity, I get the following message.
> >
> > Traceback (most recent call last):
> >   File "/usr/local/bin/sugar-activity", line 5, in 
> > activityinstance.main()
> >   File "/usr/local/lib/python2.7/dist-packages/sugar3/activity/
> > activityinstance.py", line 230, in main
> > instance = create_activity_instance(activity_constructor,
> activity_handle)
> >   File "/usr/local/lib/python2.7/dist-packages/sugar3/activity/
> > activityinstance.py", line 59, in create_activity_instance
> > activity = constructor(handle)
> >   File "/home/buba/sugar-stuff/sugar-activities/convert/activity.py",
> line 41,
> > in __init__
> > activity.Activity.__init__(self, handle, True)
> >   File
> "/usr/local/lib/python2.7/dist-packages/sugar3/activity/activity.py",
> > line 432, in __init__
> > self._jobject = self._initialize_journal_object()
> >   File
> "/usr/local/lib/python2.7/dist-packages/sugar3/activity/activity.py",
> > line 520, in _initialize_journal_object
> > datastore.write(jobject)
> >   File
> "/usr/local/lib/python2.7/dist-packages/sugar3/datastore/datastore.py",
> > line 394, in write
> > transfer_ownership)
> >   File
> "/usr/local/lib/python2.7/dist-packages/sugar3/datastore/datastore.py",
> > line 344, in _create_ds_entry
> > object_id = _get_data_store().create(dbus.Dictionary(properties),
> filename,
> >   File
> "/usr/local/lib/python2.7/dist-packages/sugar3/datastore/datastore.py",
> > line 51, in _get_data_store
> > DS_DBUS_PATH),
> >   File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in
> get_object
> > follow_name_owner_changes=follow_name_owner_changes)
> >   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in
> > __init__
> > self._named_service = conn.activate_name_owner(bus_name)
> >   File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in
> > activate_name_owner
> > self.start_service_by_name(bus_name)
> >   File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in
> > start_service_by_name
> > 'su', (bus_name, flags)))
> >   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651,
> in
> > call_blocking
> > message, timeout)
> > dbus.exceptions.DBusException:
> org.freedesktop.DBus.Error.Spawn.ChildExited:
> > Process org.laptop.sugar.DataStore exited with status 1
> > 1564548420.435550 WARNING root: DSObject was deleted without cleaning up
> first.
> > Call DSObject.destroy() before disposing it.
> >
> > I would be grateful for any suggestions on fixing this.
> >
> > Thanks.
>
> --
> 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] [FEATURE] Separate python version packages for sugar-toolkit-gtk3

[ANIKET MATHUR]

G'day Sukhdeep,
You have removed the packages repository from your github. I would be happy
to analyze those packages.
Also would you please tell how you proceeded?

Thanks!

On Tue, Jul 23, 2019 at 2:58 PM James Cameron  wrote:

> On Tue, Jul 23, 2019 at 01:02:33PM +0530, sukhdeep gill wrote:
> > Python packages:
> > https://github.com/sukhdeepg/sugar-toolkit-gtk3-python-packages.
> > This is the first step with respect to an earlier reply from James
> > Cameron. I've understood the depth of the issue from this result
> > after the Debian bug 931666 search. If this isn't the right way,
> > please let me know.
>
> Thanks.  Happy to review.  The main problem is that you did not
> examine the packages, compare them with Debian packages, or test the
> packages.
>
> (a) your package version should include something to discriminate
> against potential Debian packages yet to be provided by Debian
> developers, or packages by other Sugar Labs developers,
>
> (b) your package version should include the git hash; the file
> src/sugar3/util.py has the latest HEAD of 5043d53, but the version of
> your packages is 0.114-1,
>
> (c) your package python-sugar3_0.114-1_all.deb includes a Python 3
> program (sugar-activity3) and Python 2 artefacts in
> /usr/lib/python2.7/dist-packages/sugar3 ... but sugar-activity3 should
> not be present, and this is a fault of our build in
> sugar-toolkit-gtk3,
>
> (d) your package python-sugar3_0.114~python3-1_all.deb includes a
> Python 2 program (sugar-activity) and Python 2 artefacts in
> /usr/lib/python2.7/dist-packages/sugar3 ... but sugar-activity should
> not be present (this is a fault of our build in sugar-toolkit-gtk3)
> and the artefacts should be for Python 3 not Python 2,
>
> (e) both packages are named python-sugar3 ... but they should have
> different names (python-sugar3 and python3-sugar3), so they can be
> installed at the same time.
>
> Please do examine the packages and test them carefully before
> publishing your work.  Test by installing the packages and running
> Sugar and the set of Fructose (core) activities.
>
> Hope that helps!
>
> --
> 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] Multiversion Packages of toolkit.

[ANIKET MATHUR]

Agreed. I am working on this, still not able to get something fruitfull.

Thanks!

On Tue, Jul 9, 2019 at 12:53 PM James Cameron  wrote:

> configure does not accept --with, so it must be something specific to
> debhelper.
>
> On Tue, Jul 09, 2019 at 05:19:15PM +1000, James Cameron wrote:
> > Only if it will work.  Demonstrate that if you wish.
> >
> > It is not much different already.  It's not the problem; the problem
> > is the packaging directory; debian/rules and debian/control,
> > especially for anyone wishing to package 0.114 which won't have the
> > change.
> >
> > As you will have seen;
> >
> > 1.  sugar-toolkit-gtk3 calls AM_PATH_PYTHON for selected version
> > passed in from command line arguments, either --with-python2 or
> > --with-python3.
> >
> > 2.  dbus-python calls AM_PATH_PYTHON without version.  When --with
> > python3 is added, an AM_CONDITIONAL checks the version is not less
> > than '3'.  debian/rules calls configure --with python2,python3
> >
> > 3.  gyoto debian/rules calls configure --with python2,python3
> >
> > autoconf support for multiple Python versions seems to have matured,
> > and "--with python2,python3" is a common way to configure in Debian
> > packaging (462 package samples).
> >
> > On Tue, Jul 09, 2019 at 12:21:50PM +0530, ANIKET MATHUR wrote:
> > > Yes, Agreed. It would not be good if we configure the toolkit for only
> one
> > > version of Python.
> > > May we change our [1]configure.ac as gyoto and dbus-python and then
> try?
> > >
> > > Thanks!
> > >
> > > On Tue, Jul 9, 2019 at 12:18 PM ANIKET MATHUR <[2]
> amat...@ec.iitr.ac.in> wrote:
> > >
> > > Thanks for reminding.
> > >
> > > That's what I have got to track progress
> > > [3]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931666
> > >
> > > On Tue, Jul 9, 2019 at 12:15 PM James Cameron <[4]qu...@laptop.org>
> wrote:
> > >
> > > Debian's bug tracking system should send you a bug number by
> e-mail.
> > >
> > > Without that number, few others will be able to see progress or
> > > outcome.
> > >
> > > On Tue, Jul 09, 2019 at 08:40:17AM +0530, ANIKET MATHUR wrote:
> > > > Reported the problem as a bug to Debian using the reportbug
> program.
> > > >
> > > > Thanks!
> > > >
> > > > On Fri, Jul 5, 2019 at 8:22 PM ANIKET MATHUR <[1][5]
> > > amat...@ec.iitr.ac.in> wrote:
> > > >
> > > > Sent the email to [2][6]debian-de...@lists.debian.org
> as well.
> > > >
> > > > On Fri, Jul 5, 2019 at 4:13 PM ANIKET MATHUR <[3][7]
> > > amat...@ec.iitr.ac.in>
> > > > wrote:
> > > >
> > > > Sent an email to the Debian user mailing list [4]
> > > > [8]debian-u...@lists.debian.org requesting for
> packaging
> > > v0.114.
> > > >
> > > > Packaging of Sugar-toolkit-gtk3 (sugar3) v0.114.
> > > >
> > > > [profile_ma]
> > > > ANIKET MATHUR <[5]4:10 PM (2
> minutes
> > > > [9]amat...@ec.iitr.ac.in>ago)
>
> > >[cleardot]
> > > >
>
> > > [cleardot]
> > > > to debian-user
> > > > [cleardot]
> > > > G'day,
> > > > Aniket Mathur this side, an active contributor of
> Sugarlabs
> > > as well as
> > > > a GSoC 19 participant. This mail is a small query
> regarding
> > > the
> > > > packaging of "sugar3" module.
> > > >
> > > > We currently have v0.112 packaged. In the latest
> version
> > > (0.114)
> > > > Sugarlabs have made the toolkit compatible with both
> Python
> > > and Python
> > > > 3. But we don't have Debian multi-version packages
> for the
> > > latest
> > > > version. This prevents us to scale our testing as
> well as
> > > limits the
> > > >  

Re: [Sugar-devel] Multiversion Packages of toolkit.

[ANIKET MATHUR]

Yes, Agreed. It would not be good if we configure the toolkit for only one
version of Python.
May we change our configure.ac as gyoto and dbus-python and then try?

Thanks!

On Tue, Jul 9, 2019 at 12:18 PM ANIKET MATHUR  wrote:

> Thanks for reminding.
>
> That's what I have got to track progress
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931666
>
> On Tue, Jul 9, 2019 at 12:15 PM James Cameron  wrote:
>
>> Debian's bug tracking system should send you a bug number by e-mail.
>>
>> Without that number, few others will be able to see progress or
>> outcome.
>>
>> On Tue, Jul 09, 2019 at 08:40:17AM +0530, ANIKET MATHUR wrote:
>> > Reported the problem as a bug to Debian using the reportbug program.
>> >
>> > Thanks!
>> >
>> > On Fri, Jul 5, 2019 at 8:22 PM ANIKET MATHUR <[1]amat...@ec.iitr.ac.in>
>> wrote:
>> >
>> > Sent the email to [2]debian-de...@lists.debian.org as well.
>> >
>> > On Fri, Jul 5, 2019 at 4:13 PM ANIKET MATHUR <[3]
>> amat...@ec.iitr.ac.in>
>> > wrote:
>> >
>> > Sent an email to the Debian user mailing list [4]
>> > debian-u...@lists.debian.org requesting for packaging v0.114.
>> >
>> > Packaging of Sugar-toolkit-gtk3 (sugar3) v0.114.
>> >
>> > [profile_ma]
>> > ANIKET MATHUR <[5]4:10 PM (2 minutes
>> > amat...@ec.iitr.ac.in>ago)
>>  [cleardot]
>> >
>> [cleardot]
>> > to debian-user
>> > [cleardot]
>> > G'day,
>> > Aniket Mathur this side, an active contributor of Sugarlabs as
>> well as
>> > a GSoC 19 participant. This mail is a small query regarding the
>> > packaging of "sugar3" module.
>> >
>> > We currently have v0.112 packaged. In the latest version (0.114)
>> > Sugarlabs have made the toolkit compatible with both Python and
>> Python
>> > 3. But we don't have Debian multi-version packages for the
>> latest
>> > version. This prevents us to scale our testing as well as
>> limits the
>> > number of testers.
>> >
>> > We don't know how to make multi-version local packages, that we
>> can
>> > distribute for testing.
>> >
>> > It would be good if we have Debian packages for v 0.114.
>> >
>> > Need Help.
>> > Regards.
>> >
>> > On Tue, Jul 2, 2019 at 12:02 PM ANIKET MATHUR <[6]
>> amat...@ec.iitr.ac.in
>> > > wrote:
>> >
>> > Yes, I was asking about Debian packages. Sorry for
>> incomplete
>> > information.
>> >
>> > I read sources of some Debian packages:-
>> > ~ They do use six for keeping multi-version compatibility.
>> > ~ Instead of a [7]configure.ac, they use setup.py.
>> > ~ In setup.py, they define entry-points as per the commands
>> from
>> > the command line specifying python-foo or python3-foo.
>> >
>> > I also did a github search for 'python [8]configure.ac' ,
>> looked
>> > into a considerable amount of commits of different users and
>> > organizations with the motive of "why don't we ask for help
>> from
>> > those who seems to be successful in doing it".
>> >
>> > From my research, I found out that the guys at "balabit"
>> seems to
>> > be able to do it.
>> > I opened an [9]issue asking for help and clearance.
>> >
>> > The next step is to contact the Debian developers.
>> >
>> > Thanks!
>> >
>> > On Mon, Jul 1, 2019 at 5:21 AM James Cameron <[10]
>> qu...@laptop.org>
>> > wrote:
>> >
>> > You neglected to mention that you are asking about
>> Debian and
>> > Ubuntu
>> > binary packages.  Ubuntu packages come from Debian
>> unchanged,
>> > so your
>> > question can be reduced to Debian packaging.
>> >
>> > We're the wrong people to ask.  It's not a skill any of
>> us at
>> > Sugar
>> &

Re: [Sugar-devel] Multiversion Packages of toolkit.

[ANIKET MATHUR]

Thanks for reminding.

That's what I have got to track progress
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931666

On Tue, Jul 9, 2019 at 12:15 PM James Cameron  wrote:

> Debian's bug tracking system should send you a bug number by e-mail.
>
> Without that number, few others will be able to see progress or
> outcome.
>
> On Tue, Jul 09, 2019 at 08:40:17AM +0530, ANIKET MATHUR wrote:
> > Reported the problem as a bug to Debian using the reportbug program.
> >
> > Thanks!
> >
> > On Fri, Jul 5, 2019 at 8:22 PM ANIKET MATHUR <[1]amat...@ec.iitr.ac.in>
> wrote:
> >
> > Sent the email to [2]debian-de...@lists.debian.org as well.
> >
> > On Fri, Jul 5, 2019 at 4:13 PM ANIKET MATHUR <[3]
> amat...@ec.iitr.ac.in>
> > wrote:
> >
> > Sent an email to the Debian user mailing list [4]
> > debian-u...@lists.debian.org requesting for packaging v0.114.
> >
> > Packaging of Sugar-toolkit-gtk3 (sugar3) v0.114.
> >
> > [profile_ma]
> > ANIKET MATHUR <[5]4:10 PM (2 minutes
> > amat...@ec.iitr.ac.in>ago)
>  [cleardot]
> >
> [cleardot]
> > to debian-user
> > [cleardot]
> > G'day,
> > Aniket Mathur this side, an active contributor of Sugarlabs as
> well as
> > a GSoC 19 participant. This mail is a small query regarding the
> > packaging of "sugar3" module.
> >
> > We currently have v0.112 packaged. In the latest version (0.114)
> > Sugarlabs have made the toolkit compatible with both Python and
> Python
> > 3. But we don't have Debian multi-version packages for the latest
> > version. This prevents us to scale our testing as well as limits
> the
> > number of testers.
> >
> > We don't know how to make multi-version local packages, that we
> can
> > distribute for testing.
> >
> > It would be good if we have Debian packages for v 0.114.
> >
> > Need Help.
> > Regards.
> >
> > On Tue, Jul 2, 2019 at 12:02 PM ANIKET MATHUR <[6]
> amat...@ec.iitr.ac.in
> > > wrote:
> >
> > Yes, I was asking about Debian packages. Sorry for incomplete
> > information.
> >
> > I read sources of some Debian packages:-
> > ~ They do use six for keeping multi-version compatibility.
> > ~ Instead of a [7]configure.ac, they use setup.py.
> > ~ In setup.py, they define entry-points as per the commands
> from
> > the command line specifying python-foo or python3-foo.
> >
> > I also did a github search for 'python [8]configure.ac' ,
> looked
> > into a considerable amount of commits of different users and
> > organizations with the motive of "why don't we ask for help
> from
> > those who seems to be successful in doing it".
> >
> > From my research, I found out that the guys at "balabit"
> seems to
> > be able to do it.
> > I opened an [9]issue asking for help and clearance.
> >
> > The next step is to contact the Debian developers.
> >
> > Thanks!
> >
> > On Mon, Jul 1, 2019 at 5:21 AM James Cameron <[10]
> qu...@laptop.org>
> > wrote:
> >
> > You neglected to mention that you are asking about
> Debian and
> > Ubuntu
> > binary packages.  Ubuntu packages come from Debian
> unchanged,
> > so your
> > question can be reduced to Debian packaging.
> >
> > We're the wrong people to ask.  It's not a skill any of
> us at
> > Sugar
> > Labs have, otherwise we would have done it by now.
> >
> > The people who know how to do this are Debian and Ubuntu
> > package
> > developers.
> >
> > I've tried asking one of the Debian developers but they
> were
> > too busy
> > to give private assistance.  Private assistance does not
> scale,
> > so the
> > return on investment is meagre.
> >
> > I suggest you try these things;
> >
> > 1.  write a throw-away script 

Re: [Sugar-devel] Multiversion Packages of toolkit.

[ANIKET MATHUR]

Reported the problem as a bug to Debian using the reportbug program.

Thanks!

On Fri, Jul 5, 2019 at 8:22 PM ANIKET MATHUR  wrote:

> Sent the email to debian-de...@lists.debian.org as well.
>
> On Fri, Jul 5, 2019 at 4:13 PM ANIKET MATHUR 
> wrote:
>
>> Sent an email to the Debian user mailing list
>> debian-u...@lists.debian.org requesting for packaging v0.114.
>>
>> Packaging of Sugar-toolkit-gtk3 (sugar3) v0.114.
>> ANIKET MATHUR 
>> 4:10 PM (2 minutes ago)
>> to debian-user
>> G'day,
>> Aniket Mathur this side, an active contributor of Sugarlabs as well as a
>> GSoC 19 participant. This mail is a small query regarding the packaging of
>> "sugar3" module.
>>
>> We currently have v0.112 packaged. In the latest version (0.114)
>> Sugarlabs have made the toolkit compatible with both Python and Python 3.
>> But we don't have Debian multi-version packages for the latest version.
>> This prevents us to scale our testing as well as limits the number of
>> testers.
>>
>> We don't know how to make multi-version local packages, that we can
>> distribute for testing.
>>
>> It would be good if we have Debian packages for v 0.114.
>>
>> Need Help.
>> Regards.
>>
>> On Tue, Jul 2, 2019 at 12:02 PM ANIKET MATHUR 
>> wrote:
>>
>>> Yes, I was asking about Debian packages. Sorry for incomplete
>>> information.
>>>
>>> I read sources of some Debian packages:-
>>> ~ They do use six for keeping multi-version compatibility.
>>> ~ Instead of a configure.ac, they use setup.py.
>>> ~ In setup.py, they define entry-points as per the commands from the
>>> command line specifying python-foo or python3-foo.
>>>
>>> I also did a github search for 'python configure.ac' , looked into a
>>> considerable amount of commits of different users and organizations with
>>> the motive of "why don't we ask for help from those who seems to be
>>> successful in doing it".
>>>
>>> From my research, I found out that the guys at "balabit" seems to be
>>> able to do it.
>>> I opened an issue <https://github.com/balabit/syslog-ng/issues/2814> asking
>>> for help and clearance.
>>>
>>> The next step is to contact the Debian developers.
>>>
>>> Thanks!
>>>
>>> On Mon, Jul 1, 2019 at 5:21 AM James Cameron  wrote:
>>>
>>>> You neglected to mention that you are asking about Debian and Ubuntu
>>>> binary packages.  Ubuntu packages come from Debian unchanged, so your
>>>> question can be reduced to Debian packaging.
>>>>
>>>> We're the wrong people to ask.  It's not a skill any of us at Sugar
>>>> Labs have, otherwise we would have done it by now.
>>>>
>>>> The people who know how to do this are Debian and Ubuntu package
>>>> developers.
>>>>
>>>> I've tried asking one of the Debian developers but they were too busy
>>>> to give private assistance.  Private assistance does not scale, so the
>>>> return on investment is meagre.
>>>>
>>>> I suggest you try these things;
>>>>
>>>> 1.  write a throw-away script to download all Debian packages that
>>>> depend on Python 2 or Python 3, intersect a union of source packages
>>>> that support both versions, and then list those packages that contain
>>>> configure.ac in the source package,
>>>>
>>>> 2.  review those Debian and Ubuntu source packages that are used to
>>>> generate binary packages for both Python 2 and Python 3, and list the
>>>> package design patterns that you observe,
>>>>
>>>> 3.  contact the Debian developers using their mailing lists, or other
>>>> methods,
>>>>
>>>> 4.  engage in the Debian project by reporting a bug that asks for
>>>> packaging of a new version of the toolkit; currently 0.112 is
>>>> packaged.
>>>>
>>>> On Sat, Jun 29, 2019 at 02:32:33PM +0530, ANIKET MATHUR wrote:
>>>> > Hello everyone,
>>>> >
>>>> > I have been working on developing multi-version packages for toolkit
>>>> which can
>>>> > build for both Python and Python 3. I successfully build packages for
>>>> python,
>>>> > but not able to yet built one's having multi-version support. I have
>>>> been
>>>> > working on this for some time in the last two weeks, trying to get
>>>> something
>>>> > from the source code of existing tools that have these packages, like
>>>> 'pip' and
>>>> > a lot more.
>>>> >
>>>> > I need help and suggestions in this work. :-)
>>>> >
>>>> > Thanks!
>>>>
>>>> > ___
>>>> > 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
>>>>
>>>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Updates Regarding TelepathyGLib project

[ANIKET MATHUR]

We have completed the TelepathyGlib port of sugar, sugar-toolkit-gtk3,
collabwrapper, as well as of most of the other sugar activities.

Basic collaboration is working with TelepathyGLib.

Although there are a couple of issues with collaboration that we had
earlier with the static telepathy-python bindings as well, which are
encountered and recognised while porting.
https://github.com/sugarlabs/sugar/issues/840
https://github.com/sugarlabs/sugar/issues/842

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

Re: [Sugar-devel] Multiversion Packages of toolkit.

[ANIKET MATHUR]

Sent the email to debian-de...@lists.debian.org as well.

On Fri, Jul 5, 2019 at 4:13 PM ANIKET MATHUR  wrote:

> Sent an email to the Debian user mailing list debian-u...@lists.debian.org 
> requesting
> for packaging v0.114.
>
> Packaging of Sugar-toolkit-gtk3 (sugar3) v0.114.
> ANIKET MATHUR 
> 4:10 PM (2 minutes ago)
> to debian-user
> G'day,
> Aniket Mathur this side, an active contributor of Sugarlabs as well as a
> GSoC 19 participant. This mail is a small query regarding the packaging of
> "sugar3" module.
>
> We currently have v0.112 packaged. In the latest version (0.114) Sugarlabs
> have made the toolkit compatible with both Python and Python 3. But we
> don't have Debian multi-version packages for the latest version. This
> prevents us to scale our testing as well as limits the number of testers.
>
> We don't know how to make multi-version local packages, that we can
> distribute for testing.
>
> It would be good if we have Debian packages for v 0.114.
>
> Need Help.
> Regards.
>
> On Tue, Jul 2, 2019 at 12:02 PM ANIKET MATHUR 
> wrote:
>
>> Yes, I was asking about Debian packages. Sorry for incomplete information.
>>
>> I read sources of some Debian packages:-
>> ~ They do use six for keeping multi-version compatibility.
>> ~ Instead of a configure.ac, they use setup.py.
>> ~ In setup.py, they define entry-points as per the commands from the
>> command line specifying python-foo or python3-foo.
>>
>> I also did a github search for 'python configure.ac' , looked into a
>> considerable amount of commits of different users and organizations with
>> the motive of "why don't we ask for help from those who seems to be
>> successful in doing it".
>>
>> From my research, I found out that the guys at "balabit" seems to be able
>> to do it.
>> I opened an issue <https://github.com/balabit/syslog-ng/issues/2814> asking
>> for help and clearance.
>>
>> The next step is to contact the Debian developers.
>>
>> Thanks!
>>
>> On Mon, Jul 1, 2019 at 5:21 AM James Cameron  wrote:
>>
>>> You neglected to mention that you are asking about Debian and Ubuntu
>>> binary packages.  Ubuntu packages come from Debian unchanged, so your
>>> question can be reduced to Debian packaging.
>>>
>>> We're the wrong people to ask.  It's not a skill any of us at Sugar
>>> Labs have, otherwise we would have done it by now.
>>>
>>> The people who know how to do this are Debian and Ubuntu package
>>> developers.
>>>
>>> I've tried asking one of the Debian developers but they were too busy
>>> to give private assistance.  Private assistance does not scale, so the
>>> return on investment is meagre.
>>>
>>> I suggest you try these things;
>>>
>>> 1.  write a throw-away script to download all Debian packages that
>>> depend on Python 2 or Python 3, intersect a union of source packages
>>> that support both versions, and then list those packages that contain
>>> configure.ac in the source package,
>>>
>>> 2.  review those Debian and Ubuntu source packages that are used to
>>> generate binary packages for both Python 2 and Python 3, and list the
>>> package design patterns that you observe,
>>>
>>> 3.  contact the Debian developers using their mailing lists, or other
>>> methods,
>>>
>>> 4.  engage in the Debian project by reporting a bug that asks for
>>> packaging of a new version of the toolkit; currently 0.112 is
>>> packaged.
>>>
>>> On Sat, Jun 29, 2019 at 02:32:33PM +0530, ANIKET MATHUR wrote:
>>> > Hello everyone,
>>> >
>>> > I have been working on developing multi-version packages for toolkit
>>> which can
>>> > build for both Python and Python 3. I successfully build packages for
>>> python,
>>> > but not able to yet built one's having multi-version support. I have
>>> been
>>> > working on this for some time in the last two weeks, trying to get
>>> something
>>> > from the source code of existing tools that have these packages, like
>>> 'pip' and
>>> > a lot more.
>>> >
>>> > I need help and suggestions in this work. :-)
>>> >
>>> > Thanks!
>>>
>>> > ___
>>> > 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
>>>
>>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Unable to start collaboration on Ubuntu 18.04 VM

[ANIKET MATHUR]

Try deleting the existing file and then running ./autogen.sh

On Fri, Jul 5, 2019 at 8:14 PM Swarup N  wrote:

> Hello,
>
> I was able to establish collaboration by creating two new VM's and
> installing Sugar via the Live Build method.I used an already available .iso
> Sugar file, however it is v0.112.
> In order to upgrade to v0.114, I entered the */usr/src/* directory where
> all the 5 sugar modules are present. In each of the module, I checked to
> the master branch made pulled the latest changes, ran *./autogen.sh, make
> and make install *in the same order, logged in as root. However in the
> sugar-artwork directory, after taking the latest changes and running
> *make*, I get the following error saying *'failed to create symbolic link
> "../../cursor/sugar/cursors/default" : File already exists' *.
>
> Request help.
> Thanks
> ___
> 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] Multiversion Packages of toolkit.

[ANIKET MATHUR]

Sent an email to the Debian user mailing list
debian-u...@lists.debian.org requesting
for packaging v0.114.

Packaging of Sugar-toolkit-gtk3 (sugar3) v0.114.
ANIKET MATHUR 
4:10 PM (2 minutes ago)
to debian-user
G'day,
Aniket Mathur this side, an active contributor of Sugarlabs as well as a
GSoC 19 participant. This mail is a small query regarding the packaging of
"sugar3" module.

We currently have v0.112 packaged. In the latest version (0.114) Sugarlabs
have made the toolkit compatible with both Python and Python 3. But we
don't have Debian multi-version packages for the latest version. This
prevents us to scale our testing as well as limits the number of testers.

We don't know how to make multi-version local packages, that we can
distribute for testing.

It would be good if we have Debian packages for v 0.114.

Need Help.
Regards.

On Tue, Jul 2, 2019 at 12:02 PM ANIKET MATHUR  wrote:

> Yes, I was asking about Debian packages. Sorry for incomplete information.
>
> I read sources of some Debian packages:-
> ~ They do use six for keeping multi-version compatibility.
> ~ Instead of a configure.ac, they use setup.py.
> ~ In setup.py, they define entry-points as per the commands from the
> command line specifying python-foo or python3-foo.
>
> I also did a github search for 'python configure.ac' , looked into a
> considerable amount of commits of different users and organizations with
> the motive of "why don't we ask for help from those who seems to be
> successful in doing it".
>
> From my research, I found out that the guys at "balabit" seems to be able
> to do it.
> I opened an issue <https://github.com/balabit/syslog-ng/issues/2814> asking
> for help and clearance.
>
> The next step is to contact the Debian developers.
>
> Thanks!
>
> On Mon, Jul 1, 2019 at 5:21 AM James Cameron  wrote:
>
>> You neglected to mention that you are asking about Debian and Ubuntu
>> binary packages.  Ubuntu packages come from Debian unchanged, so your
>> question can be reduced to Debian packaging.
>>
>> We're the wrong people to ask.  It's not a skill any of us at Sugar
>> Labs have, otherwise we would have done it by now.
>>
>> The people who know how to do this are Debian and Ubuntu package
>> developers.
>>
>> I've tried asking one of the Debian developers but they were too busy
>> to give private assistance.  Private assistance does not scale, so the
>> return on investment is meagre.
>>
>> I suggest you try these things;
>>
>> 1.  write a throw-away script to download all Debian packages that
>> depend on Python 2 or Python 3, intersect a union of source packages
>> that support both versions, and then list those packages that contain
>> configure.ac in the source package,
>>
>> 2.  review those Debian and Ubuntu source packages that are used to
>> generate binary packages for both Python 2 and Python 3, and list the
>> package design patterns that you observe,
>>
>> 3.  contact the Debian developers using their mailing lists, or other
>> methods,
>>
>> 4.  engage in the Debian project by reporting a bug that asks for
>> packaging of a new version of the toolkit; currently 0.112 is
>> packaged.
>>
>> On Sat, Jun 29, 2019 at 02:32:33PM +0530, ANIKET MATHUR wrote:
>> > Hello everyone,
>> >
>> > I have been working on developing multi-version packages for toolkit
>> which can
>> > build for both Python and Python 3. I successfully build packages for
>> python,
>> > but not able to yet built one's having multi-version support. I have
>> been
>> > working on this for some time in the last two weeks, trying to get
>> something
>> > from the source code of existing tools that have these packages, like
>> 'pip' and
>> > a lot more.
>> >
>> > I need help and suggestions in this work. :-)
>> >
>> > Thanks!
>>
>> > ___
>> > 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
>>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GSoC 2019 - Learn about another project

[ANIKET MATHUR]

I went through Nikhil's weekly blogs, also viewed some of his pull requests
and tried to understand the changes.
Seems like Nikhil is doing a great job. :-)

On Tue, Jul 2, 2019 at 3:47 AM Rahul Bothra  wrote:

> G'day,
>
> We've completed the first set of evaluations for all GSoC projects. Since
> the students have made significant contributions now, we are trying a new
> activity to increase community engagement.
>
> Each student should understand about a different student's project, and
> accordingly, will be explaining his project to a third student. Here's the
> list of projects every student should understand,
>
> Nikhil Mehra - Create a Sugar Dashboard
> Hrishi Patel - Performance in Music Blocks
> Favour Kelvin - Create write activity for Sugarizer
> Ashish Aggarwal - Improve and Maintain 25 sugar activities
> Swarup N - Expand Sugarizer's Excerciser Activity
> Avinash Agarwal - Reconciling rhythm with pitch in Music Blocks widgets
> Sparsh Agarwal - Port to Python 3
> Aniket Mathur - Improve Sugarizer Server Dashboard
>
> To understand a project, you may talk to the student, it's mentors, or ask
> questions on @sugar-devel.
>
> Your responsibilities include;
>  - Understand the goals of the project and how is the student
> accomplishing them
>  - Test the work done in the project
>  - Explain your project to the student to which it is assigned
>
>
> For any questions or feedback, feel free to reach out to the Org Admins
>
> Regards
> Rahul Bothra
> ___
> 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] Multiversion Packages of toolkit.

[ANIKET MATHUR]

Yes, I was asking about Debian packages. Sorry for incomplete information.

I read sources of some Debian packages:-
~ They do use six for keeping multi-version compatibility.
~ Instead of a configure.ac, they use setup.py.
~ In setup.py, they define entry-points as per the commands from the
command line specifying python-foo or python3-foo.

I also did a github search for 'python configure.ac' , looked into a
considerable amount of commits of different users and organizations with
the motive of "why don't we ask for help from those who seems to be
successful in doing it".

>From my research, I found out that the guys at "balabit" seems to be able
to do it.
I opened an issue <https://github.com/balabit/syslog-ng/issues/2814> asking
for help and clearance.

The next step is to contact the Debian developers.

Thanks!

On Mon, Jul 1, 2019 at 5:21 AM James Cameron  wrote:

> You neglected to mention that you are asking about Debian and Ubuntu
> binary packages.  Ubuntu packages come from Debian unchanged, so your
> question can be reduced to Debian packaging.
>
> We're the wrong people to ask.  It's not a skill any of us at Sugar
> Labs have, otherwise we would have done it by now.
>
> The people who know how to do this are Debian and Ubuntu package
> developers.
>
> I've tried asking one of the Debian developers but they were too busy
> to give private assistance.  Private assistance does not scale, so the
> return on investment is meagre.
>
> I suggest you try these things;
>
> 1.  write a throw-away script to download all Debian packages that
> depend on Python 2 or Python 3, intersect a union of source packages
> that support both versions, and then list those packages that contain
> configure.ac in the source package,
>
> 2.  review those Debian and Ubuntu source packages that are used to
> generate binary packages for both Python 2 and Python 3, and list the
> package design patterns that you observe,
>
> 3.  contact the Debian developers using their mailing lists, or other
> methods,
>
> 4.  engage in the Debian project by reporting a bug that asks for
> packaging of a new version of the toolkit; currently 0.112 is
> packaged.
>
> On Sat, Jun 29, 2019 at 02:32:33PM +0530, ANIKET MATHUR wrote:
> > Hello everyone,
> >
> > I have been working on developing multi-version packages for toolkit
> which can
> > build for both Python and Python 3. I successfully build packages for
> python,
> > but not able to yet built one's having multi-version support. I have been
> > working on this for some time in the last two weeks, trying to get
> something
> > from the source code of existing tools that have these packages, like
> 'pip' and
> > a lot more.
> >
> > I need help and suggestions in this work. :-)
> >
> > Thanks!
>
> > ___
> > 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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Multiversion Packages of toolkit.

[ANIKET MATHUR]

Hello everyone,

I have been working on developing multi-version packages for toolkit which
can build for both Python and Python 3. I successfully build packages for
python, but not able to yet built one's having multi-version support. I
have been working on this for some time in the last two weeks, trying to
get something from the source code of existing tools that have these
packages, like 'pip' and a lot more.

I need help and suggestions in this work. :-)

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

Re: [Sugar-devel] Problem packaging toolkit

[ANIKET MATHUR]

Thanks.
Regarding packaging for both the version, first we have to make changes in
the configure.ac file so that the toolkit is installed for both the
versions automatically?
For Python 3 do I have to make a separate repo or just push the
python3-sugar3 to the *current repo?*
Sorry, I am confused.

On Tue, Jun 11, 2019 at 11:21 AM James Cameron  wrote:

> Look for python-foo and python3-foo packages that have been built from
> the same source package.
>
> Once you have it working, this lintian warning in
> sugar-toolkit-gtk3_0.114-1_amd64.build will vanish;
>
> W: sugar-toolkit-gtk3 source: python-foo-but-no-python3-foo python-sugar3
>
> Reviewed your packages; you have successfully reproduced what Ubuntu
> and Debian have done, plus you've adopted 0.114.  Well done.
>
> Things to do;
>
> * [ ] add new python3-sugar3 package into which the build for python3
>   will be constructed, as per above,
>
> * [ ] ensure /usr/bin/sugar-activity3 is not in the python-sugar3
>   package,
>
> * [ ] ensure /usr/bin/sugar-activity is not in the python3-sugar3
>   package,
>
> * [ ] use a developer local version number, perhaps with a git hash,
>
> * [ ] fix your mail address in debian/changelog
>
> On Tue, Jun 11, 2019 at 10:58:22AM +0530, ANIKET MATHUR wrote:
> > Thanks, made a separate github repo. [1]Link.
> > áRegarding packaging for both Python 2 and Python 3, sorry I never came
> along
> > with same Ubuntu packages installing for both the versions of Python.
> Though I
> > have seen separate packages for Python 2 and Python 3 line pip and pip3.
> I will
> > do my research regarding this and will give updates if I found anything
> useful.
> >
> > On Tue, Jun 11, 2019 at 10:23 AM James Cameron <[2]qu...@laptop.org>
> wrote:
> >
> > Put them somewhere for me to download; either a separate GitHub
> > repository, or a web server.á We can make an account for you on
> > sunjammer, see the Wiki Service/Shell page.
> >
> > You may be interested in dcmd as a quick way to simplify copying
> > these files.
> >
> > Also look at how to use reprepro, which can make a package archive
> > that you can then serve with a web server and use in sources.list
> >
> > Once you've made the packages available to me, I'll check them.
> >
> > Next step is to package for both Python 2 and Python 3.á I don't know
> > how to do that yet.á There are other Debian and Ubuntu packages with
> > dual-version source that may be used as a template.
> >
> > On Tue, Jun 11, 2019 at 10:01:08AM +0530, ANIKET MATHUR wrote:
> > > Thanks.
> > > I have build the packages.Now what should I do next, which files I
> have
> > to
> > > share?
> > >
> > > On Mon, Jun 10, 2019 at 2:28 PM James Cameron <[1][3]
> qu...@laptop.org>
> > wrote:
> > >
> > >á á áI've checked, and po/LINGUAS does contain ach.á The problem is
> caused
> > >á á áby bzr builddeb running the check-po target of the Makefile,
> which
> > >á á ácurrently fails like this;
> > >
> > >á á áhost:sugar-toolkit-gtk3$ make check-po
> > >á á á*** ach missing from po/LINGUAS ***
> > >á á áMakefile:859: recipe for target 'check-po' failed
> > >á á ámake: *** [check-po] Error 1
> > >
> > >á á áYou're welcome to fix this target.á See Makefile.am.á The
> failure is
> > >á á áunrelated to packaging and can be reproduced easily.á I don't
> plan to
> > >á á áfix it before the next release.
> > >
> > >á á áThe guide you refer to is for packaging new software for
> > >á á áUbuntu, whereas the Toolkit is existing software from Debian
> that
> > >á á áUbuntu has adopted without change.
> > >
> > >á á áUse the Debian source package instead.á You can get it from
> Ubuntu as
> > >á á áa source package using `apt source`, or `dget` the dsc from
> > >á á á[2][4]packages.ubuntu.com.á Change the version in
> debian/changelog
> > and
> > >á á ásubstitute the new source tar.xz file.
> > >
> > >á á áSee also sugar/docs/debian-packaging-example.md
> > >
> > >á á áOn Mon, Jun 10, 2019 at 01:06:00PM +0530, ANIKET MATHUR wrote:
> > >á á á> Hello everyone.
> > >á á á> I was trying to package sugar-toolkit-gtk3 v 0.114 following
> the
> > [1]
> > >á á á> documentation.
> > >á á á> I successful

Re: [Sugar-devel] Problem packaging toolkit

[ANIKET MATHUR]

Thanks, made a separate github repo. Link
<https://github.com/Aniket21mathur/sugar-toolkit-gtk3-packages>.
 Regarding packaging for both Python 2 and Python 3, sorry I never came
along with same Ubuntu packages installing for both the versions of Python.
Though I have seen separate packages for Python 2 and Python 3 line pip and
pip3. I will do my research regarding this and will give updates if I found
anything useful.

On Tue, Jun 11, 2019 at 10:23 AM James Cameron  wrote:

> Put them somewhere for me to download; either a separate GitHub
> repository, or a web server.  We can make an account for you on
> sunjammer, see the Wiki Service/Shell page.
>
> You may be interested in dcmd as a quick way to simplify copying
> these files.
>
> Also look at how to use reprepro, which can make a package archive
> that you can then serve with a web server and use in sources.list
>
> Once you've made the packages available to me, I'll check them.
>
> Next step is to package for both Python 2 and Python 3.  I don't know
> how to do that yet.  There are other Debian and Ubuntu packages with
> dual-version source that may be used as a template.
>
> On Tue, Jun 11, 2019 at 10:01:08AM +0530, ANIKET MATHUR wrote:
> > Thanks.
> > I have build the packages.Now what should I do next, which files I have
> to
> > share?
> >
> > On Mon, Jun 10, 2019 at 2:28 PM James Cameron <[1]qu...@laptop.org>
> wrote:
> >
> > I've checked, and po/LINGUAS does contain ach.  The problem is caused
> > by bzr builddeb running the check-po target of the Makefile, which
> > currently fails like this;
> >
> > host:sugar-toolkit-gtk3$ make check-po
> > *** ach missing from po/LINGUAS ***
> > Makefile:859: recipe for target 'check-po' failed
> > make: *** [check-po] Error 1
> >
> > You're welcome to fix this target.  See Makefile.am.  The failure is
> > unrelated to packaging and can be reproduced easily.  I don't plan to
> > fix it before the next release.
> >
> > The guide you refer to is for packaging new software for
> > Ubuntu, whereas the Toolkit is existing software from Debian that
> > Ubuntu has adopted without change.
> >
> > Use the Debian source package instead.  You can get it from Ubuntu as
> > a source package using `apt source`, or `dget` the dsc from
> > [2]packages.ubuntu.com.  Change the version in debian/changelog and
> > substitute the new source tar.xz file.
> >
> > See also sugar/docs/debian-packaging-example.md
> >
> > On Mon, Jun 10, 2019 at 01:06:00PM +0530, ANIKET MATHUR wrote:
> > > Hello everyone.
> > > I was trying to package sugar-toolkit-gtk3 v 0.114 following the
> [1]
> > > documentation.
> > > I successfully followed till 4.2, but on running the first command
> in 4.3
> > >
> > > bzr builddeb -- -us -uc
> > >
> > > The build failed with
> > >
> > > `
> > > make[1]: Entering directory '/home/aniket21/toolkit/build-area/
> > sugar-toolkit-gtk3-0.114'
> > > *** ach missing from po/LINGUAS ***
> > > Makefile:859: recipe for target 'check-po' failed
> > > make[1]: *** [check-po] Error 1
> > > make[1]: Leaving directory '/home/aniket21/toolkit/build-area/
> > sugar-toolkit-gtk3-0.114'
> > > dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
> > > debian/rules:18: recipe for target 'build' failed
> > > make: *** [build] Error 2
> > > dpkg-buildpackage: error: debian/rules build subprocess returned
> exit
> > status 2
> > > debuild: fatal error at line 1152:
> > > dpkg-buildpackage -rfakeroot -us -uc -ui failed
> > > bzr: ERROR: The build failed.
> > >
> > > `
> > >
> > > in the terminal. Need help.
> > >
> > > Thanks!
> > >
> > >
> > >
> > > References:
> > >
> > > [1] [3]
> http://packaging.ubuntu.com/html/packaging-new-software.html
> >
> > > ___
> > > Sugar-devel mailing list
> > > [4]Sugar-devel@lists.sugarlabs.org
> > > [5]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > --
> > James Cameron
> > [6]http://quozl.netrek.org/
> >
> > References:
> >
> > [1] mailto:qu...@laptop.org
> > [2] http://packages.ubuntu.com/
> > [3] http://packaging.ubuntu.com/html/packaging-new-software.html
> > [4] mailto:Sugar-devel@lists.sugarlabs.org
> > [5] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [6] http://quozl.netrek.org/
>
> --
> 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] Error testing collaboration using 2 Oracle virtual machines

[ANIKET MATHUR]

*Is the "Protocol 'jabber' not found on CM 'gabble'" tracebackreproducible?*
No, it is not reproducible. I get it only when I start sugar desktop for
the first time after setting sugar.

 *I don't know what you mean by "able to see the buddy icon".  In the*
*context of the thread, I'm confused.*
I meant to say that we are able to see the buddy icon of the other vm in
the neghbourhood view only if the two Vms are on the same network. So if we
are able to see the buddy icon, this means that the vm's are able to
interact, isn't it?

Thanks!

On Mon, Jun 10, 2019 at 12:53 PM James Cameron  wrote:

> Thanks.
>
> Without the Collaboration Server configured, Sugar will use link-local
> Salut.  This is a normal configuration, and is the default.  It does
> not require internet.  When using VMs, they must be on the same network.
>
> With the Collaboration Server configured, Sugar will use Jabber via
> Gabble.  This is a normal configuration, but is not the default.  It
> does require internet, or a Jabber server on a local network.  When
> using VMs, they may be on different networks.
>
> Both of these normal configurations should be tested when porting,
> thanks.  Most of my testing is link-local only.
>
> We have a Jabber server jabber.sugarlabs.org for testing.
>
> Is the "Protocol 'jabber' not found on CM 'gabble'" traceback
> reproducible?
>
> I don't know what you mean by "able to see the buddy icon".  In the
> context of the thread, I'm confused.
>
> On Mon, Jun 10, 2019 at 10:07:26AM +0530, ANIKET MATHUR wrote:
> > Do you have a Collaboration Server configured in My Setting - Network?
> > No, I don't have it configured, since . I am using both the vm's on the
> same
> > internal network, do I have to configure it.
> > Also, I am able to see the buddy icon of other instance in the
> neighbourhood
> > view of the first instance and vice versa.
> > Thanks!
> >
> > On Mon, Jun 10, 2019 at 7:42 AM James Cameron <[1]qu...@laptop.org>
> wrote:
> >
> > G'day,
> >
> > Thanks for your problem report.
> >
> > I've tested using two KVM instances of Ubuntu 19.04, with Sugar
> 0.112.
> > After login but before taking any action, these lines are in
> > shell.log;
> >
> > ```
> > /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:1630: Warning:
> > g_value_transform: assertion 'G_IS_VALUE (src_value)' failed
> >   return _Gtk_main(*args, **kwargs)
> > /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:1630: Warning:
> unable
> > to set property 'buddy' of type 'PyObject' from value of type
> '(null)'
> >   return _Gtk_main(*args, **kwargs)
> > ```
> >
> > For Ubuntu 18.04, with Sugar 0.114, these lines are in shell.log;
> >
> > ```
> > /usr/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> > g_value_transform: assertion 'G_IS_VALUE (src_value)' failed
> >   Gtk.main()
> > /usr/lib/python2.7/dist-packages/jarabe/main.py:378: Warning: unable
> to set
> > property 'buddy' of type 'PyObject' from value of type '(null)'
> >   Gtk.main()
> > ```
> >
> > I've seen these two log lines often.  I'd like them fixed, but I've
> > not found the cause.  Prefix varies, but the two log lines correspond
> > in time to the startup of Sugar, and not to the "Make friend" option.
> > You have equivalent lines in your log.  All log lines are in time
> > order.
> >
> > On both Ubuntu 18.04 and 19.04, in the Neigbourhood View of each the
> > buddy icon of the other is shown.  When I click on "Make friend"
> > option, the buddy icon remains visible.  When I switch to Group View,
> > the buddy icon of the new friend is shown.
> >
> > The traceback in your log happened during startup of Sugar, after the
> > instance of Neighborhood was created, and completion of an
> > asynchronous request for valid accounts.
> >
> > Given when the traceback happened during startup, the traceback is
> > unrelated to the "Make friend" option.
> >
> > I've not been able to reproduce the traceback.
> >
> > The error "Protocol 'jabber' not found on CM 'gabble'" suggests that
> > the telepathy-gabble connection manager has either;
> >
> > - failed,
> >
> > - taken too long to start, (especially likely on a virtual machine),
> or;
> >
> > - has not established a connection to your Jabber server.
> >
> > You reported the

[Sugar-devel] Problem packaging toolkit

[ANIKET MATHUR]

Hello everyone.
I was trying to package sugar-toolkit-gtk3 v 0.114 following the
documentation 
.
I successfully followed till 4.2, but on running the first command in 4.3

bzr builddeb -- -us -uc

The build failed with

`
make[1]: Entering directory
'/home/aniket21/toolkit/build-area/sugar-toolkit-gtk3-0.114'
*** ach missing from po/LINGUAS ***
Makefile:859: recipe for target 'check-po' failed
make[1]: *** [check-po] Error 1
make[1]: Leaving directory
'/home/aniket21/toolkit/build-area/sugar-toolkit-gtk3-0.114'
dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
debian/rules:18: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
debuild: fatal error at line 1152:
dpkg-buildpackage -rfakeroot -us -uc -ui failed
bzr: ERROR: The build failed.

`

in the terminal. Need help.

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

Re: [Sugar-devel] Error testing collaboration using 2 Oracle virtual machines

[ANIKET MATHUR]

*Do you have a Collaboration Server configured in My Setting - Network?*
No, I don't have it configured, since . I am using both the vm's on the
same internal network, do I have to configure it.
Also, I am able to see the buddy icon of other instance in the
neighbourhood view of the first instance and vice versa.
Thanks!

On Mon, Jun 10, 2019 at 7:42 AM James Cameron  wrote:

> G'day,
>
> Thanks for your problem report.
>
> I've tested using two KVM instances of Ubuntu 19.04, with Sugar 0.112.
> After login but before taking any action, these lines are in
> shell.log;
>
> ```
> /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:1630: Warning:
> g_value_transform: assertion 'G_IS_VALUE (src_value)' failed
>   return _Gtk_main(*args, **kwargs)
> /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:1630: Warning: unable
> to set property 'buddy' of type 'PyObject' from value of type '(null)'
>   return _Gtk_main(*args, **kwargs)
> ```
>
> For Ubuntu 18.04, with Sugar 0.114, these lines are in shell.log;
>
> ```
> /usr/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> g_value_transform: assertion 'G_IS_VALUE (src_value)' failed
>   Gtk.main()
> /usr/lib/python2.7/dist-packages/jarabe/main.py:378: Warning: unable to
> set property 'buddy' of type 'PyObject' from value of type '(null)'
>   Gtk.main()
> ```
>
> I've seen these two log lines often.  I'd like them fixed, but I've
> not found the cause.  Prefix varies, but the two log lines correspond
> in time to the startup of Sugar, and not to the "Make friend" option.
> You have equivalent lines in your log.  All log lines are in time
> order.
>
> On both Ubuntu 18.04 and 19.04, in the Neigbourhood View of each the
> buddy icon of the other is shown.  When I click on "Make friend"
> option, the buddy icon remains visible.  When I switch to Group View,
> the buddy icon of the new friend is shown.
>
> The traceback in your log happened during startup of Sugar, after the
> instance of Neighborhood was created, and completion of an
> asynchronous request for valid accounts.
>
> Given when the traceback happened during startup, the traceback is
> unrelated to the "Make friend" option.
>
> I've not been able to reproduce the traceback.
>
> The error "Protocol 'jabber' not found on CM 'gabble'" suggests that
> the telepathy-gabble connection manager has either;
>
> - failed,
>
> - taken too long to start, (especially likely on a virtual machine), or;
>
> - has not established a connection to your Jabber server.
>
> You reported the same error in your post of 21st May.
> http://lists.sugarlabs.org/archive/sugar-devel/2019-May/056916.html
>
> Nobody else has reported this error.
>
> Given you saw this before, and you probably did not use "Make friend"
> at the time, the traceback is again unrelated to "Make friend".
>
> Do you have a Collaboration Server configured in My Setting - Network?
>
> Is the traceback reproducible?  If so, enable debug logging for
> telepathy-gabble so you can find out why the connection manager has no
> protocol 'jabber'.  If the traceback is not reproducible, then ignore
> it; it was likely because telepathy-gabble process did not finish
> starting by the time Sugar tried to create an account on the
> connection.
>
> Speculating; this is a race condition problem; a race between Sugar
> startup and Telepathy, and the fix may have to be done in Telepathy.
>
> On Sat, Jun 08, 2019 at 12:04:32PM +0530, ANIKET MATHUR wrote:
> > Hello everyone,
> > I am using 2 Oracle Vm's having Ubuntu 18.04, using Sugar 0.112, both
> attached
> > to the same internal network. In the neigbourhood view of each the buddy
> icon
> > of other is shown. But when I click on `Make friend` option, the buddy
> icon
> > disappears and I have the following as the traceback
> >
> > ```
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604,
> in
> > msg_reply_handler
> > reply_handler(*message.get_args_list(**get_args_opts))
> >   File "/usr/lib/python2.7/dist-packages/jarabe/model/neighborhood.py",
> line
> > 738, in __got_accounts_cb
> > self._server_account = self._ensure_server_account(account_paths)
> >   File "/usr/lib/python2.7/dist-packages/jarabe/model/neighborhood.py",
> line
> > 851, in _ensure_server_account
> > properties)
> >   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in
> __call__
> > return self._proxy_method(*args, **keywords)
> >   File "/usr/lib/python2.7/dist-packages/d

Re: [Sugar-devel] Using rdesktop in Ubuntu 18.04 Vm

[ANIKET MATHUR]

Thanks. It's isn't a problem with sugar. :-)

On Fri, May 24, 2019 at 3:38 AM James Cameron  wrote:

> Ah, thanks, that's interesting.  We did have Xvnc in earlier
> instructions, but it stopped working so we switched to Xrdp.  Now that
> Xrdp has stopped working we can either switch back to Xvnc, or find
> out what the problem is.
>
> That's why I asked if the problem is unique to Sugar; if the black
> screen is Sugar's jarabe.main() hung, only the system process list may
> show it.  If Sugar is hung, we might find out why.  If the hang is
> before Sugar starts, then it is a problem with Xrdp or the Xsession
> default configuration.
>
> If it isn't a problem with Sugar, then it could be raised with Ubuntu
> or Debian against Xrdp.
>
> On Thu, May 23, 2019 at 06:43:08PM +0530, ANIKET MATHUR wrote:
> > Thanks. Xrdp uses Xorg as default, switching to Xvnc did the job for me.
> But I
> > did one step nit mentioned in the documentation, that was
> > installing tightvncserver, Following the second answer in [1]this.
> >
> > On Thu, May 23, 2019 at 3:58 PM James Cameron <[2]qu...@laptop.org>
> wrote:
> >
> > Try it with another account wihout setting up a Sugar .xsession
> file.  If
> > it fails the same way, you know it has to do with rdesktop or the
> Ubuntu
> > 18.04 X11 packages.
> >
> > On Thu, May 23, 2019 at 11:45:49AM +0530, ANIKET MATHUR wrote:
> > > I am trying to use rdesktop in Ubuntu 18.04 Vm to test port to
> > TelepathyGlib. I
> > > followed the steps given in the sugar-docs to set up a sugar
> instance
> > using
> > > rdesktop, but whenever I run "rdesktop -g 1200x900 -u guest -p
> guest
> > > 127.0.0.1", a separate window opens, but always remains black not
> showing
> > any
> > > further activity. Am I doing Something wrong or incomplete? Need
> > help.Thanks.
> >
> > > ___
> > > Sugar-devel mailing list
> > > [3]Sugar-devel@lists.sugarlabs.org
> > > [4]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > --
> > James Cameron
> > [5]http://quozl.netrek.org/
> > ___
> > Sugar-devel mailing list
> > [6]Sugar-devel@lists.sugarlabs.org
> > [7]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1]
> https://askubuntu.com/questions/797973/error-problem-connecting-windows-10-rdp-into-xrdp
> > [2] mailto:qu...@laptop.org
> > [3] mailto:Sugar-devel@lists.sugarlabs.org
> > [4] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [5] http://quozl.netrek.org/
> > [6] mailto:Sugar-devel@lists.sugarlabs.org
> > [7] 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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Problem collaborating some activities using rdesktop instances.

[ANIKET MATHUR]

To test telepathy port I made two instances of sugar using rdesktop. First
tried to collaborate using chat activity and was successful, as making the
other user friend and allowing neighborhood in the activity, gave an option
of "invite to chat activity" in the neighbourhood view.
But when I tried to do it with cookie-search or collabedit, I don't get any
such "invite to.." option. Without collaborating it's impossible for me to
test the telepathy port. Need help.
Thanks.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Using rdesktop in Ubuntu 18.04 Vm

[ANIKET MATHUR]

Thanks. Xrdp uses Xorg as default, switching to Xvnc did the job for me.
But I did one step nit mentioned in the documentation, that was
installing tightvncserver, Following the second answer in this
<https://askubuntu.com/questions/797973/error-problem-connecting-windows-10-rdp-into-xrdp>
.

On Thu, May 23, 2019 at 3:58 PM James Cameron  wrote:

> Try it with another account wihout setting up a Sugar .xsession file.  If
> it fails the same way, you know it has to do with rdesktop or the Ubuntu
> 18.04 X11 packages.
>
> On Thu, May 23, 2019 at 11:45:49AM +0530, ANIKET MATHUR wrote:
> > I am trying to use rdesktop in Ubuntu 18.04 Vm to test port to
> TelepathyGlib. I
> > followed the steps given in the sugar-docs to set up a sugar instance
> using
> > rdesktop, but whenever I run "rdesktop -g 1200x900 -u guest -p guest
> > 127.0.0.1", a separate window opens, but always remains black not
> showing any
> > further activity. Am I doing Something wrong or incomplete? Need
> help.Thanks.
>
> > ___
> > 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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Using rdesktop in Ubuntu 18.04 Vm

[ANIKET MATHUR]

Waiting for about 5 minutes resulted in the successful creation of the
sugar instance .

On Thu, May 23, 2019 at 11:45 AM ANIKET MATHUR 
wrote:

> I am trying to use rdesktop in Ubuntu 18.04 Vm to test port to
> TelepathyGlib. I followed the steps given in the sugar-docs to set up a
> sugar instance using rdesktop, but whenever I run "rdesktop -g 1200x900 -u
> guest -p guest 127.0.0.1", a separate window opens, but always remains
> black not showing any further activity. Am I doing Something wrong or
> incomplete? Need help.Thanks.
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Using rdesktop in Ubuntu 18.04 Vm

[ANIKET MATHUR]

I am trying to use rdesktop in Ubuntu 18.04 Vm to test port to
TelepathyGlib. I followed the steps given in the sugar-docs to set up a
sugar instance using rdesktop, but whenever I run "rdesktop -g 1200x900 -u
guest -p guest 127.0.0.1", a separate window opens, but always remains
black not showing any further activity. Am I doing Something wrong or
incomplete? Need help.Thanks.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

[ANIKET MATHUR]

Thanks James I was not starting Sugar as a desktop session. Now things work
fine for me.

On Tue, May 21, 2019 at 12:26 PM James Cameron  wrote:

> Thanks.
>
> Are you sure you gave me the correct log?  There's no segmentation
> fault shown there.  The log should be .sugar/default/logs/shell.log
>
> You can gather more information about a segmentation fault using gdb
> and backtrace command.
>
> Further reply in context below.
>
> On Tue, May 21, 2019 at 12:10:20PM +0530, ANIKET MATHUR wrote:
> > Regarding the Segmentation Fault.
> >
> > (main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> > gtk-widgets.css:16:32: The style property GtkExpander:expander-size
> is
> > deprecated and shouldn't be used anymore. It will be removed in a
> future
> > version
> >
> > (main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> > gtk-widgets.css:17:35: The style property
> GtkExpander:expander-spacing is
> > deprecated and shouldn't be used anymore. It will be removed in a
> future
> > version
> >
> > (metacity:2048): metacity-WARNING **: 12:04:58.799: Screen 0 on
> display
> > ":0" already has a window manager; try using the --replace option to
> > replace the current window manager.
> > 1558420503.333096 ERROR root: window manager did fail, restarting
> > Traceback (most recent call last):
>
> Confirm you are starting Sugar as a desktop session and not as a
> program inside another desktop session?
>
> For example, on my Ubuntu 18.04 test system, `ps axfww` shows jarabe
> to be a child process of gdm-x-session, gdm-session-worker, and gdm3;
> thus;
>
> ...
>  1885 ?Ssl0:00 /usr/sbin/gdm3
>  2547 ?Sl 0:00  \_ gdm-session-worker [pam/gdm-password]
>  2557 tty2 Ssl+   0:00  \_ /usr/lib/gdm3/gdm-x-session
> --run-script sugar
>  2560 tty2 Sl+0:10  \_ /usr/lib/xorg/Xorg vt2 -displayfd 3
> -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty
> -verbose 3
>  2569 tty2 Sl+0:10  \_ python2 -m jarabe.main
>  2635 ?Ss 0:00  \_ /usr/bin/ssh-agent
> /usr/bin/im-launch sugar
>  2659 tty2 Z+ 0:00  \_ [sugar] 
>  2670 tty2 Sl+0:00  \_ metacity --no-force-fullscreen
> --no-composite
>
> >   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line
> 604, in
> > msg_reply_handler
> > reply_handler(*message.get_args_list(**get_args_opts))
> >   File "/usr/local/lib/python2.7/dist-packages/jarabe/model/
> > neighborhood.py", line 738, in __got_accounts_cb
> > self._server_account = self._ensure_server_account(account_paths)
> >   File "/usr/local/lib/python2.7/dist-packages/jarabe/model/
> > neighborhood.py", line 851, in _ensure_server_account
> > properties)
> >   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70,
> in
> > __call__
> > return self._proxy_method(*args, **keywords)
> >   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145,
> in
> > __call__
> > **keywords)
> >   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line
> 651, in
> > call_blocking
> > message, timeout)
> > dbus.exceptions.DBusException:
> > org.freedesktop.Telepathy.Error.NotImplemented: Protocol 'jabber'
> not found
> > on CM 'gabble'
>
> Is Telepathy Gabble installed?
>
> > /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> > g_value_transform: assertion 'G_IS_VALUE (src_value)' failed
> >   Gtk.main()
> > /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> unable
> > to set property 'buddy' of type 'PyObject' from value of type
> '(null)'
> >   Gtk.main()
> >
> > (metacity:2175): metacity-WARNING **: 12:05:04.405: Screen 0 on
> display
> > ":0" already has a window manager; try using the --replace option to
> > replace the current window manager.
> > /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> > g_spawn_command_line_async: assertion 'command_line != NULL' failed
> >   Gtk.main()
> >
> > This is the log that I am getting on starting Sugar Desktop.
>
> Apart from the log, is there anything else that happens?  i.e. does
> Sugar start and show the activity ring or Journal?
>
> > On Wed, May 15, 2019 at 1:49 PM James Cam

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

[ANIKET MATHUR]

Regarding the Segmentation Fault.

(main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> gtk-widgets.css:16:32: The style property GtkExpander:expander-size is
> deprecated and shouldn't be used anymore. It will be removed in a future
> version
>
> (main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> gtk-widgets.css:17:35: The style property GtkExpander:expander-spacing is
> deprecated and shouldn't be used anymore. It will be removed in a future
> version
>
> (metacity:2048): metacity-WARNING **: 12:04:58.799: Screen 0 on display
> ":0" already has a window manager; try using the --replace option to
> replace the current window manager.
> 1558420503.333096 ERROR root: window manager did fail, restarting
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in
> msg_reply_handler
> reply_handler(*message.get_args_list(**get_args_opts))
>   File
> "/usr/local/lib/python2.7/dist-packages/jarabe/model/neighborhood.py", line
> 738, in __got_accounts_cb
> self._server_account = self._ensure_server_account(account_paths)
>   File
> "/usr/local/lib/python2.7/dist-packages/jarabe/model/neighborhood.py", line
> 851, in _ensure_server_account
> properties)
>   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in
> __call__
> return self._proxy_method(*args, **keywords)
>   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in
> __call__
> **keywords)
>   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in
> call_blocking
> message, timeout)
> dbus.exceptions.DBusException:
> org.freedesktop.Telepathy.Error.NotImplemented: Protocol 'jabber' not found
> on CM 'gabble'
> /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> g_value_transform: assertion 'G_IS_VALUE (src_value)' failed
>   Gtk.main()
> /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning: unable
> to set property 'buddy' of type 'PyObject' from value of type '(null)'
>   Gtk.main()
>
> (metacity:2175): metacity-WARNING **: 12:05:04.405: Screen 0 on display
> ":0" already has a window manager; try using the --replace option to
> replace the current window manager.
> /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> g_spawn_command_line_async: assertion 'command_line != NULL' failed
>   Gtk.main()
>

This is the log that I am getting on starting Sugar Desktop.

On Wed, May 15, 2019 at 1:49 PM James Cameron  wrote:

> Thanks!
>
> I've proposed a pull request to let the caller specify the Python
> version, and a draft pull request documenting how to build for both
> versions.
>
> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
> https://github.com/sugarlabs/sugar/pull/829
>
> Aniket, when you say v0.113 this means you are using either git tag
> v0.113 (i.e. e30b73f) or tarball.  Seems unlikely you are doing that,
> but instead you would be using HEAD of master branch instead.  Is my
> guess right?
>
> Regarding the segmentation fault, please check
> .sugar/default/logs/shell.log for any details, or run within gdb and
> capture a backtrace of all threads.
>
> On Wed, May 15, 2019 at 01:31:23PM +0530, ANIKET MATHUR wrote:
> > Regards,
> > I agree with, James. What I think is that since [1]this pr is not yet
> merged
> > into master, sugar requires python 2,
> > and the way I was installing Sugar builds the toolkit for Python 3. So I
> first
> > installed Sugar from sucrose and then installed the toolkit-gtk3 v0.113
> by
> > hand.
> > Doing this I am able to test ported activities through the command line
> using
> > Ubuntu 18.04 terminal, but opening Sugar home view causes "Segmentation
> fault"
> > with a warning "python2.7 has stopped unexpectedly". I am not yet able to
> > figure out the reason for this.
> >
> > Regarding the Python version in [2]configure.ac, I think that the
> caller should
> > be allowed to specify the version or alternatively since we are porting
> to six,
> > a method building for both python2 and python3 would be great.
> >
> > I don't expect myself to be 100 percent right and expect to be corrected
> > wherever required.
> >
> > Thanks a lot, everyone. ☺
> >
> > On Wed, May 15, 2019 at 3:17 AM James Cameron <[3]qu...@laptop.org>
> wrote:
> >
> > G'day Aniket,
> >
> > If you were using the native sugar build method, then you are using
> > HEAD, which contains all patches since 0.113.  Don't try to apply the
> >

Re: [Sugar-devel] development environment native sugar python 3 dependencies not documented

[ANIKET MATHUR]

* "python3 version of *telepathy"*. Sorry for the discrepancy.

On Mon, May 20, 2019 at 12:08 PM ANIKET MATHUR 
wrote:

> Thanks. Used Rahul's port of telepathy for python3. Though have to make
> some fixes, which I requested here
> <https://github.com/pro-panda/telepathy3/pull/1>. These changes finally
> resulted in a successful
> python3 toolkit installed on my system so far( it might be possible that I
> face problems as we proceed further ;-)). Since telepathy is quite an
> essential module for the python3 toolkit to run, I propose a fork of
> python3 version of toolkit to SugarLabs and mentioning of it in the
> native-sugar documentation. This would help developers to set up a testing
> environment until we completely port to TelepathyGlib.
>
> I also have some questions-
> -Activities like Pippy have import of jarabe module. So do we have a
> python3 ported version of jarabe.  Do we need it?
> - Same goes for sugargame, though for it we have a pr opened, which can be
> reviewed and merged now.
>
> On Mon, May 20, 2019 at 6:47 AM James Cameron  wrote:
>
>> Yes, the dependencies for the Python 3 build of sugar-toolkit-gtk3 are
>> not yet listed.
>>
>> Yes, the port from Telepathy static binding to TelepathyGLib is
>> necessary, if only to avoid using Rahul's port of Telepathy to Python
>> 3.
>>
>> p.s. next time please change subject, as your mail was not on topic
>> for the thread.  I've changed it now.
>>
>> On Sat, May 18, 2019 at 06:25:50PM +0530, ANIKET MATHUR wrote:
>> > Hey,
>> > After installing the toolkit for both the python versions and running
>> "sudo apt
>> > install sucrose" as per the [1]documentation native method,
>> > the packages are installed for python 2 only. There is still a need to
>> manually
>> > install packages like decorator for python 3. So what about telepathy?,
>> isn't
>> > it necessary to port to TelapathyGlib to use toolkit for python 3? Need
>> help.
>> > Thanks!
>> >
>> > On Sat, May 18, 2019 at 8:38 AM James Cameron <[2]qu...@laptop.org>
>> wrote:
>> >
>> > Sugar 0.114 is released, with a few fixes.
>> >
>> > Downloads;
>> >
>> > [3]
>> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/
>> > sugar-artwork-0.114.tar.xz
>> > [4]http://download.sugarlabs.org/sources/sucrose/glucose/
>> > sugar-datastore/sugar-datastore-0.114.tar.xz
>> > [5]http://download.sugarlabs.org/sources/sucrose/glucose/
>> > sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.114.tar.xz
>> > [6]http://download.sugarlabs.org/sources/sucrose/glucose/sugar/
>> > sugar-0.114.tar.xz
>> >
>> > A v0.114 tag has been pushed to each repository.
>> >
>> > No dependencies have changed.
>> >
>> > (After checking the mailing list subscribers for sugar-devel@,
>> there
>> > are no downstream packagers subscribed.  Use your downstream
>> > mechanisms to get their attention if necessary.)
>> >
>> > Brief change log by module below.
>> >
>> > sugar-artwork
>> >
>> > * No changes
>> >
>> > sugar-datastore
>> >
>> > * No changes
>> >
>> > sugar-toolkit-gtk3
>> >
>> > * New translations,
>> > * Build for either python 2 or python 3 (James Cameron),
>> > * Fix collaboration call_async (James Cameron),
>> > * Clean up activity environment variables (James Cameron),
>> > * Add distributed source to .gitignore (James Cameron),
>> > * Add flake8 suppression (James Cameron),
>> >
>> > sugar
>> >
>> > * Documentation for native environment configurations (James
>> Cameron),
>> > * Embed popwindow code in activitychooser (Rahul Bothra),
>> > * Add flake8 suppression (James Cameron),
>> >
>> > sha256 checksums;
>> >
>> > 0d9c63bf861d6facf8d64046ab76191a6a6b4b54daad778b40e3be1e45aa2db0
>> > sugar-artwork/sugar-artwork-0.114.tar.xz
>> > eb4256f1cbf90a9a7d5dd30446e0d0d1a240db02e3104a6339e2f4497dcda4c8
>> > sugar-datastore/sugar-datastore-0.114.tar.xz
>> > 0917276ed41684b885bdac063562fcdfb682660700ee142a02b516a3eeecdbb1
>> sugar/
>> > sugar-0.114.tar.xz
>> > 4b8ca467b85b6273fdb3ae86b1afa5071f4c0c6e11a27e9166a394620c2c77e5
>> > sugar-toolkit-gtk3/sug

Re: [Sugar-devel] development environment native sugar python 3 dependencies not documented

[ANIKET MATHUR]

Thanks. Used Rahul's port of telepathy for python3. Though have to make
some fixes, which I requested here
<https://github.com/pro-panda/telepathy3/pull/1>. These changes finally
resulted in a successful
python3 toolkit installed on my system so far( it might be possible that I
face problems as we proceed further ;-)). Since telepathy is quite an
essential module for the python3 toolkit to run, I propose a fork of
python3 version of toolkit to SugarLabs and mentioning of it in the
native-sugar documentation. This would help developers to set up a testing
environment until we completely port to TelepathyGlib.

I also have some questions-
-Activities like Pippy have import of jarabe module. So do we have a
python3 ported version of jarabe.  Do we need it?
- Same goes for sugargame, though for it we have a pr opened, which can be
reviewed and merged now.

On Mon, May 20, 2019 at 6:47 AM James Cameron  wrote:

> Yes, the dependencies for the Python 3 build of sugar-toolkit-gtk3 are
> not yet listed.
>
> Yes, the port from Telepathy static binding to TelepathyGLib is
> necessary, if only to avoid using Rahul's port of Telepathy to Python
> 3.
>
> p.s. next time please change subject, as your mail was not on topic
> for the thread.  I've changed it now.
>
> On Sat, May 18, 2019 at 06:25:50PM +0530, ANIKET MATHUR wrote:
> > Hey,
> > After installing the toolkit for both the python versions and running
> "sudo apt
> > install sucrose" as per the [1]documentation native method,
> > the packages are installed for python 2 only. There is still a need to
> manually
> > install packages like decorator for python 3. So what about telepathy?,
> isn't
> > it necessary to port to TelapathyGlib to use toolkit for python 3? Need
> help.
> > Thanks!
> >
> > On Sat, May 18, 2019 at 8:38 AM James Cameron <[2]qu...@laptop.org>
> wrote:
> >
> > Sugar 0.114 is released, with a few fixes.
> >
> > Downloads;
> >
> > [3]
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/
> > sugar-artwork-0.114.tar.xz
> > [4]http://download.sugarlabs.org/sources/sucrose/glucose/
> > sugar-datastore/sugar-datastore-0.114.tar.xz
> > [5]http://download.sugarlabs.org/sources/sucrose/glucose/
> > sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.114.tar.xz
> > [6]http://download.sugarlabs.org/sources/sucrose/glucose/sugar/
> > sugar-0.114.tar.xz
> >
> > A v0.114 tag has been pushed to each repository.
> >
> > No dependencies have changed.
> >
> > (After checking the mailing list subscribers for sugar-devel@, there
> > are no downstream packagers subscribed.  Use your downstream
> > mechanisms to get their attention if necessary.)
> >
> > Brief change log by module below.
> >
> > sugar-artwork
> >
> > * No changes
> >
> > sugar-datastore
> >
> > * No changes
> >
> > sugar-toolkit-gtk3
> >
> > * New translations,
> > * Build for either python 2 or python 3 (James Cameron),
> > * Fix collaboration call_async (James Cameron),
> > * Clean up activity environment variables (James Cameron),
> > * Add distributed source to .gitignore (James Cameron),
> > * Add flake8 suppression (James Cameron),
> >
> > sugar
> >
> > * Documentation for native environment configurations (James
> Cameron),
> > * Embed popwindow code in activitychooser (Rahul Bothra),
> > * Add flake8 suppression (James Cameron),
> >
> > sha256 checksums;
> >
> > 0d9c63bf861d6facf8d64046ab76191a6a6b4b54daad778b40e3be1e45aa2db0
> > sugar-artwork/sugar-artwork-0.114.tar.xz
> > eb4256f1cbf90a9a7d5dd30446e0d0d1a240db02e3104a6339e2f4497dcda4c8
> > sugar-datastore/sugar-datastore-0.114.tar.xz
> > 0917276ed41684b885bdac063562fcdfb682660700ee142a02b516a3eeecdbb1
> sugar/
> > sugar-0.114.tar.xz
> > 4b8ca467b85b6273fdb3ae86b1afa5071f4c0c6e11a27e9166a394620c2c77e5
> > sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.114.tar.xz
> >
> > --
> > James Cameron
> > [7]http://quozl.netrek.org/
> > ___
> > Sugar-devel mailing list
> > [8]Sugar-devel@lists.sugarlabs.org
> > [9]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1]
> https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
> > [2] mailto:qu...@laptop.org
> > [3]
> http://download.sugarlabs.org/sources/sucr

Re: [Sugar-devel] site-packages vs dist-packages, was Re: ... Sugar 0.114 stable

[ANIKET MATHUR]

Thanks a lot ;-).

On Sat, May 18, 2019 at 9:18 PM D. Joe  wrote:

> On Sat, May 18, 2019 at 05:57:57PM +0530, ANIKET MATHUR wrote:
> > Hello everyone,
> > Even after installing the toolkit for python3 I was getting the error 'No
> > module named sugar3' on running "sugar-activity3 ." command. After
> exploring a
> > bit
> > I got to know that using the native method when I built the toolkit for
> python
> > 2 the sugar3 module is built in 'usr/local/lib/python2.7/dist-packages'
> and
> > running the command "python2 -c 'import sugar3" passes. But when I
> install the
> > toolkit for python3, the module sugar3 is built in
> 'usr/local/lib/python3.6/
> > site-packages' and on running the command "sugar-activity3 ." sugar
> tries to
> > read from "usr/local/lib/python3.6/dist-packages".
> >  Is this a problem specific to my system(UBuntu 18.04)? A simple copy
> paste of
> > sugar3 module from site-packages to dist-packages would work?
> >
>
> Thought I'd seen this sort of thing mentioned before and after a little
> digging found this:
>
>
> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/383#issuecomment-425647453
>
> I can't offer much more than that pointer, but I hope it helps.
>
> --
> Joe
>
>
> ___
> 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] [RELEASE] Sugar 0.114 stable

[ANIKET MATHUR]

Hey,
After installing the toolkit for both the python versions and running "sudo
apt install sucrose" as per the documentation

native
method,
the packages are installed for python 2 only. There is still a need to
manually install packages like decorator for python 3. So what about
telepathy?, isn't it necessary to port to TelapathyGlib to use toolkit for
python 3? Need help.
Thanks!

On Sat, May 18, 2019 at 8:38 AM James Cameron  wrote:

> Sugar 0.114 is released, with a few fixes.
>
> Downloads;
>
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.114.tar.xz
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.114.tar.xz
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.114.tar.xz
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.114.tar.xz
>
> A v0.114 tag has been pushed to each repository.
>
> No dependencies have changed.
>
> (After checking the mailing list subscribers for sugar-devel@, there
> are no downstream packagers subscribed.  Use your downstream
> mechanisms to get their attention if necessary.)
>
> Brief change log by module below.
>
> sugar-artwork
>
> * No changes
>
> sugar-datastore
>
> * No changes
>
> sugar-toolkit-gtk3
>
> * New translations,
> * Build for either python 2 or python 3 (James Cameron),
> * Fix collaboration call_async (James Cameron),
> * Clean up activity environment variables (James Cameron),
> * Add distributed source to .gitignore (James Cameron),
> * Add flake8 suppression (James Cameron),
>
> sugar
>
> * Documentation for native environment configurations (James Cameron),
> * Embed popwindow code in activitychooser (Rahul Bothra),
> * Add flake8 suppression (James Cameron),
>
> sha256 checksums;
>
> 0d9c63bf861d6facf8d64046ab76191a6a6b4b54daad778b40e3be1e45aa2db0
> sugar-artwork/sugar-artwork-0.114.tar.xz
> eb4256f1cbf90a9a7d5dd30446e0d0d1a240db02e3104a6339e2f4497dcda4c8
> sugar-datastore/sugar-datastore-0.114.tar.xz
> 0917276ed41684b885bdac063562fcdfb682660700ee142a02b516a3eeecdbb1
> sugar/sugar-0.114.tar.xz
> 4b8ca467b85b6273fdb3ae86b1afa5071f4c0c6e11a27e9166a394620c2c77e5
> sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.114.tar.xz
>
> --
> 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] [RELEASE] Sugar 0.114 stable

[ANIKET MATHUR]

Hello everyone,
Even after installing the toolkit for python3 I was getting the error 'No
module named sugar3' on running "sugar-activity3 ." command. After
exploring a bit
I got to know that using the native method when I built the toolkit for
python 2 the sugar3 module is built in
'usr/local/lib/python2.7/dist-packages' and running the command "python2 -c
'import sugar3" passes. But when I install the toolkit for python3, the
module sugar3 is built in  'usr/local/lib/python3.6/site-packages' and on
running the command "sugar-activity3 ." sugar tries to read from
"usr/local/lib/python3.6/dist-packages".
 Is this a problem specific to my system(UBuntu 18.04)? A simple copy paste
of sugar3 module from site-packages to dist-packages would work?

On Sat, May 18, 2019 at 8:38 AM James Cameron  wrote:

> Sugar 0.114 is released, with a few fixes.
>
> Downloads;
>
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.114.tar.xz
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.114.tar.xz
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.114.tar.xz
>
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.114.tar.xz
>
> A v0.114 tag has been pushed to each repository.
>
> No dependencies have changed.
>
> (After checking the mailing list subscribers for sugar-devel@, there
> are no downstream packagers subscribed.  Use your downstream
> mechanisms to get their attention if necessary.)
>
> Brief change log by module below.
>
> sugar-artwork
>
> * No changes
>
> sugar-datastore
>
> * No changes
>
> sugar-toolkit-gtk3
>
> * New translations,
> * Build for either python 2 or python 3 (James Cameron),
> * Fix collaboration call_async (James Cameron),
> * Clean up activity environment variables (James Cameron),
> * Add distributed source to .gitignore (James Cameron),
> * Add flake8 suppression (James Cameron),
>
> sugar
>
> * Documentation for native environment configurations (James Cameron),
> * Embed popwindow code in activitychooser (Rahul Bothra),
> * Add flake8 suppression (James Cameron),
>
> sha256 checksums;
>
> 0d9c63bf861d6facf8d64046ab76191a6a6b4b54daad778b40e3be1e45aa2db0
> sugar-artwork/sugar-artwork-0.114.tar.xz
> eb4256f1cbf90a9a7d5dd30446e0d0d1a240db02e3104a6339e2f4497dcda4c8
> sugar-datastore/sugar-datastore-0.114.tar.xz
> 0917276ed41684b885bdac063562fcdfb682660700ee142a02b516a3eeecdbb1
> sugar/sugar-0.114.tar.xz
> 4b8ca467b85b6273fdb3ae86b1afa5071f4c0c6e11a27e9166a394620c2c77e5
> sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.114.tar.xz
>
> --
> 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 2019 - Welcome to Sugar Labs

[ANIKET MATHUR]

Thank you, James.
I got a clarification from your reply. I don't think that a meeting is
required now. I will surely ask for a meeting if I am stuck anywhere. ;-)


On Fri, May 17, 2019 at 10:54 AM James Cameron  wrote:

> Thanks for asking.
>
> I've removed CCs, as these people are all on sugar-devel@, and replies
> do trigger limit on addressee count reported by Mailman software.
>
> I don't think a meeting is needed, but I can attend one if you call
> it.  Please choose a time that both Rahul and I can be available.
>
> What to do and how to start is summarised by our GitHub project "Port
> to Python 3 via Six";
>
> https://github.com/orgs/sugarlabs/projects/1
>
> It is a big job, but completing any part of it brings the finish
> closer.  Rahul did good work on it last year.
>
> Each step will bring new errors and seemingly impossible problems that
> have to be solved.  We don't necessarily have the solutions until we
> can consider the problems in detail.  It isn't a class exercise.  ;-)
>
> In general the sequence is;
>
> - port, test, and package the toolkit,
>   https://github.com/sugarlabs/sugar-toolkit-gtk3
>   https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/382
>
> - port, test, and bundle the Hello World sample activity,
>
> - port, test, and bundle all the other activities in the core set,
>
> - port, test, and package the shell,
>   https://github.com/sugarlabs/sugar
>   https://github.com/sugarlabs/sugar/issues/787
>
> - port, test, and package any dependencies,
>   (Xapian has been mentioned by our Fedora people),
>
> - port, test, and package the datastore,
>   https://github.com/sugarlabs/sugar-datastore
>   https://github.com/sugarlabs/sugar-datastore/issues/7
>
> - port, test, and release any of our own dependencies used by
>   activities, such as collabwrapper, or gwebsockets,
>   https://github.com/sugarlabs/collabwrapper/issues/11
>
> - port from Telepathy to TelepathyGLib,
>   https://github.com/orgs/sugarlabs/projects/4
>
> - port, test, and bundle as many non-core activities as we can.
>
> Do ask questions to clarify, but with changed subject line.  I suggest
> a subject prefix of "Port to Python 3".
>
> On Fri, May 17, 2019 at 10:28:25AM +0530, ANIKET MATHUR wrote:
> > Hello everyone,
> > Looking forward to have a meeting for discussing how to start with
> project Port
> > to Python 3.
> > It would be good to discuss, how and from where to start. ;-)
> > Mentors - Rahul and James.
> > Thanks!
> >
> > On Mon, May 6, 2019 at 11:39 PM Rahul Bothra <[1]rrbot...@gmail.com>
> wrote:
> >
> > Greetings everyone,
> >
> > Congratulations to the 9 students selected for GSoC 2019 with Sugar
> Labs.
> > We
> > hope that you are as excited as we are. We had some great proposals
> to go
> > through and yours' really stood out.
> >
> > Here are a few things to get you onboard,
> > 1. Please subscribe to sugar-devel if you haven't already,
> > See [2]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > 2. Contact your project mentors to get started. Decide a weekly
> meeting
> > time
> > which suits you and your mentors. Regular communication is an
> integral part
> > of
> > working on a project of this scale.
> > It can be tempting to communicate in private, but please use public
> forums
> > like
> > #sugar, #sugar-meeting, or @sugar-devel while communicating, so that
> other
> > community members can also join in.
> >
> > 3. You are required to write weekly blog posts about your GSoC
> progress.
> > You
> > can start off by setting a blog up if you haven't already. Reply to
> this
> > thread with
> > the link to your blog.
> >
> > 4. We'll be having a weekly group meeting on #sugar-meeting, where
> all
> > mentors and students will discuss their progress. Since we have
> people from
> > Australia, France, India, Nigeria, and the US (pardon me if I've
> missed
> > anyone),
> > it'll be difficult to find a time suitable for everyone. Reply to
> this
> > thread with your
> > preference of time. Here are a few suggested options,
> > * Monday 4:30 PM UTC / 10:00 PM IST
> > * Monday 6:30 PM UTC / 12:00 PM IST
> >
> > 5. If you have any issues with your mentor, or otherwise during the
> GSoC
> > project, please feel free to get in touch with the GSoC Org Admins.
> They
> > are
> > James <[3]qu...@laptop.org>, 

Re: [Sugar-devel] GSoC 2019 - Welcome to Sugar Labs

[ANIKET MATHUR]

Hello everyone,
Looking forward to have a meeting for discussing how to start with project
Port to Python 3.
It would be good to discuss, how and from where to start. ;-)
Mentors - Rahul and James.
Thanks!

On Mon, May 6, 2019 at 11:39 PM Rahul Bothra  wrote:

> Greetings everyone,
>
> Congratulations to the 9 students selected for GSoC 2019 with Sugar Labs.
> We
> hope that you are as excited as we are. We had some great proposals to go
> through and yours' really stood out.
>
> Here are a few things to get you onboard,
> 1. Please subscribe to sugar-devel if you haven't already,
> See http://lists.sugarlabs.org/listinfo/sugar-devel
>
> 2. Contact your project mentors to get started. Decide a weekly meeting
> time
> which suits you and your mentors. Regular communication is an integral
> part of
> working on a project of this scale.
> It can be tempting to communicate in private, but please use public forums
> like
> #sugar, #sugar-meeting, or @sugar-devel while communicating, so that other
> community members can also join in.
>
> 3. You are required to write weekly blog posts about your GSoC progress.
> You
> can start off by setting a blog up if you haven't already. Reply to this
> thread with
> the link to your blog.
>
> 4. We'll be having a weekly group meeting on #sugar-meeting, where all
> mentors and students will discuss their progress. Since we have people from
> Australia, France, India, Nigeria, and the US (pardon me if I've missed
> anyone),
> it'll be difficult to find a time suitable for everyone. Reply to this
> thread with your
> preference of time. Here are a few suggested options,
> * Monday 4:30 PM UTC / 10:00 PM IST
> * Monday 6:30 PM UTC / 12:00 PM IST
>
> 5. If you have any issues with your mentor, or otherwise during the GSoC
> project, please feel free to get in touch with the GSoC Org Admins. They
> are
> James , Rahul , and Walter
> .
>
> Welcome to Sugar Labs.
> Looking forward to a productive summer with you guys
>
> Regards,
> Rahul Bothra
> ___
> 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] Toolkit Installation Sugar v0.113

[ANIKET MATHUR]

Thanks. James.
Agreed, there can be a number of runtime dependencies that the user has to
install. I don't think mentioning them all in the documentation
will be a good idea. What do you think?

On Thu, May 16, 2019 at 9:31 AM James Cameron  wrote:

> Thanks for testing, Aniket.
>
> Because 0.113 introduces a dependency on Six for the first time, the
> method of resolving dependencies in the instructions is out of date.
>
> I've added
>
> https://github.com/sugarlabs/sugar/pull/829/commits/97d1ef60b65a0fffe52ec4070944e2b03fe56ac2
> to the pull request.
>
> Yes, you are correct that dependencies are not added during build,
> this is something you may have to do yourself.
>
> For instance, after you've built Sugar, there are a set of run-time
> dependencies to install.  I'm working on refining the instructions
> some more.  Let me know how you go.
>
> On Thu, May 16, 2019 at 09:23:08AM +0530, ANIKET MATHUR wrote:
> > hey,
> > I tested the changes that James made.
> > I started with a fresh Ubuntu 18.04 VM. Cloned artwork, datastore,
> > toolkit-gtk3, and sugar.
> > Applied his patch to toolkit-gtk3 and then followed the native procedure
> in the
> > documentation considering his changes.
> > I installed the toolkit for both python2 and python3.
> > But when I run sugar from the command line I got an import error
> > "import six
> > "ImportError:No module named six"
> > I am not sure why I got this error, do the dependencies and libraries
> used by
> > python3 do not get installed when the toolkit for python 3 is built?
> > Please help.
> > Thanks!
> >
> > On Wed, May 15, 2019 at 1:49 PM James Cameron <[1]qu...@laptop.org>
> wrote:
> >
> > Thanks!
> >
> > I've proposed a pull request to let the caller specify the Python
> > version, and a draft pull request documenting how to build for both
> > versions.
> >
> > [2]https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
> > [3]https://github.com/sugarlabs/sugar/pull/829
> >
> > Aniket, when you say v0.113 this means you are using either git tag
> > v0.113 (i.e. e30b73f) or tarball.  Seems unlikely you are doing that,
> > but instead you would be using HEAD of master branch instead.  Is my
> > guess right?
> >
> > Regarding the segmentation fault, please check
> > .sugar/default/logs/shell.log for any details, or run within gdb and
> > capture a backtrace of all threads.
> >
> > On Wed, May 15, 2019 at 01:31:23PM +0530, ANIKET MATHUR wrote:
> > > Regards,
> > > I agree with, James. What I think is that since [1]this pr is not
> yet
> > merged
> > > into master, sugar requires python 2,
> > > and the way I was installing Sugar builds the toolkit for Python
> 3. So I
> > first
> > > installed Sugar from sucrose and then installed the toolkit-gtk3
> v0.113
> > by
> > > hand.
> > > Doing this I am able to test ported activities through the command
> line
> > using
> > > Ubuntu 18.04 terminal, but opening Sugar home view causes
> "Segmentation
> > fault"
> > > with a warning "python2.7 has stopped unexpectedly". I am not yet
> able to
> > > figure out the reason for this.
> > >
> > > Regarding the Python version in [2][4]configure.ac, I think that
> the
> > caller should
> > > be allowed to specify the version or alternatively since we are
> porting
> > to six,
> > > a method building for both python2 and python3 would be great.
> > >
> > > I don't expect myself to be 100 percent right and expect to be
> corrected
> > > wherever required.
> > >
> > > Thanks a lot, everyone. ☺
> > >
> > > On Wed, May 15, 2019 at 3:17 AM James Cameron <[3][5]
> qu...@laptop.org>
> > wrote:
> > >
> > > G'day Aniket,
> > >
> > > If you were using the native sugar build method, then you are
> using
> > > HEAD, which contains all patches since 0.113.  Don't try to
> apply the
> > > patch that Alex pointed out, as it is already applied.
> > >
> > > The error message "ImportError: No module named sugar3" is
> caused by
> > > not installing the Toolkit for Python 2.
> > >
> > > Sugar 0.113 requires Python 2.
> > >
> > >  

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

[ANIKET MATHUR]

hey,
I tested the changes that James made.
I started with a fresh Ubuntu 18.04 VM. Cloned artwork, datastore,
toolkit-gtk3, and sugar.
Applied his patch to toolkit-gtk3 and then followed the native procedure in
the documentation considering his changes.
I installed the toolkit for both python2 and python3.
But when I run sugar from the command line I got an import error
"import six
"ImportError:No module named six"
I am not sure why I got this error, do the dependencies and libraries used
by python3 do not get installed when the toolkit for python 3 is built?
Please help.
Thanks!

On Wed, May 15, 2019 at 1:49 PM James Cameron  wrote:

> Thanks!
>
> I've proposed a pull request to let the caller specify the Python
> version, and a draft pull request documenting how to build for both
> versions.
>
> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
> https://github.com/sugarlabs/sugar/pull/829
>
> Aniket, when you say v0.113 this means you are using either git tag
> v0.113 (i.e. e30b73f) or tarball.  Seems unlikely you are doing that,
> but instead you would be using HEAD of master branch instead.  Is my
> guess right?
>
> Regarding the segmentation fault, please check
> .sugar/default/logs/shell.log for any details, or run within gdb and
> capture a backtrace of all threads.
>
> On Wed, May 15, 2019 at 01:31:23PM +0530, ANIKET MATHUR wrote:
> > Regards,
> > I agree with, James. What I think is that since [1]this pr is not yet
> merged
> > into master, sugar requires python 2,
> > and the way I was installing Sugar builds the toolkit for Python 3. So I
> first
> > installed Sugar from sucrose and then installed the toolkit-gtk3 v0.113
> by
> > hand.
> > Doing this I am able to test ported activities through the command line
> using
> > Ubuntu 18.04 terminal, but opening Sugar home view causes "Segmentation
> fault"
> > with a warning "python2.7 has stopped unexpectedly". I am not yet able to
> > figure out the reason for this.
> >
> > Regarding the Python version in [2]configure.ac, I think that the
> caller should
> > be allowed to specify the version or alternatively since we are porting
> to six,
> > a method building for both python2 and python3 would be great.
> >
> > I don't expect myself to be 100 percent right and expect to be corrected
> > wherever required.
> >
> > Thanks a lot, everyone. ☺
> >
> > On Wed, May 15, 2019 at 3:17 AM James Cameron <[3]qu...@laptop.org>
> wrote:
> >
> > G'day Aniket,
> >
> > If you were using the native sugar build method, then you are using
> > HEAD, which contains all patches since 0.113.  Don't try to apply the
> > patch that Alex pointed out, as it is already applied.
> >
> > The error message "ImportError: No module named sugar3" is caused by
> > not installing the Toolkit for Python 2.
> >
> > Sugar 0.113 requires Python 2.
> >
> > Toolkit by default installs for Python 3.
> >
> > You can verify this is the situation by testing the import by hand
> > using different versions of Python;
> >
> > python3 -c 'import sugar3'  # expect pass
> >
> > python2 -c 'import sugar3'  # expect fail
> >
> > You'll find in [4]configure.ac where the Python version is chosen.
> >
> > [5]
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac
> > #L18
> >
> > Perhaps that line should allow the caller to specify the version.
> >
> > What do you think?
> >
> > On Tue, May 14, 2019 at 04:42:16PM +0530, ANIKET MATHUR wrote:
> > > Greetings everyone,
> > >
> > > I was installing Sugar v0.113 using the Native Sugar build
> method [1]
> > here. I
> > > was using Ubuntu 18.10. After installation, on running Sugar I
> received
> > the
> > > error message "ImportError: No module named sugar3". Need help
> with a
> > couple of
> > > questions
> > > 1) Is there a need to have a build of the older version for v0.113
> to
> > work
> > > properly?
> > > (never paid attention to that before).
> > >  2) What is the correct procedure for installing v0.113?
> > > Thanks!
> > >
> > > References:
> > >
> > > [1] [6]https://github.com/sugarlabs/sugar/blob/master/docs/
> > development-environment.md
> >
> > > ___
> > > Sug

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

[ANIKET MATHUR]

James by v 0.113 I mean HEAD. Sorry for the confusion.

On Wed, 15 May 2019, 1:49 pm James Cameron,  wrote:

> Thanks!
>
> I've proposed a pull request to let the caller specify the Python
> version, and a draft pull request documenting how to build for both
> versions.
>
> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
> https://github.com/sugarlabs/sugar/pull/829
>
> Aniket, when you say v0.113 this means you are using either git tag
> v0.113 (i.e. e30b73f) or tarball.  Seems unlikely you are doing that,
> but instead you would be using HEAD of master branch instead.  Is my
> guess right?
>
> Regarding the segmentation fault, please check
> .sugar/default/logs/shell.log for any details, or run within gdb and
> capture a backtrace of all threads.
>
> On Wed, May 15, 2019 at 01:31:23PM +0530, ANIKET MATHUR wrote:
> > Regards,
> > I agree with, James. What I think is that since [1]this pr is not yet
> merged
> > into master, sugar requires python 2,
> > and the way I was installing Sugar builds the toolkit for Python 3. So I
> first
> > installed Sugar from sucrose and then installed the toolkit-gtk3 v0.113
> by
> > hand.
> > Doing this I am able to test ported activities through the command line
> using
> > Ubuntu 18.04 terminal, but opening Sugar home view causes "Segmentation
> fault"
> > with a warning "python2.7 has stopped unexpectedly". I am not yet able to
> > figure out the reason for this.
> >
> > Regarding the Python version in [2]configure.ac, I think that the
> caller should
> > be allowed to specify the version or alternatively since we are porting
> to six,
> > a method building for both python2 and python3 would be great.
> >
> > I don't expect myself to be 100 percent right and expect to be corrected
> > wherever required.
> >
> > Thanks a lot, everyone. ☺
> >
> > On Wed, May 15, 2019 at 3:17 AM James Cameron <[3]qu...@laptop.org>
> wrote:
> >
> > G'day Aniket,
> >
> > If you were using the native sugar build method, then you are using
> > HEAD, which contains all patches since 0.113.  Don't try to apply the
> > patch that Alex pointed out, as it is already applied.
> >
> > The error message "ImportError: No module named sugar3" is caused by
> > not installing the Toolkit for Python 2.
> >
> > Sugar 0.113 requires Python 2.
> >
> > Toolkit by default installs for Python 3.
> >
> > You can verify this is the situation by testing the import by hand
> > using different versions of Python;
> >
> > python3 -c 'import sugar3'  # expect pass
> >
> > python2 -c 'import sugar3'  # expect fail
> >
> > You'll find in [4]configure.ac where the Python version is chosen.
> >
> > [5]
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac
> > #L18
> >
> > Perhaps that line should allow the caller to specify the version.
> >
> > What do you think?
> >
> > On Tue, May 14, 2019 at 04:42:16PM +0530, ANIKET MATHUR wrote:
> > > Greetings everyone,
> > >
> > > I was installing Sugar v0.113 using the Native Sugar build
> method [1]
> > here. I
> > > was using Ubuntu 18.10. After installation, on running Sugar I
> received
> > the
> > > error message "ImportError: No module named sugar3". Need help
> with a
> > couple of
> > > questions
> > > 1) Is there a need to have a build of the older version for v0.113
> to
> > work
> > > properly?
> > > (never paid attention to that before).
> > >  2) What is the correct procedure for installing v0.113?
> > > Thanks!
> > >
> > > References:
> > >
> > > [1] [6]https://github.com/sugarlabs/sugar/blob/master/docs/
> > development-environment.md
> >
> > > ___
> > > Sugar-devel mailing list
> > > [7]Sugar-devel@lists.sugarlabs.org
> > > [8]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > --
> > James Cameron
> > [9]http://quozl.netrek.org/
> >
> > References:
> >
> > [1] https://github.com/sugarlabs/sugar/pull/805
> > [2] http://configure.ac/
> > [3] mailto:qu...@laptop.org
> > [4] http://configure.ac/
> > [5]
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac#L18
> > [6]
> https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
> > [7] mailto:Sugar-devel@lists.sugarlabs.org
> > [8] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [9] http://quozl.netrek.org/
>
> --
> 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] Toolkit Installation Sugar v0.113

[ANIKET MATHUR]

Regards,
I agree with, James. What I think is that since this pr
<https://github.com/sugarlabs/sugar/pull/805> is not yet merged into
master, sugar requires python 2,
and the way I was installing Sugar builds the toolkit for Python 3. So I
first installed Sugar from sucrose and then installed the toolkit-gtk3
v0.113 by hand.
Doing this I am able to test ported activities through the command line
using Ubuntu 18.04 terminal, but opening Sugar home view causes
"Segmentation fault" with a warning "python2.7 has stopped unexpectedly". I
am not yet able to figure out the reason for this.

Regarding the Python version in configure.ac, I think that the caller
should be allowed to specify the version or alternatively since we are
porting to six, a method building for both python2 and python3 would be
great.

I don't expect myself to be 100 percent right and expect to be corrected
wherever required.

Thanks a lot, everyone. ☺



On Wed, May 15, 2019 at 3:17 AM James Cameron  wrote:

> G'day Aniket,
>
> If you were using the native sugar build method, then you are using
> HEAD, which contains all patches since 0.113.  Don't try to apply the
> patch that Alex pointed out, as it is already applied.
>
> The error message "ImportError: No module named sugar3" is caused by
> not installing the Toolkit for Python 2.
>
> Sugar 0.113 requires Python 2.
>
> Toolkit by default installs for Python 3.
>
> You can verify this is the situation by testing the import by hand
> using different versions of Python;
>
> python3 -c 'import sugar3'  # expect pass
>
> python2 -c 'import sugar3'  # expect fail
>
> You'll find in configure.ac where the Python version is chosen.
>
>
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac#L18
>
> Perhaps that line should allow the caller to specify the version.
>
> What do you think?
>
> On Tue, May 14, 2019 at 04:42:16PM +0530, ANIKET MATHUR wrote:
> > Greetings everyone,
> >
> > I was installing Sugar v0.113 using the Native Sugar build
> method [1]here. I
> > was using Ubuntu 18.10. After installation, on running Sugar I received
> the
> > error message "ImportError: No module named sugar3". Need help with a
> couple of
> > questions
> > 1) Is there a need to have a build of the older version for v0.113 to
> work
> > properly?
> > (never paid attention to that before).
> >  2) What is the correct procedure for installing v0.113?
> > Thanks!
> >
> > References:
> >
> > [1]
> https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
>
> > ___
> > 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

[Sugar-devel] Toolkit Installation Sugar v0.113

[ANIKET MATHUR]

Greetings everyone,

I was installing Sugar v0.113 using the Native Sugar build method here
.
I was using Ubuntu 18.10. After installation, on running Sugar I received
the error message "ImportError: No module named sugar3". Need help with a
couple of questions
1) Is there a need to have a build of the older version for v0.113 to work
properly?
(never paid attention to that before).
 2) What is the correct procedure for installing v0.113?
Thanks!
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Fwd: Port to Python 3, GSoC 2019, Private Mentor Student Discussion

[aniket mathur]

Hello, Greetings
I have a couple of questions that I want to ask.
- Regarding the development environment. What is the preferred development
environment, in terms of OS and the version of Sugar or any other
compatibilities that I must have installed?
-Regarding blogs. What will be the frequency of writing blogs, and when
should we start writing those and when will the weekly meetings be
scheduled?
Looking for advice. Thanks a lot!


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

Re: [Sugar-devel] GSoC 2019 - Welcome to Sugar Labs

[aniket mathur]

Hello everyone,

I will like to write blogs on medium (https://medium.com/@aniketmathur).
My preferred time slot would be 12 pm IST/10:30 pm UTC.

Thank you!

On Wed, 8 May 2019, 7:52 am Ashish Aggarwal, 
wrote:

> Hello Everyone ,
>
> I would love to write the blogs on medium at here
>  . As @nikhilMehra asked if there is
> a preferred platform , then we can write blogs there .
> My preferred time would be Monday 4:30 PM UTC / 10:00 PM IST ( Also
> available on other time slot ) .
> Regards
> Ashish Aggarwal
>
> On Wed, 8 May 2019 at 02:35, James Cameron  wrote:
>
>> Good point.  Any new assisting mentors should introduce themselves to the
>> students now, and CC sugar-devel@.  Be sure to mention your skills,
>> special focus, and experience with Sugar Labs.
>>
>> This is also a reminder to the coding mentors and students that as much
>> as possible of what you say and do together should be in public, so that
>> the assisting mentors and others in our community can be involved.
>>
>>
>> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#assisting-mentors
>>
>> Let's get started!
>>
>> On Tue, May 07, 2019 at 12:33:33PM +0100, Ifeanyi Ekperi wrote:
>> > Congratulations Students and Mentors!
>> >
>> > What happened to the Assistant Mentors thingy?
>> >
>> > On Tue, May 7, 2019, 12:17 Samson Goddy <[1]samsongo...@gmail.com>
>> wrote:
>> >
>> > Congratulations to all the students and mentors.
>> >
>> > Regards.
>> >
>> > Samson
>> >
>> > On Mon, May 6, 2019, 9:36 PM Rahul Bothra <[2]rrbot...@gmail.com>
>> wrote:
>> >
>> > Here is the list of selected projects for GSoC' 19,
>> >
>> > * Improve Sugarizer Server Dashboard;
>> >   Student: Nikhil Mehra
>> >   Mentors: Lionel Laské, Tarun Kumar Singhal
>> >
>> > * Create a Sugar Dashboard
>> >   Student: Hrishi Patel
>> >   Mentors: Rahul Bothra, Peace Ojemeh, Chihurumnaya Ibiam
>> >
>> > * Performance in MusicBlocks
>> >   Student: Favour Kelvin
>> >   Mentors: Sumit Srivastava, Devin Ulibarri, Walter Bender
>> >
>> > * Create Write Activity for Sugarizer
>> >   Student: Ashish Aggarwal
>> >   Mentors: Michaël Ohayon, Tarun Kumar Singhal
>> >
>> > * Improve and Maintain 25 Sugar Activities
>> >   Student: Swarup N
>> >   Mentors: Rahul Bothra, Chihurumnaya Ibiam, James Cameron
>> >
>> > * Expand Sugarizer’s Exerciser Activity
>> >   Student: Avinash Agarwal
>> >   Mentors: Michaël Ohayon, Lionel Laské
>> >
>> > * Reconciling rhythm with pitch in Music Blocks widgets
>> >   Student: Sparsh Agarwal
>> >   Mentors: Sumit Srivastava, Devin Ulibarri, Walter Bender
>> >
>> > * Performance in Music Blocks
>> >   Student: Ankur Bambharoliya
>> >   Mentors: Sumit Srivastava, Devin Ulibarri, Walter Bender
>> >
>> > * Port Sugar to Python 3
>> >   Student: Aniket Mahur
>> >   Mentors: Rahul Bothra, James Cameron
>> >
>> > Regards,
>> > Rahul Bothra
>> >
>> > On Mon, May 6, 2019 at 11:32 PM Rahul Bothra <[3]
>> rrbot...@gmail.com>
>> > wrote:
>> >
>> > Greetings everyone,
>> >
>> > Congratulations to the 9 students selected for GSoC 2019
>> with Sugar
>> > Labs. We
>> > hope that you are as excited as we are. We had some great
>> proposals
>> > to go
>> > through and yours' really stood out.
>> >
>> > Here are a few things to get you onboard,
>> > 1. Please subscribe to sugar-devel if you haven't already,
>> > See [4]http://lists.sugarlabs.org/listinfo/sugar-devel
>> >
>> > 2. Contact your project mentors to get started. Decide a
>> weekly
>> > meeting time
>> > which suits you and your mentors. Regular communication is
>> an
>> > integral part of
>> > working on a project of this scale.
>> > It can be tempting to communicate in private, but please
>> use public
>> > forums like
>> > #sugar, #sugar-meeting, or @sugar-devel while
>> communicating, so
>> > that other
>> > community members can also join in.
>> >
>> > 3. You are required to write weekly blog posts about your
>> GSoC
>> > progress. You
>> > can start off by setting a blog up if you haven't already.
>> Reply to
>> > this thread with
>> > the link to your blog.
>> >
>> > 4. We'll be having a weekly group meeting on
>> #sugar-meeting, where
>> > all
>> > mentors and students will discuss their progress. Since we
>> have
>> > people from
>> > Australia, France, India, Nigeria, and the US (pardon me if
>> I've
>> > missed anyone),
>> > 

Re: [Sugar-devel] GSoC 2019 - Welcome to Sugar Labs

[ANIKET MATHUR]

Hello everyone,

I will like to write blogs on medium(https://medium.com/@aniketmathur).
My preferred time slot is 6:30 pm UTC/12 pm IST.

Thank you!

On Mon, 6 May 2019, 11:39 pm Rahul Bothra,  wrote:

> Greetings everyone,
>
> Congratulations to the 9 students selected for GSoC 2019 with Sugar Labs.
> We
> hope that you are as excited as we are. We had some great proposals to go
> through and yours' really stood out.
>
> Here are a few things to get you onboard,
> 1. Please subscribe to sugar-devel if you haven't already,
> See http://lists.sugarlabs.org/listinfo/sugar-devel
>
> 2. Contact your project mentors to get started. Decide a weekly meeting
> time
> which suits you and your mentors. Regular communication is an integral
> part of
> working on a project of this scale.
> It can be tempting to communicate in private, but please use public forums
> like
> #sugar, #sugar-meeting, or @sugar-devel while communicating, so that other
> community members can also join in.
>
> 3. You are required to write weekly blog posts about your GSoC progress.
> You
> can start off by setting a blog up if you haven't already. Reply to this
> thread with
> the link to your blog.
>
> 4. We'll be having a weekly group meeting on #sugar-meeting, where all
> mentors and students will discuss their progress. Since we have people from
> Australia, France, India, Nigeria, and the US (pardon me if I've missed
> anyone),
> it'll be difficult to find a time suitable for everyone. Reply to this
> thread with your
> preference of time. Here are a few suggested options,
> * Monday 4:30 PM UTC / 10:00 PM IST
> * Monday 6:30 PM UTC / 12:00 PM IST
>
> 5. If you have any issues with your mentor, or otherwise during the GSoC
> project, please feel free to get in touch with the GSoC Org Admins. They
> are
> James , Rahul , and Walter
> .
>
> Welcome to Sugar Labs.
> Looking forward to a productive summer with you guys
>
> Regards,
> Rahul Bothra
> ___
> 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] Doubt regarding proposal draft

[aniket mathur]

On GSoC official site there is an option to submit a draft for review
before final pdf upload, but my proposal is already reviewed twice through
the mailing list, so should I skip that part and submit a final proposal?
___
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

[Sugar-devel] GSoC proposal changes

[aniket mathur]

 "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/edit?usp=sharing
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] GSoC proposal - Port to Python 3

[aniket mathur]

Hello everyone, I am Aniket Mathur.
Here is a link to my GSoC proposal. Please review it and suggest changes.
https://docs.google.com/document/d/1uGwlzPMUG7Z_ZJEloORGc8tEiXs72qLurO-R7GlomsU/edit?usp=sharing
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Regarding port to python 3 project

[aniket mathur]

Are gwebsockets made fully compatible with python 3 and just needs a
release or some porting work is still needed to be done before a release.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Port to python 3 project

[aniket mathur]

Porting of all fructose activities was included as a part of the GSOC
project. Does porting other activities to python 3 is not required  or
simply  it is of less priority?
Sugargame is also not ported to python 3.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Regarding GSOC 2019 project

[aniket mathur]

Hey everyone, I am Aniket mathur (@Aniket21mathur) an undergraduate at IIT
Roorkee. I am contributing to sugarlabs since December 2018 and recently
being added as the member of the organisation. I am GSOC 2019 aspirant, and
I am looking forward for python based projects but I am not certain on
which project I should write my proposal on. But I have my inclination
towards port to python3 and maintain 25 activities projects, I have two
queries :
1) Can I submit more than one proposal?
2) Are there any other projects or possibility of any other projects which
are of high
priority to the organisation?
Thanks!
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel