Re: [Sugar-devel] GCI 2019 Announced

[Pratul Kumar]

Great News.

On Tue 24 Sep, 2019, 10:17 PM ANIKET MATHUR,  wrote:

> 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 <
>>> freddie.nicholson...@gmail.com> 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 mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GSOC proposal

[Pratul Kumar]

Hello Ashish,
Glad to see your interest in  "Improve Sugarizer server dashboard",

   1. Few things which I feel could be better is that You can elaborate the
   proposal a bit, the current proposal looks quite condensed.
   2. Communicate further discussion in the mailing list.
   3. Also, the timeline is quite hard to read, if you can add it in the
   format of a table, then it can improve readability.
   4. You dont need to put the complete link of PR and issues, just write
   their number and attack link to those numbers, this can reduce the number
   of pages needed also visuality will be better.
   5. The Timeline can be more in detail.
   6. Personal view: ( Proposal ranging from 15-20 pages is the best fit,
   in terms of elaboration, readability)

Regards,
Pratul Kumar


On Fri, Mar 22, 2019 at 10:24 AM Ashish Aggarwal 
wrote:

> Hello sir,
> My name is Ashish aggarwal . My Github profile is " ashish0910
> <https://github.com/ashish0910> " . I want to participate in gsoc19 in
> sugarlabs for the project ' improve sugarizer server dashboard ' and I have
> been contributing to that project for a while now . I have attached my
> proposal. It would be great if you could review and suggest changes in it .
> Thanks
> warm regards
> ashish aggarwal
>


-- 

*Pratul Kumar | Prefinal Year** LNMIIT** | +91-8107525493*

*GSoC, GCI-Mentor* Sugarlabs,
Coursera Mentor,* HKUST University*
*PyJaipur *Organiser
  [image: LinkedIn]  <https://www.linkedin.com/in/pratul1997/> [image:
Github]  <https://github.com/Pratul1997>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Fwd: GSoC 2019: Sugar Labs has been accepted as a mentor organization!

[Pratul Kumar]

upp...@google.com.
>>>>>>>>>> Replies to this message go to an unmonitored mailbox.
>>>>>>>>>>
>>>>>>>>>> © 2019 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA
>>>>>>>>>> 94043, USA
>>>>>>>>>> <https://maps.google.com/?q=1600+Amphitheatre+Parkway,+Mountain+View,+CA+94043,+USA&entry=gmail&source=g>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>> ___
>>>>>>>> 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
>>>>>
>>>> --
>>>> 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 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
>


-- 

*​Pratul Kumar | Prefinal Year** LNMIIT** | +91-8107525493*

*​GSoC, GCI​-​Mentor* Sugarlabs,
Coursera Mentor,* HKUST University*
*PyJaipur *Organiser
  [image: LinkedIn]  <https://www.linkedin.com/in/pratul1997/> [image:
Github]  <https://github.com/Pratul1997>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GCI Thank you

[Pratul Kumar]

We are pleased that GCI served a great learning for you.

Keep contributing in Sugarlabs.
Cheers!

On Wed 12 Dec, 2018, 7:28 PM Hrishi Patel  Good read.
> Thanks for being a part of GCI and the community
> Good luck :)
>
> On Wed, Dec 12, 2018, 6:35 PM Freddie N  wrote:
>
>> Dear GCI Mentors,
>>
>> As GCI comes to a close, I would like to thank all the mentors who took
>> part this year. As a GCI student, I have learnt more than I ever would have
>> expected during the process and each task has always got me engaged.
>> Initiatives like GCI would not be possible without your dedication and time
>> that you put towards it. Although I will miss having my tasks being
>> approved, I look forward to contributing to Sugar Labs in the future.
>>
>> If you are interested, I wrote about my experiences here:
>> https://medium.com/@freddie.nicholson123/the-journey-i-think-every-young-programmer-should-take-my-experience-with-gci-83cd63f98565
>>
>> I hope you manage to get a well-deserved break this holiday season.
>>
>> Freddie
>>
>> ___
>> 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] Workshop held on Sugar... An Introduction of Turtleblocks and Musicblocks

[Pratul Kumar]

Great work, brother !!

If you plan to organize any such workshop in Jaipur, kindly let me know, I
would love to join you.

