105
edits
Changes
Jump to navigation
Jump to search
Line 46:
Line 46: + + + + + + + + + + + + + + + + + +
→Starting the process
= Starting the process =
= Starting the process =
== Are there specific things I should consider when proposing a feature? ==
Yes.
# How well does this fit into a classroom environment?
#* Of course, Sugar is also designed for use outside of the classroom, but those features that can really enhance the classroom experience are key to increasing the adoption of Sugar.
# How usable and useful is this feature to a young child?
#* The majority of our users are '''12 years old or under''', and have little computing experience.
# Does it scale?
#* Anything that involves a setup process of a person touching each computer is not suitable for deployments.
#* Are there technical aspects which might make your feature workable with a set of 10 computers, but useless with a set of 100? 1000? 10000?
# Does it present technicalities to the deployer?
#* If so, you may be excluding them from using this feature. Unfortunately, many deployments are limited in terms of their technical capabilities, especially when dealing with Linux/open source technologies.
#* If you ''can'' document a technical process in simple terms on a short wiki page, then it may be a realistic task for deployment teams to undertake. But keep in mind that the reader likely does not understand exactly what they are doing, so it needs to be a copy-paste type process.
# Does it rely on (or use) infrastructure or star-style connectivity?
#* If your feature relies or uses networking to talk to some kind of centralized server, then it's probably going to get overloaded after your feature gains adoption in our large user base.
#* Deployers are likely to disable this part of your feature due to the painfully high latencies and costs of internet connections throughout the developing world.
#* If networking is a core part of your feature then make sure it is replicable, e.g. on the OLPC XS school server. Make sure that this process is fully documented with support channels available. For reasons of cost, latency or simply lack of connectivity, many deployments will replicate the global infrastructure you have set up and use your feature exclusively on a LAN level.
== How do I propose a feature idea, even if I can't build it myself? ==
== How do I propose a feature idea, even if I can't build it myself? ==
Community members are encouraged to create new pages for features that enhance or improve Sugar. Anyone can propose new features for Sugar by following these steps:
Community members are encouraged to create new pages for features that enhance or improve Sugar. Anyone can propose new features for Sugar by following these steps: