Supported systems/Technical considerations: Difference between revisions
No edit summary |
KachachanC (talk | contribs) No edit summary |
||
| (7 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{Stub}} | {{Outdated}} | ||
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude> | |||
{{Stub}}{{TOCright}} | |||
There are a number of technical considerations for providing Sugar support. | There are a number of technical considerations for providing Sugar support. | ||
== | ==Integration== | ||
Sugar is designed to be started as desktop option | Sugar is designed to be started as a desktop option | ||
alongside Gnome and KDE rather than a plain "start menu" | alongside Gnome and KDE rather than a plain "start menu" | ||
application. This means that we should consider a "switch | application. This means that we should consider a "switch | ||
desktop" function if it is a requirement to ship multiple environments. | desktop" function if it is a requirement to ship multiple environments. | ||
== | ==Applications== | ||
In order to provide a consistent environment, | In order to provide a consistent environment, | ||
| Line 21: | Line 23: | ||
a thin shell around Firefox's engine. | a thin shell around Firefox's engine. | ||
== | ==[[Packaging Team|Packaging]]== | ||
At this time, we have alpha-quality packages | At this time, we have alpha-quality packages | ||
| Line 27: | Line 29: | ||
require additional packaging work, especially for the | require additional packaging work, especially for the | ||
networking features. Packaging Sugar for other distributions would be | networking features. Packaging Sugar for other distributions would be | ||
done in collaboration; appropriate contacts within those communities | done in collaboration; see [[Packaging Team]], appropriate contacts within those communities are welcome to join. | ||
== | ==Software stacks== | ||
Sugar is based on quite a different set | Sugar is based on quite a different set | ||
| Line 39: | Line 41: | ||
the footprint of Sugar should be reasonably small. | the footprint of Sugar should be reasonably small. | ||
== | ==Vendor customization== | ||
Sugar is moving to become an upstream | Sugar is moving to become an upstream | ||
| Line 47: | Line 49: | ||
criteria. | criteria. | ||
== | ==Engineering support== | ||
We are aware that Sugar still requires | We are aware that Sugar still requires | ||
much more engineering work to polish the user interface, | much more engineering work to polish the user interface, | ||
stabilize the codebase, and complete missing features. Since | stabilize the codebase, and complete missing features. Since | ||
we started the Sugar Labs, we have already | |||
attracted | attracted fresh volunteers. But we'd appreciate hardware | ||
vendors (and others) assigning resources to work with us and make things happen | vendors (and others) assigning resources to work with us and make things happen | ||
faster. | faster. | ||
== | ==Community involvement== | ||
We are in contact with several government | We are in contact with several government | ||
| Line 65: | Line 67: | ||
in this process. | in this process. | ||
== | ==Content== | ||
We are also looking for localized open content. Industry partners | We are also looking for localized open content. Industry partners | ||
might be able to help here. | might be able to help here. | ||
== | ==Design proposals== | ||
We'd appreciate feedback and marketing input | We'd appreciate feedback and marketing input | ||
from hardware manufacturers (and others) to enhance our environment. | from hardware manufacturers (and others) to enhance our environment. | ||