On Mon 10 Dec, 2018, 11:10 PM Amaan Iqbal  Great work! Really liked it.
>
> On Dec 10, 2018 11:05 PM, "Hrishi Patel"  wrote:
>
>> Great!
>>
>> On Mon, Dec 10, 2018, 10:44 PM Ashnidh Khandelwal > wrote:
>>
>>> It is great to share with you that on Saturday, Dec  8th, I organized a
>>> workshop in a prominent school of my locality. In the workshop I made the
>>> students aware about SugarLabs, Turtleblocks and Musicblocks.
>>>
>>> Venue- Jaipur International School, Jaipur, Rajasthan, India
>>> Held on- Dec 8th 2018, 12 noon to 1 pm
>>> Size- 25 Students (aged 13 to 17 years)
>>>
>>> Kindly see the blog post
>>>
>>> https://ashnidh1.blogspot.com/2018/12/workshop-on-sugar-introduction-of.html
>>>
>>> Thank you very much
>>> Regards
>>> Ashnidh Khandelwal
>>> A GCI 2018 Student
>>> ___
>>> 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] Workshop Success

[Pratul Kumar]

Appreciated your work !!

On Sun 9 Dec, 2018, 6:34 PM Amaan Iqbal  Great! Keep up the good work.
>
> On Sun, Dec 9, 2018 at 6:29 PM Jaskirat Singh 
> wrote:
>
>> Nice work. Keep going
>>
>> On Sun, 9 Dec 2018, 6:24 pm Hrishi Patel, 
>> wrote:
>>
>>> Great. Thanks for the effort :)
>>>
>>> On Sun, Dec 9, 2018, 6:22 PM Sarthak Agrawal <1sarthak@gmail.com
>>> wrote:
>>>
 I held the workshop today at my home.I invited all the primary school
 kids from my locality and taught them about Sugarizer.They did many
 activities such as Grid Activity,Tank Activity,Paint Activity etc. The
 workshop was a huge success and the kids got to learn a lot through the
 activities. I also gave away a trophy to the one who participated the best
 in this workshop and many prizes to others. I created a slideshow on my
 workshop and here is the YouTube link to it :
 https://youtu.be/coAB52apG_Q
 ___
 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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [SLOB] GCI 2018

[Pratul Kumar]

I would also love to contribute as Google Code-In mentor this year.


On Sun, Sep 9, 2018 at 5:11 PM Vipul Gupta  wrote:

> As stated already, count me in as well. Would be my first Googe Code-In
>
> On Sun, Sep 9, 2018 at 3:54 PM Sumit Srivastava 
> wrote:
>
>> Hi, can I please be a mentor? I'm a musician-coder-teacher.
>> I've been following sugar labs code base, specifically music blocks
>> religiously.
>>
>> I've also been following the mailing list for every advancement in the
>> community.
>>
>> Can I please be a mentor. I haven't contributed to the codebase a lot,
>> like other GSoC students since I haven't applied for any of these but I
>> believe I can bring some unique expertise regarding music and it's
>> intricacies since I had engaged in few fruitful discussions on issues
>> related to my expertise.
>>
>> Can I please be a mentor for music blocks, alongside others?
>>
>> Regards,
>> Sumit Srivastava
>>
>> On Sat, 8 Sep 2018, 2:12 am Walter Bender, 
>> wrote:
>>
>>> We seem to have sufficient interest from the community to apply to
>>> Google Code-in again this year. Lots of returning mentors and some students
>>> who have morphed into mentors as well. But I will not apply w/o SLOB
>>> approval.
>>>
>>> Motion: Sugar Labs will apply to participate in Google Code-in 2018.
>>> Walter will be the primary administrator.
>>>
>>> Time in of the essence as the schedule this year has applications
>>> starting this week, so please respond ASAP.
>>>
>>> regards.
>>>
>>> -walter
>>>
>>> --
>>> 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
>>
>
>
> --
> Cordially,
> Vipul Gupta
> Mixster <https://mixstersite.wordpress.com/> | Github
> <https://github.com/vipulgupta2048>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


-- 
*​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

*GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
* HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
LNMIIT, *Head of Developers* Group *HackerEarth*
  [image: LinkedIn]  <https://www.linkedin.com/in/pratul1997/> [image:
Github]  <https://github.com/Pratul1997>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Final Report GSoC 2018

[Pratul Kumar]

Hi,
Here is the report for my GSoC project this summer: https://goo.gl/D9KqrG

It has been a great learning curve this summer,
Please share your suggestions and feedback.

Thanks

-- 
*Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

*GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
* HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
LNMIIT, *Head of Developers* Group *HackerEarth*
  [image: LinkedIn]  <https://www.linkedin.com/in/pratul1997/> [image:
Github]  <https://github.com/Pratul1997>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Response in Re: you needed Assistance

[Pratul Kumar]

Hello James,
Hope you are doing well.

> No, not really.  Members of Sugar Labs have never been _required_ to keep
their contributions in one place.  You would have to ask each member.

I looked at your mail several times and analyzed that there is a threat
that many of our valuable Sugarlabs projects are not part of Sugarlabs
Github organization and
They are forked from the developer's profile to the Sugarlabs organization
like:

