Changes for page Incubator Project & Working Group Proposals
Last modified by Stefano Maffulli on 2023/05/16 18:19
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - [Project]TLDRLegal- Linkbacks1 +Open Source Initiative Working Groups - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. KevinWang1 +XWiki.pmasson - Content
-
... ... @@ -1,78 +1,124 @@ 1 -** Start/Duedate:**August13, 2015 - September 13th, 20151 +**Table of Contents** 2 2 3 -**Working Group Chair: **Kevin Wang 3 +* [[Characteristics of OSI Working Groups & Working Group Process>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HCharacteristicsofOSIWorkingGroups26WorkingGroupProcess]] 4 +* [[Proposed/Current Working Groups>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HProposed2FCurrentWorkingGroups]] 5 +** [[Awareness Expansion>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HAwarenessExpansion]] 6 +** [[FLOSS Desktop Refurbishment and Distribution>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HFLOSSDesktopRefurbishmentandDistribution]] 7 +** [[FLOSS Entities Working Group Proposal>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HFLOSSEntitiesWorkingGroupProposal]] 8 +** [[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">>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HFree2FLibre2FOpenWorks28FLOW29ManagementEducationQuestionnaireandAnalysistoIdentifyPrioritiesforAdvancing:22AManagementEducationSyllabusontheMethods2CProcesses2CResourcingandGovernanceofFree2FLibre2FOpenWorks22]] 9 +** [[Management Education About Free/Libre/Open Methods, Processes and Governance>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HManagementEducationAboutFree2FLibre2FOpenMethods2CProcessesandGovernance]] 10 +** [[Open Source Bug Bounty (FS-ISAC)>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HOpenSourceBugBounty28FS-ISAC29]] 11 +** [[Practices in Open Source Software Crowd-funding>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HPracticesinOpenSourceSoftwareCrowd-funding]] 12 +** [[Public Policy>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HPublicPolicy]] 13 +** [[The Value of Support in Open Source>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HTheValueofSupportinOpenSource]] 14 +** [[TLDR>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HTLDR]] 15 +** [[A Government Open Source Manual>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HAGovernmentOpenSourceManual]] 16 +** [[Founding an Open Source Software Engineering Laboratory (FOSSEL)>>url:http://wiki.opensource.org/bin/Projects/Open+Source+Initiative+Working+Groups#HFoundinganOpenSourceSoftwareEngineeringLaboratory28FOSSEL29]] 4 4 5 - **Working GroupSponsor:**Patrick Masson18 += Characteristics of OSI Working Groups & Working Group Process = 6 6 7 - **OSI General Manager:** Patrick Masson20 +[[Characteristics of OSI Working Groups>>url:http://wiki.opensource.org/bin/Projects/Characteristics+of+OSI+Working+Groups]] 8 8 9 -= Background=22 += Proposed/Current Working Groups = 10 10 11 - Since2012, there's been an ongoing discussion towork collaboratively betweenTLDRLegal & the OSI (outlined elsewhere). TLDRLegal hasnow reached a level of traffic, maturity, critical review andsupport through the OpenSource ecosystem that it makes sense to move forward.24 +== Awareness Expansion == 12 12 26 +* **Sponsor:** Deb Bryant & Tony Wasserman 27 +* [[Working Group Home Page>>url:http://wiki.opensource.org/bin/Projects/awareness_home]] 28 +* **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. 29 +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. 13 13 14 -O nAugust13th, Kevin + the Boardagreed to actively moveforward with asetofactivities, includinglinkbacksas outlinedonthis page.31 +== FLOSS Desktop Refurbishment and Distribution == 15 15 16 -= Project Goals = 33 +* **Co-Chairs:** Katie Osterdahl & Kris Navratil 34 +* **Sponsor:** Patrick Masson 35 +* [[Working Group Page>>url:http://wiki.opensource.org/bin/Projects/FLOSS+Desktop+Refurbishment+and+Distribution]] 36 +* **Description:** Student workshops run through schools providing access to a variety of project-based learning activities in FLOSS, including: 37 +** Hardware refurbishment: Students will rebuild and bring to operational condition decommissioned computers from local school districts. 38 +** Software Administration: Students will install and configure FLOSS software: operating systems and various desktop applications (LibreOffice, GIMP, etc.). 39 +** 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. 40 +** 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. 17 17 18 - Thegoalofthis projects to direct visitorsthat are lookingforhelpful, simple community interpretationstowards TLDRLegal by establishing linkbacks between summaries and their respective license pages. In termsof execution, it's important to havesimple,accessiblenavigation while maintaining the following conditions:42 +== FLOSS Entities Working Group Proposal == 19 19 20 - - Explicit disclaimers of endorsement of content, review and sourcing of summary data 44 +* **Sponsor:** Allison Randal 45 +* [[Working Group Home Page>>url:http://wiki.opensource.org/bin/Projects/entities%2Dwg]] 46 +* **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. 21 21 22 - -Explicit disclaimersoflegaladvice48 +== 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" == 23 23 24 - - Clear separation between TLDR & the OSI designating it as a neutral 3rd party 50 +* **Sponsor:** Joseph Potvin, Operations Manager | Gestionnaire des opérations 51 +The Opman Company | La compagnie Opman 52 +[[[email protected]>>url:http://mailto:[email protected]]] 53 +* **OSI Working Group Page:** [[Free/Libre/Open Works (FLOW) Management Education Questionnaire and Analysis>>url:http://wiki.opensource.org/bin/Projects/FreeLibreOpenWorksManagementEducationQuestionnaire]] project. 54 +* **Description:** 55 +** 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.” 56 +** 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. 57 +** 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; 58 +** Results may be used in consideration and planning of a broader questionnaire by the OSI Management Education Working Group in early in 2014. 25 25 26 -= Deliverables=60 +== Management Education About Free/Libre/Open Methods, Processes and Governance == 27 27 28 -=== Execution Format === 62 +* **Sponsor:** Joseph Potvin, Operations Manager | Gestionnaire des opérations 63 +The Opman Company | La compagnie Opman 64 +[[[email protected]>>url:http://mailto:[email protected]]] 65 +* **OSI Working Group page: [[Management Education on Free/Libre/Open Works>>url:http://wiki.opensource.org/bin/Projects/FreeLibreOpenWorksManagementEducation]]** 66 +* **Description:** 67 +** 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. 68 +** 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. 29 29 30 - Thecurrentlyproposedformatof executionisthefollowing:70 +== Open Source Bug Bounty (FS-ISAC) == 31 31 32 -**Link text + (disclaimer link)** 72 +* **Sponsor:** Wayne Jackson, CEO 73 +Sonatype, Inc. 74 + [[[email protected]>>path:mailto:[email protected]]] 75 +* **OSI Working Group Page:** Open Source Bug Bounty (FS-ISAC) 76 +* **Description:** 77 +** Address security issues within [[FS-ISAC>>url:https://www.fsisac.com/]] by establishing a 'bug bounty' type of program for open source software. 33 33 34 - Examples:(%style="font-size:14px;background-color: rgb(236, 245, 250);" %) "View[Community] SummaryofMIT License on TLDRLegal(disclaimer)"79 +== Practices in Open Source Software Crowd-funding == 35 35 36 -The goal is to have a short & simple link for those that want a quick overview of the license first. Then, for those who care about the explicit relationship between OSI + TLDR, right next to it is a long, thorough & accessible disclaimer just a click away. 81 +* **Sponsor:** Patrick Masson 82 +* [[Working Group Hope Page>>url:http://wiki.opensource.org/bin/Projects/crowdfunding%2Dwg]] 83 +* **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. 37 37 38 - **Mockup:**85 +== Public Policy == 39 39 40 -[[image:https://gm1.ggpht.com/O2pYna0gTiFGUIu03NSeFGgNhSjw1y-NowSMz3hzuGyqOoSGSV_fGRVuVNeeQlir5EuP6iRwzDn1lPnoOlluZQdsczWdOBrZI-uTU9IZ2gyA8p5Tdosi5b162BTv-EswRNHhFKV3yhjfGcBcMrHQoNm_ks5df0NuZIHFP36PUYdafidrgyaS0CL8f2otIqYjWkmEGjgPg1WyBRPQSL4uOHVyVXxxODKYJ-a8jOgT8eVrYZtCybF9paLSPFxNGS6pz5cLOU3GSmR36-4v-q7CM1Bw4JwLM5kzs-4PiOwXEuW6xaKpYSVvNjg5hcUo5CFazRka1X8hijPQE-YiLcDoO3y5yP6BH_cZNQ7qnjCHfLtQaVBxRmv5RmZySkTdu106A76aCn0OI2UBEe9XjVeho5vtD8-GqfHVGGcAhgzuugO2C5If9srA-OkXSVliy8cdtNqDIF9Z4JU8F7iHluEh5pK5I23Ja56RUad5g-4ay0BJUfunUKx-BW15ZMqSnVARQdNqop_jmTOgm7XA1ynJCpoaf_BkYkzZ43Y2hI9xaOujTcBfad-SBEh-1akiBltVyA8sY8PdGbhJsH1_gA3Acdg2XgYqueF7isk-Uw-K8vYhb2Gm7mZTe0en5VUV=w600-h458-l75-ft]] 87 +* **Sponsor **OSI Board Director Deb Bryant 88 +* [[OSI Working Group Page>>url:http://wiki.opensource.org/bin/Projects/PublicPolicyIP]] 89 +* **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: 90 +** Model policies for government agencies, operations, contracts and procurement policies 91 +** Public policies for broad adoption of free and open source software 92 +** Executive orders and other high-level policy guidance 93 +** National referendums 94 +** Economic Development initiatives 95 +* 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. 41 41 42 -== =FullDisclaimerLanguage ===97 +== The Value of Support in Open Source == 43 43 44 -Current Draft: 99 +* **Sponsor:** Michal Papis ([[[email protected]>>path:mailto:[email protected]]]) 100 +* OSI Working Group Page: [[Value of Support in Open Source>>url:http://wiki.opensource.org/bin/Projects/Value+of+Support+in+Open+Source]] 101 +* **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. 45 45 46 - "Whilethe OSI acknowledgesTLDRLegalas a helpful resource to the community, it does not endorse its content, contributors or interpretations. The OSI is not involved in the production or review of any license summaries on TLDRLegal and exists as a neutral, separate third-party. TLDRLegal provides no legal advice, exists for only informational purposes and creates no attorney-client relationship between you, TLDRLegal or its contributors, or the OSI. TLDRLegal's summaries do not include every detail of every license, and some of those details may apply to you. If you have questions about how the licenses apply to you or your products, you should seek legal advice."103 +== TLDR == 47 47 48 - ===Optional Announcement===105 +[[Draft proposal>>url:http://wiki.opensource.org/bin/Projects/tldr]] 49 49 50 - Optionally,wecan announcethis mutually on both sides to pre-emptively definetheOSI + TLDR's relationshipsothere'sno confusionand explicit,forthright messaging of no-endorsement, etc...107 +== A Government Open Source Manual == 51 51 52 -= OSI Resources & Timeline = 109 +* **Sponsor:** [[Bill Shelton>>url:http://wiki.opensource.org/bin/XWiki/virtix]] 110 +* OSI Working Group Page: TBD 111 +* Current Working Site: [[https:~~/~~/github.com/OnOpenSource/government-opensource-manual>>url:https://github.com/OnOpenSource/government-opensource-manual]] 112 +* **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. 53 53 54 - Theonlyresourceswe needare:114 +== Founding an Open Source Software Engineering Laboratory (FOSSEL) == 55 55 56 -~1. Board Approval of this plan (including disclaimer language) 116 +* **Sponsor:** Kevin W. Shockey ([[[email protected]>>path:mailto:[email protected]]]) 117 +* OSI Working Group Page: [[Founding an Open Source Software Engineering Laboratory (FOSSEL)>>url:http://wiki.opensource.org/bin/Projects/FOSSEL]] 118 +* 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. 57 57 58 - 2.Execution ofLinks onLicensePages120 +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. 59 59 60 - 3.(Optionally)An announcementto draft up122 +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. 61 61 62 -Kevin is happy to take over the manual work making the links when ready. 63 - 64 - 65 -**Goal Dates:** 66 - 67 - 68 -* (% style="font-size: 14px; background-color: rgb(236, 245, 250);" %)Mon, Aug 24th - first-pass review of proposal details and begin iterations 69 -* (% style="background-color: rgb(236, 245, 250);" %)Fri, Sept 4th - finish iterating and freeze project plan, Kevin, Patrick or others execute link drafts 70 -* (% style="background-color: rgb(236, 245, 250);" %)Weds, Sept 9th - finish drafts, confirm publishing details and (optionally) draft & review announcements. Publish all by Sept 15th. 71 -* (% style="background-color: rgb(236, 245, 250);" %)Tues, Sept 15th - trigger has already been publically pulled on links or announcements, close this project 72 - 73 -After the end-date of the project, Kevin & Patrick will work together to continually keep information updated, which will be covered in a separate working group proposal. 74 - 75 -Next steps may include review of OSI-approved summaries, and etc... also covered in separate proposals. 76 - 77 - 78 - 124 +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.