Nercomp PM Connect Proposal

1

The OSI Board has reached out to Nercomp and PM Connect about possibly presenting on topics related to open source. This page provides a space to develop an outline for those presentations. It is recommended we present on the same topic for both groups.

2

3

Both of these groups' members are concerned with the identification, adoption, management of open source software as well as how they and their organizations may participate within open source communities. The audiences will include:

4

5

**Nercomp ([[Monday, April 28th>>url:http://nercomp.org/index.php?section=events&date=2014-04-28]]): **Higher education professionals using technology in support of academic institutions (both teaching and learning and administrative)

6

7

* C-level IT professionals (CFO, CIO, CTO)

8

* Directors of IT departments/programs

9

* IT Project managers

10

* Application administrators

11

* Educational technologists

12

* Faculty and other educators

13

* Academic/administrative technology end-users

14

15

**PM Connect (Thursday, May 1st):** Government and public sector professionals managing technology in support of state agencies and offices.

16

17

* C-level IT professionals (CFO, CIO, CTO)

18

* Directors of IT departments/programs

19

* IT Project managers

20

* Application administrators

21

* Operational/Staff technologists

22

* Systems/application/technology end-users

23

24

It is recommended our presentation cover these issues.

25

26

The presentation should be about 2 hours.

27

28

**//(It's a wiki, please feel free to improve)//**

29

30

= Draft Outline - Open Source: Identifying, Implementing & Engaging =

31

32

7:30am ~-~- 9:00am Registration and Coffee

33

\\9:00am ~-~- 9:15am Welcome and Introductions

34

35

Speaker: Patrick Masson, OSI General Manager

36

\\9:15am ~-~- 9:45am Simon Phipps, OSI Board President

37

Open Source Development, Community and Practice - Mr. Phipps will explain a conceptual framework~-~-where open source is an expression of a larger transformation happening in society enabling people and organizations to make their own decisions~-~-that shifts from hierarchical models, with their inherent control points, to a meshed model with the potential for individuals and entities to play multiple roles. Optimal open source policies within organizations should align with the grain of this transformed society, rather than attempting to re-impose the policies of the hierarchical society.

38

\\9:45am ~-~- 10:15am Deb Bryant, OSI Board Director

39

Identifying and Assessing Open Source - The implementation of open source software within organizations does not easily align with traditional procurement practices and processes inherent to typical government agencies or educational institutions. Ms. Bryant will provide several considerations organizations should address as they identify, assess, deploy and administer open source tools and importantly how those differ from what departments may be accustom to.

40

\\10:15am - 10:30am Break

41

\\10:30am ~-~- 11:00am Richard Fontana, OSI Board Director

42

Open Source Licenses for Contributors and Consumers - The past five years have been a time of significant transformation in the legal and policy side of open source, particularly concerning expectations around relationships between open source community projects and corporate/government participants. Mr. Fontana will discuss these developments and explain how they are illustrated by the launch of the OpenStack project and the licensing, contribution and governance models it has adopted.

43

\\11:00am ~-~- 11:30am Tony Wasserman, OSI Board Director

44

45

Managing Your Open Source Project/Portfolio - Dr. Wasserman will provide a model and best practices for open source software engineering, by which individuals or teams can organize, contribute and manage the co-creation of open source software-intensive systems, from concept through one or more formal releases.

46

\\\\11:30am -12:00pm ??????

47

\\12:00pm ~-~- 1:00pm Lunch

48

\\1:00pm ~-~- 2:00pm Q and A Session

\\2:00pm End

== Abstract ==

Open Source Software as passed~-~-indeed, leaped over~-~-the tipping point. Once questioned by senior IT leaders, unsure about how a community or peers could provide high-quality, reliable, secure, feature rich tools, Open Source Software is now prevalent (perhaps dominate) in several technology-driven sectors: education, government, healthcare, manufacturing, media. In 1998, the year the Open Source Initiative was founded, only 10% of organizations were using open source software; by 2011 more than 50% of organizations, surveyed by Gartner, reported using open source software. Gartner predicts that by 2015 at least 95% of mainstream IT organizations will leverage open source solutions within mission critical software deployments. And while adoption grows, so too do open source projects, with more than 2,000,000 expected by the end of 2014 – twice as many as in 2012. Today, it's not only IT working with technology, but the entire organization (procurement, IP, legal, HR, project management, senior leadership) must understand the Open Source ecosystem: the remote, distributed and decentralized communities of practice which enables collaboration, contribution and co-creation of mission-critical services and systems.

61

62

Several members of the Open Source Initiative's Board of Directors~-~-experts in licensing, development and adoption~-~-will provide insights and examples of how traditional organizations and IT shops can not only work with, but within, Open Source Software communities to enhance and extend operations and the organization as a whole.

63

64

== What is open source software? ==

65

66

* The Open Source Definition

67

* Open Source Certified Licenses

68

69

== Who is using open source software in the public sector? ==

70

71

(relevant to both government and higher ed.)

72

73

== Benefits of open source... ==

74

75

76

Present one or all based on time, format, relevance to audience.

(((

* **Customizable** – Ability to modify base level functionality to meet unique local needs

81

* **Participate in project governance**: anyone can contribute to defining the direction of the project: technical aspects, functionality/features priorities, decision-making, community practice, etc.

82

* **Organizational audibility**: ability to assess how well the open source community, project and governance is aligned with local (adopting organization’s) needs/goals/expectations.

83

* **Community audibility**: ability to assess what the level of shared knowledge and experience is within the community; number of participants, contributors and commiters there are in the project; what the level of adoption/deployments is.

84

* **Business process audibility**: ability to evaluate how needs are identified and assessed, how work is prioritized, what the workflows and practices are, etc.

85

* **Technical audibility**: ability to assess quality of code, architecture, development practices, etc.

86

* **Reduced development time**: more contributors and contributions to solve problems, write code, test enhancements, document versions, etc.

87

* **Avoid vendor lock-in**: not tied to, and controlled by any third party and their direction, interests, plans, migrations, enhancements, upgrades, sunsetting, integrations, dependencies, etc.

88

* **Broader support options**: options range from local internal resources, to communities of practice, and multiple commercial vendors rather than a single commercial provider (the developer)

89

* **Greater security:** vulnerabilities can be discovered more quickly (the more folks with access to the code, the more likely issues are to be discovered) with the best solutions applied to address issues (more folks involved can offer a greater variety of approaches, ideas solutions)

90

* **Faster implementation**: no procurement process

91

* **Higher quality**: meritocracy (best approach) is implemented

92

* **Mitigates longterm risk**: no chance of discontinuing development/support due to purchase, or a new version ( and thus forced migration to stay up to date with support/service contracts)

93

* **Higher reliability:** bugs will be discovered and fixed more quickly (see, greater security)

94

* **Business/operations continuity:** local organizational operations and practices are not disrupted through forced timelines for migrations, upgrades, enhancements etc.

95

* **Professional (personal and organizational) development opportunities**: individuals can gain experience through participation and organizations can gain prestige through contribution.

96

* **Try before you buy (Test drive)**: assess one, or many, options, before investing.

97

* **Multiple instances (no per copy fees)**: can extend use on demand without additional costs or contract negotiations.

98

* **Reduced acquisition costs**: no licensing fees

99

* **Emphasizes concepts, not products**: end users are not tied to branded or copyrighted features, workflows, tools.

100

* **Breaks the hardware upgrade cycle**: open source software is often designed to require less resource intensive hardware.

101

* **Community access**: ability to meet and network with like minded people and organizations–peers.

102

* **Standards based**: provides greater integration and interoperability (no proprietary specifications)

103

* **Standards setting**: participants are often directly involved in the development of new standards, or learn of them first.

104

* **Lower total cost of ownership (cumulative of other benefits)**: no licensing fees, no procurement process, competitive support contracts (even none with internal), no forced SP upgrades, re-purposed legacy hardware, greater scaling

105

)))

106

107

== Procurement: Assessment/Section ==

108

109

* Needs Analysis: Features/Functionality

110

* Community: Activeness, Participation & Governance

111

* Procurement/Acquisition: vs. traditional approaches (RFI/RFP)