DCIPs/EIPS/dcip-2.md

134 lines
5.5 KiB
Markdown
Raw Normal View History

2023-04-12 20:28:52 +00:00
---
eip: 2
2023-04-14 01:55:14 +00:00
title: DCIP-2 Meetings
author: David E. Perez Negron R. (@P1R)
2023-04-12 20:28:52 +00:00
status: Final
type: Standards Track
category: Core
2023-04-14 01:55:14 +00:00
created: 2023-02-01
2023-04-12 20:28:52 +00:00
---
2023-04-14 01:55:14 +00:00
## Simple Summary
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
Agile Meeting, types, organization and incentives.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
## Abstract
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
The Proposal is an extension from the DCF DAO Phase0 time measurements proposal to be implemented at the DCF DAO Phase1. There where DCF Agile mandatory meetings, but also some community request meetings and emergency or extra meetings online or even AFK at the foundation office. This proposal intends to Standarize the way meetings can be measured, whichones are mandatory and make them as more agile as possible.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
## Motivation
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
To have more agile, responsable and organized meetings.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
## Specification: meeting types, participant types and incentives
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
### 1. Mandatory Meetings (Agile):
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
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:
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
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.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
>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.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
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
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
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).
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
$$ t >= 315min $$
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
Any skipped minute will be slashed from the total payment as following this equation:
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
$$ TP = TTD * \dfrac{MA}{t}$$
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
where:
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
TP = Total Payment
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
TTD = Total Tasks Deliveries
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
MA = Minutes Attendance
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
t = Total of minutes calls for the month
>**Currently monthly total calls time is 420 minutes**
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
##### Extra considerations:
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
1.1. There is also Right to change one 15 min call right monthly (24Hrs before)
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
1.2. If the Minutes Attendance /420 = 1; there should be a consideration or badge for attendance with a future reward.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
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.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
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.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
##### The only situation where we can skip Minutes Attendance are:
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
* Medical issues which require a justification proof (not always from the same source medic since it can be part of a corruption model).
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
### 2. Community Calls
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
2.1. Community calls should be approved by the DAO.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
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
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
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.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
### 3. Office or AFK Meetings
> All participants should be considered [`Active User`](#Active-User) since it is hard to fake out this type of meeting.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
### Incentive and Participants types
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
**Justification**: Team Call incentives, meetings and others, should be consider more as simbolic since we are working on an already incentiviced tasks:
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
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.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
#### Participative User
incentive: 1.4USD Hour.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
> Note: To review how to verify participative person
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
#### Active User
Mostly a Speaker/ Moderator
incentive: 6USD Hour.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
#### How to verify Participance?
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
##### 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.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
## Implementation
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
DCF Phase0 Proposal was already implemented and tested while we found multiple issues that
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
## References
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
\[1\] P1R0; Bleecker,"DCF DAO Phase0", https://hackmd.io/A9LNZFTlQsC32gqDw1C7EQ, 01-2023.
2023-04-12 20:28:52 +00:00
2023-04-14 01:55:14 +00:00
## Copyright
```
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".
```
2023-04-12 20:28:52 +00:00