Work Regulation for EOSC Mainnet Secretariat

7 min readApr 19, 2020

1.Introduction

Since June 22, 2018, the Secretariat has started exploring the decentralized community governance upon launch. As the first distributed autonomous organization, the Secretariat of EOSC Mainnet BP Meeting has experienced 5 terms. During the 5 terms, we have not only continuously promoted the construction of the mainnet based on community proposals, but also improved the governance mechanism of the Secretariat itself. We believe that the development of the community lies in both the continuous improvement and open source of codes, and the continuous improvement of the community governance mechanism.

Based on the above cognition, we edited Work Regulation for EOSC Mainnet Secretariat. On the one hand, it can set a better working reference for the new secretariat. On the other hand, it can promotes the discussions on the experience of distributed organization governance with other blockchain communities.

2.Routine Work

2.1 Work Division

The Secretariat shall be elected by BPs. At the first regular meeting, the Secretariat will divide up the work. Generally, there shall be 1 seat for the Secretary-General, 3 seats for the Deputy Secretary-General. The specific work divisions are as follows:

Meeting Host: Responsible for hosting regular meetings and BP meetings.
Meeting Recorder&Media Synchronization: Responsible for recording meeting minutes and media synchronization of regular meetings and BP meetings.
Meeting Organizer: Responsible for organizing meetings.
Meeting Notice Editor&Person in charge of communication with development team: Responsible for writing meeting notices and communicating with the development team

Remarks:

1. The meeting notice shall be reviewed by all the members of the Secretariat after editing. After it is confirmed correct, the
notice shall be sent to BPs by the Secretary-General.

2. The notice of the meeting shall be publicized in time on the community forums and media platforms.

3. Meeting notice and meeting minutes shall be publicized both in Chinese and English communities.

2.2 Regular Meetings of the Secretariat

The secretariat shall hold a regular meeting once a week, and the specific meeting time shall be determined at the first regular meeting of the new Secretariat.

The host of the secretariat’s regular meetings is responsible for hosting the meeting.

The editor of meeting notice is also responsible for the meeting minutes. After the meetings, the meeting mibutes shall be synchronized on forums, communities and Github.

2.3 Organize Discussions on Community Proposals

Organizing discuussions on community proposals is one of the main tasks of the Secretariat. The specific process is as follows:

2.3.1 Collect Proposals

The primary approaches for the Secretariat to collect proposals is through the Secretariat’s mailbox BPproposal@eosforce.io, the official forum and the community daily discussions. The Secretariat shall collect the latest proposals based on the key issues of community’s concern.

2.3.2 Standardize Proposals

For the proposals submitted by the community, the secretariat shall communicate with the proposer to ensure the correct format and logical specifications of the proposals. Specifically refer to EOSFORCE Mainnet Proposal Example.

2.3.3 Organize Community Discussions on Proposals

For proposals of community governance type, the Secretariat shall organize the community to discuss the proposal before the BP meeting.

2.3.4 Organize Voting for Proposals

This process can refer to the work content of Chapter 4.

2.4 Organize BP/Community Meetings

The workflow for organizing EOSC Mainnet BP Meetings and community meetings is as follows:

2.4.1 Write Meeting Notice

The notice shall be written by editor in charge. For the format, please refer to EOSC Mainnet BP Meeting Notice Example.

Before writing the meeting notice, it shall be confirmed that whether the development team will attend the meeting to synchronize the development progress with the community. If necessary, the meeting agenda shall includes: Representative from the ndevelopment team synchronizes the development progress with the community.

2.4.2 Publish Meeting Notice

The Secretary-General shall be responsible for it. The meeting notice shall be notified to the person in charge of each BP at least three days in advance, and ensure that the person in charge of the node receives the notice.

On the day of the meeting, the Secretariat shall notify the person in charge of the BP again and confirm whether to attend the meeting on time and make a note.

The Secretariat shall make sure that at least two thirds of the BPs attend the meeting (including proxy voting by the Secretariat).

Remarks:

1. The process of meeting notice should be rigorous and reasonable.

2. The notice of the meeting can only be officially released after all members of the Secretariat have ensured it is correct.

2.4.3 Host Meeting

The meeting host is responsible for hosting the meeting. For the meeting process, please refer to EOSC Mainnet BP Meeting Process Example.

2.4.4 Synchronize Meeting Minutes

The meeting recorder & the person in charge of the media synchronization is responsible for meeting minutes synchronization. Please refer to EOSC Mainnet BP Meeting Minutes Example.

The meeting minutes shall be edited in Markdown format and output both in Markdown format and PDF format.

