How.Camp aims to be a free, open and cooperative event about free software and open source.
💡 Be infomed about the latest development in the free and open soource software world.
✨ Meet humans who can help you with theit knowldge, ideas and experience.
🤩 Share info and/or start a career based on the FOSS.
🙌 Discuss the foundametal freedoms in the software.
- Do you have a mastodon account?
Yes, we do - @firstname.lastname@example.org. As you can see it was just created. Please follow us and boost our toots.
- Why is the event free?
We want to give the opportunity to everyone to learn about the free and opensource software.
- Do you have a code of conduct?
Yep. See the header or the footer of our website and read more about what we expect from you during the event.
- Why Gabrovo?
Actually why not? Gabrovo deserves its own opensource event. The last one was long time ago!
Open source operating systems for phones
The phones you can buy nowadays are all running proprietary software and are full with tracking that infringe on your privacy and your software freedoms. I will introduce you to some projects that aim to make usable open-source (to various degrees) operating systems for phones. How they differ, how they protect user freedoms and what makes them great.
- By Luca Weiss
Community, Thunderbird and Heavy Metal
lang: 🇬🇧 or 🇧🇬 | 💚
A short overview of the open-source e-mail client Thunderbird from a community perspective: What happened in the past, and how did we come strong out of it?, What is the plan for the next year? How you can help and why? A bit about contributing to FOSS in general A few words about using heavy metal to inspire yourself.
- By Bogomil Shopov
lang: 🇬🇧 or 🇧🇬 | 💚
Hardware for teaching exploratory testing
The original idea comes from James Lyndsay with more recent implementation from Claudiu Draghia.
The premise of these exercises is that when analyzing/exploring a complex system under test (SUT) it is not very easy to be exercising the system and observing what happens and analyzing your own actions to figure out if you are missing something or not. The goal of all exercises is to figure out how each of them works, e.g. how each box works.
The term black-box testing is used when we have to deal with a SUT whose internals are unknown to the observer. The only way we can interact with SUT is by input values and the only feedback that we get is observing if/how SUT changes its final state. All of the examples here are designed with this in mind, hence the boxes are black in color.
The opposite term also exists: white box testing - this is when SUT internals are known to us, either via documentation or source code or schematics, something else and/or all of the above.
- By Alexander Todorov