http://www.fiware.orghttp://lab.fiware.orgFollow @FIWARE on Twitter

FIWARE Open Community: an introductionJuanjo HierroFIWARE Coordinator and Chief Architect

2

Principles which have guided our approach

Openness: able to engage those who have something to contribute (following procedures)

Transparency: well-defined, documented and publicly available procedures

Based on meritocracy: only active technology contributors would be able to govern decisions on the technology

Market-oriented approach: Those committed to transfer results to the market gain a prominent role

Don’t reinvent the wheel: follow models and best practices from successful OSS communities (concretely, OpenStack)

3

FIWARE Open Community membership Individual member:

• Contributes to FIWARE in a variety of ways

Regular member (corporate/organizations):• Strategy aligned with FIWARE Mission

• Provide resources for ongoing activities (e.g. developers)

• Fees based on organization size / nature

• Elect representatives to the Board of Directors (BoD) Core member:

• Corporate strategy aligned with FIWARE Mission• Appoints a member to the Board of Directors (BoD) • Provides substantial funding, in kind and in resources (e.g., developers, legal

resources, marketing)

Ethic, all to• Must adhere to a community code of conduct• Wear the FIWARE hat and always act with integrity

… to an open community that is designed to last and be open to anyone who wish to actively contribute

4

FIWARE Board of Directors

FIWARE Accelerator Programme DTC chair

DomainTechnical

Committee

Ecosystem Support Committees

Technical Committees

Core member assigned seats

growth

new members

new members

elected seats

Mission Support Chapter Leaders

FIWARE TC chair

Arch Chapter 1 Leaders

FIWARE Technical

Committee

Arch Chapter n Leaders

Individual seats

(important note: logos of core members and regular members are only ilustrative)

• Board of Directors (BoD) made up of member representatives (core members + elected members):• Approves changes to governance model• Oversees activities of Ecosystem Support

Committees• Elects Officers of Foundation• Foundation (future):• Secretariat and other

support• Owns FIWARE brand

Core Members

Regular Members

FIWARE Mundus

Programme

5

Governance Bodies for a strategic vision

Board of Directors:• Keeps the FIWARE Mission• Steer activities of Ecosystem Support Committees• Manages Budget/Resources Definition and oversees their consumption• 50% Regular Members, 50% Core Members

FIWARE Technical Committee (TC):• Technical leadership for the OS Community• TC Chairman elected for 1 year among TC members• Chapter leaders are also elected regularly• Members: Chapter Leaders + 1/3 seats

Domain Technical Committee (DC) – one per domain• Technical leadership for Domain Specific Enablers• Responsible of consistency of Domain RA with FIWARE Vision• Members: Active Contributors in the Domain Specific Area• Seats to be defined

FIWARE Technical Committee

6

• Technical Chapters:• Architecture Chapters• Mission Support chapters

• TC deals with overall technical coordination• Made up of Technical

Chapter Leaders, plus additional seats

• Active Chapter Contributors elect corresponding Chapter Leaders and additional seats

• chair elected among members

elected, coordinate

elected, coordinate

elected, coordinate

FIWARE Ops, FIWARE Lab, FIWARE community tools

Contributes resources to development

Mission Support Chapter Leaders

FIWARE TC chair

Arch Chapter 1 Leader

FIWARE Technical

Committee

Arch Chapter n Leader

growth

new membe

rs

Incubated GEs

FIWARE GEs

new membe

rs

Individual seats

• New FIWARE GEs can be proposed for incubation and later be part of the FIWARE Core, once they gain traction and subject to approval of Technical Committee

Core Members

Regular Members

(important note: logos of core members and regular members are only ilustrative)

7

Growing the FIWARE OS community perimeter

At FIWARE Platform Level:• Driven by Active Chapter Contributors through the

Technical Committee• Open, transparent process• Incubated GEs: new GEs proposed by third parties • Incubated GEs and compliant GEs will be visible in

the FIWARE Catalogue

At the level of specific vertical Domains:• Creation of dedicated Domain Committees• Rely on existing organizations (not necessarily

incubated within the PPP) to run Domain Committees, that way getting them engaged

Give also visibility to App providers

8

Community Tools and Processes

FIWARE Catalogue tool

Q/A platform tool

FIWARE community membership management process

GE life cycle management process

FIWARE Funding process

GE lifecycle management1. GE incubation

9

New GE/GEri

proposal

OutsideFIWARE

FIWAREChapter

submits

Asks opinionopinion

IncubatedGE/GEri

promotes

FIWAREGE/GEri

accepts

discards

Discarded GE/GEri

discards

Asessment

FIWAREChapter

submits

keeps incubation

TC

manages

FIWARETechnologies

Roadmap

periodic feedback

AppsDevelopers(3 monts)

Initialasessment fast-

track

GE lifecycle management2. GE deprecation

10

AppsDevelopersAssessment

No, changes are required

FIWARE GEQuaranteened

FIWARE GE/GEri

OK to keep in the catalogueFIWARE

Chapter

evolves

GEDeprecated

Deprecates

evolves

periodic feedback

Not yet, changes still required

TC

OK to keep in the catalogue

periodic feedback

Assessment

11

The FIWARE Catalogue

12

Stackoverflow and Q&A platform

http://ask.fiware.org

http://stackoverflow.com/search?q=fiware

13

Developers’ Homehttp://developer.fiware.org

http://fiware.org

http://lab.fiware.org

Follow @Fiware on Twitter !

Thanks!

14