Line 1: |
Line 1: |
| == Intention == | | == Intention == |
| | | |
− | * Having common project(s) and friendly support customization on purpose in downstream products: | + | * Having common project(s) and friendly support of customization on purpose in downstream products: |
− | ** Modularizing when components might be included on purpose to fulfill local needs, | + | ** Modularizing, when components might be included on purpose to fulfill local needs, |
− | ** Not patching in downstream but supplementing the upstream, e.g., install upstream packages and just add additional packages with local customization without patching upstream code/configuration, | + | ** Not patching in downstream but supplementing the upstream, e.g., install upstream packages and just add new packages with local customization or overrides (but not overriding installed files to let PMS work smooth) of upstream, |
− | ** Provide useful API for any new components; | + | ** Provide useful API for components; |
− | * Be a GNU/Linux distribution agnostic. It doesn't make much sense in case of having only Server on a school server and, e.g., installing Server from the ISO but it makes sense if downstream organizations ship their products based on the Server and having particular GNU/Linux distribution is important; | + | * Be a GNU/Linux distribution agnostic. It doesn't make much sense in case of having only Server on a school server installed from an iso but it makes sense sugar-serve will be installed in already configured and maintained environment or if downstream organizations ship their products based on the Server and having particular GNU/Linux distribution is important; |
| * It is not only about supporting XO laptops but about any Sugar based environments; | | * It is not only about supporting XO laptops but about any Sugar based environments; |
| * Up to 1000 students per server. | | * Up to 1000 students per server. |