Re: [Sugar-devel] happy birthday Sugar Labs

[Amaan Iqbal]

🎂🎉🎉🎊

On Fri, May 15, 2020 at 7:34 PM prakash ujjwal 
wrote:

> 🎂🥳🥳
>
> On Fri, May 15, 2020, 7:30 PM Favour Kelvin 
> wrote:
>
>> 🥳🥳🎂🎉🎉
>>
>> On Fri, 15 May 2020, 14:57 Jaskirat Singh, 
>> wrote:
>>
>>> 🎉🎊🎊🎊🎉✌😀
>>>
>>> On Fri, 15 May 2020, 7:21 pm ANIKET MATHUR, 
>>> wrote:
>>>
 🥳🥳🥳

 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

>>> ___
>>> 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] Participating in Google Code-In

[Amaan Iqbal]

You can head over to
https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
to
see the steps you need to follow in order to set up Sugar Development
Environment on your system.

Also please visit
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md  to
learn how to start contributing.

Feel free to post here in case you require any help with the setup.

Thanks,
Amaan


On Sat, Nov 16, 2019 at 3:36 PM Vaibhav Aren  wrote:

> Go to the section "Sugar on a Virtual Machine" or head directly to
> Sugar-VirtualBox  guide.
>
>
> On Sat, Nov 16, 2019 at 2:09 PM Abhay Malik 
> wrote:
>
>> Thanks for the suggestion,
>> I checked the web version and played around with it, I checked the
>> getting started document (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  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  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 
>> 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
>>> 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
>>
> ___
> 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

[Amaan Iqbal]

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

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

[Amaan Iqbal]

Thrilled to hear that we are participating this time too.
I am interested in mentoring again this year.

Thanks,
Amaan

On Fri, Oct 11, 2019 at 8:57 PM ANIKET MATHUR  wrote:

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

Re: [Sugar-devel] How can I contribute?

[Amaan Iqbal]

Hi Oluebube,
Welcome to SugarLabs!
Glad to hear that you are interested to contribute to SugarLabs. Since you
have experience mostly with front-end development, I would suggest you jump
to some javascript related repository on https://github.com/sugarlabs/.
There are a lot of PRs currently open and you can choose any of them
according to your skills which are not being worked upon by anyone else.

Following is a list by James which is suggested for any newcomer.

New to Sugar Labs?  Unlock these achievements.  Work from top to
> bottom.
>
> 1.  Use Sugar or Sugarizer,
>
>
> https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md
>
> * by using Sugar or Sugarizer you will learn how it works, and
>   what can be improved.
>
> * mandatory,
>
> 2.  Read our Code of Conduct,
>
>
> https://github.com/sugarlabs/sugar-docs/blob/master/src/CODE_OF_CONDUCT.md
>
> * especially note the need to choose an appropriate forum, and
>   remind others to do the same,
>
> * mandatory,
>
> 3.  Join the developer mailing list,
>
> https://lists.sugarlabs.org/listinfo/sugar-devel
>
> * for asking questions and helping others,
>
> * subscribe before posting,
>
> * don't use digest mode if you plan to post messages or replies,
>   as it breaks threads,
>
> * try to keep discussions public; the default reply mode is
>   private, use reply-all,
>
> * mandatory,
>
> 4.  Get a GitHub account,
>
> https://github.com/
>
> * for reporting issues that you won't fix,
>
> * for fixing problems in source code,
>
> * recommended,
>
> 5.  Join the Sugar Labs GitHub organisation,
>
> https://github.com/sugarlabs
>
> * for regular source code contributors, and reviewers, by
>   invitation, contact one of the existing members,
>
> * helpful for mail notification of GitHub activity,
>
> * optional,
>
> 6.  Join as a Member of Sugar Labs,
>
> https://wiki.sugarlabs.org/go/Sugar_Labs/Members
>
> * requires some contribution; code, documentation, translations,
>   maintenance, running a Sugar deployment, or any other
>   non-trivial activities which benefit Sugar Labs,
>
> * reviewed by committee,
>
> * optional,
>
> 7.  Get a wiki.sugarlabs.org account,
>
> https://wiki.sugarlabs.org/
>
> * needed for maintaining Wiki content,
>
> * needed as part of moving Wiki content to GitHub,
>
> * for subscribing to edit notifications.
>
> * optional,
>
> 8.  Get an activities.sugarlabs.org account,
>
> https://activities.sugarlabs.org/
>
> * needed for releasing new versions of Sugar activities,
>
> * optional,
>
> 9.  Get a shell.sugarlabs.org account,
>
> https://wiki.sugarlabs.org/go/Service/shell#Requesting_a_shell_account
>
> * requires a justification,
>
> * also provides a @sugarlabs.org mail alias,
>
> * for releasing new versions of Sugar components, test builds,
>   or large data sets,
>
> * for limited experimentation with non-root network services, such
>   as bots or IRC proxies,
>
> * optional,
>
> 10. Get a translate.sugarlabs.org account,
>
> https://translate.sugarlabs.org/
>
> * if you are bi- or multi-lingual, use your skills,
>
> * especially if you can test Sugar activities and components, as
>   this will inform your translations,
>
> * optional,
>
> 11. Get a bugs.sugarlabs.org account,
>
> https://bugs.sugarlabs.org/
>
> * only if you must maintain old bug reports,
>
> * new issues may be reported via GitHub,
>
> * optional,
>
> 12. Join Sugar on Fedora live system mailing list,
>
> https://lists.sugarlabs.org/listinfo/soas
>
> * download, test, report bugs, fix bugs, package,
>
> * share your experience with others who focus on this
>   distribution,
>
> * optional,
>
> 13. Join Sugar on Debian mailing lists,
>
>
> https://github.com/sugarlabs/sugar/blob/master/docs/debian.md#packaging
>
> * download, test, report bugs, fix bugs, package,
>
> * share your experience with others who focus on this distribution,
>
> * optional,
>
> 14. Join the Internet Relay Chat channel #sugar
>
> irc://irc.freenode.net/#sugar
>
> * for synchronous chat with others,
>
> * requires registration with freenode.net,
>
> * optional,
>
> 15. Join the Internet Relay Chat channel #sugar-meeting
>
> irc://irc.freenode.net/#sugar-meeting
> http://meeting.sugarlabs.org/
>
> * for meetings, but keep your own transcripts and minutes,
>
> * requires registration with freenode.net,
>
> * optional,
>
> 16. Join Gitter
>
> https://gitter.im/
>
> * for chat with others,
>
> * best is mailing list sugar-devel@ for topics of general interest,
>
> * requires registration with one of several organisations,
>
> * optional,
>
> 17. Maintain an Activity
>
>
> https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer
>
> 

Re: [Sugar-devel] first-time only issues

[Amaan Iqbal]

I meant these trivial tasks should just be for providing confidence to the
newcomers so that they can at least get started. It may be less productive
but will help them keep going.

We can also have a *Suggestions *section on the readme of every repo. I
just thought about this. And there can be a new set of issues on every repo
to come up with 2 specific suggestions, say

   - Come up with an updated look of specific section of an activity/website
   - Come up with a latest idea of some specific functionality
   - Come up with two new feature suggestions for xyz activity/website
   - Find redundant codes etc.

I strongly feel some of the suggestions could be worth having and may be
such that we have not thought about it so far. But overall these will be a
basic reason for the newcomers to go through the code base and start
helping. After having an understanding of the code base, our mission, and
our community, it may be onto them how longer they want to be a part of us.

All in all, there has to be a *Why? *for every question, then only we could
maximize our potential. For instance, if the following Why?'s could be
answered properly, it will mean we are going in right direction otherwise
we need to find the answer to these Why?'s. Some of them are

   - Why should a newcomer contribute?
   - Why should past contributor keep contributing?
   - Why should I learn something new for SugarLabs?


*If none sounds good, I have another idea!*
Can we have a seasonal/monthly/quarterly competition for the newcomers? We
may have SugarLabs T-shirt or some other award for the top 3-5 contributors.
Here newcomers may be defined as anyone with less than 50 commits or so.
Also, SugarLabs T-Shirt will be another reason for Offline Publicity and
hence will encourage the friends of the winners to compete next time.

I find it much more interesting to be honest.

What do you think?
(Any newcomer to sugar-devel, please feel free to share what do you think
about this)

Thanks,
Amaan

On May 3, 2019 11:32 AM, "James Cameron"  wrote:

> Thanks.  Yes, it makes sense.
>
> But it is like directing an investigation.  A true and well-done
> investigation is one where the investigator is independent of bias.
>
> When we bias the newcomers toward certain tasks, we tend only to get
> those tasks done.  An example is how we've had many activities ported
> to GTK 3 and still not yet released.
>
> I've got "Maintain an activity" on my "How to get started as a Sugar
> Labs developer";
>
> http://lists.sugarlabs.org/archive/sugar-devel/2019-April/056615.html
>
> And also on our "Contribute code"
>
>
> https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#modifying-activities
>
> There seems to be a hope that the reason why we don't have newcomers
> doing this is because they find it too hard, and they want something
> easier, like changing colours.
>
> I'm not sure that this is true.  I think the reasons why we don't have
> newcomers doing anything this are far more profound;
>
> 1.  very few other people are doing anything; development has slowed,
>
> 2.  work done by others earlier has not been merged, or not released,
>
> 3.  there are more interesting things to do,
>
> A way to be sure is to ask our newcomers why they chose not to do
> anything.  Or why a newcomer made a few patches and did not help to
> get an activity released.  We might also ask the oldtimers why they
> have chosen not to help, or not to learn new skills.
>
> On Fri, May 03, 2019 at 11:08:44AM +0530, Amaan Iqbal wrote:
> > I meant if the color palette update(actual update in the code),
> Improvised look
> > (in the code), suggestion etc is of some value, then their PR can
> directly be
> > merged.
> >
> > Also we can have a section in each repo Readme for some 'expected
> > functionalities' to have, which the newcomers can directly update. So
> that they
> > can get the feel of getting the PR merged.
> >
> > For redundant codes, the newcomers may find 2 places where similar code
> is
> > appearing and remove either of them and send corresponding PR.
> >
> > Regarding console errors, we may have basic issues, specific to each
> error say
> > of datatype mismatch etc which doesn't block the expected behavior but
> better
> > to fix them. These issues can be worked upon by the newcomers and will
> require
> > finding out which module is located where. This will help them dig
> deeper into
> > the code base and contribute further.
> >
> > I hope it makes sense.
> >
> > Thanks,
> > Amaan
> >
> > On May 3, 2019 9:37 AM, "James Cameron" <[1]qu...@laptop.org> wrote:
> >
> 

Re: [Sugar-devel] first-time only issues

[Amaan Iqbal]

I meant if the color palette update(actual update in the code), Improvised
look(in the code), suggestion etc is of some value, then their PR can
directly be merged.

Also we can have a section in each repo Readme for some 'expected
functionalities' to have, which the newcomers can directly update. So that
they can get the feel of getting the PR merged.

For redundant codes, the newcomers may find 2 places where similar code is
appearing and remove either of them and send corresponding PR.

Regarding console errors, we may have basic issues, specific to each error
say of datatype mismatch etc which doesn't block the expected behavior but
better to fix them. These issues can be worked upon by the newcomers and
will require finding out which module is located where. This will help them
dig deeper into the code base and contribute further.

I hope it makes sense.


Thanks,
Amaan

On May 3, 2019 9:37 AM, "James Cameron"  wrote:

> Interesting idea.  But I've an ethical problem with creating issues
> that don't need to be fixed, and will never merge.  It seems arbitrary
> and unfair to a new contributor.
>
> On the other hand, some of the issues you listed have general value;
> such as minimising console output.
>
> On Fri, May 03, 2019 at 09:05:07AM +0530, Amaan Iqbal wrote:
> > I have a suggestion here. We may create some issues with beginner
> labels, such
> > that solving it may not be really helpful to us at first, but it can give
> > insights of the code base to the new contributors.
> >
> > For instance, an issue for trying new color palette for our SugarLabs
> website.
> > Or an issue for trying different border radius, color to a section of any
> > activity  etc.
> >
> > These may be useful in the long run especially if a new contributor can
> come up
> > with something out of the box. Or atleast it will help them get familiar
> to our
> > code base.
> >
> > These can be marked as 'reserved for beginners'. Some examples of these
> issue
> > can be
> > * Try color palette ABC to our website
> > * Try color palette EFG to our website
> > * Change the border radius of xyz element to make it look better
> > * Update padding/look of xyz section of abc activity
> > * Come up with 2 instances of redundant codes in xyz repo of SugarLabs
> > * Come up with the idea of 2 features improvement for xyz repo
> > * Come up with an idea to implement xyz functionality
> > * Minimize console errors of abc activity
> >
> > I guess some of these would be interesting to the user even if they
> don't know
> > how to code. It will definitely help in attracting a good number of new
> > contributors.
> >
> > Also, it would not affect the development time of the experienced
> contributors
> > since these issues would not require deep understanding of the code base
> or any
> > skill.
> >
> > Thanks,
> > Amaan
> >
> >
> > On May 3, 2019 4:07 AM, "James Cameron" <[1]qu...@laptop.org> wrote:
> >
> > You're saying leave some flaws rather than fix them.
> >
> > In general that's a good idea for attracting new members to a
> > community, but it takes investment in preparing the issue, and if
> that
> > investment is greater than fixing the flaw there's not much benefit.
> >
> > Also, when I do create issues, some experts use it as an opportunity
> > to post off-topic criticism, and some beginners don't apply any
> > diligence before asking questions.  The issues sit there with the
> > criticism or questions and answers, and nothing else gets done.  We
> > have plenty of them.
> >
> > What we really need is a well-functioning community of people with a
> > common goal who will listen to each other.  Create that first, then
> > the beginner issues can be created.
> >
> > On Thu, May 02, 2019 at 06:23:13PM +0530, Sumit Srivastava wrote:
> > > I've already been saying we need more issues that are marked as
> beginner
> > > issues.
> > >
> > > We have too few!
> > >
> > > To the community: Let me know if you see an issue that needs to be
> marked
> > as a
> > > beginner issue, or comment on it and someone will tag it.
> > >
> > > Regards
> > > Sumit
> > >
> > > On Thu, 2 May 2019, 5:29 pm Walter Bender, <[1][2]
> walter.ben...@gmail.com
> > > wrote:
> > >
> > > Something to consider: [2][3]https://
> publiclab

Re: [Sugar-devel] first-time only issues

[Amaan Iqbal]

I have a suggestion here. We may create some issues with beginner labels,
such that solving it may not be really helpful to us at first, but it can
give insights of the code base to the new contributors.

For instance, an issue for trying new color palette for our SugarLabs
website. Or an issue for trying different border radius, color to a section
of any activity  etc.

These may be useful in the long run especially if a new contributor can
come up with something out of the box. Or atleast it will help them get
familiar to our code base.

These can be marked as 'reserved for beginners'. Some examples of these
issue can be
* Try color palette ABC to our website
* Try color palette EFG to our website
* Change the border radius of xyz element to make it look better
* Update padding/look of xyz section of abc activity
* Come up with 2 instances of redundant codes in xyz repo of SugarLabs
* Come up with the idea of 2 features improvement for xyz repo
* Come up with an idea to implement xyz functionality
* Minimize console errors of abc activity

I guess some of these would be interesting to the user even if they don't
know how to code. It will definitely help in attracting a good number of
new contributors.

Also, it would not affect the development time of the experienced
contributors since these issues would not require deep understanding of the
code base or any skill.


Thanks,
Amaan


On May 3, 2019 4:07 AM, "James Cameron"  wrote:

> You're saying leave some flaws rather than fix them.
>
> In general that's a good idea for attracting new members to a
> community, but it takes investment in preparing the issue, and if that
> investment is greater than fixing the flaw there's not much benefit.
>
> Also, when I do create issues, some experts use it as an opportunity
> to post off-topic criticism, and some beginners don't apply any
> diligence before asking questions.  The issues sit there with the
> criticism or questions and answers, and nothing else gets done.  We
> have plenty of them.
>
> What we really need is a well-functioning community of people with a
> common goal who will listen to each other.  Create that first, then
> the beginner issues can be created.
>
> On Thu, May 02, 2019 at 06:23:13PM +0530, Sumit Srivastava wrote:
> > I've already been saying we need more issues that are marked as beginner
> > issues.
> >
> > We have too few!
> >
> > To the community: Let me know if you see an issue that needs to be
> marked as a
> > beginner issue, or comment on it and someone will tag it.
> >
> > Regards
> > Sumit
> >
> > On Thu, 2 May 2019, 5:29 pm Walter Bender, <[1]walter.ben...@gmail.com>
> wrote:
> >
> > Something to consider: [2]https://publiclab.org/notes/gauravano/
> 03-29-2019/software-community-growth-through-first-timers-only-issues
> >
> > --
> > Walter Bender
> > Sugar Labs
> > [3]http://www.sugarlabs.org
> > [4]
> > ___
> > Sugar-devel mailing list
> > [5]Sugar-devel@lists.sugarlabs.org
> > [6]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1] mailto:walter.ben...@gmail.com
> > [2] https://publiclab.org/notes/gauravano/03-29-2019/software-
> community-growth-through-first-timers-only-issues
> > [3] http://www.sugarlabs.org/
> > [4] http://www.sugarlabs.org/
> > [5] mailto:Sugar-devel@lists.sugarlabs.org
> > [6] 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

