Diverse2013 Osnabruck - The MediaMosa Foundation


Published on

The MediaMosa Foundation – From innovation project to a sustainable open source community

Frans Ward, Michel van de Ven

In January 2013 the MediaMosa Foundation was established by SURFnet and Kennisnet.
The primary goals of the foundation are to promote the use of the MediaMosa Open
Source Digital Asset Management System, to bring together its international community,
and facilitate the continued development of the platform. The MediaMosa Foundation owns
all rights to the code, domains and trademarks of MediaMosa.
The MediaMosa Foundation is governed by a three member board, which mostly plays a
ceremonial role. The Board carries financial responsibility and will publish results and plans on a yearly basis.
All operational activities are delegated to the Member Council, which is elected by the
community members, from the community members. All persons engaging with
MediaMosa and contributing to it in time, money or resources are eligible to become
members of the foundation.
This presentation will elaborate on the lessons learned from forming an open source
foundation. What are the organisational issues that need to be addressed? What does it
take to successfully commit an active open source community to a foundation? How can
you address the international community members? How can you guarantee future
commitments? How do you secure financial independence and assurance?
This presentation will also detail how the Foundation is organised, how people can
become part of it as a member, and what benefits this will bring to them and the
MediaMosa project. We describe the new possibilities the foundation will bring to
MediaMosa. We will make a call to action for people to join the foundation, and/or become
a sponsor. Finally we will make an announcement for the first event to be organised by the
MediaMosa Foundation.

About MediaMosa
MediaMosa is software to build a Full Featured, Webservice Oriented Media Management
and Distribution platform. With MediaMosa you can build a stateoftheart,
scalable Middleware Media Distribution Platform that facilitates access to, and usage of (shared) storage capacity, metadata databases, transcoding and streaming servers.
The MediaMosa platform offers functionality for searching, playing, uploading, transcoding,
as well as a fine granularity media access control system towards its users. MediaMosa is
based on the Representational State Transfer (REST) architecture and is designed to
support content streaming applications by providing a backend, audio and video infrastructure.
MediaMosa is developed and used by all kinds of people, organisations and companies in
The Netherlands, Belgium, Germany, France, United Kingdom, Norway, Italy, Ukraine, and
the USA, amongst others.

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Diverse2013 Osnabruck - The MediaMosa Foundation

  1. 1. The MediaMosaFoundationFrom innovation project to a sustainableopen source communityDIVERSE201324 June, Osnabrueck, GermanyFrans Ward - Michel van de Ven
  2. 2. About MediaMosa
  3. 3. REST based SOA> Flexibility by combining components> Open source and using open source components> Scalable for future expansion
  4. 4. Can haz API?Play videoAuthenticationAuthorization (Play restriction)Upload (PUT, POST, FTP)TranscodingMedia Management: media files,assets and collectionsSearchJobsMetadata and OAI/PMHNotificationLogging and StatisticsStills....
  5. 5. Vehicle for innovation projects• MediaMosa Rich Media Application• Content Supplier Application• MediaMosa and Matterhorn• HTML5 Video• Video Annotation• Rich Media Systems Compared• MediaMosa Building Block forBlackboard• MediaMosa and support for othercontent• Full text search engines• Content in the Cloud• MediaMosa and Open API• Transcripting Technology• Open Live Streaming
  6. 6. Open & Public from the start
  7. 7. Open Source is....
  8. 8. Open Source is....“The realization of anopen sourceproject does notguarantee thecreation of a community”
  9. 9. Community website & demo
  10. 10. A growing community
  11. 11. Innovation project lifecycle
  12. 12. Innovation project lifecycleCompleted?
  13. 13. What were the options?
  14. 14. Why a foundation?
  15. 15. Founded!
  16. 16. Core Activities
  17. 17. Foundation Bootstrap• How to build an Open Source Foundation• Parties you need to involve• Rights / Brand / Trademark owners• Programmers, authors, “natural" leaders• Users• Hire a legal counsel• Inform on local / global laws• Validate charter texts• Prepare paperwork for notary• Hire a notary• Look at other foundations: FreeBSD, Debian
  18. 18. • Who establishes the foundation?• Foundation name• Goals of the foundation• Financial sources• Governance• The Board (ceremonial, financial): whos on it andwhat are their tasks, rights and responsibilities? Howare decisions taken? How are elections held?• Operational Board: same questions.• Devise rules for good and for bad times• Who does the (financial) paperwork?Foundation Charter
  19. 19. Member Council Charter• This is where the action is• Not a part of the foundation charter, butdemanded by it.• Lay down the operationalrules within the maincharter framework• Roles: Chair, Secretary, Master Committer, andother important roles that emerge, like awebmaster• Tasks, rights and responsibilities• How and when to do elections• How to resolve problems and disagreements• Foundation Board can interfere when needed
  20. 20. Foundation Governance
  21. 21. Foundation Governance
  22. 22. Foundation Governance
  23. 23. Foundation Governance
  24. 24. Foundation Governance
  25. 25. Organisation model• Contribute with time, money or resources• Time: write code, write documentation, takeup a Council position, organise events,update the website.• Money: donate for software projects, forevents.• Resources: provide a venue for an event,provide server capacity, provide food anddrinks.
  26. 26. Benefits• Align your efforts with other adopters and getmore and better features in MediaMosa,faster.• Meet other people with similar mindsets andproblems regarding Digital AssetManagement.• Be part of a transparent organisation withclear goals and internal procedures.
  27. 27. • Use common sense guiding principles.• Be honest, be open, be transparent.• Consider every aspect from multipleperspectives:• What if I would have to accept these rules?• Do these rules still work 5 years from now?• What if we become a very large organisation?• What if someone goes ballistic?• Make the rules inherently modifiable andextensible so they can grow and adapt to real-world circumstances; but stay within charterlimits, and no self-destruction.General Guidelines
  28. 28. Ponderings & Collateral Damage• Things we considered but didnt include.• Things we explicitly do not want to do.• Do not become a financial broker betweencustomers and suppliers. Just be an informationbroker, a linking pin.• Do not hide information, publish everything.• No membership fees with voting rights; wouldallow commercial entities to dominate theCouncil.
  29. 29. Lessons Learned• What are the organisational issues that needto be addressed?• What does it take to successfully build anactive open source community?• How can you address the internationalcommunity members?• How can you guarantee future commitments?• How do you secure financial independenceand assurance?
  30. 30. Call to ActionJoin the communityTalk to us @DiverseWill do BoF sessions to go into specificsContributeBecome a sponsorUse MediaMosa and tell us about itHave funhttp://foundation.mediamosa.org<board@mediamosa.org>
  31. 31. MediaMosa DirectionsWWWhttp://mediamosa.orghttp://foundation.mediamosa.orgTwitterhttp://twitter.com/mediamosaOnline Demohttp://demo.mediamosa.orgSource Codehttps://github.com/mediamosaSlidesharehttp://www.slideshare.net/mediamosa