*1*>>>>>https://github.com/sugarlabs/sugarizer

*2*>>>>>https://github.com/llaske/sugarizer

And there might be several other situations too and there might be some
which don't be even forked.

So the problem arises that In link_1 Issues are not listed and in link_2
issues are listed but it is not a part of Sugarlabs GitHub organization,
Currently, my API call is such that in Github Sugarlabs organization, I am
looking for all the open issues which are labeled with some specific labels.

So What solution I seek to this problem is that if Sugarlabs community
members can share links to those Github Repo which are not part of current
Github organization, so that I can add search issues API call from those
repositories too.
For this method, I would share a google doc where the community members can
share the link to there GitHub repository.

Or another method is that if we add those repo to Github organization and
further work is done in the GitHub organization repositories.

If there is any other possible solution to it, then kindly let know
regarding it.

Thanks,
Pratul Kumar

On Mon, May 14, 2018 at 12:30 PM, James Cameron  wrote:

> On Mon, May 14, 2018 at 12:03:51PM +0530, Pratul Kumar wrote:
> > *Hello James,
> > Hope you are doing well.
> >
> >  This all information would be part of Developer Dashboard
> >
> > > Repositories must also include those that are not in the /sugarlabs/
> > organization, such as the Help Activity and many others.
> >
> > For this, if you can let me know regarding other potential repositories,
> then I
> > can have a add them to my script too.
>
> No, not really.  Members of Sugar Labs have never been _required_ to
> keep their contributions in one place.  You would have to ask each
> member.
>
> We have some of those repositories cloned to /sugarlabs/, but probably
> not all of them.  Cloned repositories are not kept up to date.
>
> An example of an important repository that should be tracked is the
> repository from which /sugarlabs/sugarizer is cloned.
>
> > > I still don't think a developer dashboard will help Sugar Labs at
> a social
> > level, because we have so few developers.
> >
> > Each year new developer's are there around GCI who are looking for the
> > organization to contribute and be their part,
>
> We may not be successful in applying for GCI this year.  Our care and
> diligence as a community should recognise that possibility and plan
> for it as well.
>
> > What I feel that want things to be ease contribute to the organization
> through
> > Github, but without having the knowledge to do so they step back.
> > Further, new developers need some social rewards for their work, if that
> can be
> > reflected in our Developer Dashboard.
> > Let us give a try to improve our developer count through this
> methodology,
> > although it won't give a drastic improvement.
>
> As I said, I don't mind if you try, it's just that your argument and
> others argument is unconvincing.  Amazing claims need amazing
> evidence, and the evidence so far is not amazing.  Tony's assessment
> of how badly Sugar runs on Ubuntu 18.04 is more real.
>
> > If required then that can be used to organize our own program like GCI
> for
> > about a months before GCI with a bit similar methodology, where our new
> mentors
> > can know what they need to do during GCI. This is to engage a greater
> number of
> > Developers to Sugarlabs.
> > ‌
> > Regards,
> > Pratul Kumar
> >
> > On Mon, May 14, 2018 at 11:33 AM, Pratul Kumar <[1]
> pratulkumar1...@gmail.com>
> > wrote:
> >
> > *Hello Vipul,
> > Hope you are doing well.
> >
> > Thanks, Vipul for your initiative for help, yesterday I figured out
> the
> > methodology for my problem.
> > I used GitHub API instead using any NPM module or library. I read
> your mail
> > after I had sorted out the problem.
> > Once again I would like to thank you for the same.
> >
> > Regards,
> > Pratul Kumar
> >
> > On Mon, May 14, 2018 at 2:27 AM, James Cameron <[2]qu...@laptop.org>
> wrote:
> >
> > All data from GitHub issu

Re: [Sugar-devel] Response in Re: you needed Assistance

[Pratul Kumar]

Hello James,
Hope you are doing well.

 This all information would be part of Developer Dashboard

> Repositories must also include those that are not in the /sugarlabs/
organization, such as the Help Activity and many others.

For this, if you can let me know regarding other potential repositories,
then I can have a add them to my script too.

> I still don't think a developer dashboard will help Sugar Labs at a social
level, because we have so few developers.

Each year new developer's are there around GCI who are looking for the
organization to contribute and be their part,
What I feel that want things to be ease contribute to the organization
through Github, but without having the knowledge to do so they step back.
Further, new developers need some social rewards for their work, if that
can be reflected in our Developer Dashboard.
Let us give a try to improve our developer count through this methodology,
although it won't give a drastic improvement.

