258
edits
Changes
Jump to navigation
Jump to search
mLine 22:
Line 22: +
Summer of Code/2010/Improved Sugar on a Stick (view source)
Revision as of 15:51, 5 April 2010
, 15:51, 5 April 2010→About your project
#* If, at this point, time should be left, I will continue to investigate on integrating upstream projects, such as [https://fedorahosted.org/abrt/ ABRT] into Sugar. Giving users a way of reporting crashes in Sugar automatically is another aspect, that will allow even less experienced students to contribute to the community by simply reporting their experiences with Sugar on a Stick.
#* If, at this point, time should be left, I will continue to investigate on integrating upstream projects, such as [https://fedorahosted.org/abrt/ ABRT] into Sugar. Giving users a way of reporting crashes in Sugar automatically is another aspect, that will allow even less experienced students to contribute to the community by simply reporting their experiences with Sugar on a Stick.
#* Finally, working on a [http://packagekit.org/ PackageKit] interface to provide users with an actual upgrade path using the distribution's RPM packages would be a huge improvement, compared to requiring users to wait for the next release and start from scratch each time. This is a key part of Sugar on a Stick's way to become actually deployable in masses. However, since time is scarce, this aspect will only be tackled if the other ideas are completed early.
#* Finally, working on a [http://packagekit.org/ PackageKit] interface to provide users with an actual upgrade path using the distribution's RPM packages would be a huge improvement, compared to requiring users to wait for the next release and start from scratch each time. This is a key part of Sugar on a Stick's way to become actually deployable in masses. However, since time is scarce, this aspect will only be tackled if the other ideas are completed early.
#* I'll be evaluating options of different options on file system usage for Sugar on a Stick, if time permits.
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
#* May 24 - 30: initial gathering of information, diving into python
#* May 24 - 30: initial gathering of information, diving into python