Last modified by Stefano Maffulli on 2023/05/16 18:19

<
From version < 25.1 >
edited by Patrick Masson
on 2017/12/08 01:30
To version < 26.1 >
edited by Patrick Masson
on 2017/12/08 01:38
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,6 +14,14 @@
14 14  
15 15  = Proposed/Current Working Groups =
16 16  
17 +
18 +== A Government Open Source Manual ==
19 +
20 +* **Sponsor:** [[Bill Shelton>>url:http://wiki.opensource.org/bin/XWiki/virtix]]
21 +* Working Group Home Page: TBD
22 +* Current Working Site: [[https:~~/~~/github.com/OnOpenSource/government-opensource-manual>>url:https://github.com/OnOpenSource/government-opensource-manual]]
23 +* **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.
24 +
17 17  == Archived Discussions on Not Approved Licenses ==
18 18  
19 19  * **Sponsor(s): **Richard Fontana, Luis VIlla
... ... @@ -31,7 +31,7 @@
31 31  
32 32  * **Co-Chairs:** Kris Navratil
33 33  * **Sponsor:** Patrick Masson
34 -* [[Working Group Page>>url:http://wiki.opensource.org/bin/Projects/FLOSS+Desktop+Refurbishment+and+Distribution]]
42 +* [[Working Group Home Page>>url:http://wiki.opensource.org/bin/Projects/FLOSS+Desktop+Refurbishment+and+Distribution]]
35 35  * **Description:** Student workshops run through schools providing access to a variety of project-based learning activities in FLOSS, including:
36 36  ** Hardware refurbishment: Students will rebuild and bring to operational condition decommissioned computers from local school districts.
37 37  ** Software Administration: Students will install and configure FLOSS software: operating systems and various desktop applications (LibreOffice, GIMP, etc.).
... ... @@ -44,12 +44,26 @@
44 44  * [[Working Group Home Page>>url:http://wiki.opensource.org/bin/Projects/entities%2Dwg]]
45 45  * **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.
46 46  
55 +
56 +== Founding an Open Source Software Engineering Laboratory (FOSSEL) ==
57 +
58 +* **Sponsor:** Kevin W. Shockey ([[[email protected]>>path:mailto:[email protected]]])
59 +* Working Group Home Page: [[Founding an Open Source Software Engineering Laboratory (FOSSEL)>>url:http://wiki.opensource.org/bin/Projects/FOSSEL]]
60 +* 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.
61 +
62 +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.
63 +
64 +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.
65 +
66 +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.
67 +
68 +
47 47  == 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" ==
48 48  
49 49  * **Sponsor:** Joseph Potvin, Operations Manager | Gestionnaire des opérations
50 50  The Opman Company | La compagnie Opman
51 51  [[[email protected]>>url:http://mailto:[email protected]]]
52 -* **OSI Working Group Page:** [[Free/Libre/Open Works (FLOW) Management Education Questionnaire and Analysis>>url:http://wiki.opensource.org/bin/Projects/FreeLibreOpenWorksManagementEducationQuestionnaire]] project.
74 +* **Working Group Home Page:** [[Free/Libre/Open Works (FLOW) Management Education Questionnaire and Analysis>>url:http://wiki.opensource.org/bin/Projects/FreeLibreOpenWorksManagementEducationQuestionnaire]] project.
53 53  * **Description:**
54 54  ** 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.”
55 55  ** 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.
... ... @@ -56,10 +56,18 @@
56 56  ** 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;
57 57  ** Results may be used in consideration and planning of a broader questionnaire by the OSI Management Education Working Group in early in 2014.
58 58  
81 +
82 +== Global Digital Payment Systems ==
83 +
84 +
85 +* **Sponsor:** Joseph Potvin
86 +* [[Working Group Home Page>>doc:Main.Open Source Initiative Working Groups.Global Digital Payment Systems.WebHome]]
87 +* **Description:** The WG Chair would serve as OSI's eyes and ears to provide structured liaison with the forthcoming W3C Web Payments Steering Group [1].; coordinate a consultative community to advance specific OSI interests and profile in this domain (explained below); coordinate and be contributing editor for the drafting of occasional formal OSI submissions to W3C, UNCITRAL, and other top-level bodies; and, travel to two events per year (one within N.America), on a minimalist budget. (I would add OSI FLOW Syllabus side activities to such trips.)
88 +
59 59  == Journal of Open Source Software ==
60 60  
61 61  * **Sponsor:**
62 -* **[[OSI Working Group Page>>doc:Main.Open Source Initiative Working Groups.Journal of Open Source Software.WebHome]]**
92 +* [[Working Group Home Page>>doc:Main.Open Source Initiative Working Groups.Journal of Open Source Software.WebHome]]
63 63  * **Description:**
64 64  
65 65  == Management Education About Free/Libre/Open Methods, Processes and Governance ==
... ... @@ -75,13 +75,13 @@
75 75  == Open Education (Proposed) ==
76 76  
77 77  * **Sponsors**: Molly de Blanc (chair) & Leslie Hawthorn
78 -* [[Working Group Proposal Page>>doc:OpenEduWG]]
108 +* [[Working Group Home Page>>doc:OpenEduWG]]
79 79  * **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.
80 80  
81 81  == Open Source and Standards Working Group ==
82 82  
83 83  * **Sponsors**: Patrick Masson & Simon Phipps
84 -* [[Working Group Proposal Page>>doc:OSandStandardsWG]]
114 +* [[Working Group Home Page>>doc:OSandStandardsWG]]
85 85  * **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; 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, and; 5. Encourage SSOs to request and maintain formal peer relationships with OSI. The Working Group will act as the formal Correspondent.
86 86  
87 87  == Open Source Bug Bounty (FS-ISAC) ==
... ... @@ -102,7 +102,7 @@
102 102  == Public Policy ==
103 103  
104 104  * **Sponsor **OSI Board Director Deb Bryant
105 -* [[OSI Working Group Page>>url:http://wiki.opensource.org/bin/Projects/PublicPolicyIP]]
135 +* [[Working Group Home Page>>url:http://wiki.opensource.org/bin/Projects/PublicPolicyIP]]
106 106  * **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:
107 107  ** Model policies for government agencies, operations, contracts and procurement policies
108 108  ** Public policies for broad adoption of free and open source software
... ... @@ -115,13 +115,13 @@
115 115  
116 116  * **OSI Sponsor:** Allison Randal
117 117  * **Project Sponsor**: Aaron Wolf
118 -* **OSI Working Group Page:** [[Snowdrift.coop Sponsorship Proposal>>doc:Main.Open Source Initiative Working Groups.Snowdrift\.coop sponsorship proposal.WebHome]]
148 +* **Working Group Home Page:** [[Snowdrift.coop Sponsorship Proposal>>doc:Main.Open Source Initiative Working Groups.Snowdrift\.coop sponsorship proposal.WebHome]]
119 119  * **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.
120 120  
121 121  == The Value of Support in Open Source ==
122 122  
123 123  * **Sponsor:** Michal Papis ([[[email protected]>>path:mailto:[email protected]]])
124 -* **OSI Working Group Page:** [[Value of Support in Open Source>>url:http://wiki.opensource.org/bin/Projects/Value+of+Support+in+Open+Source]]
154 +* **Working Group Home Page:** [[Value of Support in Open Source>>url:http://wiki.opensource.org/bin/Projects/Value+of+Support+in+Open+Source]]
125 125  * **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.
126 126  
127 127  == TLDRLegal Linkbacks ==
... ... @@ -128,7 +128,7 @@
128 128  
129 129  (((
130 130  * **Sponsor:** Kevin Wang ([[[email protected]>>mailto:[email protected]]])
131 -* OSI Working Group Page: [[TLDRLegal Linkbacks>>doc:Main.Open Source Initiative Working Groups.TLDR Legal.WebHome]]
161 +* Working Group Home Page: [[TLDRLegal Linkbacks>>doc:Main.Open Source Initiative Working Groups.TLDR Legal.WebHome]]
132 132  * **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:
133 133  ** Explicit disclaimers of endorsement of content, review and sourcing of summary data
134 134  ** Explicit disclaimers of legal advice
... ... @@ -135,22 +135,3 @@
135 135  ** Clear separation between TLDR & the OSI designating it as a neutral 3rd party
136 136  \\Note: The [[Initial Draft proposal>>url:http://wiki.opensource.org/bin/Projects/tldr]] is available for historical purposes.
137 137  )))
138 -
139 -== A Government Open Source Manual ==
140 -
141 -* **Sponsor:** [[Bill Shelton>>url:http://wiki.opensource.org/bin/XWiki/virtix]]
142 -* OSI Working Group Page: TBD
143 -* Current Working Site: [[https:~~/~~/github.com/OnOpenSource/government-opensource-manual>>url:https://github.com/OnOpenSource/government-opensource-manual]]
144 -* **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.
145 -
146 -== Founding an Open Source Software Engineering Laboratory (FOSSEL) ==
147 -
148 -* **Sponsor:** Kevin W. Shockey ([[[email protected]>>path:mailto:[email protected]]])
149 -* OSI Working Group Page: [[Founding an Open Source Software Engineering Laboratory (FOSSEL)>>url:http://wiki.opensource.org/bin/Projects/FOSSEL]]
150 -* 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.
151 -
152 -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.
153 -
154 -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.
155 -
156 -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 [email protected]

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