Re: [Sugar-devel] Google Season of Docs-2019

[Amaan Iqbal]

Hello Shivanshu,

Welcome to SugarLabs. As such, there is no prerequisite for contributing to
SugarLabs. You can visit https://github.com/sugarlabs/GSoD to see our
updates about GSoD anytime as mentioned by Vipul.

Best way to begin is to start contributing to any of our repositories on
https://github.com/sugarlabs/ with the technologies you are already
familiar with.

Here is a list by James to get started.

New to Sugar Labs?  Unlock these achievements.  Work from top to
> bottom.
>
> 1.  Use Sugar or Sugarizer,
>
>
> https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md
>
> * by using Sugar or Sugarizer you will learn how it works, and
>   what can be improved.
>
> * mandatory,
>
> 2.  Read our Code of Conduct,
>
>
> https://github.com/sugarlabs/sugar-docs/blob/master/src/CODE_OF_CONDUCT.md
>
> * especially note the need to choose an appropriate forum, and
>   remind others to do the same,
>
> * mandatory,
>
> 3.  Join the developer mailing list,
>
> https://lists.sugarlabs.org/listinfo/sugar-devel
>
> * for asking questions and helping others,
>
> * subscribe before posting,
>
> * don't use digest mode if you plan to post messages or replies,
>   as it breaks threads,
>
> * try to keep discussions public; the default reply mode is
>   private, use reply-all,
>
> * mandatory,
>
> 4.  Get a GitHub account,
>
> https://github.com/
>
> * for reporting issues that you won't fix,
>
> * for fixing problems in source code,
>
> * recommended,
>
> 5.  Join the Sugar Labs GitHub organisation,
>
> https://github.com/sugarlabs
>
> * for regular source code contributors, and reviewers, by
>   invitation, contact one of the existing members,
>
> * helpful for mail notification of GitHub activity,
>
> * optional,
>
> 6.  Join as a Member of Sugar Labs,
>
> https://wiki.sugarlabs.org/go/Sugar_Labs/Members
>
> * requires some contribution; code, documentation, translations,
>   maintenance, running a Sugar deployment, or any other
>   non-trivial activities which benefit Sugar Labs,
>
> * reviewed by committee,
>
> * optional,
>
> 7.  Get a wiki.sugarlabs.org account,
>
> https://wiki.sugarlabs.org/
>
> * needed for maintaining Wiki content,
>
> * needed as part of moving Wiki content to GitHub,
>
> * for subscribing to edit notifications.
>
> * optional,
>
> 8.  Get an activities.sugarlabs.org account,
>
> https://activities.sugarlabs.org/
>
> * needed for releasing new versions of Sugar activities,
>
> * optional,
>
> 9.  Get a shell.sugarlabs.org account,
>
> https://wiki.sugarlabs.org/go/Service/shell#Requesting_a_shell_account
>
> * requires a justification,
>
> * also provides a @sugarlabs.org mail alias,
>
> * for releasing new versions of Sugar components, test builds,
>   or large data sets,
>
> * for limited experimentation with non-root network services, such
>   as bots or IRC proxies,
>
> * optional,
>
> 10. Get a translate.sugarlabs.org account,
>
> https://translate.sugarlabs.org/
>
> * if you are bi- or multi-lingual, use your skills,
>
> * especially if you can test Sugar activities and components, as
>   this will inform your translations,
>
> * optional,
>
> 11. Get a bugs.sugarlabs.org account,
>
> https://bugs.sugarlabs.org/
>
> * only if you must maintain old bug reports,
>
> * new issues may be reported via GitHub,
>
> * optional,
>
> 12. Join Sugar on Fedora live system mailing list,
>
> https://lists.sugarlabs.org/listinfo/soas
>
> * download, test, report bugs, fix bugs, package,
>
> * share your experience with others who focus on this
>   distribution,
>
> * optional,
>
> 13. Join Sugar on Debian mailing lists,
>
>
> https://github.com/sugarlabs/sugar/blob/master/docs/debian.md#packaging
>
> * download, test, report bugs, fix bugs, package,
>
> * share your experience with others who focus on this distribution,
>
> * optional,
>
> 14. Join the Internet Relay Chat channel #sugar
>
> irc://irc.freenode.net/#sugar
>
> * for synchronous chat with others,
>
> * requires registration with freenode.net,
>
> * optional,
>
> 15. Join the Internet Relay Chat channel #sugar-meeting
>
> irc://irc.freenode.net/#sugar-meeting
> http://meeting.sugarlabs.org/
>
> * for meetings, but keep your own transcripts and minutes,
>
> * requires registration with freenode.net,
>
> * optional,
>
> 16. Join Gitter
>
> https://gitter.im/
>
> * for chat with others,
>
> * best is mailing list sugar-devel@ for topics of general interest,
>
> * requires registration with one of several organisations,
>
> * optional,
>
> 17. Maintain an Activity
>
>
> https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer
>
> * many learner focused activities (apps) need simple ma

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

