1 / 6

Organizing OpenLMIS: Structuring a Collaborative and Open Source Approach

This proposal outlines the organization and communication strategy for the OpenLMIS initiative. It addresses key questions such as the criteria for membership, board compositions, secretariat roles, and funding strategies. The focus is on creating a grassroots, open-source organization that promotes shared resources, voluntary participation, and collaborative development. By establishing working groups, prioritizing internal information sharing, and facilitating external advocacy, this framework aims to enhance efficiency and adaptability in achieving project goals.

xander
Télécharger la présentation

Organizing OpenLMIS: Structuring a Collaborative and Open Source Approach

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Proposal for Organization & Communications Working Group Allen Wilcox (VillageReach) Mimi Whitehouse (JSI)

  2. How to Organize OpenLMIS? • Initial questions • Who can become a member? • Who will sit on the board of directors? • Who will serve as the Secretariat? • How will the work plans be approved? • How will the organization raise money? • What if OpenLMIS • Is not a separate entity? • Is a place to develop standards? • Is a repository of shared value? • Develops organically rather than through a top-down structure?

  3. Open Source Organization • Shared problem, common development effort, shared resource • Participants not subject to a common command structure • Development is consensual, grassroots, evolutionary • Leadership is required, but following is not mandatory • Voluntary participation encouraged through incentives • Extending limited resources • Access to broader talent pool • Shared resource provides foundation for enhanced results • Downsides • Additional investment to collaborate, modularize, document • Competitive advantage lost in shared resource space • Freeriding

  4. Licensing Framework • License agreements help organize the effort by • Empowering users through source code access • Granting most rights to users vs. reserving them for the authors • Preventing users from restricting others • Eclipse Public License (EPL) (code/documentation) • Broad, royalty-free license to use, modify and distribute • Modifications must be contributed back to the shared resource • May incorporate into commercial products • No warranties or liabilities • Must attribute to original authors • Creative commons license (documentation) • Similar approach to EPL

  5. Communications • Key considerations • How to support internal information share? • How to facilitate external promotion/advocacy? • What is the structure and process to accomplish the above? • Information share requirements • LMIS implementations - use cases, requirements, software • Documentation - user/developer guides • Discussion forum - queries to the group from within/outside • Resources – tools, documentation, whitepapers, collateral • Near-term priority is information share not advocacy

  6. Proposal for Working Groups • For the fall • Three working groups • Volunteer participants organized by chair person(s) • Work on their respective tasks as defined today • Be prepared to report back to the full group early next year • Organization & Communications Working Group • Determine what additional organizational elements are needed for the two substantive working groups to be effective • Adopt communications tools to support internal/external information share • Determine website evolution

More Related