New TODO Member: Bloomberg (Kevin Fleming)
21 views
Skip to first unread message
Chris Aniszczyk
Nov 28, 2017, 5:32:52 PM11/28/17
to TODO Private, Kevin P. Fleming
Hey all, I'd like to introduce Bloomberg and Kevin Fleming to the group!
Here's some more information about them:
Bio:
Member of the CTO Office at Bloomberg
--
Member of the CTO Office at Bloomberg
Kevin P. Fleming has 25+ years of programming experience, with every major programming language. Industry experience includes traditional client/server database applications, open source messaging and networking, and mainframe operating systems. Kevin's primary skill is producing solutions that use resources effectively through problem analysis and solution design.
A member of the worldwide open source community for nearly twenty years, Kevin most recently was the technical architect for the Asterisk and Asterisk Scalable Communications Framework open source communications projects.
Since late 2012, he has been the open source and open technology community coordinator at Bloomberg in New York. His role encompasses all forms of technology community engagement: open source software publication/contribution/consumption, conference sponsorship and presentations, standards body participation, and much more. He speaks regularly on subjects related to enterprise involvement in open source software, and advocates for college/university student engagement in open source projects of all kinds.
Open Source at Bloomberg:
Bloomberg began engaging with the open source community in 2012, and our involvement has grown to include hundreds of people across our global engineering workforce (over 5,000 at this time, and still growing). We publish tools created at Bloomberg, and we contribute to dozens of projects. In some areas especially relevant to our infrastructure needs, our engineers have become project leaders and committers, and in the Apache Lucene/Solr project a member of our team was given the privilege of joining the Project Management Committee.
We take a very pragmatic approach to adoption of open source software, choosing it for our infrastructure needs even when the available software will only meet 80% of our requirements: we'd rather extend the software to provide the other 20% than use a proprietary, closed-source solution. We also encourage contributions across our entire engineering organization, and at least three hundred members of our team have provided code, documentation, tests, or other improvements to projects across the spectrum.
We take a very pragmatic approach to adoption of open source software, choosing it for our infrastructure needs even when the available software will only meet 80% of our requirements: we'd rather extend the software to provide the other 20% than use a proprietary, closed-source solution. We also encourage contributions across our entire engineering organization, and at least three hundred members of our team have provided code, documentation, tests, or other improvements to projects across the spectrum.
Since 2013, we've also hosted Open Source Day/Weekend events, where we provide a venue, food, power, Internet access, and mentors, and bring together 20-80 (or more) of our employees, local community members, and students, to 'sprint' on open issues in an open source project. To date the projects that have benefited include Git, Clang/LLVM, Eclipse, Python, Perl, NumPy/SciPy/Matplotlib, and more.
What we're looking for:
Primarily I'd like to help develop and publish 'best practices' guides for enterprise organizations who are undertaking the same journey we did, especially those in domains which are regulated or closely aligned with regulated domains, as that can provide some extra challenges. I'd also like to more strongly advocate for simplified and consistent CLA processes for project contributions, to make it easier for developers at large companies to be able to contribute.
Primarily I'd like to help develop and publish 'best practices' guides for enterprise organizations who are undertaking the same journey we did, especially those in domains which are regulated or closely aligned with regulated domains, as that can provide some extra challenges. I'd also like to more strongly advocate for simplified and consistent CLA processes for project contributions, to make it easier for developers at large companies to be able to contribute.
Welcome Kevin!
Reply all
Reply to author
Forward
0 new messages