Na kuchni unosił się zapach smażonych kotletów schabowych. Kasia sprawnie obracała je na patelni, czekając, aż osiągną ten idealny złocisty kolor. Mały Jaś cicho pochrapywał w łóżeczku w sąsiednim pokoju. Dzień był wyczerpający — noc bez snu, pranie, sprzątanie, gotowanie, znów pieluchy. I wszystko sama.
Nagle — płacz. Ten rodzaj krzyku, od którego matkom lodowacieje serce.
— Arek, podejdź do Jasia! — krzyknęła Kasia, nie odwracając się, ale licząc na reakcję męża.
Cisza.
Rzuciła łopatkę, zostawiła patelnię na kuchence i pobiegła do pokoju. Wzięła synka na ręce, przytuliła, uspokoiła. Wróciła i poczuła — kotlety przypaliły się. Zapach spalenizny rozniósł się po całej kuchni.
— No cóż, kotlety do śmieci. Dzięki, Arek — powiedziała z goryczą.
Syn znów zaczął marudzić. A Arek? Siedział jak przyklejony przed telewizorem, oglądając swój ukochany mecz.
— Arek! Nic nie zdążę! Zajmij się dzieckiem! — podniosła głos Kasia. Wtedy z pokoju rozległ się entuzjastyczny okrzyk:
— GOOOOOOL!!!
Na ten krzyk Jaś rozpłakał się jeszcze głośniej.
Kasia znów pobiegła do synka, przytuliła go mocno. Już nie czuła zmęczenia — w środku wszystko w niej wrzeło. Wróciła do kuchni, usiadła przy stole, zamykając oczy. Potem podeszła do męża.
— Arek, proszę. Wyjdź z Jasiem na spacer. Muszę skończyć w kuchni, no i złapać oddech…
— Co, nie widzisz? Jestem zajęty! — machnął ręką, nie odrywając wzroku od ekranu.
— Wystarczy. Mam dość — powiedziała zimno Kasia. — Ciesz# Writing a New PRB: A Guide
This guide walks through the steps of writing a PRB (Protocol Research Brief). You can think of a PRB as a research document that captures technical problems and solutions for a protocol. Writing a PRB helps document PRB-related discussions in a structured way as well as introduces innovation into the protocol.
## What is a PRB?
A PRB is a document that provides information to the Vega community about a proposed change or introduction of a protocol feature. The PRB should contain technical detail and a rationale for the PRB’s existence (what problem is it solving?).
A PRB should typically represent technical problems and solutions for the Vega protocol. These can range from solving a bug, a small optimisation, or a new feature introduced (such as a new asset type or a new kind of market).
## Before you start
Before you start work on a PRB, you should ensure that the idea is discussed with the community and reached a level of maturity (i.e. people generally agree on an approach and technical solution). This process can happen via community governance (forums) or through Discord.
Once the idea is mature, you should have identified whether the PRB belongs in the protocol or not. If it’s not clear, you should ask the question in the appropriate place (discord channel, forums, etc.). You can always start with a RFC (Request-for-Comments) that helps structure the problem and potential solutions to get a sense of what the technical solution may look like.
## PRB Statuses
PRB has the following statuses:
– **Draft**: The PRB is in development and being iterated on. It’s not reached the final state yet.
– **Review**: The PRB is ready for review by the community, core teams, and validators.
– **Last Call**: The PRB is nearing completion and needs final comments.
– **Final**: The PRB has been agreed and PRB number has been assigned.
## PRB Structure
This section describes the structure of the PRB.
### Title section
The **title** of the PRB should capture the essence of the problem (or solution) succinctly.
The **PRB number** will be assigned by the maintainers once the PRB is accepted, but you should update the title with the appropriate number (e.g PRB-1) before submitting a PR.
**Author(s)** section should include the full name, and optionally a GitHub username of the people who have contributed to the PRB.
**Status** of the PRB should reflect the current PRB Status (Draft, Review, Last Call, Final).
**Created** date should be the date the PRB was first drafted.
### Simple Summary
The **Simple Summary** section should contain 2-3 sentences that explain the PRB at a very high level, and that anyone in the community should be able to understand.
### Abstract
The **Abstract** is a slightly longer summary (~2 paragraphs). You can use it to explain the problem and the solution in more detail.
### Motivation
The **Motivation** section explains why Vega should implement the PRB. It should articulate the problem clearly.
### Specification
The **Specification** section describes the solution to the problem. This section is the most important part of the PRB. It should be detailed and include technical information, such as interfaces and data structures (if appropriate). If your PRB introduces a new concept, make sure to define that concept clearly.
### Backwards Compatibility
The **Backwards Compatibility** section should outline whether the PRB breaks backward compatibility with the protocol (e.g. data structures, APIs, etc.), and whether/how to migrate existing data. If the PRB requires a network upgrade, it should state it in this section.
### Copyright
The **Copyright Waiver** section is for any copyright-related PRB. In most cases, this should be: `Copyright and related rights waived via CC0.`
## Submitting a PRB
PRBs are created and stored in the `/PRBs` directory, and once completed must be submitted as a PR into that directory. The filename should contain the PRB number (e.g. `PRB-1.md`) and the PR title should be the PRB title (e.g. `PRB-1: PRB Process`). You should add the PRB label to the PR.
A maintainer will pick up your PR, review it, and assign a PRB number to it. You’ll need to update the title of the PRB (in the file) with the number. The PRB will then be merged.
## Review Process
Once your PRB is submitted as a PR, the maintainers will assign relevant reviewers, which may include the community, validators, or core protocol teams. They’ll provide their feedback or ask for clarifications.
Once all feedback has been addressed and reviewers are happy, the PRB is merged and assigned a status of `Final`. You may be asked to update the PRB (via another PR), but the PRB number remains the same.
Following the PRB being marked as `Final`, the next step is to implement the PRB. The implementation may be part of a voting on Vega’s governance, or done via contract by the core teams.
## Implementing a PRB
Each PRB that is merged must be implemented. The implementation steps are a little different based on whether the PRB requires a network upgrade (and a vote) or whether it can be implemented without the network upgrade (such as a bug fix or a small PRB that doesn’t affect consensus).
## Conclusion
PRBs are a way to capture protocol innovation and potential protocol changes in a structured way, as well as provide a way to transparently track the progress of protocol updates.
If you have any questions about writing a PRB, reach out in the community Discord and drop a message in the protocol-research channel.