If required then that can be used to organize our own program like GCI for
about a months before GCI with a bit similar methodology, where our new
mentors
can know what they need to do during GCI. This is to engage a greater
number of Developers to Sugarlabs.
‌
Regards,
Pratul Kumar

On Mon, May 14, 2018 at 11:33 AM, Pratul Kumar 
wrote:

> Hello Vipul,
> Hope you are doing well.
>
> Thanks, Vipul for your initiative for help, yesterday I figured out the
> methodology for my problem.
> I used GitHub API instead using any NPM module or library. I read your
> mail after I had sorted out the problem.
> Once again I would like to thank you for the same.
>
> Regards,
> Pratul Kumar
>
> On Mon, May 14, 2018 at 2:27 AM, James Cameron  wrote:
>
>> All data from GitHub issues would be useful for a developer dashboard.
>>
>> It's not simple.  Repositories must also include those that are not in
>> the /sugarlabs/ organisation, such as the Help Activity, and many
>> others.
>>
>> Pratul is writing a web application, and likely coding in JavaScript,
>> so the GitHub REST API https://developer.github.com/v3/ should have
>> what is needed.  If Pratul has a problem with the API, ask GitHub Help
>> team or #github IRC channel. The GitHub API is not part of Sugar.
>>
>> I still don't think a developer dashboard will help Sugar Labs at a
>> social level, because we have so few developers, but I've no objection
>> to someone trying it.
>>
>> On Sun, May 13, 2018 at 10:44:59AM +0530, Vipul Gupta wrote:
>> > Hi,
>> > Over the problem, you were having - You need all issues of a every
>> Repository
>> > in Sugar Labs. I would need some clarification on the same.
>> >
>> > 1. How do you need all the issues (Issue description, just titles, on
>> respect
>> > to what, repo to repo or some other criteria?)
>> > 2. Why Javascript, I couldn't understand this part. Shouldn't you need
>> the
>> > output in a more accessible format like JSON for instance? You can use
>> the
>> > GitHub API for the same (I strongly recommend PyGitHub)
>> >
>> > Cordially,
>> > Vipul Gupta
>> > [1]Mixster | [2]Github
>> > Ps - I did read your messages, that day on IRC. I made the draft at
>> night but
>> > forgot to send it until now and yesterday I was busy with my community
>> meetup.
>> >
>> > References:
>> >
>> > [1] https://mixstersite.wordpress.com/
>> > [2] https://github.com/vipulgupta2048
>>
>> > ___
>> > Sugar-devel mailing list
>> > Sugar-devel@lists.sugarlabs.org
>> > http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>> --
>> James Cameron
>> http://quozl.netrek.org/
>>
>
>
>
> --
> *​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*
>
> *GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
> * HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
> LNMIIT, *Head of Developers* Group *HackerEarth*
>   [image: LinkedIn]  <https://www.linkedin.com/in/pratul1997/> [image:
> Github]  <https://github.com/Pratul1997>
>
>


-- 
*​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

*GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
* HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
LNMIIT, *Head of Developers* Group *HackerEarth*
  [image: LinkedIn]  <https://www.linkedin.com/in/pratul1997/> [image:
Github]  <https://github.com/Pratul1997>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Response in Re: you needed Assistance

[Pratul Kumar]

Hello Vipul,
Hope you are doing well.

Thanks, Vipul for your initiative for help, yesterday I figured out the
methodology for my problem.
I used GitHub API instead using any NPM module or library. I read your mail
after I had sorted out the problem.
Once again I would like to thank you for the same.

Regards,
Pratul Kumar

On Mon, May 14, 2018 at 2:27 AM, James Cameron  wrote:

> All data from GitHub issues would be useful for a developer dashboard.
>
> It's not simple.  Repositories must also include those that are not in
> the /sugarlabs/ organisation, such as the Help Activity, and many
> others.
>
> Pratul is writing a web application, and likely coding in JavaScript,
> so the GitHub REST API https://developer.github.com/v3/ should have
> what is needed.  If Pratul has a problem with the API, ask GitHub Help
> team or #github IRC channel. The GitHub API is not part of Sugar.
>
> I still don't think a developer dashboard will help Sugar Labs at a
> social level, because we have so few developers, but I've no objection
> to someone trying it.
>
> On Sun, May 13, 2018 at 10:44:59AM +0530, Vipul Gupta wrote:
> > Hi,
> > Over the problem, you were having - You need all issues of a every
> Repository
> > in Sugar Labs. I would need some clarification on the same.
> >
> > 1. How do you need all the issues (Issue description, just titles, on
> respect
> > to what, repo to repo or some other criteria?)
> > 2. Why Javascript, I couldn't understand this part. Shouldn't you need
> the
> > output in a more accessible format like JSON for instance? You can use
> the
> > GitHub API for the same (I strongly recommend PyGitHub)
> >
> > Cordially,
> > Vipul Gupta
> > [1]Mixster | [2]Github
> > Ps - I did read your messages, that day on IRC. I made the draft at
> night but
> > forgot to send it until now and yesterday I was busy with my community
> meetup.
> >
> > References:
> >
> > [1] https://mixstersite.wordpress.com/
> > [2] https://github.com/vipulgupta2048
>
> > _______
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> --
> James Cameron
> http://quozl.netrek.org/
>



