Re: [Sugar-devel] Starting with the contributions to sugar labs

[James Cameron]

Welcome Swathi.

Please see "How to get started as a Sugar Labs developer [v8]"
http://lists.sugarlabs.org/archive/sugar-devel/2019-November/057323.html

Please ask any specific questions on the mailing list, thanks.

On Mon, Dec 02, 2019 at 10:52:29AM +0530, Swathi Kasikala wrote:
> Hey,
> 
> This is Swathi Kasikala a sophomore from Amrita Vishwa Vidyapeetam, Kerala
> pursuing CSE. I am very interested and excited to be a part of the sugar labs
> organization. As of it, I would like to start my contributions so can anyone
> help me out regarding how to stat with things and proceed further.
> 
> --
> Regards,
> 
> Swathi Kasikala.
> [1]Blog || [2]GitHub || [3]LinkedIn
> [4]Foss@Amrita
> [5]Amrita Vishwa Vidyapeetham
> 
> References:
> 
> [1] https://wordpress.com/view/missflash54.wordpress.com
> [2] https://github.com/swathi-0901
> [3] https://www.linkedin.com/in/swathi-kasikala-2938a9179/
> [4] https://amfoss.in/accounts/222/
> [5] https://www.amrita.edu/

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


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

Re: [Sugar-devel] Starting with the contributions to sugar labs

[Swathi Kasikala]

Hey,

This is Swathi Kasikala a sophomore from Amrita Vishwa Vidyapeetam, Kerala
pursuing CSE. I am very interested and excited to be a part of the sugar
labs organization. As of it, I would like to start my contributions so can
anyone help me out regarding how to stat with things and proceed further.

-- 
Regards,

Swathi Kasikala.
Blog  || GitHub
 || LinkedIn

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

[Sugar-devel] GCI begins in less than 24 hours

[Walter Bender]

Just a reminder that GCI begins at 13:00 ET on 1 December.

Please try to be available in the Sugar Labs IRC channel to help field
questions from the contestants.

Also, please remember that the contestants are youths ages 13-17, here not
just to participate but also to learn. Try to be patient with them.

Feel free to help them as you would any contributor. At the same time, we
expect them to adhere to our community standards and maintain
high standards. As far as approving tasks, please consult with one of the
admins (Ibiam, Lionel, and me) so that we can maintain a consistent
standard.

Communication about individual tasks is generally handled inside the
proprietary GCI platform, making it inaccessible to non-mentors. But we
should encourage the students to use IRC and this list when possible so
that the entire community can have a window into the work and discussions.
Mentors, please use this email list for our communications about GCI (with
the exception of a situation that would compromise the privacy of a
contestant).

We have 201 tasks published. We can add more as the contest progresses.
Mentors and non-mentors, please feel free to make suggestions to this list.

If you have any questions, please let Lionel, Ibiam, or me know.

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

Re: [Sugar-devel] Participating in Google Code-In

[James Cameron]

Welcome Abhay.  Nice game, thanks.  Well done for a first time.

I've a few suggestions, in no particular order;

1.  the game initially starts with the snake moving very quickly. but
slows down on the first change of direction; perhaps it should start
at the speed that it means to go on with,

2.  someone who has never used the game may find it a struggle to
understand what to do; perhaps add some instructions or demonstration
at the beginning, before starting the game.  If you do this, write and
design for a small child who is yet to read.

3.  add copyright and license; something like GPLv3+ would be very
welcome,

4.  review other snake games and borrow features, have a look at
https://github.com/sugarlabs/hfoss-sugar-snake

5.  add the Sugar wrapper for PyGame, so that the game can be bundled
and run as a Sugar activity, have a look at
https://github.com/sugarlabs/sugargame

6.  let the game operate in full screen, and adjust the snake and
apple sizes to proportions of the full screen size; at the moment the
game runs in a 640x480 VESA size window, which on a large high
resolution display is very small,

7.  the CPU use is very high, which leads to energy loss, low battery
and cooling fans; in turn this is because of (a) the frame rate, (b)
no dirty rectangle management, and (c) competition with lots of
Terminal output caused by print(running, points).

Humans find 25 to 50 frames per second acceptable for these types of
games.

Dirty rectangle management is a technique where only the parts of the
screen that have changed are updated instead of using flip.  You can
find how to manage dirty rectangles in our Sugargame test activity;

https://github.com/sugarlabs/sugargame/blob/master/test/TestGame.py

Removing the print is easy.