[Amaan Iqbal]

Amazing!!

Congratulations to us!

On Feb 26, 2019 4:26 AM, "Samson Goddy"  wrote:

> Awesome!
>
>
> Regards
>
> On Mon, Feb 25, 2019, 8:47 PM Walter Bender 
> wrote:
>
>>
>> :)
>>
>> -- Forwarded message -
>> From: Google Summer of Code 
>> Date: Mon, Feb 25, 2019 at 1:16 PM
>> Subject: GSoC 2019: Sugar Labs has been accepted as a mentor organization!
>> To: 
>>
>>
>> [image: Google Summer of Code]
>>
>> Congratulations! Sugar Labs has been selected as a Google Summer of Code
>> 2019 mentor organization.
>>
>> The list of accepted 2019 GSoC mentoring organizations will be published
>> at February 26, 2019 20:00 UTC at https://g.co/gsoc.
>>
>> After it is published, you will be able to invite mentors and update your
>> organization profile.
>>
>> We've let you know before the public announcement, so you can make sure
>> your project ideas are ready for students to review and your org admins and
>> mentors are ready to answer emails from prospective students.
>>
>> Please click here to visit your dashboard: https://summerofcode.
>> withgoogle.com/dashboard/
>>
>> This email was sent to walter.ben...@gmail.com.
>>
>> You are receiving this email because of your participation in Google
>> Summer of Code 2019.
>> https://summerofcode.withgoogle.com
>>
>> To leave the program and stop receiving all emails, you can go to your
>> profile  and
>> request deletion of your program profile.
>>
>> For any questions, please contact gsoc-supp...@google.com. Replies to
>> this message go to an unmonitored mailbox.
>>
>> © 2019 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043,
>> USA
>> 
>>
>>
>> --
>> 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] GSoC 2019 call for assisting mentors