-- 
*​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

*GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
* HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
LNMIIT, *Head of Developers* Group *HackerEarth*
  [image: LinkedIn]  <https://www.linkedin.com/in/pratul1997/> [image:
Github]  <https://github.com/Pratul1997>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Review Request of GSoC Proposal: Making a Beginner Guide

[Pratul Kumar]

Hello,
Thanks for the guidance, reviews and feedbacks.

Kindly help me with the answer to one of the questions of "You and
Community".

Question:  If your project is successfully completed, what will its impact
be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in
length. The first one should be yours. The other two should be answers from
members of the Sugar Labs community, at least one of whom should be a Sugar
Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
https://docs.google.com/document/d/1Xzn-ub8pBCQuz9-RfltzHqDZqY7uZ2xF77MFP_9fKzw/edit?usp=sharing


Thanks,
Pratul Kumar

On Tue, Mar 20, 2018 at 8:45 PM, Pratul Kumar 
wrote:

> Hello,
>
> Thanks for providing feedback and guiding me in the right direction.
> I have worked on it and tried to add them and make things bit more refined.
>
> https://docs.google.com/document/d/1Xzn-ub8pBCQuz9-
> RfltzHqDZqY7uZ2xF77MFP_9fKzw/edit?usp=sharing
>
> Kindly have a look at it and if there is something which can be improved,
> kindly let me know,
> I will be more than happy to work on it.
>
> Regards,
> Pratul Kumar
>
> On Mon, Mar 19, 2018 at 1:02 PM, James Cameron  wrote:
>
>> G'day Pratul,
>>
>> Thanks for the opportunity to comment on your draft proposal.
>>
>> Your proposal suffers from lack of measurable controls for risks.  In
>> general, you've added responses to the risks which are mostly either
>> aspirational, hopeful, or procedural.  Some of the responses don't
>> address the risks.
>>
>> For reference, here is what I had previously written on these risks;
>>
>> http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055030.html
>>
>> Please do not use HTML for the beginner guide.  Instead, please use
>> Markdown.  Markdown has a wider audience of authors.  HTML should be
>> generated automatically.
>>
>> Please consider better controls for risk #3.  My post on 14th February
>> gave some ideas.  Just claiming that you'd like to keep working on the
>> project after GSoC ... doesn't seem probable.  It is aspirational.
>>
>> --
>> James Cameron
>> http://quozl.netrek.org/
>>
>
>
>
> --
> *​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*
>
> *GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
> * HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
> LNMIIT, *Head of Developers* Group *HackerEarth*
>   [image: LinkedIn]  <https://www.linkedin.com/in/pratul1997/> [image:
> Github]  <https://github.com/Pratul1997>
>
>


-- 
*​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

*GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
* HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
LNMIIT, *Head of Developers* Group *HackerEarth*
  [image: LinkedIn]  <https://www.linkedin.com/in/pratul1997/> [image:
Github]  <https://github.com/Pratul1997>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Review Request of GSoC Proposal: Making a Beginner Guide

[Pratul Kumar]

 Hello,

Thanks for providing feedback and guiding me in the right direction.
I have worked on it and tried to add them and make things bit more refined.

https://docs.google.com/document/d/1Xzn-ub8pBCQuz9-RfltzHqDZqY7uZ2xF77MFP_9fKzw/edit?usp=sharing

Kindly have a look at it and if there is something which can be improved,
kindly let me know,
I will be more than happy to work on it.

Regards,
Pratul Kumar

On Mon, Mar 19, 2018 at 1:02 PM, James Cameron  wrote:

> G'day Pratul,
>
> Thanks for the opportunity to comment on your draft proposal.
>
> Your proposal suffers from lack of measurable controls for risks.  In
> general, you've added responses to the risks which are mostly either
> aspirational, hopeful, or procedural.  Some of the responses don't
> address the risks.
>
> For reference, here is what I had previously written on these risks;
>
> http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055030.html
>
> Please do not use HTML for the beginner guide.  Instead, please use
> Markdown.  Markdown has a wider audience of authors.  HTML should be
> generated automatically.
>
> Please consider better controls for risk #3.  My post on 14th February
> gave some ideas.  Just claiming that you'd like to keep working on the
> project after GSoC ... doesn't seem probable.  It is aspirational.
>
> --
> James Cameron
> http://quozl.netrek.org/
>



