In an effort to better address the various concerns and questions raised by members of our community, I wanted to use this opportunity to provide additional information and clarification on several key points. By doing so, we hope to foster a greater sense of transparency and openness!

With that in mind, I would like to offer the following insights and perspectives that will hopefully answer the questions asked, and invite further dialogue and engagement on this topic.

It’s a universal habit for people to skim past mission statements, visions, values, and similar content — and I’m definitely guilty of it myself. In the case of the Community Team, however, I believe it is imperative to go through each item one by one because they all hold significant value.

Five duties are currently listed in the mission statement — let’s try to re-order them from “standard moderation activity” to “not-so-standard” activities expected of a moderation and support team.

The never-ending battle with scammers and impersonators is real. I don't think I need to elaborate much on the first two, as they are standard duties of any type of community moderation and support teams.

🚨 However — it should be duly noted that the Evmos community support team has been through some real rough waters on more than a few occasions. That’s one of the many consequential beauties of supporting a community that is on the frontier of innovation and constantly shipping new technology.

The CMS Team has the necessary duty of constantly managing the flow of information with the community at large. However, the team not being recognized as a formal workstream puts the DAO in an awkward position. If the following flow-chart is confusing to follow, then it has served its purpose!

The DAO is looking to participate with Evmos core team in the further development of fundamental documents and resources for both the Academy and the Community docs. While the CMS team is always educating and assisting the community on a daily basis, the vision of CMS is to be more than just a support team — ECP-2B is a necessity for the CMS team to effectively expand its importance and assistance to the Evmos ecosystem.

(Both documentation repos are very new and is needing more content)

The CMS team is also responsible for fostering an engaging and inclusive environment for the Evmos community. As someone who has assisted many communities before, I can tell you confidently that it is not an easy job to foster community growth — it takes countless initiatives, countless hours of commitment, and an alignment of long term goals and incentives.

This includes promoting community events, highlighting community contributions, and providing opportunities for community members to get involved in the DAO — and this is just scratching the surface.

As a community bootstrapped by the Rektdrop, Evmos didn't have the chance to grow naturally. With the Rektdrop behind us, the community we build now and moving forward will be the members we count on to joke around with, lend a helping hand to, and rely on. Real community building needs to happen now!

Do we need 11 moderators? Actually, after community feedback the number was cut down to 7 moderators and 1 workstream steward. The latest draft can be seen here with the discussion.

"Do we need 8 members in CMS?" Well, the community should now recognize the importance of the CMS team to the long-term growth of Evmos. Their work is much more than simply "covering three channels."

8 members were deemed an ideal number for CMS because it would be difficult to achieve efficient 24-hour shift coverage with fewer members.

The moderators were originally contracted by Tharsis, with the mutual understanding that the CMS workstream would one day become its own entity under the community as a subDAO. As for initiatives, we have a relatively small contributing community! Although I’m not sure which initiatives are being specified, we really do hope that our pool of contributors will continue to grow.

We are currently in the planning stages of a multi-faceted approach to:

1) reduce the overall funding ask amount; and 2) a program to reduce Evmos sell pressure from DAO contributors — for good measure, as contributors potentially selling their Evmos wouldn’t have made a dent on the macro price. But we understand the heinous market that we’re in and are thankful for our tough governing community for always keeping us on our toes. Lastly, 3) we may rebrand the workstream to better represent their duties and commitment to the Evmos ecosystem.

There should be an announcement in the next week or two regarding this program, and we’re pretty excited.

We would love community help! Although governance is a slow grind, it gives me strength knowing that it took MakerDAO four years to decentralize itself — but the result is just beautiful.

The community is always welcome to jump in at anytime with ideas, concerns, and suggestions!