Open source software is software whose code is published under a licence that lets anyone read it, change it and share it. Much of what you use every day, from the server behind a website to the language you write code in, is built this way.
What makes software open source
Every program starts as source code: the human-readable instructions a developer writes. Most commercial apps ship only the compiled result, so you can run them but can't see how they work. An open source project publishes the source as well.
Publishing the code isn't enough on its own. Code is protected by copyright the moment it's written, so code sitting on a public page with no licence still belongs to its author, and you have no right to copy or change it. What makes a project open source is its licence: a document that grants everyone permission to use, study, modify and redistribute the code.
The Open Source Initiative maintains the widely used definition. Among other things, an open source licence must allow free redistribution, include the source code, allow modified versions, and not discriminate against any person, group or field of use. A licence that says 'free for students only' or 'no commercial use' fails that test.
Free as in freedom
Open source doesn't always mean free of cost. The free software movement puts it as 'free as in free speech, not free beer'. The freedoms are to run the program, to study and change it, and to share it, changed or not. Nothing stops someone charging for a copy, for support or for a hosted version, and many companies built on open source make their money exactly that way.
Open source vs closed source
Closed-source, or proprietary, software keeps its code private. You get a compiled program and a licence agreement that usually forbids taking it apart. That isn't automatically worse: the vendor is responsible for fixes, and there's often a support contract.
The difference shows when something goes wrong or you need something new. With closed source you file a request and wait. With open source you can read the code to see why it behaves as it does, fix a bug yourself or add the feature you need, then offer the change back so everyone gets it.
There's also a middle ground called source-available: the code is public, but the licence restricts what you can do with it, for example by banning competitors from offering it as a hosted service. You can read it, but it isn't open source by the OSI definition. Some companies have moved projects from an open source licence to a source-available one, and in more than one case the community has forked the last open version and carried on without them.
Wondering how this was made? How we make these