Skip to content

how-we-work.md

Latest commit

 

History

History
68 lines (57 loc) · 4.18 KB

how-we-work.md

File metadata and controls

68 lines (57 loc) · 4.18 KB

How we work

Within bitspossessed we want to promote our values by working transparently in terms of organizational structure and contribute to "open source" structures to inspire other collectives.

We as collective members are all freelancers and we have both individual and collective projects.

Our projects can be for external clients, collaborations or internally initiated projects. Sometimes they are financed by the client themselves and sometimes through grants.

We like to use our internal resources to support the projects and communities that are aligned with our values.

As a team we can join efforts with other teams or be hired as a complete team by an external client. It can be the whole collective or only some members.

Within the collective we share our connections and networks to find suitable projects for us to work on. We also support each other in our individual freelancer work. Being a freelancer can be lonely and tough. Therefore we engage in moral support, skill-sharing and professional advice in our different areas of expertise.

To develop our skills we also learn together through study circles on different topics and individual learning sessions.

We believe that our approach to work allows us to collaborate more effectively which benefits both our clients and the world beyond.

If you would like to know more about our internal structure you are welcome to get in contact! We especially want to support other collectives and cooperatives who share similar values.

Roles

We created a non-hierarchical structure with clear and healthy roles that are rotated regularly. 
<ul>
  <li>Navigator / Collective Tasks Coordination</li>
  <li>Warp drive engineer / Infrastructure / house builder / Collective Dev-Ops</li>
  <li>Finances / Pre-post-scarcity planning</li>
  <li>Spaceship Counsellor / Spock-Hand</li>
  <li>Fun coordinator / Dynamisation / "Fun-raising"</li>
  <li>External Communication / Social Media / Website / E-Mail</li>
  <li>Librarian / Secretary</li>
  <li>Meeting Moderator</li>
  <li>Meetup coordinator</li>
  <li>Repository maintainer</li>
  <li>Note Taker</li>
  <li>Project Coordinator</li>
  <li>Project Finances</li>
</ul>

Virtual office

As we work primarily remote-first, we have virtual office with the following spaces:

<ul>
  <li>We host many of the services in a Debian Server provided by <a href="https://maadix.net/en/" target="_blank">Maadix</a>.</li>
  <li><a href="https://nextcloud.com/" target="_blank">Nextcloud</a>  sharing for files, calendar, contacts, and project boards. We use OnlyOffice for collaborative writting.</li>
  <li><a href="https://rocket.chat/" target="_blank">Rocket.Chat</a> for internal communication.</li>
  <li><a href="https://jitsi.org/" target="_blank">Jitsi</a> for video calls.</li>
  <li><a href="https://hedgedoc.org/" target="_blank">HedgeDoc</a> https://hedgedoc.org/ for collaborative note taking in Markdown.</li>
  <li><a href="https://freescout.net/" target="_blank">FreeScout</a> for managing shared mailboxes.</li>
  <li><a href="https://list.org/" target="_blank">Mailman</a> for managing mailing lists.</li>
  <li><a href="https://www.rainloop.net/" target="_blank">Webmail Rainloop</a>  as a web-based email client.</li>
  <li><a href="https://bitwarden.com/" target="_blank">Bitwarden</a> to centrally store credentials.</li>
  <li><a href="https://clockify.me/" target="_blank">Clockify</a> for tracking our working time.</li>
  <li><a href="https://github.com/" target="_blank">GitHub</a> for hosting our code repositories.</li>
  <li><a href="https://obsproject.com/" target="_blank">OBS</a> to record locally the content we want to preserve.</li>
</ul>

We prioritize maintaining our own infrastructure, and using open source software internally to our own ability.