SMArt GovernanceBen Adida

26 August 2010SMArt Developers’ Meeting

Governing what?

•code: SMArt APIs and data formats

•app store: app approval

•brand: who can call themselves “SMArt?”

Code

•led by the SMArt team,with community feedback

•all source code free/open-source,all standards and documentation open

•Apps need not be open-source, butmodifications to API libraries should be

•eventually, a steering committee.

“App Store”

•The SMArt App Exchange will feature appsapproved by the SMArt committee

•Other organizations can operateand vouch for alternate app exchanges

•Each SMArt container installationwill decide which apps it wants to featurein its App Gallery

•Each user may select his preferred apps placed in his App Dashboard

SMArt Brand

•code is open, but the brand is not.

•to call your product “SMArt”, it has to comply with the SMArt specification

•we’ll be developing compliance tests

•goal: ensure users have a consistent, meaningful brand name.

Governance

•code: open-source, open formats,led by SMArt team

•app store: one app exchange to start, but others can be built. Installations manage their app gallery. Users manage their dashboards.

•brand: compliance test to ensure that “SMArt” is meaningful