Changes for page Walker2017

Last modified by JohnMarkWalker on 2017/02/17 02:37

<
From version < 1.3 >
edited by JohnMarkWalker
on 2017/02/16 00:32
To version < 2.2 >
edited by JohnMarkWalker
on 2017/02/17 02:36
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,6 +6,7 @@
6 6  1. License compliance and software asset management. Many organizations take on the risk of open source software without doing their due diligence. There's a good chance that many companies are out of compliance with their software licensing. There are literally millions of developers on GitHub, yet there is the prevailing opinion that many of them don't quite understand how license compliance works. I believe the OSI has a role to play in helping companies and individuals accurately determine the risk exposure of their current software asset management process while simultaneously helping them to participate more fully in upstream communities. To wit, what are the ramifications of making certain licensing choices, and how can the OSI help developers and users navigate the licensing landscape?
7 7  1. It's about communities. Lots of people use open source software. Lots of developers build on or create new open source software. But many of them don't understand the importance of community building and management. The OSI can help open source communities to understand how adherence to community and governance best practices makes for a better all-around ecosystem. Many participate in open source communities on some level, but too few understand how communities fit into the bigger picture and why their individual health matters. Communities are the lifeblood of open source development, and they have traditionally served a role in checking the balance of power between vendors and other community participants. The OSI can help ensure that the role of strong communities is better understood and that the tradition of the community's role in checking the balance of power continues.
8 8  1. Outreach and marketing. The OSI as an organization is not well understood, outside of its members and those in the know. We need to work with our members and sponsors to develop a comprehensive marketing strategy and plan that will help us deliver the OSI message to more developers and users than ever. We should be more visible!
9 +1. Diversity. If you look around at most open source events, there is still too little representation from women, LGBTQ, and people of color. The OSI should be a strong voice in advocating for and conducting outreach towards underrepresented communities. We should set goals and follow up with metrics reporting on demographic representation at major conferences, as well as work with the greater open source community and partner organizations to create programs that help close representation gaps. Compared with events from other tech sectors, we lag very far behind, and we should be appalled and demanding more action.
9 9  
10 10  
11 11  **About Me**

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