Summer of Code/Jatin Dhankhar: Difference between revisions

Line 85:

===GOALS===

Overview can be divided into following sub goals:

* Improve look/theme of ASLO: Current theme of ASLO seems outdated in comparison to

* Improve look/theme of ASLO: Current theme of ASLO seems outdated in comparison to rest of the sugar ecosystem and making it look modern and easy to user. Here is an instance developer/user register is not visually appealing and there is not sufficient whitespace.

rest of the sugar ecosystem and making it look modern and easy to user. Here is an

instance developer/user register is not visually appealing and there is not sufficient

whitespace.

* Maintain ASLO: This involves fixing the platform, closing in bugs and finding new ones,

also migration to new languages and tooling. For instance making project work with new

also migration to new languages and tooling. For instance making project work with new version of Sphinx, since current version used in source repo is 0.9.9-rc2 (which is over two years old and archived).

version of Sphinx, since current version used in source repo is 0.9.9-rc2 (which is

over two years old and archived).

Relevant PR - https://github.com/sugarlabs/aslo/pull/2

* Adding a CI Pipeline: Adding a CI pipeline will help test integrity of the project, run

* Adding a CI Pipeline: Adding a CI pipeline will help test integrity of the project, run automate tests with each new pull request and help collaboration easier as well as automate the deployment.

automate tests with each new pull request and help collaboration easier as well as

* Develop new ASLO: Following point conflicts with second point, but seems a more viable option than maintaining a slightly dormant system. Develop a new ASLO, preferably under a new subdomain, like activities3.sugarlabs.org, using Django as backend and using git based backend for storing activities to ensure easy rollback and maintenance for developers. Arch Linux, did the same for user provided packages, this approach can be quite useful Arch User Repository. Include robust and useful metadata available which can help in sorting,categorization based upon version number of the activity itself, sugar version with which activity is compatible.

automate the deployment.

* Develop new ASLO: Following point conflicts with second point, but seems a more viable

option than maintaining a slightly dormant system. Develop a new ASLO, preferably under

a new subdomain, like activities3.sugarlabs.org, using Django as backend and using git

based backend for storing activities to ensure easy rollback and maintenance for

developers. Arch Linux, did the same for user provided packages, this approach can be

quite useful Arch User Repository. Include robust and useful metadata available which

can help in sorting,categorization based upon version number of the activity itself, sugar

version with which activity is compatible.

===Benefits to Sugar Labs===

Above mentioned goals will help Sugar Lab by

@@ Line 85: / Line 85: @@
 ===GOALS===
 Overview can be divided into following sub goals:
-* Improve look/theme of ASLO: Current theme of ASLO seems outdated in comparison to
+* Improve look/theme of ASLO: Current theme of ASLO seems outdated in comparison to rest of the sugar ecosystem and making it look modern and easy to user. Here is an instance developer/user register is not visually appealing and there is not sufficient whitespace.
-rest of the sugar ecosystem and making it look modern and easy to user. Here is an
-instance developer/user register is not visually appealing and there is not sufficient
-whitespace.
 * Maintain ASLO: This involves fixing the platform, closing in bugs and finding new ones,
-also migration to new languages and tooling. For instance making project work with new
+also migration to new languages and tooling. For instance making project work with new version of Sphinx, since current version used in source repo is 0.9.9-rc2 (which is over two years old and archived).
-version of Sphinx, since current version used in source repo is 0.9.9-rc2 (which is
-over two years old and archived).
 Relevant PR - https://github.com/sugarlabs/aslo/pull/2
-* Adding a CI Pipeline: Adding a CI pipeline will help test integrity of the project, run
+* Adding a CI Pipeline: Adding a CI pipeline will help test integrity of the project, run automate tests with each new pull request and help collaboration easier as well as automate the deployment.
-automate tests with each new pull request and help collaboration easier as well as
+* Develop new ASLO:  Following point conflicts with second point, but seems a more viable option than maintaining a slightly dormant system. Develop a new ASLO, preferably under a new subdomain, like activities3.sugarlabs.org, using Django as backend and using git based backend for storing activities to ensure easy rollback and maintenance for developers. Arch Linux, did the same for user provided packages, this approach can be quite useful Arch User Repository. Include robust and useful metadata available which can help in sorting,categorization based upon version number of the activity itself, sugar version with which activity is compatible.
-automate the deployment.
-* Develop new ASLO:  Following point conflicts with second point, but seems a more viable
-option than maintaining a slightly dormant system. Develop a new ASLO, preferably under
-a new subdomain, like activities3.sugarlabs.org, using Django as backend and using git
-based backend for storing activities to ensure easy rollback and maintenance for
-developers. Arch Linux, did the same for user provided packages, this approach can be
-quite useful Arch User Repository. Include robust and useful metadata available which
-can help in sorting,categorization based upon version number of the activity itself, sugar
-version with which activity is compatible.
 ===Benefits to Sugar Labs===
 Above mentioned goals will help Sugar Lab by