[Amaan Iqbal]

G'day James, I will try confirming before 26th or will let you know about
any other updates from my end.

Thanks!

On Thu, Feb 14, 2019 at 3:59 AM James Cameron  wrote:

> G'day Amaan,
>
> Thanks for your interest.  When you have had the time to confirm,
> please make a pull request to our GSoC 2019 Ideas, or if you can't do
> that let me know and I'll make one for you.
>
> We did change requirements for mentors, as you can see here;
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#coding-mentors
>
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#assisting-mentors
>
> Our GSoC 2019 Ideas shows who have offered to be mentors.  Sugar Labs
> will select mentors based on those offers and the student proposals
> received.  It might be all of the mentors, it might be a few of them,
> we can't really know yet.  Walter will be the most involved, but don't
> go trying to contact him directly, that's unfair on everyone else.
>
> Timeline for GSoC 2019 is here
> https://developers.google.com/open-source/gsoc/timeline
>
> I don't know if there is a final date for mentors to apply, and I'm
> not sure if the question makes sense.  As an organisation we agree to;
>
> *  "Select and invite trusted, capable, and qualified mentors",
>
> *  "Oversee activity of all mentors and students ensuring
>responsibilities are being met", and;
>
> *  "Ensure adequate and appropriate mentoring coverage, particularly
>near holidays".
>
> https://developers.google.com/open-source/gsoc/help/responsibilities
>
> Given the timeline;
>
> *  mentors _should_ get themselves listed by 26th February so that the
>ideas are well defined, and the mentors are visible when the
>mentoring organisations are published, and;
>
> *  mentors _must_ get themselves listed or delisted before the 9th
>April student proposals deadline.
>
> Hope that helps!
>
> On Wed, Feb 06, 2019 at 08:03:26PM +0530, Amaan Iqbal wrote:
> > Hello Everyone,
> >
> > I am interested in mentoring a few of the following projects:
> >
> >   • [1]Reconciling rhythm with pitch in Music Blocks widgets
> >   • [2]Expand Sugarizer Exerciser activity
> >   • [3]Write activity for Sugarizer
> >   • [4]Colored desktop and activity icons
> >   • [5]Improve Sugarizer Server Dashboard
> >
> > But I am unsure of the time which I would be able to allocate during
> May-June
> > due to some specific reasons. I will mostly be available during
> July-August.
> >
> > So I need some time to confirm whether I would be able to mentor or not.
> >
> > Can the board members please tell until when can an organization add
> mentors to
> > GSoC? And if there is any other pre-requisite to be done from my side to
> be
> > eligible to mentor.
> >
> > Regards,
> > Amaan,
> > GCI Mentor,
> > SugarLabs
> >
> > On Mon, Feb 4, 2019 at 11:13 AM James Cameron <[6]qu...@laptop.org>
> wrote:
> >
> > A call for "assisting mentors" for the GSoC 2019 project ideas.
> >
> > You don't need to be able to code.  Please reply to the mailing
> list(s) if
> > you'd like to help with non-coding mentoring, including gathering
> > requirements, visual design, testing, or deployment.
> >
> > Here's a proposed list;
> >
> > [7]https://github.com/sugarlabs/GSoC/blob/
> > 4afd32d144fd0a8df67ed89c58e412ad160e3616/Ideas-2019.md
> >
> > --
> > James Cameron
> > [8]http://quozl.netrek.org/
> > ___
> > Sugar-devel mailing list
> > [9]Sugar-devel@lists.sugarlabs.org
> > [10]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1]
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#reconciling-rhythm-with-pitch-in-music-blocks-widgets
> > [2]
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#expand-sugarizer-exerciser-activity
> > [3]
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#write-activity-for-sugarizer
> > [4]
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#colored-desktop-and-activity-icons
> > [5]
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#improve-sugarizer-server-dashboard
> > [6] mailto:qu...@laptop.org
> > [7]
> https://github.com/sugarlabs/GSoC/blob/4afd32d144fd0a8df67ed89c58e412ad160e3616/Ideas-2019.md
> > [8] http://quozl.netrek.org/
> > [9] mailto:Sugar-devel@lists.sugarlabs.org
> > [10] 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] GSoC 2019 call for assisting mentors

[Amaan Iqbal]

Hello Everyone,

I am interested in mentoring a few of the following projects:

   - Reconciling rhythm with pitch in Music Blocks widgets
   

   - Expand Sugarizer Exerciser activity
   

   - Write activity for Sugarizer
   

   - Colored desktop and activity icons
   

   - Improve Sugarizer Server Dashboard
   


But I am unsure of the time which I would be able to allocate during
May-June due to some specific reasons. I will mostly be available during
July-August.

So I need some time to confirm whether I would be able to mentor or not.

Can the board members please tell until when can an organization add
mentors to GSoC? And if there is any other pre-requisite to be done from my
side to be eligible to mentor.


Regards,
Amaan,
GCI Mentor,
SugarLabs

On Mon, Feb 4, 2019 at 11:13 AM James Cameron  wrote:

