Make Linux approachable.
Bring useful capabilities into clear, comfortable tools. Less friction for people getting started, with room to grow as they learn.
OPEN SOURCE AT PETACOMM
Good software.
Open to possibility.
Linux is better when knowledge is shared.
We build tools that make it easier to take part.
Explore the code behind our open-source projects, understand how they work and help shape what comes next.
OUR APPROACH
Useful tools.
Shared understanding.
We value open source because it lets people look closer: at a design decision, a fix, or an idea they can build on. It makes room for learning and for improvements that begin with someone simply asking, “Could this be easier?”
Let the work be understood.
Source code and documentation give people a way to examine how a project works and make informed choices about using it.
Improve it together.
A clear bug report, a better explanation or a thoughtful change can make the next person’s experience easier.
EXPLORE THE SOURCE
Three projects.
Plenty to build on.
Find the source, documentation and issue tracker for each project.
01 / FILES
PetaFiles
A terminal file manager that makes navigating and working with your files more comfortable.
02 / DEVELOPMENT
Petacore
A native Linux software workshop for your project files, snapshots, testing, packaging and releases.
03 / LINUX
Spindle
A Linux assistant that helps make everyday terminal tasks easier to approach.
TAKE PART
You don’t have to start
with a pull request.
Start with a project you use. Read its documentation and existing issues, then choose a contribution that fits what you know.
Report a problem.
Include your Linux distribution, the application version, what you expected and the steps to reproduce the issue. Remove personal information from logs and screenshots.
Make something clearer.
Point out confusing instructions, suggest a documentation improvement or help with a translation. Small explanations can make a big difference to someone new.
Share an idea.
Describe the task you are trying to complete and where the current workflow gets in your way. For a substantial change, discuss the approach in an issue first.
Contribute code.
Follow the repository’s contribution instructions where available. Keep changes focused, explain the problem they solve and describe how you checked them.
LICENCES & RESPONSIBILITY
Know what you’re building on.
Each repository’s licence defines how its code can be used, modified and redistributed. Review that licence and any dependency licences before incorporating code into your own project.
Software licences, explained simply →
For installation requirements, supported platforms and known limitations, use the documentation for the version you’re working with.
Found a security issue?
Send sensitive vulnerability reports privately, rather than posting details in a public issue.
[email protected] ↗BUILT IN ISTANBUL. SHARED WITH YOU.
Take a look.
Make a difference.
Find a project that interests you and start with the source.