Version 21.1 by Patrick Masson on 2017/12/03 18:55
Show last authors
1 **Table of Contents**
2
3 {{toc/}}
4
5
6 = Characteristics of OSI Working Groups & Working Group Process =
7
8 [[Characteristics of OSI Working Groups>>url:http://wiki.opensource.org/bin/Projects/Characteristics+of+OSI+Working+Groups]]
9
10
11 = Working Group Initial Proposal Template =
12
13 This [[template>>doc:Main.Open Source Initiative Working Groups.Working Group Initial Proposal Template.WebHome]] can be used to create/submit your own proposal for a working group or incubator project.
14
15 = Proposed/Current Working Groups =
16
17 == Awareness Expansion ==
18
19 * **Sponsor:** Deb Bryant & Tony Wasserman
20 * [[Working Group Home Page>>url:http://wiki.opensource.org/bin/Projects/awareness_home]]
21 * **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.
22 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.
23
24 == FLOSS Desktop Refurbishment and Distribution ==
25
26 * **Co-Chairs:** Kris Navratil
27 * **Sponsor:** Patrick Masson
28 * [[Working Group Page>>url:http://wiki.opensource.org/bin/Projects/FLOSS+Desktop+Refurbishment+and+Distribution]]
29 * **Description:** Student workshops run through schools providing access to a variety of project-based learning activities in FLOSS, including:
30 ** Hardware refurbishment: Students will rebuild and bring to operational condition decommissioned computers from local school districts.
31 ** Software Administration: Students will install and configure FLOSS software: operating systems and various desktop applications (LibreOffice, GIMP, etc.).
32 ** Mentorship: Students will develop a curriculum and teach "desktop literacy" to their peers and other members of the community using the refurbished FLOSS computers. After completion of the course, the participants will be able to take the computer home.
33 ** Peer Support Center: Students will create, manage and operate a "help desk" providing those who complete the course and using the refurbished computers a resource for ongoing support.
34
35 == FLOSS Entities Working Group ==
36
37 * **Sponsor:** Allison Randal
38 * [[Working Group Home Page>>url:http://wiki.opensource.org/bin/Projects/entities%2Dwg]]
39 * **Description:** This working group is aligned with the OSI's misson to promote and protect Open Source, especially focusing on the "protect" aspects. Applying for 501(c)(3) or (c)(6) status has become the norm for new FLOSS projects. If that route were no longer feasible, it could result in serious harm to the future growth of Open Source. It is critical both to research the recent responses from the IRS and determine if we are in the midst of a trend-shift, and to explore alternatives to IRS 501(c) status for young projects.
40
41 == 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" ==
42
43 * **Sponsor:** Joseph Potvin, Operations Manager | Gestionnaire des opérations
44 The Opman Company | La compagnie Opman
45 [[jpotvin@opman.ca>>url:http://mailto:jpotvin@opman.ca]]
46 * **OSI Working Group Page:** [[Free/Libre/Open Works (FLOW) Management Education Questionnaire and Analysis>>url:http://wiki.opensource.org/bin/Projects/FreeLibreOpenWorksManagementEducationQuestionnaire]] project.
47 * **Description:**
48 ** 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.”
49 ** 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.
50 ** 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;
51 ** Results may be used in consideration and planning of a broader questionnaire by the OSI Management Education Working Group in early in 2014.
52
53 == Journal of Open Source Software ==
54
55 * **Sponsor:**
56 * **[[OSI Working Group Page>>doc:Main.Open Source Initiative Working Groups.Journal of Open Source Software.WebHome]]**
57 * **Description:**
58
59 == Management Education About Free/Libre/Open Methods, Processes and Governance ==
60
61 * **Sponsor:** Joseph Potvin, Operations Manager | Gestionnaire des opérations
62 The Opman Company | La compagnie Opman
63 [[jpotvin@opman.ca>>url:http://mailto:jpotvin@opman.ca]]
64 * **OSI Working Group page: [[Management Education on Free/Libre/Open Works>>url:http://wiki.opensource.org/bin/Projects/FreeLibreOpenWorksManagementEducation]]**
65 * **Description:**
66 ** 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.
67 ** 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>>url:http://www.greycampus.com/pmp-training-instructor-led]] (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.
68
69 == Open Education (Proposed) ==
70
71 * **Sponsors**: Molly de Blanc (chair) & Leslie Hawthorn
72 * [[Working Group Proposal Page>>doc:OpenEduWG]]
73 * **Description**: The purpose of the Open Education OSI Working Group is to provide any interested parties with information and resources around open source in education, with a focus on incorporating open source technologies into curriculum.
74
75 == Open Source and Standards Working Group ==
76
77 * **Sponsors**: Patrick Masson & Simon Phipps
78 * Working Group Proposal Page
79 * **Description**: The The Supporting Standards Setting Organizations (SSSO) Working Group will: 1. explore current SSO understanding of OSI approved licenses, and more generally, open source software, development, and projects; 2. educate SSO in current principles and practices widely excepted by open source communities of practice; 3. support authentic engagement across open source communities (i.e. implementors, contributors, projects, foundations) to ensure alignment with best practices in open source licensing, development and distribution, and; 4. produce reference resources (educational materials, professional development activities, expert opinions, consulting services, etc.) to address gaps in understanding, support current practices, and increase the recognition of OSI approved licensing and the OSI License Review Process.
80
81 == Open Source Bug Bounty (FS-ISAC) ==
82
83 * **Sponsor:** Wayne Jackson, CEO
84 Sonatype, Inc.
85 [[wayne@sonatype.com>>path:mailto:wayne@sonatype.com]]
86 * **OSI Working Group Page:** Open Source Bug Bounty (FS-ISAC)
87 * **Description:**
88 ** Address security issues within [[FS-ISAC>>url:https://www.fsisac.com/]] by establishing a 'bug bounty' type of program for open source software.
89
90 == Practices in Open Source Software Crowd-funding ==
91
92 * **Sponsor:** Patrick Masson
93 * [[Working Group Home Page>>url:http://wiki.opensource.org/bin/Projects/crowdfunding%2Dwg]]
94 * **Description:** This working group is aligned with the OSI's mission to educate about and protect Open Source Software, expressly focusing on the "protect" aspects. Open source software, as both a development and business model, as well as crowd-funding for raising start-up capitol, have become popular. Despite increased interest in these approaches, many software project owners who use crowd-funding sites, as well as their potential contributors, lack the fundamental understanding of open source software communities and licensing to undertake informed decision-making in creating or contributing to projects labeled as "open" "open source" or "open source software." This effort will seek to partner with crowd-funding services to create and make available educational materials to help both developers and contributors authentically engage in the open source software development community.
95
96 == Public Policy ==
97
98 * **Sponsor **OSI Board Director Deb Bryant
99 * [[OSI Working Group Page>>url:http://wiki.opensource.org/bin/Projects/PublicPolicyIP]]
100 * **Description **OSI is often approached for assistance with questions and expressed interests and need from the public sector about policy for free and open source software. This includes a range of expressions of policy. Examples of requests for help historically have included:
101 ** Model policies for government agencies, operations, contracts and procurement policies
102 ** Public policies for broad adoption of free and open source software
103 ** Executive orders and other high-level policy guidance
104 ** National referendums
105 ** Economic Development initiatives
106 * A working group is proposed to be established to extend the Open Source Initiative's resources to create an international collaborative effort to create a network of policy practitioners for the purpose of sharing best practices, documentation, and general knowledge and support for individuals and organizations with an interest in or responsibility for creating and implementing effective policies. In phase one of the project, we will identify a network of the willing and informed and create a sustainable inventory of existing policies (implemented). Phase two will be defined by the group based on what is learned along the way as opportunity and challenge.
107
108 == Snowdrift.coop Prototyping ==
109
110 * **OSI Sponsor:** Allison Randal
111 * **Project Sponsor**: Aaron Wolf
112 * **OSI Working Group Page:** [[Snowdrift.coop Sponsorship Proposal>>doc:Main.Open Source Initiative Working Groups.Snowdrift\.coop sponsorship proposal.WebHome]]
113 * **Description:** Snowdrift.coop is prototyping a new form of cooperative community sponsorship / long-term patronage for Open Source projects. While we hope long-term to operate as a full foundation handling donations between large numbers of donors and projects, this proposal is to support the prototyping stage. At this stage, we are focused on creating, presenting, and studying the concept of a network-driven many-to-many matching pledge as a mechanism to improve overall support for Open Source.
114
115 == The Value of Support in Open Source ==
116
117 * **Sponsor:** Michal Papis ([[mpapis@gmail.com>>path:mailto:mpapis@gmail.com]])
118 * **OSI Working Group Page:** [[Value of Support in Open Source>>url:http://wiki.opensource.org/bin/Projects/Value+of+Support+in+Open+Source]]
119 * **Description:** Based on the initial work researching an article, "The value of support in Open Source" ([[https:~~/~~/docs.google.com/document/d/1H7hY9tgA6M6mYIdCBVbqMMYNftpzddMy_MfB0faW7RU/edit?usp=sharing>>url:https://docs.google.com/document/d/1H7hY9tgA6M6mYIdCBVbqMMYNftpzddMy_MfB0faW7RU/edit?usp=sharing]]), it was proposed a repository allowing contributions of first-person accounts related to the value of support for open source would be beneficial. This resource could evolve to provide references and/or peers in identifying organizational, technical, developmental, etc. benefits; case studies on adoption, practice, etc.; material for promotion in OSI publications or at events.
120
121 == TLDRLegal Linkbacks ==
122
123 (((
124 * **Sponsor:** Kevin Wang ([[kevin+osi@tldrlegal.com>>mailto:kevin+osi@tldrlegal.com]])
125 * OSI Working Group Page: [[TLDRLegal Linkbacks>>doc:Main.Open Source Initiative Working Groups.TLDR Legal.WebHome]]
126 * **Description:** The goal of this project is to direct visitors that are looking for helpful, simple community interpretations towards TLDRLegal by establishing linkbacks between summaries and their respective license pages. In terms of execution, it's important to have simple, accessible navigation while maintaining the following conditions:
127 ** Explicit disclaimers of endorsement of content, review and sourcing of summary data
128 ** Explicit disclaimers of legal advice
129 ** Clear separation between TLDR & the OSI designating it as a neutral 3rd party
130 \\Note: The [[Initial Draft proposal>>url:http://wiki.opensource.org/bin/Projects/tldr]] is available for historical purposes.
131 )))
132
133 == A Government Open Source Manual ==
134
135 * **Sponsor:** [[Bill Shelton>>url:http://wiki.opensource.org/bin/XWiki/virtix]]
136 * OSI Working Group Page: TBD
137 * Current Working Site: [[https:~~/~~/github.com/OnOpenSource/government-opensource-manual>>url:https://github.com/OnOpenSource/government-opensource-manual]]
138 * **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.
139
140 == Founding an Open Source Software Engineering Laboratory (FOSSEL) ==
141
142 * **Sponsor:** Kevin W. Shockey ([[kevin@prpig.org>>path:mailto:kevin@prpig.org]])
143 * OSI Working Group Page: [[Founding an Open Source Software Engineering Laboratory (FOSSEL)>>url:http://wiki.opensource.org/bin/Projects/FOSSEL]]
144 * 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.
145
146 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.
147
148 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.
149
150 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.

Submit feedback regarding this wiki to webmaster@opensource.org

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