Markdown format shall be synchronized in the official forum and Github-DAO-FIPS directory, PDF format shall be synchronzied to the community.

2.4.5 Exceptional Case

If the BP is not able to attend the meeting, the Secretariat shall confirm whether a proxy voting is needed. If necessary, the Secretariat shall ask the node to vote for, against, or abstain from the meeting proposal. Then, a person from the Secretariat will be specifically assigned for the proxy voting. If not necessary, and the BP does not attend the meeting, it will be recorded as Absent in the meeting minutes.

For BP meetings, the Secretariat shall make sure that at least two thirds of the BPs attend the meeting (including proxy voting by the Secretariat).

2.5 Organize Node Multi-Signature

For the cases that approved proposals are required to take effect by BPs’ multi-signature, the Secretariat shall lead the mainnet multi-signature upgrade. The specific workflow is as follows:

2.5.1 Preparation Work

The Person in charge of communication with development team shall communicate the code development matters and ask for feedback, including development cycle, multi-sigature commands and related documentations.

2.5.2 Write Notice

Before the official multi-signature, the meeting editor shall edit the multi-sig notice, including multi-sign time, multi-sig commands and remarks. Please refer to EOSC Mainnet Node Multi-Signature Notice Example.

2.5.3 Publish Notice

The Secretary-General is responsible for publishing the formal multi-signature notice.

2.5.4 Follow Up Progress

The secretariat shall follow up on the progress of multi-signature and promptly reminds nodes to complete multi-signature commands.

2.5.5 Complete Multi-Signature, Publish to the Community

After the completion of the multi-signature, an news flash shall be issued to the community. Please refer to EOSC Mainnet Multi-Signature Completion Announcement.

2.5.6 Publish on Media Platform

The news flash shall be synchronized in both Chinese and English communities.

2.6 Offline Nodes Recovery

The status of the offline nodes is mainly in the charge of the communicator with the coordination of other members of the secretariat. In the event of node failure or disconnection, the Secretariat shall start an emergency mechanism to cooperate with community nodes to restore the block status as soon as possible.

2.6.1 Notify Offline Node to Locate Fault

After the node goes offline, the Secretariat shall notify the node operator as soon as possible, and confirm whether the node can recover by itself. If not, locate the fault and provide a screenshot of the error report.

2.6.2 Coordinate with Development Team or Other Node Operator to Provide Support

When the node cannot recover by itself, the Secretariat should contact the development team or other nodes in the community to provide technical support to assist the node to recover the block status as soon as possible.

2.6.3 Announce the Community with Node Repair

After the node restores its status, the Secretariat shall announce that the community node has recovered.

3. Community Operation

3.1 BP Community Operation

The Secretariat is responsible for the operation of the BP WeChat community. After the first regular meeting of the new secretariat, the authority of the supernode community administrator will be transferred to the new members. Members shall modify the remark name in the BP community (for example: Secretary-General & star.eosc_Guo Ying) to facilitate the publishment of notices by the Secretariat. The Telegram community of overseas communities is the same as above.

3.2 Daily Community Article Operation

The members of the Secretariat shall synchronize the community with the development team’s daily output articles at the first time. At the same time, they need to organize community discussions or development team sharing on the development content and updates.

4. Work Report

Generally, the meeting minutes shall be edited and organized by the meeting recorder and reported by the Secretary-General.

5.Term Changing of the Secretariat

The term changing of the Secretariat shall be in the charge of the Secretary-General. The specific process is as follows:

5.1 Publish Registration Notice

The term changing notice shall be published at least half a month in advance with the Github address for registration.

5.2 Confirm Registration Information

Confirm whether the registration personnel and number meet the requirements before the formal meeting.

5.3 Election Speech

The Secretariat shall notice the candidates to prepare the election speech in advance, including both Chinese and English versions.

5.4 Participant Confirmation

The Secretariat shall synchronize the term changing meeting information to the candidates confirm the participation on time.

5.5 Official Election

Please refer to EOSC Mainnet BP Meeting Procedure Example.

6.Salary

The salary of the Secretariat shall paid by the decentralized budget system, and the Secretary-General is responsible for applying the salary.

7. Authorities

7.1 Administrative Authority of Github-DAO Board

The Secretariat possesses the Administrative Authority of Github-DAO Board. The person in charge of communication shall coordinates the authorization from the development team.

7.2 Administrative Authority of Community Forums

The Secretariat possesses the Administrative Authority of Community Forums. The person in charge of communication shall coordinates the authorization from the development team.

8. Other

This regulation is written based on the experience of the first five terms of the EOSC Mainnet Secretariat as a daily work reference. It is hoped that the follow-up terms of the secretariat will continue to improve in the process of community governance.