On this page we transcribe and summarise the audio below.
http://transcript.thought.garden/assets/engineering-team/Engineering Team.wav Engineering Team
# Summary
This audio note details the inception of our engineering team, which is set to be led by an astral engineer, a role distinct from a physical engineer. This initial team leader is tasked with creating the systems and structures required to manage the team efficiently. This includes the administrative, legal, and technical aspects of the team, as well as the practical implementation and management of these systems. The astral engineer operates with substantial autonomy, with the ability to structure the team as they see fit, although it is encouraged that they draw upon existing governance structures and tools used within the broader organisation. The engineering team's primary administrative tool is an ASANA project. This project operates as the team's unique administrative space and is structured according to the team leader's preferences. It is recommended, however, that the team leader draws upon existing ASANA project structures to save time and maintain consistency across the organisation. The ASANA project also serves as a prototype for the team's wiki and DAO, with its structure and content being independent of the ASANA software. The project's structure is meant to reflect the structure of the open-source core of the organisation's software platform.
# Tidied Transcript
This audio note details the process of creating our first team - the engineering team. The engineering team will be led by an astral engineer, who will manage the virtual online aspects of engineering. This primarily involves systems, technical, legal, administrative, and the practical realization and running of those technical systems. This week, TABs will serve as the astral engineer, while I oversee the engineering team as its captain. The long-term goal is to expand my captaincy and have a captain team, with others forming their own teams. To create the engineering team, we currently have one ASANA project that serves as the main sociocracy circle, or the main governance circle. When we start a new team, it needs its own project, essentially its own administrative space. The engineer will create this project and decide how to structure it. The engineer can develop their own culture, their own way of structuring the ASANA project, their own routine of meetings or lack thereof. While the engineer is free to decide, it would be beneficial to fork the governance and the structure of the main circle and apply it to the engineering structure. However, creating a new structure requires extra administrative effort and the engineer will need to justify the need for this investment. In the worst-case scenario, if the engineer spends too much time developing an engineering DAO without doing any actual engineering, and a dispute arises, we might need to replace the engineer. Despite this, we still try to give full autonomy to the engineer to run their own affairs. The ASANA project will serve as a prototype for the DAO of the engineering team as well as a prototype for the wiki of the engineering team. It needs to be structured in a way that it is not dependent on ASANA as a piece of software. This structure needs to map to the open source core of our software platform. The engineering team will be delegated tasks and will report back at the end of the week. They will provide a summary of the work that was done. This way, tasks from the main circle now get delegated to a sub team. In terms of licensing, we are currently assuming that all licenses and content are Creative Commons license and our open source license in terms of software. However, at certain stages some of these things might not be those licenses, they might be a new commons license that we have or we use an existing peer to peer foundation or other license and some of it might be private IP that is governed by the DAO to be released in a commons license at some future date. The first step in setting up the engineering department is to create the ASANA project. Writing descriptions for ASANA tasks will become wiki pages. We will have microservices that take the text from ASANA, produce the wiki page, other microservices that take that text on the wiki page and link it to Wikipedia and chat up. Next week, we will be setting up the ASANA project. The first step is for the engineer to do that, to talk with the captain before doing that about that structure, to invite other people to that meeting, to maybe discuss the structure, to quickly set up that ASANA project and to start with the tasks that we allocate this week for the engineering team to be managed within that new ASANA project and to make a linkage between that new ASANA project and the agile circle that we have.
# Keywords ASANA project, Engineering team, Astral Engineer, Governance structure, Administrative space, Autonomy, Prototype, Wiki, DAO, Open-source core, Software platform, Team structure
# Graph
digraph { layout=fdp; "ASANA project" -> "Engineering team"; "ASANA project" -> "Administrative space"; "ASANA project" -> "Prototype"; "Engineering team" -> "Astral Engineer"; "Engineering team" -> "Team structure"; "Astral Engineer" -> "Autonomy"; "Astral Engineer" -> "Governance structure"; "Prototype" -> "Wiki"; "Prototype" -> "DAO"; "Wiki" -> "Open-source core"; "DAO" -> "Software platform"; "Software platform" -> "Open-source core"; }
# Assets
engineering-team
# See also - Voice Notes
# Tools
The tools below will use generative AI to edit the contents of the page displayed above.
Tidy the raw transcript with generative AI: