While starting something new at an organization always has unique challenges, there are likely others in similar fields who can offer their expertise. Let's learn from the experience of others.
We've put together some resources on the following topics:
- Creating an innersource culture
- Leadership as an internal stakeholder
- Open Source for Enterprises
- Teaching Git & GitHub
- GitHub workflow success stories
Each topic has a list of resources (articles, white papers, videos, etc.) and a list of discussion questions. As a group, we'll focus on the same topic.
- First, we'll each get to know the available resources and respond to issue prompts individually. You won't have time to get through every resource, and that's OK.
- Then, as a group, we'll discuss the prompts. Most importantly, we'll discuss how the information is useful within your organization.
- InnerSource Fundamentals course on GitHub Learning Lab
- Innersource commons
- Free book: Getting Started With InnerSource
- An introduction to innersource GitHub white paper
- Innersource patterns, especially those which are proven and reviewed
- New to InnerSource? blog and video, 45 minutes Bloomberg
- Innersource presentation by GitHub at Humana video, 52 minutes
- Tools as a catalyst for culture change video, 40 minutes
- Global software development with InnerSource video, 31 minutes
- What do you think are the biggest challenges of innersource?
- Have you seen innersource concepts at your organization already? If so, how did they come about, and how was the team affected? If not, what are some instances where innersource concepts could have improved an outcome?
- How common are silos within your organization? How does it affect collaboration, quality, and productivity?
- Break down the concepts or tenants of innersource into 5-10 small, concrete things that could plausibly be achieved within the next two years. (Assume company buy-in). What would be the first one you'd attempt, and why?
- Do you think innersource is possible at your organization? Why or why not?
- How do you think innersource as cultural change intersects with new tools, like GitHub?
- What problems do you think many of your colleagues face that could be alleviated by adopting innersource collaboration?
- 4 user adoption strategies to help employees embrace new tech
- User adoption methodology
- GitHub at SAP
- Increase user adoption rate of new features
- 5 Strategies to help employees adopt new technology
- Changing company culture requires a movement, not a mandate
- How to change your culture
- Changing company culture: It's a matter of principles
- 10 ways to actually, finally improve company culture article and video, 5 minutes
- What it takes to be a subject matter expert
- Six ways to turn subject matter experts into leaders
- The emotionally fit leader video, 33 minutes
- Transformative changes in challenging times video, 23 minutes
- How are you a leader in your current role?
- How can you become more of a leader in your current role?
- What are the qualities of a good leader, and why? What are some examples you can share?
- How much control do you feel you have over change within your organization? Do you feel your colleagues agree?
- What advice would you give others who want to lead or influence change within your organization?
- How can you be most effective at helping others learn and adopt Git and GitHub in the future?
- What are some examples of how you or someone else has shared knowledge or excitement about Git and GitHub? How can these examples be repeated, or learned from?
- What is the most discouraging thing about using Git and GitHub? Do you think others agree? How would you help ease this burden for others?
- How do your colleagues like to learn?
- What are some examples of change or transition within your organization? How can you learn from those examples when moving forward change in the future?
- What are the social aspects involved in transition? How can these social aspects negatively or positively influence a transition or change?
- Case studies from being a maintainer
- Resources from The Todo group
- Open Source enterprise challenges and myths
- 5 Open Source software trends
- Why Enterprises should embrace Open Source
- A Guide to Developing an Open Source Strategy
- The Linux Foundation's Open Source guides for the enterprise
- opensource.com, especially 10 advantages of Open Source for the enterprise
- Five reasons for enterprise use of Open Source
- Pros & cons of Open Source software at the enterprise level
- Fostering Open Source culture for healthier minds video, 36 minutes
- The unbearable vulnerability of Open Source video, 37 minutes
- Microsoft loves Open Source: Becoming the biggest contributor video, 38 minutes
- The power of the Open Source community video, 27 minutes
- Git much? The Top 10 companies contributing to Open Source
- How have you experienced Open Source software as a user, contributor, or maintainer?
- What do you think most people don't know, but should, about Open Source software?
- How do you think your organization could benefit from becoming more involved with the Open Source community?
- What are the biggest challenges and advantages of participating in Open Source?
- What advice would you give someone who is interested in participating in Open Source?
- What fears, worries, or hesitations do you have about Open Source as an individual? As an organization?
- Do you think your organization has any products which would be good candidates for becoming Open Source software? If not, why not? If so, what are the qualities of those products which make them good candidates?
- What questions do you have about Open Source software?
- Characteristics of a good teacher
- GitHub best practices
- Top 5 qualities of effective teachers
- Planning a workshop
- 10 tips for a successful lunch & learn
- Lunch & learn planner
- 3 ways to increase knowledge sharing within your team
- 6 ways to create a knowledge sharing culture at a workplace
- Awesome lists, especially:
- Git-Tower's list of frequently asked Git & GitHub questions
- 15 interview questions about Git that every developer should know
- 5 highly effective teaching practices
- 16 ways to be a smarter teacher
- Empowering non-developers to use Git video, 25 minutes
- Teaching GitHub Flow with LEGO and Arduino video, 25 minutes
- Git tips and tricks video, 25 minutes
- What was the hardest thing about learning Git and GitHub for you?
- How have good teachers influenced your life? Think beyond school.
- What are some examples of positive learning environments in your life? What are the attributes of those environments? Alternatively, what are some examples of negative environments?
- What do you think the most important thing to learn about Git and GitHub is for beginners?
- What is the difference between telling and teaching?
- How can learning be influenced by subject-matter experts within an organization?
- What are some examples of learning that you've experienced in your workplace?
- How can learning be made more memorable?
- How can you create learning opportunities within your organization?
- What are the biggest challenges when teaching? Are those specific to Git and GitHub? Are they specific to you or your organization?
- How could you have benefited from more Git and GitHub learning opportunities? How could your colleagues benefit?
- GitHub at SAP
- Regulated industries, limitless possibilities video, 40 minutes
- Fine tuning your GitHub Flow: A deeper dive into GitHub workflows video, 30 minutes
- Building interconnected workflows video, 25 minutes
- The GitHub guide to organizations
- How a federal agency transformed work and adopted DevOps with GitHub video, 40 minutes
- How we use Git at Microsoft
- A successful Git branching model
- Team collaboration with GitHub
- Using GitHub as a team
- What is GitHub, and why should my company use it?
- Using Git in a team: A cheatsheet
- How we use GitHub to manage change in software engineering teams
- What workflows are currently in use within your organization? Do you think they're the most beneficial workflows? If yes, what can be shared with other teams? If not, what could be improved?
- Do you think a workflow should be stipulated for your entire organization? Why or why not?
- How can the workflow within GitHub improve work within your organization?
- What patterns did you read or hear about that your organization could learn from?
- What are some examples of workflows that haven't worked, either within not within your organization?
- How much control over their own workflow should any team or individual have? Why?
- What are the challenges associated with introducing or adopting new workflows? How can those be eased?
- Why do workflows matter?