Summer of Code/2017: Difference between revisions

Line 42:

;Expected results: Deployment of a new website for Sugar Labs

;Knowledge prerequisites: JavaScript, HTML, CSS, Ruby, JQuery

|-

| valign=top width="15%" style="background:#e3e4e5;" |Maintenance of activities.sugarlabs.org (ASLO)

| valign=top width="15%" | (volunteers?)

| align=left valign=top |

;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded. Some maintenance tasks are needed. Sugar uses activities.sugarlabs.org in Software Update in My Settings, and has a link to it in the Browse default page.

;Expected results: Fix downloads by non-Sugar browsers; old versions are offered. Fix downloads by new versions of Sugar; old versions are offered. Make activity maintainer take-over easier; not easy at the moment. Adopt the new look from the new [http://www.sugarlabs.org/ sugarlabs.org] site; theme now is quite old. Show new activity.info metadata such as source repository. Other problems listed in [http://bugs.sugarlabs.org bugs.sugarlabs.org] against component [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=activities.sugarlabs.org&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone&order=priority activities.sugarlabs.org]. Semi-automate common maintenance tasks; like adding a new Sugar version. Document future maintenance on the Wiki.

;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git. See [https://github.com/sugarlabs/aslo source code].

|}

@@ Line 42: / Line 42: @@
 ;Expected results: Deployment of a new website for Sugar Labs
 ;Knowledge prerequisites: JavaScript, HTML, CSS, Ruby, JQuery
+|-
+| valign=top width="15%" style="background:#e3e4e5;" |Maintenance of activities.sugarlabs.org (ASLO)
+| valign=top width="15%" | (volunteers?)
+| align=left valign=top |
+;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded.  Some maintenance tasks are needed.  Sugar uses activities.sugarlabs.org in Software Update in My Settings, and has a link to it in the Browse default page.
+;Expected results: Fix downloads by non-Sugar browsers; old versions are offered.  Fix downloads by new versions of Sugar; old versions are offered.  Make activity maintainer take-over easier; not easy at the moment.  Adopt the new look from the new [http://www.sugarlabs.org/ sugarlabs.org] site; theme now is quite old.  Show new activity.info metadata such as source repository.  Other problems listed in [http://bugs.sugarlabs.org bugs.sugarlabs.org] against component [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=activities.sugarlabs.org&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone&order=priority activities.sugarlabs.org].  Semi-automate common maintenance tasks; like adding a new Sugar version.  Document future maintenance on the Wiki.
+;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git.  See [https://github.com/sugarlabs/aslo source code].
 |}