We strongly believe that autonomy is one of the best source for motivation and creativity.
While collaboration calls for organisation, we want to provide the most rule-free possible environment.
That's why our framework mainly relies on quigdelines and support, along with the minimum set of rules needed to protect ourselves.
Here are the fondamentals of it:
Everything we produce is open sourced or under creative commons and belongs to everyone.
Our products are developed publicly and are available from day one.
We believe the journey is as interesting as the result, and that shared is better than finished.
Everyone can join the community.
The only request is to follow our code of conduct (available as our discord server rules) and post a short introduction uppon joining.
Once part of the community, everyone can become an active member by creating or joining a Team.
There is nothing done alone, nor with everyone. There is no specialized teams.
Each member declares a set of Energies they want to bring: dev, scripting, documentation, modeling, animation, editing, production management, ... any digital content creation related talent is welcome !
Members organize themselves into cross enegy Teams of 3 to 9.
"Cross energy" means at least two differents energies emanating from two different members of the team.
Any team can invest itself on any Goal which requires a compatible set of energies.
We host a list of scoped Modules.
Each module is animated by at least one Module Animator who drives the module life. (meetings, reviews, etc).
Any team can create a module and modules are valid as long as they have an active animator.
Module meetings are used to identify needs and craft the Goals to fulfill them.
A Goal objective it fulfill a need. It lists the energies required to achieve it.
A Product is the result of achieving a goal.
A product can be anything (a report, a schema, a feature list, a set of user stories, a whitepaper, a version of a library, a character design, a 3D modeling, an EDL, a post-mortem report, ... whatever the goal needs) as long as it is shareable, comes with the appropriate level of documentation and has a commitment for support.
As an example, an idea is not a product. But writing down an idea and how it helps can be the product of a "Find a solution for xxx" goal.
Producing is not our raison d'être ! What we aim for is to leverage our passions and energies in a meanifull way.
While our products are great opportunities to be usefull and to help others, Chapters are where we help and learn from our peers.
Each energy has a corresponding chapter which regroups all the members with this energy.
A chapter is ruled by its members, but we ask for at least one official Chapter Animator who is responsible for the chapter life. (meetings, workshops, case studies, etc)
As crutial influencers of the community happyness, the chapter animators are in close relation with the Trust and the Org.
Those two chapters have a special purpose, and special rules.
The Trust chapter regroups experts serving as mentors, brainstorm feeders, advisors and inspirationnal sources.
They can be consulted by other chapters, modules and teams on any topic. Their interventions and feedbacks are use by the requesters as they see fit: the Trust only has the influence the teams want to give.
The Org chapter regroups TGZR's dedicated energies. Its purpose is to guide and support the community members in our processes and continually evaluate the organisation effeciency, as well as giving the community an appropriate exposure.
It does so by gathering feedbacks, producing reports, communicating about the community and representing it in external meetings, events and talks.
In order to join one of those chapters (aka, register to the Trust or the Org energy), there must be an agreement from the community.
The terms of this "agreement" are defined by the community itself and, as of today, is: "In absence of a stated veto from an active member, the community agrees".
None of this is set in stone and we'll always welcome critics and suggestions from anyone in the community.
Fixing our process is part of our process ! :)
We did not come up with this by ourselves ! We might even not have anything new here :)
Credit is due to many sources we've drained and many people we had the chance debate with.
There's no way we can cite them all but here are some of the most influentials and inspirationals:
Arman Yahin and his work on breaking silos at Main Road Post
Pype.club and every one from LePipeline.org
Thierry "Mamouth" Lauthelier, Alexis Casas, Pierrot Jacquet, Zwib Ho, Loïc Voisin, and many more...
And of course: our sponsors :)