-- 
*​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

*GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
* HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
LNMIIT, *Head of Developers* Group *HackerEarth*
  [image: LinkedIn]  <https://www.linkedin.com/in/pratul1997/> [image:
Github]  <https://github.com/Pratul1997>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Review Request of GSoC Proposal: Making a Beginner Guide

[Pratul Kumar]

Hello Everyone,
I am Pratul Kumar, a sophomore at LNMIIT Jaipur.

After discussion with community members previously, I have drafted a
proposal with well-thought implementation workflow.

As I always believe that nothing in this world is perfect, there is always
a scope for improvement in everything.

I am eager to discuss much more about the proposal and your reviews and
feedback are vital and valuable for this project.

https://wiki.sugarlabs.org/go/Summer_of_Code/2018/Making_a_Beginner_Guide

Regards,
Pratul Kumar
-- 
*​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

* Mentor* & Beta Tester at *Coursera*,
* HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
LNMIIT, *Head of Developers* Group *HackerEarth*
  [image: LinkedIn]  <https://www.linkedin.com/in/pratul1997/> [image:
Github]  <https://github.com/Pratul1997>




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

Re: [Sugar-devel] GSoC Project Contribution

[Pratul Kumar]

 Hello Walter,

I went through this link https://publiclab.github.io/community-toolbox/
<https://publiclab.github.io/community-toolbox/> and thanks for sharing it
with me.

It looks like its functioning is mainly governed by a bot name plotsbot
<https://github.com/publiclab/plotsbot>.

Another organization which we have kept in the look from beginning Coala
also use such bot corobo <https://github.com/coala/corobo>.
This bot mainly functions on their Gitter channel, I have seen its working
in past few days.
These days I am looking forward how it is made, seems that it is itself
going to be a decent project.

I am looking how to make it in the easier way and if feasible I will try to
work on it.

Regards,
Pratul Kumar

On Fri, Feb 16, 2018 at 6:48 PM, Walter Bender 
wrote:

> https://publiclab.github.io/community-toolbox/ is an example of a
> direction we might want to consider. Especially in light of the fact that
> we have issues spread across so many different repositories.
>
> On Fri, Feb 16, 2018 at 12:24 AM, Pratul Kumar 
> wrote:
>
>> Hello,
>> Hope you all are doing well.
>>
>> As we have already discussed my interest in the project - "Making a
>> Beginner Guide" since this project can be highly valuable to our community
>> for future aspects.
>>
>> After reading the conversation regarding the coding and programming touch
>> for GSoC projects, I went through Beginner Guides of few other
>> organizations, observed them.
>>
>>  and I have few suggestions which we can add to the current draft of this
>> project idea(Making a beginner guide).
>>
>> We can add login and dashboard feature to our website where we are going
>> to write beginner guide like the one Mozilla has written (link
>> <https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction>).
>>  The
>> purpose of making dashboard is to make a newcomer feel more close to the
>> community. The dashboard will have certain features of adding Profile
>> Photo, About us section.Also, privacy can be maintained by the users.
>>
>> The dashboard can be logged in through single click integrated with
>> Google Gmail ID or Github like KDE
>> <https://season.kde.org/?q=program_home&prg=46>.
>>
>> Some of the benefits of adding this property to the current plans are
>> given.
>> 1. The user can add shortcuts to their dashboard just by single click if
>> they want to add some pages of the beginner guide for their future
>> reference, It will make things better and easy to use.
>>
>> 2. Badges: We can add the feature of badges like you get some badge when
>> you complete the certain portion of the guide, And more badges get added
>> when you completed other parts of the guide. It will be a motivation factor
>> for the students.
>>
>> The option of login will not be the compulsory part, the documentation
>> can be viewed without even logging.
>> These features will be the add-on to the current idea of Beginner Guide.
>>
>> It will bring good coding touch to the project and also this dashboard
>> feature can be explored in the much better way in future like Season of KDE
>> dashboard and certain other competitions like BOSS - Bountiful Open
>> Source Summer <https://lab.codingblocks.com/boss/>.
>>
>> Currently, I have skills required to implement this project and I am very
>> much enthusiastic and eager to do more on this project.
>>
>> Prerequisite:HTML,CSS,JavaScript,Bootstrap,Jquery,NodeJs,Angular,MongoDB.
>>
>> Regards,
>> Pratul Kumar
>>
>> On Wed, Feb 14, 2018 at 9:22 PM, Pratul Kumar 
>> wrote:
>>
>>> Hi James,
>>>
>>> .>  - use your other students _during_ the project rather than _after_,
>>> so that the content can be reviewed and refined by beginners,
>>>
>>> I also think getting feedback from newcomer from starting will be more
>>> beneficial.
>>>
>>>
>>>
>>> >  So it will be helpful to Sugar Labs if your content can be maintained by
>>> others.
>>>
>>> So for it, I think we can utilize Github pages and Cname them to our
>>> link.
>>> So other collaborators can also use and change them from Github
>>> according to their requirements and needs.
>>> Therefore others can also maintain it.
>>>
>>>
>>>
>>> Yes, I will try to use only those Tools and Frameworks which are Open
>>> Source and are extremely easy to deploy.
>>>
>>> Regards,
>>> Pratul Kumar
>>>
>>> On Wed, Feb 14, 20

