Jim Hall

Submitted by jhall on Sun, 2022-03-06 20:33
Pronouns: 
he/him
Description of the candidate: 

Jim Hall is a senior IT leader, and a long-time open source software advocate and developer. His first contribution to open source was in 1993, with a patch to GNU Emacs. Since then, Jim has authored, contributed to, or maintained dozens of open source programs and projects. Notable projects include FreeDOS and GNOME.

In addition to writing open source software, Jim also works in usability testing for open source software.

In addition to his open source work, Jim is an innovative, high-achieving senior IT leader with over twenty years' experience in IT Leadership, including more than eight years as Chief Information Officer in government and higher education, and three years as CEO of Hallmentum. Jim believes in developing the next generation of IT Leadership, to help IT organizations better respond to the changing technology landscape.

Jim often speaks about open source software, including the Teaching Open Source in University Systems Symposium, FOSDEM, Kieler Open Source und Linux Tage, State of the Source, SeaGL - in addition to webinars and podcasts. Jim is also a featured speaker on IT Leadership and Technology Innovation at conferences including Government IT Symposium, SINC Midwest IT Forum, International Institute of Business Analysis, Premier CIO Forum, Minnesota e-Learning Summit, and others.

Jim is a frequent contributing writer on open source software for publications including OpenSource.com, CloudSavvy IT, Linux Journal, TechRound, Linux.UK, Linux Magazine, Linux Voice, and FOSS Force Magazine. Jim is also a published author on IT Leadership, and is the author of Coaching Buttons, a collection of essays about leadership and vision in information technology. Jim has also contributed chapters to several other books on Open Organizations and IT Leadership, including The Open Organization Leaders Manual (2nd Edition), The Open Organization Workbook, and Cultivating Change in the Academy. 

Jim has a master's degree in Scientific and Technical Communication from the University of Minnesota, and a bachelor's degree in Physics from the University of Wisconsin-River Falls.

 

Looking ahead, open source will continue to evolve. As a director on the Board, I will bring my background in strategic leadership to help OSI navigate the future landscape for open source - not just licensing, but in identifying future challenges. What are the next major challenges in open source software in the next 5, 10, or 15 years? How will OSI's role change in meeting those future challenges? 

 

If you elect me to the Board, I will work to enhance the role that OSI plays in open source. Many organizations leverage or use open source software - running part (or all) of their business using open source software, using open source to run part (or all) of their stack, or running their back office operations .. among other ways to use open source.

I believe OSI can do more than just maintain the Open Source Definition. I will help OSI define how OSI should engage with organizations that want to use or contribute to open source. What should these organizations know about how to use and engage with open source software? We can take a more strategic and proactive role, and that's what I'll do.

Type of seat: 
Individual

Comments

Submitted by jhall on Tue, 2022-03-08 14:24

Luis asked several questions on Twitter to the board candidates, and while I'm responding there too, I also wanted to post answers here that everyone can see - and with more detail than I can post in 280 characters.

1. What should OSI do about the millions of people who collaborate to build software online (often calling that collaboration "open source") but have no idea what OSI is or what it does?

We need to do more here. I said in my original statement that OSI can do more than just maintain the Open Source Definition. I will help OSI define how OSI should engage with organizations that want to use or contribute to open source. What should these organizations know about how to use and engage with open source software?

We can take a more strategic and proactive role. I like the Practical Open Source Information mini-conference that OSI hosted; that's a great way to help organizations learn more about open source.

But we should also be more visible at other events where we can talk about "what is open source" and "what does OSI bring to the table?" OSI shouldn't be just the maintainer of the Open Source Definition; we should be the go-to reference point - an "information center" about what open source is and how organizations can use open source.

2. What should OSI's relationship be with the Organization for Ethical Source and the Free Foundation Foundation?

I am aware of the Organization for Ethical Source but I have not worked with them. I don't have an issue with them. I think some of the ideals they are aiming for are good starting points, but misplaced. For example, the Open Source Definition doesn't allow Discrimination Against Persons or Groups, or Discrimination Against Fields of Endeavor. 

I think OSI can be (and should be) friendly with them. But I don't think we need to be proactive in taking things beyond that.

The FSF is a complex matter. I would prefer to see a change in FSF leadership and some board members before I (personally) will engage with them.

3. What additive skills and perspectives do you bring to the board? (finance/money, ED/staff management, non-Valley/EU perspective, ..)

I bring a few things. I have a long history in IT leadership, including serving as Chief Information Officer in government and higher ed. And I'd like to see more government units (local, state, and fed) using open source software and releasing internal tools as open source software. Governments have embraced open data; the next step from open data is open source.

I also have a broad background that also includes working as an independent contractor providing training, workshops, and coaching. My most popular program is IT leadership, including strategic planning. I can bring that experience to help OSI shift to a staff-driven org.

4. OSI is shifting from a board-driven to staff-driven org. How do you plan to support that transition in particular, and OSI staff in general?

See my answer to #3. I have a broad background that also includes working as an independent contractor providing training, workshops, and coaching. My most popular program is IT leadership, including strategic planning. I can bring that experience to help OSI shift to a staff-driven org.

5. You have 24 hrs in a day and are talented enough to do many things. Why give some of that time to OSI?

I've been part of open source software since 1993, since before we adopted the term "open source software." I also write about open source software for magazines and websites. As a long-time open source developer and contributor, I want to keep open source strong. And not to be cliche, but I want to give back. I've served on the GNOME board and done other work in open source, but the OSI board is another way to support open source - and do it more directly. That's why I'm running for board.

To promote and protect open source software and communities...

For over 20 years the Open Source Initiative (OSI) has worked to raise awareness and adoption of open source software, and build bridges between open source communities of practice. As a global non-profit, the OSI champions software freedom in society through education, collaboration, and infrastructure, stewarding the Open Source Definition (OSD), and preventing abuse of the ideals and ethos inherent to the open source movement.

Open source software is made by many people and distributed under an OSD-compliant license which grants all the rights to use, study, change, and share the software in modified and unmodified form. Software freedom is essential to enabling community development of open source software.