The Guild is a group of open source developers.
We were formed in order to bring a different approach for sustainable open source development.
We believe in the interaction between internal teams with real world challenges and open source.
We are the team that links those together.
One of our main guidelines of open source is solving real issues for real people.
That’s why we work with and help companies like Microsoft, KLM-AirFrance, Schneider-Electric, Wix and others.
We do everything that’s needed to improve developer productivity and product performance.
That can include:
- Remove any blocker that might takes away time from a developer - CI/CD pipelines, Complex Build systems, developer toolings, making them active decision makers in the open source tools and libraries they rely on, Connecting teams across different levels of their tech stack
- Performance, security audits and fixes for API Gateways
All of that always follows with real code changes, otherwise it’s free.
We do open source slow but well.
We want our open source libraries to be built for the long term, in a sustainable way, with extreme high quality, thanks to continuous improvements and the ability to always learn and respond to the community’s feedback, working closely on a daily basis with companies and individuals from the community, solving real issues for them.
And we are managing to do so. If you check out our libraries, some have been around for many years, they are always up to date, with low number of issues and are always actively maintained.
We also revived many libraries of the community (you can read more of that on our blog).
That way of open source is not instead of other ways (venture capital startups, teams from large corporations), it is complimentary.
Another main guideline for us in open source is Individuality.
Each library is under a person’s name, not under The Guild organization on Github.
The benefits of that approach are:
- Bigger sense of responsibility on the maintainer
- The individual maintainers get the credit they deserve
- Resiliency of the code - if maintenance is not on par, it is far easier to fork and compete, compared to a famous organization/company, making the code and the community more distributed and resilient
- It helps our individuals members promote themselves, their own Github users, their own social media
- Maximizing the individual and personal growth of our members
The way we work and our structure also incentivises us to contribute to other solutions instead of working on our own.
We would rather contribute to an active project than to create our own.
But, we have a very high standard to what it means to be an active open source project and unfortunately, finding libraries like that is hard.
So we always try to help and support first.
Also, we rely on you, the community.
Here is how you can help:
- Spread the word about us - Tell people about our libraries and our services, create guides and tutorials
- Answer and help others on Github Issues, Discord, Stack Overflow, Twitter, Reddit
- Contribute to our docs and also to graphql.org
- Create failing tests and reproducible projects
- Improve the WhatsApp clone tutorial
- Schedule a free meeting for architectural review - we love to learn from you and hopefully we can give valuable advice back
- Hire us to work with you - we’ll be that extra nice member on your team
- Get a training with us
- Join us! - Are you maintaining a popular open source library and thinking of how to spend more time doing just that?
- Just contact us directly and tell us your story