Re: [Sugar-devel] GSoC Project Contribution

[Pratul Kumar]

 Hello,
Hope you all are doing well.

As we have already discussed my interest in the project - "Making a
Beginner Guide" since this project can be highly valuable to our community
for future aspects.

After reading the conversation regarding the coding and programming touch
for GSoC projects, I went through Beginner Guides of few other
organizations, observed them.

 and I have few suggestions which we can add to the current draft of this
project idea(Making a beginner guide).

We can add login and dashboard feature to our website where we are going to
write beginner guide like the one Mozilla has written (link
<https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction>).
The
purpose of making dashboard is to make a newcomer feel more close to the
community. The dashboard will have certain features of adding Profile
Photo, About us section.Also, privacy can be maintained by the users.

The dashboard can be logged in through single click integrated with Google
Gmail ID or Github like KDE <https://season.kde.org/?q=program_home&prg=46>.

Some of the benefits of adding this property to the current plans are given.
1. The user can add shortcuts to their dashboard just by single click if
they want to add some pages of the beginner guide for their future
reference, It will make things better and easy to use.

2. Badges: We can add the feature of badges like you get some badge when
you complete the certain portion of the guide, And more badges get added
when you completed other parts of the guide. It will be a motivation factor
for the students.

The option of login will not be the compulsory part, the documentation can
be viewed without even logging.
These features will be the add-on to the current idea of Beginner Guide.

It will bring good coding touch to the project and also this dashboard
feature can be explored in the much better way in future like Season of KDE
dashboard and certain other competitions like BOSS - Bountiful Open Source
Summer <https://lab.codingblocks.com/boss/>.

Currently, I have skills required to implement this project and I am very
much enthusiastic and eager to do more on this project.

Prerequisite:HTML,CSS,JavaScript,Bootstrap,Jquery,NodeJs,Angular,MongoDB.

Regards,
Pratul Kumar

On Wed, Feb 14, 2018 at 9:22 PM, Pratul Kumar 
wrote:

> Hi James,
>
> .>  - use your other students _during_ the project rather than _after_, so 
> that
> the content can be reviewed and refined by beginners,
>
> I also think getting feedback from newcomer from starting will be more
> beneficial.
>
>
>
> >  So it will be helpful to Sugar Labs if your content can be maintained by
> others.
>
> So for it, I think we can utilize Github pages and Cname them to our link.
> So other collaborators can also use and change them from Github according
> to their requirements and needs.
> Therefore others can also maintain it.
>
>
>
> Yes, I will try to use only those Tools and Frameworks which are Open
> Source and are extremely easy to deploy.
>
> Regards,
> Pratul Kumar
>
> On Wed, Feb 14, 2018 at 11:14 AM, James Cameron  wrote:
>
>> G'day Pratul,
>>
>> Thanks for your answer.  The controls you propose for risks seem well
>> thought out, though I'd propose one small change;
>>
>> - use your other students _during_ the project rather than _after_, so
>>   that the content can be reviewed and refined by beginners,
>>
>> I'll try to answer your other questions;
>>
>> Content hosted by Sugar Labs is maintained by many collaborators,
>> using different editing or deployment tools.
>>
>> Your project is to make some more content.
>>
>> So it will be helpful to Sugar Labs if your content can be maintained
>> by others.
>>
>> Measuring maintainability of content, by measuring the involvement by
>> others, is my proposed control for the risk #3 of content being
>> abandoned.
>>
>> Using certain front-end frameworks means nothing to me without first
>> knowing the work flow for maintenance; what form will the content be
>> maintained in, and what tools will be required by any maintainer?  Are
>> the tools and frameworks open source and easily deployed?
>>
>> Recently, we have begun to favour GitHub Markdown; it has a low
>> barrier of entry, and is reasonably easy to understand.
>>
>> --
>> James Cameron
>> http://quozl.netrek.org/
>>
>
>
>
> --
> *​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*
>
> *GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
> * HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
> LNMIIT, *Head of Developers* Group *HackerEarth*
> *C.A*.@*GeeksforGeeks*, Interntheory, *

