Development Team/API policy: Difference between revisions
New page: == Policy == Each interface, being a python module, a service or a protocol can be in one of the following states. The state should be always explicitly documented. === Unstable === Cha... |
categorize |
||
| (7 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
<noinclude>[[Category:Policy]][[Category:API]]</noinclude> | |||
== Policy == | == Policy == | ||
| Line 17: | Line 18: | ||
== Current state == | == Current state == | ||
=== Datastore DBus service === | |||
STABLE. | |||
=== Window management protocols === | |||
STABLE. | |||
=== Presence DBus service === | |||
UNSTABLE. It was developed in the early Sugar days without a clear idea of the actual requirements. A large part of it is used only by jarabe and will be made internal to it. We have a stable python wrapper which is what most activities uses anyway. | |||
=== jarabe python package === | |||
UNSTABLE. We are working on extensibility of the core components provided by jarabe, but we don't have enough resources to maintain a stable API, nor a clear idea of the requirements yet. We will be moving towards stability but since it's not a basic, essential part of the system, we are punting on it for now. | |||
=== sugar python package === | |||
The state is different for each module. See the documentation for details. | |||