Wiki Home » Projects Home » Open Source Initiative Working Groups

Open Source Initiative Working Groups

Last modified by Kevin Shockey on 2014.10.28 at 04:48:04 PDT

Table of Contents

Characteristics of OSI Working Groups & Working Group Process

Characteristics of OSI Working Groups

Proposed/Current Working Groups

Awareness Expansion

  • Sponsor: Deb Bryant & Tony Wasserman
  • Working Group Home Page
  • Description: OSI’s presence and ability to communicate its mission, goals, activities and in the marketplace of ideas is need of improvement, as it is with many evolving non-profits. We propose creation of a working group focused on expanding global awareness of OSI and strengthening its ability to fulfill its mission.
    The work group would be comprised of experienced communications professionals and enthusiasts, marketing/research and brand experts, and community development and management leaders. Their task will be to review OSI’s communications strengths, weaknesses, opportunities and challenges, and to recommend steps that can follow to increase global awareness of OSI, while keeping within OSI's community culture, volunteer goodwill and financial resources.

Free/Libre/Open Works (FLOW) Management Education Questionnaire and Analysis to Identify Priorities for Advancing: "A Management Education Syllabus on the Methods, Processes, Resourcing and Governance of Free/Libre/Open Works"

  • Sponsor: Joseph Potvin, Operations Manager | Gestionnaire des opérations
    The Opman Company | La compagnie Opman
  • OSI Working Group Page: Free/Libre/Open Works (FLOW) Management Education Questionnaire and Analysis project.
  • Description:
    • This qualitative data will be analyzed in a short academic research paper due on 16 December 2014 for grading as part of J.Potvin's doctoral program at University of Québec. The hypothesis to be tested is: “Manager competencies in methods and processes for free/libre/open source software projects, portfolios or foundations are sufficiently distinct from those appropriate to work under restrictive software business models, as to require the adaptation and/or extension of current mainstream project management training resources, programs and certifications.”
    • Responses should be useful to the team preparing an “OSI Management Education Working Group Charter”, under the Outreach and Learning Committee of the Open Source Initiative (OSI). The draft Charter will be considered for approval the OSI Board on 4 December 2013.
    • Responses should be useful to advance Version 1.0 of the Free/Libre/Open Works Management Syllabus to Version 2.0, as a shared asset going forward under management of the OSI Management Education Working Group. This work is being planned for January through March 2014;
    • Results may be used in consideration and planning of a broader questionnaire by the OSI Management Education Working Group in early in 2014.

Management Education About Free/Libre/Open Methods, Processes and Governance

  • Sponsor: Joseph Potvin, Operations Manager | Gestionnaire des opérations
    The Opman Company | La compagnie Opman
  • OSI Working Group page: Management Education on Free/Libre/Open Works
  • Description:
    • Mainstream management education has not kept pace with the evolution of successful free/libre/open source peer-to-peer scenarios. Other than through individual project leaders who happen to be based at educational institutions, the management education field as a whole is only superficially engaging this approach. For the most part it's missing the substantial academic and formal business literature on free/libre/open ethics, methods, processes, governance, HR management, corporate strategy, law and financing, all of which have come to prominence in the operational life of business, government and science.
    • To give a prominent tangible example of the disconnect, in the past decade many commercial and government organizations worldwide have adjusted their competitive hiring and procurement processes to include a mandatory requirement for PMP Certification (Project Management Professional) or PRINCE2 Certification (Projects in Controlled Environments, v.2). But these frameworks assume projects that are under exclusive organizational terms, and hierarchical management. They have recently included “agile methods”, but they continue to lack significant accommodation of other key aspects of the free/libre/open way.

Open Source Bug Bounty (FS-ISAC)

  • Sponsor: Wayne Jackson, CEO
    Sonatype, Inc. 
  • OSI Working Group Page: Open Source Bug Bounty (FS-ISAC)
  • Description:
    • Address security issues within FS-ISAC by establishing a 'bug bounty' type of program for open source software.

The Value of Support in Open Source


Draft proposal

A Government Open Source Manual

  • Sponsor: Bill Shelton
  • OSI Working Group Page: TBD
  • Current Working Site:
  • Description: Federal, State, and Local governments need cohesive and applicable instructions describing how to produce and use open source software.  Today, governments are left to figure that out with little, if any, official or practical guidance. Some governments and agencies have demonstrated success while others still struggle with the numerous complexities and salient constraints within government.  The primary goal of this working group is to create an authoritative reference manual that governments can use to implement open source as part of the culture. It will address and recommend processes and activities, highlight challenges with procurement, provide templates, references, studies, and guidance on privacy, paperwork reduction act (PRA), and cyber security. 

Founding an Open Source Software Engineering Laboratory (FOSSEL)

  • Sponsor:  Kevin W. Shockey (
  • OSI Working Group Page: Founding an Open Source Software Engineering Laboratory (FOSSEL)
  • Description: At the foundation of open source is the software development methodology which has changed the way software is conceived of, created, and maintained.  While this methodology has been quickly adopted and practiced in many of the leading economies of the world, it remains on the fringes in many of the smaller economies.  

As an example, within Puerto Rico, proprietary software and cultural bias has limited the impact and adoption of open source software.  Most of the software development methodology being taught on the island is limited to proprietary technologies.  Exposure to and education in open source development tools and methodologies are extremely limited.

This working group will focus on creating the policies, procedures, and processes that can help any country in establishing an Open Source Software Engineering Laboratory.  The end result of this group will be a strategic road map that eases the burden of anyone wishing to establish a localized resource that can increase the adoption and usage of open source software. 

The key to sustainability of the laboratory will be largely dependent on whether the local community adopts the open source software development methodology.  Our largest contribution to that goal will be to produce software engineers who can increase the use of open source in the local talent pool.  Generous funding and donations would help a lot too.  The deeper we can make the open source talent pool, the closer we will be, to the adoption of the new practice in Puerto Rico.

Created by Patrick Masson on 2013.11.29 at 10:57:36 PST

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 5.2.2 - Documentation