Operations Working Group
The Operations Working Group (OPWG) is a cross-functional team responsible for optimizing technical workflows, infrastructure, and internal processes to ensure smooth and scalable operations of the organization.
The key priority for this team is ensuring the efficiency, security, and collaboration of the overall products, while supporting the development, supervision and delivery of high-quality tools, and engineering solutions. Secondary priorities include the operation of the API servers and deployments.
Get in touch with the whole team for general discussion: hello@bbjprojek.org
Activities
The main tasks and activities of the Operations Working Group is the forecasting of demand and the purchasing of hardware required to meet the priorities.
Some more tasks include:
- DevOps & Infrastructure Optimization, such as CI/CD pipelines, cloud deployments, and server management
- Managing risk assessments and audits for systems and data protection
- Aligning engineering, product, and support teams to reduce bottlenecks in development cycles
- Creating policies for services, such as the CDN Server usage policy or API usage policy
- Proposing architectural improvements for scalability
It does not concern itself with:
- Maintaining internal wikis, runbooks, and onboarding guides for consistency
- Defining coding standards, deployment checklists, and security protocols
- Authoring software to run on the services. This is left to the DEWG
- Day-to-day running of the servers. This is the remit of the sys admins group
Services & priority levels
This working group oversees server functionality to ensure optimal performance and reliability. The following table shows priority levels for subdomains, along with their respective usage policies for reference.
| Subdomain | Priority | Description | Usage policy |
|---|---|---|---|
| api.bbjprojek.org | P1 | Automation API | dl1 |
| get.cdn.bbjprojek.org | P1 | CDN server API | dl1 |
| mail.bbjprojek.org | P2 | Email infrastructure | dp2 |
| git.bbjprojek.org | P2 | GitLab server | dk5 |
| cdn.bbjprojek.org | P3 | Drive / CDN Frontent | dl1 |
| total-eclipse.bbjprojek.org | P3 | Internal use infrastructure | dl1 |
| wiki.bbjprojek.org | P4 | The documentation website | ff0 |
| bbjprojek.org | P4 | The intro website | ff0 |
| playground.bbjprojek.org | P5 | Playground for experiments | dp4 |
| forum.bbjprojek.org | P5 | The community forum | dp2 |
| cabinet.bbjprojek.org | P5 | Other personal team projects | ff0 |
Who we are
The Operations Working Group welcomes inquiries through multiple channels. For general requests, users are encouraged to send a message (preferred method) or email the group directly at hello@bbjprojek.org. Technical inquiries may be directed to individual members as needed.
| Member | Contact languages | |
|---|---|---|
| Dyne Larsen | dynelarsen@bbjprojek.org | English, Swedish |
| Damian Brey | dbrey@bbjprojek.org | English |
| Giulia Mancia | giulia@bbjprojek.org | English, Italian, Spanish |
| Tristam Marsell | tmarsell@bbjprojek.org | English, Italian |
| Issac Ross | iross@bbjprojek.org | English |
| Grant Slater | glater@bbjprojek.org | English |
| Geg Zakaryan | g.zakaryan@bbjprojek.org | English, German |
We gratefully acknowledge the contributions of former members, including Gabriel Howard, Paloma García, Sergio Fernández, Antoni Sarosi, and Alex Graur, who were part of this working group in previous years. More information or members on legal request.
Our policies
Historic
- Latest Reports (2025-04-12)
- Reports (2024-04-29)
- Reports (2023-11-16)
- The 2021 Plan — Expanding OWG
- Formerly known as the "Technical Working Group"