> A call for "assisting mentors" for the GSoC 2019 project ideas.
>
> You don't need to be able to code.  Please reply to the mailing list(s) if
> you'd like to help with non-coding mentoring, including gathering
> requirements, visual design, testing, or deployment.
>
> Here's a proposed list;
>
>
> https://github.com/sugarlabs/GSoC/blob/4afd32d144fd0a8df67ed89c58e412ad160e3616/Ideas-2019.md
>
> --
> 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] Sl.org Down?

[Amaan Iqbal]

Yes, it's showing unreachable.

On Jan 26, 2019 5:48 PM, "Sumit Srivastava"  wrote:

> Can't access it too.
>
> On Sat, 26 Jan 2019, 5:46 pm Vipul Gupta, 
> wrote:
>
>> Just tried on Chrome, can't seem to access it.
>>
>> On Sat, Jan 26, 2019 at 4:17 PM Samson Goddy 
>> wrote:
>>
>>> Hello,
>>>
>>> Is it just me or is https://www.sugarlabs.org down?
>>>
>>>
>>> ___
>>> Sugar-devel mailing list
>>> Sugar-devel@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>
>>
>> --
>> Cordially,
>> Vipul Gupta
>> Mixster  | Github
>> 
>> ___
>> 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] Suggestions for GSoC 2019

[Amaan Iqbal]

James Cameron wrote:
>  You replied to me, but that wasn't me you quoted, it was Rahul.

Ya, I know. I just replied to all.

> However, it would be wrong
> to set expectations of colourful software by adding lots of colour to
> the web site.

I just meant to update the color palette, never to have many colors.

> We also need to remain accessible for vision impaired.

True!

> Activities for Sugar are presented by activities.sugarlabs.org and by
> Fedora SoaS.  Activities for Sugarizer are pre-bundled, not presented;
> you'll see the https://sugarizer.org/ web site is much better at
> getting people to engage with the software.

I was not knowing about the latter site. That's really good in terms of
user engagement.

Overall I agree with your opinion James, and also of other board members
and now I too feel this may not be one of the important projects for GSoC.

Thanks,
Amaan

On Wed, Jan 23, 2019 at 7:19 AM James Cameron  wrote:

> Amaan Iqbal wrote:
> > > I don't expect revamping a website to be a _goal_.
> >
> > Without a proper website with the latest content, how can we expect
> > the activities to reach the audience?
>
> You replied to me, but that wasn't me you quoted, it was Rahul.
>
> At the moment activities generally reach the audience through OLPC OS,
> Fedora SoaS, activities.sugarlabs.org and Sugarizer.  Almost never the
> web site.
>
> > > Even if we add a project for improving the website, 2 years down
> > > the line we might again face a similar email pointing out the
> > > drawbacks of the new model and another revamping of the website.
> >
> > This doesn't mean that we will have the same website with the old
> > foundation 10 years down the line. Web technologies and standards
> > have changed significantly in the past 2-3 years and its
> > recommended we too keep our components updated.  The main reason
> > would be similar to why we are updating our activities. Fixing/
> > Updating activities has to do with more engagement with current
> > users and improving the website, to try for more new users. I guess
> > both are equally important.
>
> That wasn't me you quoted, it was Rahul.
>
> Web site components can be kept updated by using a maintained open
> source theme and not tweaking it as incessantly as we have been doing
> with airspace.
>
> While it is similar in general to how we update our activities, this
> is not relevant, because the web site is not an activity.
>
> > > Having less projects does not imply our failure in any sense, lack
> > > of existing contributors might indicate that
> >
> > I agree, but it will be underutilization of potential of an
> > organization which has participated in GSoC for last 10 successive
> > years. We might consider having few more mentors this time if proper
> > mentoring was the issue last time. Even if we are not having this
> > project, we should think of utilizing GSoC to the fullest with tasks
> > related to all the activities wherever significant work is
> > pending. Further, even if we desire to have some new activities, we
> > should think of including that too.
>
> That wasn't me you quoted, it was Rahul.
>
> I'm not worried about underutilisation of potential; there is plenty
> to do, and if anyone is attentive and dutiful toward it they will
> easily find what to do without having to do any updates to the web
> site.  I'm also not worried about having less active projects for this
> GSoC, because we certainly have less active developers, and the last
> thing we want is mentors who aren't active developers, as it leads to
> under-mentoring; project never properly defined, mentor has little
> idea of what the student is doing, and ultimately the student produces
> code that isn't useful, or disappears.  See Google Summer of Code
> Guides, What Makes a Good Mentor?
>
> https://google.github.io/gsocguides/mentor/what-makes-a-good-mentor
>
> Of course, our thanks to all those developers who have made small
> updates to our software in the past few weeks, I appreciate it.
>
> > > I added why a user should get sugar.
> > >
> > > It’s still a work in progress as I figured even the last design
> > > that’s under development now Wouldn’t really solve the problem. We
> > > need MORE call to action buttons, more exciting colors, a better
> > > navigation processes.
> >
> > That's what. I would too suggest improving the color palette we are
> > currently using. The current color palette is not that pleasing at
> > first sight. Also call to action and download buttons on the main
> >

Re: [Sugar-devel] Suggestions for GSoC 2019

[Amaan Iqbal]

> I don't expect revamping a website to be a _goal_.

Without a proper website with the latest content, how can we expect the
activities to reach the audience?

> Even if we add a project for improving the website, 2 years down the line
> we might again face a similar email pointing out the drawbacks of the new
> model and another revamping of the website.

This doesn't mean that we will have the same website with the old
foundation 10 years down the line. Web technologies and standards have
changed significantly in the past 2-3 years and its recommended we too keep
our components updated. The main reason would be similar to why we are
updating our activities. Fixing/Updating activities has to do with more
engagement with current users and improving the website, to try for more
new users. I guess both are equally important.

> Having less projects does not imply our failure in any sense,
> lack of existing contributors might indicate that

I agree, but it will be underutilization of potential of an organization
which has participated in GSoC for last 10 successive years. We might
consider having few more mentors this time if proper mentoring was the
issue last time. Even if we are not having this project, we should think of
utilizing GSoC to the fullest with tasks related to all the activities
wherever significant work is pending. Further, even if we desire to have
some new activities, we should think of including that too.

> I added why a user should get sugar.
>
> It’s still a work in progress as I figured even the last design that’s
> under development now Wouldn’t really solve the problem. We need MORE
> call to action buttons, more exciting colors, a better navigation
> processes.

That's what. I would too suggest improving the color palette we are
currently using. The current color palette is not that pleasing at first
sight. Also call to action and download buttons on the main page itself
would be a good idea to improve the conversion rate. Further better and
clearer navigation is also missing.

>  Hoping to move most primary information from wiki to the site, instead
> of breaking their section on the site to go to wiki(it lost them
> totally)

This is the most important point. I strongly agree with this. Our website
should only have the important information instead of the wikis. It breaks
the flow and makes the user end up getting confused.

> This is as important as improving Sugar Labs tools. Without an
> actionable site our tools won't reach our potential users. We need the
> users (students parents, school administration) to be able to download
> and use Sugar and every other Sugar Labs tools effectively without
> stress then we can record an increase in downloads of these tools we
> put in so much to build.

This is why I thought of this idea. My primary intention is not to get
anything revamped but to improve the way we present our activities to the
user. Also for better maintenance, it is required that we keep our site up
to date and consistent with the standards.

Ultimately I would suggest that we should utilize GSoC to the fullest in
any way we can, be it only with improving the activities.

I will leave further discretion to the board members.


Regards,
Amaan

On Tue, Jan 22, 2019 at 6:18 AM James Cameron  wrote:

> Thanks.  But my vote is no.
>
> It's not three months of coding.
>
> It doesn't solve a problem we have with our software products; Sugar,
> activities, Music Blocks, or Sugarizer.
>
> Our problem with the web site is with the content, in turn because we
> have had few content producers, and too many people proposing style and
> layout changes instead.
>
> Last month, or November, we had a team formed to do A/B testing, but
> the A/B testing has not yet begun.  I'm guessing they are too busy.
> Perhaps it is time for more people to speak up in order to slow it
> down even further.
>
> On Mon, Jan 21, 2019 at 07:44:28PM +0530, Amaan Iqbal wrote:
> > Hello,
> >
> > I see we only have 6 projects so far in our Ideas list in comparison to
> 11
> > which were selected in GSoC last year. Being a successful Open Source
> > organization, I sincerely hope we have the potential of having many more
> > projects in GSoC this year(most probably 15+ if we can come up with such
> > promising ideas).
> >
> > Here I would suggest an idea for the renovation of our Website, [1]blog,
> and
> > creation of a customized/integration of existing CMS to our website from
> where
> > admins can create articles directly. Also some other web pages can also
> be
> > added to this list if I am missing something. The end product will be
> expected
> > to have :
> >
> >   • Material Designed
> >   • no/minimal redundancies in code
> >

[Sugar-devel] Suggestions for GSoC 2019

[Amaan Iqbal]

Hello,

I see we only have 6 projects so far in our Ideas list in comparison to 11
which were selected in GSoC last year. Being a successful Open Source
organization, I sincerely hope we have the potential of having many more
projects in GSoC this year(most probably 15+ if we can come up with such
promising ideas).

Here I would suggest an idea for the renovation of our Website, blog
, and creation of a customized/integration of
existing CMS to our website from where admins can create articles directly.
Also some other web pages can also be added to this list if I am missing
something. The end product will be expected to have :

   - Material Designed
   - no/minimal redundancies in code
   - faster load time
   - Use of latest website standards
   - Wider reach in terms of accessibility
   - Faster and easier updates from the admins to the website
   - Elimination of device specific issues
   - Removal of most of the issues on www-sugarlabs
   
   - Easy setup for a new contributor


After mentoring for few design tasks in GCI and collaborating with several
pull requests I found that the website was mostly constructed with many
components placed forcefully in their places including a search box in the
navbar, such that website looks somehow decent. But the design is not at
all generic and so as a result there use to be many small issues with looks
and behavior of components on different devices. Also, the website is not
updated to the latest web standards.

Further, publicity in the best way with appropriate accessibility
 of the
website is important for any organization and I sincerely hope this idea
has that potential.

Looking forward to hearing your opinion on this before sending a Pull
Request on the GSoC ideas list.



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

Re: [Sugar-devel] [IAEP] GCI design tasks

[Amaan Iqbal]

Great,
There has been a significant improvement in the number and quality of
designs in GCI 2018 in comparison to previous years. Good to see all of
them together.

Thanks

On Sat, Jan 5, 2019 at 3:28 PM Peace Ojemeh  wrote:

> Greetings,
>
> I've upload the designs and attached it to the marketing materials
>  as
> suggested by James n Jaskirat along with the names of the students
>
> Here: GCI'18 Design Tasks
> 
>
> Regards.
>
>
> On Sun, 16 Dec 2018 at 19:37, James Cameron  wrote:
>
>> Yes, Wiki would be better idea, for metadata and presentation.
>>
>> http://people.sugarlabs.org/peaceojemeh/GCI18/ is difficult to browse;
>> have to click on each file, which is time consuming.
>>
>> Also, no idea who did what design.  Loss of credit.
>>
>> On Sat, Dec 15, 2018 at 08:03:52PM +0100, Peace Ojemeh wrote:
>> > Thanks Jaskirat for the suggestion.
>> >
>> > But I had already created one earlier, some file couldn't
>> upload(error:files
>> > are large), sunjammer came to the rescue :)
>> >
>> > here are some of the ones on [1]wiki
>> >
>> > Regards.
>> >
>> > On Sat, 15 Dec 2018 at 18:21, Jaskirat Singh <[2]juskirat2...@gmail.com>
>> wrote:
>> >
>> > Thanks Peace
>> >
>> > Well in the previous GCI, I created a wiki page to collect all the
>> design
>> > related promotional work of GCI student in this wiki [3]https://
>> > wiki.sugarlabs.org/go/Marketing_Team/Marketing_Materials
>> > So I would suggest that if you can paste all the designs here so
>> that they
>> > could be kept on the wiki record too.
>> >
>> > Thanks
>> >
>> > On Sat, Dec 15, 2018 at 10:46 PM Peace Ojemeh <[4]
>> perriefide...@gmail.com>
>> > wrote:
>> >
>> > Greetings,
>> >
>> > Here are the [5]designs from GCI'18.
>> >
>> > Regards.
>> > --
>> > Peace Ojemeh(Perrie)
>> > Twitter: [6]https://twitter.com/Peace_Ojemeh
>> > Email: [7]perriefide...@gmail.com
>> >[8]peaceoje...@sugarlabs.org
>> >
>> > ___
>> > Sugar-devel mailing list
>> > [9]Sugar-devel@lists.sugarlabs.org
>> > [10]http://lists.sugarlabs.org/listinfo/sugar-devel
>> >
>> > --
>> > Jaskirat Singh
>> >
>> > Designer, Developer and community member at Sugar Labs
>> > Open Source Initiative Member
>> > Google Code-In Mentor (2017) for Sugar Labs at Google
>> > Google Summer of Code mentor (2018) for Sugar Labs at Google.
>> >
>> >
>> > --
>> > Peace Ojemeh(Perrie)
>> > Twitter: [11]https://twitter.com/Peace_Ojemeh
>> > Email: [12]perriefide...@gmail.com
>> >[13]peaceoje...@sugarlabs.org
>> >
>> > References:
>> >
>> > [1] https://wiki.sugarlabs.org/go/GCI%2718_Design_Tasks
>> > [2] mailto:juskirat2...@gmail.com
>> > [3] https://wiki.sugarlabs.org/go/Marketing_Team/Marketing_Materials
>> > [4] mailto:perriefide...@gmail.com
>> > [5] http://people.sugarlabs.org/peaceojemeh/GCI18/
>> > [6] https://twitter.com/Peace_Ojemeh
>> > [7] mailto:perriefide...@gmail.com
>> > [8] mailto:peaceoje...@sugarlabs.org
>> > [9] mailto:Sugar-devel@lists.sugarlabs.org
>> > [10] http://lists.sugarlabs.org/listinfo/sugar-devel
>> > [11] https://twitter.com/Peace_Ojemeh
>> > [12] mailto:perriefide...@gmail.com
>> > [13] mailto:peaceoje...@sugarlabs.org
>>
>> > ___
>> > IAEP -- It's An Education Project (not a laptop project!)
>> > i...@lists.sugarlabs.org
>> > http://lists.sugarlabs.org/listinfo/iaep
>>
>>
>> --
>> James Cameron
>> http://quozl.netrek.org/
>>
>
>
> --
> *Peace Ojemeh*(Perrie)
> *Twitter:* https://twitter.com/Peace_Ojemeh
> *Email:* perriefide...@gmail.com
>peaceoje...@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] Sugar Labs 2018-2020 Oversight Board Election Results

