Request for Change
As an organisation grows, it makes multiple decisions on how to do things. All these decisions are made with the information avaiable to the members at that point in time. Every decision is right. Every decision has it's own context. However, with time, these decision may seem dated as the context would have changed. To move forward quickly and with agitility, we need to reassess such decisions. These decisions can be as big as how Zamp is structured to as small as the variable name on a helper file. To make change come throught, we raise requests for change and take buy in of individuals to get it implemented.
How to make a cultural change ?
A lot of Zamp cultures is codified as a part of this handbook. If you'd like to make a change, the best course of action would be to raise a PR to this repo and get approval from the required quorum. Once approved and merged, your change should come into effect immidiately. There are some changes would require some implmentations as well. In such cases, we refrain from merging the PR until the implementation is done to a certain critical degree.
How to make a technical change ?
If your change is related to an engineering piece, we request you to raise a IMPL and get buy in from folks. You should also take feedback to ensure the change is sustainable, scalable and extendible. Once your IMPL is approved, execution is planned and implemented.
How to implement something that never existed?
Often times, change would mean bringing into life something that never existed. In that scenario as well, we request you to raise a RFC and IMPL. Once approved, it is executed and brought to life.