[Sugar-devel] Suggestions for GSoC 2019

James Cameron quozl at laptop.org
Mon Jan 21 19:47:58 EST 2019

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
>   • 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 [2]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 [3]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
> References:
> [1] http://planet.sugarlabs.org/
> [2] https://github.com/sugarlabs/www-sugarlabs/issues
> [3] https://developer.mozilla.org/en-US/docs/Learn/Accessibility/HTML

> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

James Cameron

More information about the Sugar-devel mailing list