[Amaan Iqbal]

Congratulations to all the deserving SLOBs members.

Cheers!!

On Sat, Dec 15, 2018 at 4:38 PM Jaskirat Singh 
wrote:

> Congratulations to new SLOB
>
> On Sat, 15 Dec 2018, 4:35 pm Anmol Mishra, 
> wrote:
>
>> Congratulations to new SLOB members.
>>
>> On Sat, 15 Dec, 2018, 16:32 Samson Goddy >
>>> Hello,
>>>
>>> 43 out of 167 Sugar Labs member voted during the Sugar Labs 2018-2020
>>> Election.
>>>
>>> Congratulations to the winners who have been selected for the 2018-2020
>>> period:
>>>
>>> 1. *Walter Bender*
>>> 2. *James Cameron*
>>> 3. *Lionel Laské*
>>> *4. Alex Perez *
>>> *5. Devin Ulibarri*
>>>
>>> Results are available at the following URL:
>>>
>>>
>>> https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_7e20f77cd6595bfe&rkey=dd2850a107103a39
>>>
>>> For more information about the Condorcet Internet Voting Service, see
>>> http://civs.cs.cornell.edu
>>>
>>> Many thanks to Ibiam Chihurumnaya, Rahul Bothra, Jaskirat Singh, Anmol
>>> Mishra, and Amaan Iqbal for their candidacies submissions and for their
>>> interest to be part of the Sugar Labs Oversight Board.
>>>
>>> Many thanks to everyone in the Membership and Elections Committee, for
>>> all their efforts and time dedicated to maintaining the Sugar Labs member's
>>> list.
>>>
>>> Many thanks to the Wiki and Systems teams for their ongoing support.
>>>
>>>
>>>
>>> *Membership and Elections Committee*
>>> Project Sugar Labs
>>>
>>>
>>> ___
>>> 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] GCI Thank you

[Amaan Iqbal]

Thanks for being a part of GCI this year for SugarLabs. The article was
really amazing.

Looking forward to seeing many more contributions from you for SugarLabs
ahead.

Cheers

On Wed, Dec 12, 2018 at 8:28 PM Jaskirat Singh 
wrote:

> Thanks for your great support during GCI. We had a very good time working
> with you.
> Keep moving forward with your contribution to the community.
>
> Thanks
>
> On Wed, 12 Dec 2018, 8:18 pm Pratul Kumar, 
> wrote:
>
>> 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
>>
> ___
> 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

[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

Re: [Sugar-devel] Workshop Success

[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

Re: [Sugar-devel] GCI plan for chatbot functionality and updating website to bootstrap v4.1.x

[Amaan Iqbal]

Here I am referring to a chatbot functionality for our website and not of a
personal chatbot for someone which can be made to learn in different ways
depending upon the user. If it's brought to the website directly, it may be
trained by some user in an abusive manner which we don't want.

Currently, the chatbot will only guide users in appropriate directions to
serve the purpose of visitor due to which they are visiting our website.
And it won't talk like a real-life bot.


Regards,
Amaan


On Mon, Dec 3, 2018 at 8:03 AM Tony Anderson  wrote:

> Hi Amaan
>
> You are, of course, aware that a chatbot capability is offered by the
> Speak Activity based on Alice. Alice can be 'taught' so that its dialogs
> can be improved. With a simple modification, it can be made to respond by
> default: 'I don't know'. to a question such as 'What is the third planet?'
> to which the user responds: 'The third planet is Mars' would become the
> bots answer to that question. It would be a simple change to add multiple
> chatbots so that a user could build their own.
>
> Naturally, this approach has the benefit of 'low entry' and 'no ceiling'
> to which we aspire in enabling our learners to learn and to learn how to
> learn.
>
> Tony
>
>
> On 12/2/18 12:10 PM, Amaan Iqbal wrote:
>
> Hello Everyone,
>
> I am attaching the plans which our GCI students have created for having a
> chatbot functionality on our website and for updating our website to
> Bootstrap 4.1 which will result in removal of dependency on some plugins
> like owl-carousel and many other custom stylings.
>
> Please find the links below. Any reviews would be appreciated.
>
> Plan for Chatbot functionality
> <https://docs.google.com/document/d/1p4nw0D-oomE7Jrze67kXAyEEUfINlpIKuoSFU8rimQk/edit#heading=h.fnvfgb36iyez>
> Plan for updating the website to bootstrap 4.1.x
> <https://storage.googleapis.com/codein-prod.appspot.com/gci-2018/core_taskupdate/doc/4657339716075520_1542461902_plan.pdf?Expires=1543838895&GoogleAccessId=codein-prod%40appspot.gserviceaccount.com&Signature=huyqIyR0P78oO4JOYt%2BuRhW08LqzCmG8gibMyurQYjHjv8tNnT%2F3%2FzSd53wx03axoYbx%2BbZNOwJm0ED3Nkqy%2FZiUMOm%2FkqAH%2BMedXTTCKb0C%2BdeXA6RDo3nqj6UY7dwbtiTJtNQf3o3WReA3ix8Yd9bX6k1Zxz6WAHQLM6HEgc1kSpNtEQnQDqwi82KfX57WWfdFmdBap4s2mcPOD5WA05VMqe9VWREn5B88KPENXqF4parH1TcsWWR%2B%2FfYlFaWQTNdtooub%2FEXZWWWu4cabA7mUQIBrsJPAYw5znZ1dpt8BmWMYOi3GksqYip3J7x%2BJLUfmYfB8auL9Qz4eO6uM0w%3D%3D>
>
>
> Regards,
> Amaan
>
>
> ___
> Sugar-devel mailing 
> listSugar-devel@lists.sugarlabs.orghttp://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 plan for chatbot functionality and updating website to bootstrap v4.1.x

[Amaan Iqbal]

Thanks. Here I am referring to Collect Chat <https://collect.chat/> chatbot.
Its basic template sends mail to a specified email address with the
response a user has given. Also, the responses can be monitored from
Collect Chat dashboard. For doing these things, just 3 lines of js is
required to be added to the head section which they assign uniquely and
nothing else is needed to be done on the server side from us.

Also, its advanced features support Zapier and API integration to auto sync
data to 500+ apps.

Please visit https://collect.chat/features to know more about it.


Regards

On Sun, Dec 2, 2018 at 7:39 PM Amaan Iqbal  wrote:

> Thanks. Here I am referring to Collect Chat <https://collect.chat/>
> chatbot. Its basic template sends mail to a specified email address with
> the response a user has given. Also, the responses can be monitored from
> Collect Chat dashboard. For doing these things, just 3 lines of js is
> required to be added to the head section which they assign uniquely and
> nothing else is needed to be done on the server side from us.
>
> Also, its advanced features support Zapier and API integration to auto
> sync data to 500+ apps.
>
> Please visit https://collect.chat/features to know more about it.
>
>
> Regards
>
> On Sun, Dec 2, 2018 at 6:01 PM Anmol Mishra 
> wrote:
>
>> I mean, how you plan to accomplish?
>> Chatbot will need a server for query response.
>>
>> On Sun, 2 Dec, 2018, 17:59 Amaan Iqbal >
>>> What do you mean?
>>>
>>> On Dec 2, 2018 5:47 PM, "Anmol Mishra" 
>>> wrote:
>>>
>>>> What options are your hosting options?
>>>>
>>>> On Sun, 2 Dec, 2018, 17:41 Amaan Iqbal >>>
>>>>> Hello Everyone,
>>>>>
>>>>> I am attaching the plans which our GCI students have created for
>>>>> having a chatbot functionality on our website and for updating our website
>>>>> to Bootstrap 4.1 which will result in removal of dependency on some 
>>>>> plugins
>>>>> like owl-carousel and many other custom stylings.
>>>>>
>>>>> Please find the links below. Any reviews would be appreciated.
>>>>>
>>>>> Plan for Chatbot functionality
>>>>> <https://docs.google.com/document/d/1p4nw0D-oomE7Jrze67kXAyEEUfINlpIKuoSFU8rimQk/edit#heading=h.fnvfgb36iyez>
>>>>> Plan for updating the website to bootstrap 4.1.x
>>>>> <https://storage.googleapis.com/codein-prod.appspot.com/gci-2018/core_taskupdate/doc/4657339716075520_1542461902_plan.pdf?Expires=1543838895&GoogleAccessId=codein-prod%40appspot.gserviceaccount.com&Signature=huyqIyR0P78oO4JOYt%2BuRhW08LqzCmG8gibMyurQYjHjv8tNnT%2F3%2FzSd53wx03axoYbx%2BbZNOwJm0ED3Nkqy%2FZiUMOm%2FkqAH%2BMedXTTCKb0C%2BdeXA6RDo3nqj6UY7dwbtiTJtNQf3o3WReA3ix8Yd9bX6k1Zxz6WAHQLM6HEgc1kSpNtEQnQDqwi82KfX57WWfdFmdBap4s2mcPOD5WA05VMqe9VWREn5B88KPENXqF4parH1TcsWWR%2B%2FfYlFaWQTNdtooub%2FEXZWWWu4cabA7mUQIBrsJPAYw5znZ1dpt8BmWMYOi3GksqYip3J7x%2BJLUfmYfB8auL9Qz4eO6uM0w%3D%3D>
>>>>>
>>>>>
>>>>> Regards,
>>>>> Amaan
>>>>>
>>>>> ___
>>>>> 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 plan for chatbot functionality and updating website to bootstrap v4.1.x

[Amaan Iqbal]

What do you mean?

On Dec 2, 2018 5:47 PM, "Anmol Mishra"  wrote:

> What options are your hosting options?
>
> On Sun, 2 Dec, 2018, 17:41 Amaan Iqbal 
>> Hello Everyone,
>>
>> I am attaching the plans which our GCI students have created for having a
>> chatbot functionality on our website and for updating our website to
>> Bootstrap 4.1 which will result in removal of dependency on some plugins
>> like owl-carousel and many other custom stylings.
>>
>> Please find the links below. Any reviews would be appreciated.
>>
>> Plan for Chatbot functionality
>> <https://docs.google.com/document/d/1p4nw0D-oomE7Jrze67kXAyEEUfINlpIKuoSFU8rimQk/edit#heading=h.fnvfgb36iyez>
>> Plan for updating the website to bootstrap 4.1.x
>> <https://storage.googleapis.com/codein-prod.appspot.com/gci-2018/core_taskupdate/doc/4657339716075520_1542461902_plan.pdf?Expires=1543838895&GoogleAccessId=codein-prod%40appspot.gserviceaccount.com&Signature=huyqIyR0P78oO4JOYt%2BuRhW08LqzCmG8gibMyurQYjHjv8tNnT%2F3%2FzSd53wx03axoYbx%2BbZNOwJm0ED3Nkqy%2FZiUMOm%2FkqAH%2BMedXTTCKb0C%2BdeXA6RDo3nqj6UY7dwbtiTJtNQf3o3WReA3ix8Yd9bX6k1Zxz6WAHQLM6HEgc1kSpNtEQnQDqwi82KfX57WWfdFmdBap4s2mcPOD5WA05VMqe9VWREn5B88KPENXqF4parH1TcsWWR%2B%2FfYlFaWQTNdtooub%2FEXZWWWu4cabA7mUQIBrsJPAYw5znZ1dpt8BmWMYOi3GksqYip3J7x%2BJLUfmYfB8auL9Qz4eO6uM0w%3D%3D>
>>
>>
>> Regards,
>> Amaan
>>
>> ___
>> 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] GCI plan for chatbot functionality and updating website to bootstrap v4.1.x

[Amaan Iqbal]

Hello Everyone,

I am attaching the plans which our GCI students have created for having a
chatbot functionality on our website and for updating our website to
Bootstrap 4.1 which will result in removal of dependency on some plugins
like owl-carousel and many other custom stylings.

Please find the links below. Any reviews would be appreciated.

Plan for Chatbot functionality

Plan for updating the website to bootstrap 4.1.x



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

Re: [Sugar-devel] Hello guys please i want to ask if any one can help me on how to convert colors that are in hex to the color name :)