On Sat, Nov 30, 2019 at 04:59:02PM +0530, Abhay Malik wrote:
> Hey,
> Hope you all are doing fine, after getting all the suggestions I checked the
> sugar labs GitHub account. I got to see some repositories having python and
> they were using PyGame, so I decided to learn PyGame because I was very
> fascinated, in the process I built a a Snake Game from scratch myself. Have a
> look at this <[1]https://github.com/Abhay-dot/Snake-Game-> 
> Please let me know your suggestions, will I be able to use python in the GCI.
>   
> 
> On Nov 16, 2019, at 14:09, Abhay Malik <[2]eshanmalik150...@gmail.com>
> wrote:
> 
> Thanks for the suggestion,
> I checked the web version and played around with it, I checked the getting
> started document ([3]https://wiki.sugarlabs.org/go/Getting_Started). I’m a
> bit confused, I have a Mac book air, I just wanted to know what steps
> should I do so that I can get the software running on my Mac.
> 
> Thank you,
> Abhay
> 
> On Nov 7, 2019, at 00:03, Abhay Malik <[4]eshanmalik150...@gmail.com>
> wrote:
> 
> Thank you so much Mr. Walter, I’m really excited to complete tasks in
> GCI.
> Any quick pointers for me, for example, where should I start from?
> I have my holidays and have a lot of time so I can learn.
> 
> Thank you,
> Abhay 
> 
> On Nov 5, 2019, at 01:44, Walter Bender 
> <[5]walter.ben...@gmail.com
> > wrote:
> 
> You don't need to "join" Sugar Labs to participate in GCI. Just
> enter the contest when it becomes available to students and look
> for projects on the Sugar Labs page in GCI. We'll have lots of
> Python and JavaScript projects, as well as design, research,
> documentation, and out reach projects to choose from. Plan on
> having fun!!!
> 
> On Mon, Nov 4, 2019 at 10:41 AM Abhay Malik <[6]
> eshanmalik150...@gmail.com> wrote:
> 
> Hi,
> This is Abhay, I’m 13 years old and I live in Singapore. I
> recently got to know about Google Code-In and as a hobby I
> learned python, after looking at the Google Code-In website I
> found about Sugar Labs. I spent some time on the demo and I
> liked it, I wanted to know what should be my next step to join
> Sugar Labs and contribute to the Google Code-In.
> 
> Thank you,
> Abhay
> 
> ___
> Sugar-devel mailing list
> [7]Sugar-devel@lists.sugarlabs.org
> [8]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> Walter Bender
> Sugar Labs
> [9]http://www.sugarlabs.org
> [10]
> 
> References:
> 
> [1] https://github.com/Abhay-dot/Snake-Game-
> [2] mailto:eshanmalik150...@gmail.com
> [3] https://wiki.sugarlabs.org/go/Getting_Started
> [4] mailto:eshanmalik150...@gmail.com
> [5] mailto:walter.ben...@gmail.com
> [6] mailto:eshanmalik150...@gmail.com
> [7] 

[Sugar-devel] [Announcement] Sugarizer Server v1.2 is available

[Lionel Laské]

Hi all,


I'm proud to announce the version 1.2 of Sugarizer Server [1] the server
side of Sugarizer application [2].

Thanks to our recent participation to Google Summer of Code and to
feedbacks from our users and from our Sugarizer Deployment in Saint-Ouen
[3], this new Sugarizer Server version integrate major features and
improvements.

 Specifically, new features in this version are:

   - Teacher profile: teachers are now able to connect with a specific
   account and handle their classrooms and students without a global view of
   the deployment.
   - Customizable Stats: Statistics view in dashboard is now fully
   customizable with more than 15 charts to understand all aspects of
   Sugarizer usage in your school.
   - Tutorial: The dashboard contains now a full tutorial to explain all
   features for all screens to admins and teachers.
   - Import/Export: The dashboard integrate import/export features to
   populate easily your database with new teachers and students accounts.
   - Improved UI: Columns sorting, more user friendly error messages,
   improved classroom view, more responsive IO, … the dashboard UI has been
   reviewed to be more usable by teachers/admins.
   - QRCode connection: Connect your Sugarizer application to your server
   in in few seconds by using the QR Code integrated within the dahsboard,
   - Unlimited storage: Database now support unlimited Journal size and
   Journal item up to 256mb,
   - Improved command line options: activate/desactivate logs, detect and
   show node.js version, … new options and features allow you to have more
   control on your server.
   - Optimization: ESLint and Grunt minimizer are now integrated to improve
   code quality and performance. A new aggregate API has also been created to
   optimize stats generation.



Find a detailed change log on [4].

Sugarizer Server 1.2  is available for any computer using Docker or could
be directly installed on Linux, MacOS or Windows. A specific documentation
explain how to deploy on a RaspberryPI, Google Cloud Platform or Amazon Web
Service. See here for more [5].

Note that since Sugarizer v1.0, Sugarizer Application and Sugarizer Server
are split and are updated separately. So Sugarizer Server v1.2 could be use
by Sugarizer Application v1.0, v1.1 or v1.2.



   Lionel.


P.S.: Special thanks for their contribution on this version to  Nikhil Mehra,
Tarun K. Singhal, Ashish Aggarwal and to all GSoC contributors.


[1] https://github.com/llaske/sugarizer-server

[2] https://sugarizer.org

[3] https://wiki.sugarlabs.org/go/Sugarizer_Saint-Ouen_deployment

[4] https://github.com/llaske/sugarizer-server/blob/master/CHANGELOG.md

[5]
https://github.com/llaske/sugarizer-server/tree/master#running-sugarizer-server
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel