This is proposal to structure the proceedings of Golem Tech Council in order to streamline the flow of related work items and make the approval process efficient.
The purpose is to ensure the Tech Council operates efficiently, with as few synchronous actions (like meetings) as possible, and with transparency to all Golem Factory team members.
The main purpose of this proposed process is to make proceedings of Tech Council items more efficient and asynchronous (eg. have them raised and reviewed offline, and only use Tech Council sessions to discuss questions on items which have been already digested by participants).
This is why the responsibilities of the Facilitator also must include upfront facilitation of the Tech Council session’s topic so that the participants are given an early heads-up and are able to prepare for the session (eg. by reading and reviewing proposed topic).
This section specifies the rules for Tech Council proceedings, by defining key elements and workflow.
Two roles of Tech Council members are specified:
A GitHub’s GAP Project board where all Tech Council items are recorded and their status indicated.
The topics for discussion by Tech Council can be raised by any Tech Council member, in a form of:
A issue in golem-architecture repo
NOTE: issue raised in this way should include following elements at minimum:
A GAP item
Just raise a GAP as per GAP Process
The newly raised topics shall be reviewed by the Facilitator and dedicated if/when Tech Council session (wth comments if relevant) should be scheduled.
Note that Facilitator is not only responsible for raising items for Tech Council. Participants strongly encouraged to raise items for Tech Council asynchronously, without hard-dependency on Facilitator.
A Tech Council session is an opportunity for participants to address the questions which have been raised against the Tech Council items.
This proposal is a response to Tech Council approach whereby all Tech Council members were meeting weekly and viewing/reading/explaining the status of all items on Kanban board. This approach was inefficient. With further changes to have bi-weekly Tech Council sessions, they were abandoned after some time. Later, incidental Tech Council-ish sessions regarding specific GAP with on-demand sessions shown more value than previous process iterations.
There is no backward compatibility issue - we are proposing to improve the process and leave no dependencies on its previous shape.
N/A
The proceedings of Tech Council are to happen using online conferencing, GAPs and documents which all comply with Golem Factory’s information security policies.
Copyright and related rights waived via CC0.