[Amaan Iqbal]

As James pointed out, there is very less color names than all possible hex
colors. There are in total 256*256*256 different RGB colors combinations
and it's silly if someone starts to assign them names. Even many colors can
be formed by a range of RGB combinations which cannot be distinguished.

Maybe we can help more if you could tell for what purpose it's required.



Regards,
Amaan

On Dec 1, 2018 1:30 AM, "Sean DALY"  wrote:

> One possible approach could be to model a hex-name lookup table such as on
> this page [1], rounding to the nearest named color. Some ideas are here [2].
>
> Sean
>
> 1. https://imagemagick.org/script/color.php
> 2. https://stackoverflow.com/questions/38923744/how-to-map-
> a-range-of-hex-values-to-a-color
>
>
>
> On Thu, Nov 29, 2018 at 4:47 PM Walter Bender 
> wrote:
>
>> Not a very easy task. I have some code that could get you a Munsell
>> representation of the color (the hue designation as well as its lightness
>> and vividness, but you'd still need to determine that dark orange == brown,
>> etc.
>>
>> On Thu, Nov 29, 2018 at 4:17 PM Joel Arrey  wrote:
>>
>>>
>>> ___
>>> 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
>>
>
> ___
> 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 task ideas

[Amaan Iqbal]

Hello everyone,

I would like to add tasks for improvising existing sugarlabs website. Like
tasks related to fixing existing issues on www-sugarlabs and updating
atleast the main page of the website in steps to a materialized version of
the same.

Further I see that we have used some redundant libraries too. And at most
places apart from the fact that similar stylings are available in
bootstrap, I see someone tried to use custom css for the same. Also
currently we are having 2 blocking scripts and 3 blocking css resources.
One can find them here
.
Apart from these I can see that we are using obsolete versions of bootstrap
and other plugins.

Because of these overall loading time of the website is also too much and
there is significant room for improvement. I guess it might be important
consideration for SugarLabs to work on few of these in this year GCI. I
will start creating tasks from Friday or latest by Saturday onwards.

Please share your thoughts on this.


Regards
Amaan

On Oct 11, 2018 7:50 AM, "Vipul Gupta"  wrote:

> Very excited for the coming weeks of GCI, created about 10 tasks on GCI
> interface, complete with problem case and references to avoid confusion.
> Please review.
>
> On Thu 11 Oct, 2018, 6:33 AM Walter Bender, 
> wrote:
>
>> We have another two weeks before the contest begins. While we can add
>> tasks at any point, it would be great to get a few more tasks published
>> sooner than later. If you have task ideas (or open issues you think would
>> make good tasks), please share them here.
>>
>> 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