DCIP-1: Purpose and Guidelines

Authors David E. Perez Negron R.(@P1R)
Created 2023-06-26

Table of Contents

Simple Summary

DCIP-01, specifies what is an DCIP (Decentralized Climate Improvement Porposals) and how to write one.

Abstract

This proposal specifies a standard procedure to create DCIPs, what a DCIP should include as a minimum requirement, their life cycle, and workflow for making the decentralized climate foundation and its projects operate in the most collaborative and decentralized manner through its DAO Governance Model.

Motivation

The goal of the Decentralize Climate Foundation is to be as Decentralized as posible, these also includes its organization, governance, operations, projects development and even founding.

The Decentralized Climate Fundation base philosophy is considering that by bringing together a diversity of perspectives and encouraging open, evidence-based discussion, it is possible to reach better decisions and minimize corruption and mistakes. The Decentralized Climate Foundation seeks to take advantage of collective wisdom and challenge individual biases through a participatory and transparent process.

The Decentralized Climate Foundation aims to operate in a decentralized manner, involving various participants in its governance and projects. It seeks to promote inclusion, transparency and informed participation to make evidence-based decisions and avoid corruption. Through a decentralized governance model, quadratic and rating voting mechanisms, openness in its operations and continuous evaluation, the foundation seeks to take advantage of the diversity of perspectives and knowledge to address climate change effectively.

ToDo

Specification: meeting types, participant types and incentives

1. Mandatory Meetings (Agile):

For the members which are asociated to the foundation, gets incentives by the foundation/projects and/or donates work, requires a constant comunication and organization, this members are responsable to attend at least 75% and being active participant of the mandatory meetings which are the following:

The 60 min calls are on 19:00 Mexico City time are Mondays. Topics to perform:

  • Review the last sprint tasks and approve the economic incentive by the DAO.
  • Fill a balance Sheet/Table for each participant and his tasks with the project and total finished task added balance.
  • Asign task for the current sprint (week) between the team members and areas (currenty Administration and Development).
  • Brainstorm an approach by consensus an estimate economic incentive for the tasks developers.

Sprint tasks must be considered either as finished or functional. They should not be considered if they are partially done or something that is not proven to be functional.

The 15 min calls on 19:00 Mexico City time are Tuesdays, Thursdays and Saturdays. Topics: Communication, Syncronization and Support between the team on the workflow and tasks

The 25% of the whole payment is for attending to this meetings which is the biggest responsibility for our workflow and communication. So anyone involved into the workflow should be at least at 75% of the measured calls time (t).

\[ t >= 315min \]

Any skipped minute will be slashed from the total payment as following this equation:

\[ TP = TTD * \dfrac{MA}{t}\]

where:

TP = Total Payment

TTD = Total Tasks Deliveries

MA = Minutes Attendance

t = Total of minutes calls for the month

Currently monthly total calls time is 420 minutes

Extra considerations:

1.1. There is also Right to change one 15 min call right monthly (24Hrs before)

1.2. If the Minutes Attendance /420 = 1; there should be a consideration or badge for attendance with a future reward.

1.3. If some one attends less or equal to 75% of the meetings unjustified there should be a quorum to propose a solution in regards the issue.

1.4. Proposed by Bleecker. If the mandatory call extends there should be an incentive based on the incentives model section. The extension can only be at maximum 50% extra from the original schueduled time, other way there should be a rescheduled call.

The only situation where we can skip Minutes Attendance are:
  • Medical issues which require a justification proof (not always from the same source medic since it can be part of a corruption model).

2. Community Calls

2.1. Community calls should be approved by the DAO.

2.2. Community Calls that can ensure income to the foundation either economical or by community work donation should be considered for an incentive to the Participants

2.3. Proposed by Bleecker. All comunity calls should have a total time scheduled, with no extra time added, the moderator and time set for the participants that will get incentives can be marked as active for the time they perform the community call.

3. Office or AFK Meetings

All participants should be considered Active User since it is hard to fake out this type of meeting.

Incentive and Participants types

Justification: Team Call incentives, meetings and others, should be consider more as simbolic since we are working on an already incentiviced tasks:

  1. We do not want to promote useless long calls following the agile methodologies,
  2. Incentives must not be too big but enough to promote teamwork, this is a proposed price to each individual (per hour on a specific task).
  3. On mandatory calls unattendance or missing minutes attendance users should not be include into the incentive extra time.

Participative User

incentive: 1.4USD Hour.

Note: To review how to verify participative person

Active User

Mostly a Speaker/ Moderator
incentive: 6USD Hour.

How to verify Participance?

Random Ping Pong verification

Proposed model by p1r0 where the Moderator ask random time random participation cuestion to random asistend to consider elegible to participative incentive.

Implementation

DCF Phase0 Proposal was already implemented and tested while we found multiple issues that

References

[1] P1R0; Bleecker,"DCF DAO Phase0", https://hackmd.io/A9LNZFTlQsC32gqDw1C7EQ, 01-2023.

Copyright (C)  DECENTRALIZED CLIMATE FOUNDATION A.C.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU
Free Documentation License".
Select a repo