ThreeFold Collaboration Template: Story and Brainstorm #263
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ThreeFold Collaboration Template
Table of Contents
Introduction
The following document highlights general procedures for ThreeFold collaboration with external parties.
Background
ThreeFold is by design a project aimed at building thriving relationships between different entities. ThreeFold is open-source, is a Decentralized Autonomous Organization (DA) where Grid Enhancement Proposals (GEP) are voted by community members holding ThreeFold tokens. Anyone can provide nodes to the grid, and anyone can deploy on any nodes on the grid. This project is for everyone, everywhere. ThreeFold also provides a support service and has a strong service level agreement for 99.9% uptime support.
ThreeFold has different collaborations from around the world, in different countries. Throughout the collaborations, we span different time zones and cultures. The ThreeFold grid is distributed in more than 60 countries and we can say that the sun never sets on ThreeFold. We are proud of our collaborations around the world and we know deeply that it is part of our identity.
Along the years, we have learned and explored different ways to collaborate. It has been nourishing to learn from those experiences and build from this foundation. We take the opportunity here to assemble some ideas concerning how to efficiently work through collaborations and partnerships. We believe each collaboration is unique, and represent the opportunity to build the vision of planet and people first that is driven our work for over a decade now.
The following represents inviting guidelines and procedures that is meant to enhance and align collaborations for ThreeFold and external parties.
Memorandum of Understanding (MOM)
A Memorandum of Understanding (MOU) is a non-binding agreement between two or more parties that outlines the terms and conditions of their understanding and cooperation on a particular project, initiative, or idea. It is typically used as a preliminary step to formalize an agreement before entering into a more comprehensive contract or partnership. An MOU usually includes key elements such as the scope of work, roles and responsibilities, timelines, and goals, but does not include detailed financial terms, warranties, or other contractual obligations. The purpose of an MOU is to provide a clear understanding between parties and to facilitate further discussion and negotiation, rather than creating a legally binding contract.
ThreeFold MOM Template
We propose a variation of the Memorendum of Understanding (MOM).
To ensure optimal collaboration, it is good to offer some general procedures and templates to facilitate the work between parties.
Each project should be able to generate the following filled template. This ensures that all parties concerned are aligned for a common goal.
Questions to Answer
Template Filled with Specific Example
We propose a basic MOM. It can and should be extended for a clear and thorough project. This can be used as a basic example to understand the essence.
MOM Questions and Answers: Fictitious Project: Node Workshops
Ecosystem Evolution
It is in the inner roadmap for ThreeFold to offer all different products and services needed for the completion of a project from A to Z via a ThreeFold UI. This would allow ThreeFold+External Parties collaborations to be smooth and organized.
Indeed, we are in the process of building a general user interface (UI) and its accompanied tools such as calendar, video conferencing, chats, etc. that will allow a project to live 100% within the grid in dApps ensuring security and clear communication. For now, we are using some tools, open-source as much as possible, but not always, e.g. Google Calendar.
@gosam @scott @Amanda @marionrvrn
To be discussed and brainstormed in the upcoming comms meeting if you want!
It's good Mik put down these thoughts but I wouldn't say this is priority for now.
We can close and use later if/when needed