β€οΈβπ₯ Volunteers
Why to volunteerβ
Volunteering means you work for free, because youβre motivated by other things:
- You want to learn and become a beekeeper, believing in Company mission, trying to help π§βπ Hobby beekeepers and the πΒ bees
- Gaining open-source proof of experience you can use at applying to other jobs & positions (ex. you are a student and you want to show contribution with CAD model or typescript code)
- Learning something new in the area that you are not yet familiar with (ex. IoT if you are a web developer)
- Having more freedom of trying oneself in different role, compared to an established enterprise where entry barrier is so high (ex. Trying to be an engineer if you are a PM)
- Teaching others if you are experienced in one area (ex. as Robotics engineer streaming lessons on twitch & youtube)
Howβ
Before you start, be prepared that in startups like ours, in opposite to large companies, you won't be explicitly told what to do. You pretty much need to find the work yourself of what you feel helps the project (and you) the most. Adapt to change ποΈ
As we are in volunteer mode, its expected that people are contributing with different levels of their activity
. So if you collaborate with others, do not expect much. People may suddenly disappear due to personal reasons (family, work, study etc). Lower your expectations as lower entry barrier for volunteers. Humbly kind π§Έ
What to doβ
You can contribute by following these steps:
- Join our discord
- Read about βοΈ Features and tasks
- Pick a feature if you want to work on a large, full-stack part of the product. In large companies features are maintained by product managers
- Alternatively, pick a task from task list π https://github.com/orgs/Gratheon/projects/5 if you want to work on internal, infrastructural task or a feature improvement. Tasks are more specialized.
- Ask for more information in discord to get attention and document more information for the feature
- Follow docs on web-app if you need to change code and run services locally
- Think how your contribution will look like. Usually its a code pull-request to a specific repository
Contributionsβ
Because of this, short and atomic contributions as artifacts are important both to the community as to the contributor. Contribution adds value to the product (Gather value π―). Contribution must have a permissive license for us to reuse the work.
Asking for information is not a contribution
A weak contribution
- Reporting a bug (raises awareness)
- Suggesting an idea for a new feature, improvement or change
A strong contribution is:
- design doc, research paper, RFC that describes in-depth solution for product or feature
- a file, image, cad model, design, device shared with us
- documenting or clarifying a feature
- recording a youtube video how thing is working
- a github commit that fixes a bug or adds new features
- a new repository, microservice
Examples of contributionsβ
- A github pull-request to an existing repository or a new repository that we can fork is one way to show your results. Examples - backend services, CAD models
- A penpot draft for UX (ask for invite to get access)
- QA testing session conducted that found various bugs and issues with suggestions how to mitigate them. Results were a mix of google-docs, excel and chat messages reporting specific issues. Use
#product-feedback
discord channel to report issues. Use one message per issue to have separate threads. - Annotations for training Machine Learning models
Communicationβ
If Discord is not enough, we also try to have weekly meetings over google meet. Its free form, but we try to record meetings into All-hands meeting recordings and stream it to twitch.
- We use Discord (specialized
#layer-*
channels for discussion to resolve blockers) and Notion to link results, knowledge and documentation (although we transition to native markdown nowdays for docs to be available on website too)
Acknowledgementβ
If you are a contributor, we try to highlight this (in a list below)
- you are also seen in github repository if you are a contributor
- in discord you will get a π‘ yellow name if you contributed some code to common namespace
- on request, we can also add acknowledgement to linkedin
If you stick around for a long while and do the hard work today, you get a promise to get compensated in the future based on equity plan if we succeed, as it is in company interest to keep the talent
Contributorsβ
title | description |
---|---|
Alonso Solis | participated in andmetorm hackathon, worked on UI design and FE components |
Adrian Ala | participated in andmetorm hackathon, worked on UX flow and pitching |
Roop Runjan Khan | participated in andmetorm hackathon |
Arina Turgeneva | Helped with web-app testing |
Kurban Ramazanov | Helped with UI/UX, designing prototypes to imporove web-app experience |
Maria Lutsiv | helped with web-app testing |
Anastassia Tsalko | helped with web-app testing |
Andrei Kuzmin | helped with web-app testing |
Vladislav TjagunovitΕ‘ | helped with web-app testing |
Ahmed Daoudi | Helped with telemetry-api, building initial service version in express/nodejs |
Muhammad Zain Shakeel | Helped with 3D model of the robotic beehive |
Natalia Kinash | Participated in the hackathon where she helped Reinis Indans with satellite imagery processing |
Reinis Indans | Participated in a hackathon where he did most of the heavy work on data collection and model training for satellite pollination sub-project - satellite-pollination-map microservice |
Aleksei Boris | Participated in 2 hackathons and helped with pitching |
Olena Stoliarova | participated in a Climathon hackathon, helping with pitching |
Thank you all!