Re: [Sugar-devel] GSoC Project Contribution

[Pratul Kumar]

Hi James,

.>  - use your other students _during_ the project rather than _after_, so that
the content can be reviewed and refined by beginners,

I also think getting feedback from newcomer from starting will be more
beneficial.



>  So it will be helpful to Sugar Labs if your content can be maintained by
others.

So for it, I think we can utilize Github pages and Cname them to our link.
So other collaborators can also use and change them from Github according
to their requirements and needs.
Therefore others can also maintain it.



Yes, I will try to use only those Tools and Frameworks which are Open
Source and are extremely easy to deploy.

Regards,
Pratul Kumar

On Wed, Feb 14, 2018 at 11:14 AM, James Cameron  wrote:

> G'day Pratul,
>
> Thanks for your answer.  The controls you propose for risks seem well
> thought out, though I'd propose one small change;
>
> - use your other students _during_ the project rather than _after_, so
>   that the content can be reviewed and refined by beginners,
>
> I'll try to answer your other questions;
>
> Content hosted by Sugar Labs is maintained by many collaborators,
> using different editing or deployment tools.
>
> Your project is to make some more content.
>
> So it will be helpful to Sugar Labs if your content can be maintained
> by others.
>
> Measuring maintainability of content, by measuring the involvement by
> others, is my proposed control for the risk #3 of content being
> abandoned.
>
> Using certain front-end frameworks means nothing to me without first
> knowing the work flow for maintenance; what form will the content be
> maintained in, and what tools will be required by any maintainer?  Are
> the tools and frameworks open source and easily deployed?
>
> Recently, we have begun to favour GitHub Markdown; it has a low
> barrier of entry, and is reasonably easy to understand.
>
> --
> James Cameron
> http://quozl.netrek.org/
>



-- 
*​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

*GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
* HKUST University**Stanford* Scholar Internship,* Mozilla* Club Captain
LNMIIT, *Head of Developers* Group *HackerEarth*
*C.A*.@*GeeksforGeeks*, Interntheory, *Sub-Coordinator* Innovation, and
Incubation Center, Finance@*IEEE* LNMIIT
<https://github.com/Pratul1997>
  <https://twitter.com/PRATUL1997>
<https://www.linkedin.com/in/pratul1997/>

<https://www.quora.com/profile/Pratul-Kumar-2>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GSoC Project Contribution

[Pratul Kumar]

Hi James,
Thanks for such well explained response.

Risk #1; your beginner guide does not help a beginner.
Regarding it, I had thought that bringing all the resources at a single
place with proper linking within, it might help to properly navigate.
So, instead of having multiple newcomer guides resources, we can add all
the resource in one place.

I have large student community in my college, so after the project
completes, I had a thought to organize a Sugarlabs online seminar, where we
can guide them about Open Source contribution, and direct them to these
newcomer guide website.
So, it will provide me raw feedback from them and I can improve that guide
further.




Risk #2; your beginner guide conflicts with other information.
I had thought to add current beginner guide information to the new
project's website(beginner guide website), and then remove information from
the current existing guide and put the link to new guide at those places.
So, it will be easy to maintain and update them at one place.





Risk #3; your beginner guide is abandoned soon after publishing.

Sugarlabs is my first organization where I got to know what and how Open
Source work and Walter has been great support all this time.
I would like to keep modifying and maintaining them according to community
guideline and projects, even after GSoC overs.
So the work and guide will always be nearly updated according to the
current standards of the community.


Few Parts I was unable to understand, Kindly explain them:

>  So in working on this "making a beginner guide" project, please;
>  - measure or assess the edits by others, (which will depend on the tools
or sources you choose to use),
>  - promote edits by others,
>  - provide some form of social reward.

I wanted to know while making the website can I use certain front-end
frameworks like Bootstrap, Material or any other.

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

[Sugar-devel] GSoC Project Contribution

[Pratul Kumar]

Hello all,
I am Pratul Kumar, I am second year undergraduate from LNM Institute of
Information Technology, India.

I have been part of Sugarlabs community and was one of the mentor for GCI
this year.
During my initial time it was bit difficult for me to set up projects
because of the lack of beginner guide.
I would like to make a beginner guide and work on the project " Making a
Beginner Guide ".
I have started observing Coala and other organisation New comer guide.

I would like to take the opportunity to work and develop this project and
contribute to Sugarlabs via this project.

I wanted to start working on it, so I need guidance on how to draft the
work for this project.

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