You can find the original announcement in the
#announcements discord channel (see link: here). For ongoing discussions, please see the
#server-general channel under the Active DAO Projects category.
This is the Season 1 budget proposal for the Server Architecture Team. It outlines the high-level goals, how we plan to get there, the team working to make this happen and the proposed budget we’re applying for.
This team is tasked with overseeing the ongoing maintenance of the different categories and channels within the Developer DAO discord — and its overarching purpose is to make it easier for members to navigate the server, and to quickly find the information that they are looking for.
The genesis of this team stems from the original Onboarding Proposal — in that its premise is also rooted member flow.
Coming into the server can feel very overwhelming for new members; and even some members who have been around in excess of 6 months, have reported that they still find it ‘chaotic’. Considerations towards the Discord server architecture are inherently a UX issue.And so this team falls under the Community Guild in large part, because its focus is primarily on the members of the community.
The intention is that each season, there is an allocation set aside to fund the work undertaken by the SATeam. The logistics of which, do not have to be immediately defined; and are subject to change in future seasons.
As this particular effort is multi-layered, and has particular crossover with initiatives such as Onboarding; I’m strongly encouraging us to be pedantic about focusing on only a few core goals for Season 1 - in addition to starting small and scaling up gradually.
Two core themes across the DAO heading into Season 1, are clarity and focus. And that is what we want to dedicate our efforts towards: bringing clarity to the Discord’s structure, which in turn, should make it easier for members to focus on the things that they need to focus on.
Thus in light of the above, the scope of work for Season 1 will be divided into 3 phases:
- Requests to add descriptions to channels
- Enquiries into the purpose behind a channel
- Archiving channels that are no longer needed, or have failed to meet one of the above standards
- Establish a new Guild (category) framework
- Consolidate projects into their own categories (where necessary)
- Restructure the placements of categories and channels (i.e. rearranging the position of Guilds in the server’s hierarchy)
- Roll out new category framework in sections
- Design the Point Of Contact channels
- Establish new Role structures
- Create read-only Discord Map channel (big undertaking, and may flow into Season 2)
At a more granular level, the above also includes (but is not limited to):
Weighing in on discussions around channel management
Offering consultative services to Guild and project leads, as required
QA testing bots and software (luan)
Other miscellaneous tasks which serve this effort
The requested budget is based on a projected idea of operations that are needed to fulfil the Season 1 scope of work, as laid out above. The nature of the work we’re doing, sometimes means that we are not working in strict 1hr time frames. It can be much longer, and it can also be shorter. Regardless, these efforts are impactful. And so I want to reframe how we quantify and ascribe value to that work.
Taking a cue from the legal profession — billable hours. Any work we do that is in service of the server architecture mission, is valuable; and thus should accrue remuneration in the form of
Budget Calculation = 𝒙 hours per-week X 16-week Season X 15
Buffer (miscellaneous) = 9,960
Total requested Budget = 15,000
|Contributor||Est. Weekly Hours||
|luan (Team Lead)||10hrs||2,400|
The following people will comprise the initial team, based on prior work already completed, and previously expressing an interest in building this out.
@MichelleBakels (MichelleBakels#9769): core contributor
@aakansha12 (aakansha#9163): core contributor
@myz1237.eth (Alex1237#2487): core contributor
@luan (lu.an#9388): core contributor, Team Lead
Archive 20% of channels in the main server (i.e. non-Onboarding channels) by the end of Season 1.
Rollout a new framework for Guild categories.
Design, test, and roll out v1.0 of the new role structure for the main server.
Maintain a first-response time of 48 hrs for all inbound enquiries
Maintain a first-response time of 24 hrs for all active channel petitions
Maintain a first-response time of 72 hrs for all archived channel petitions
The immediate next steps are focusing on finalizing the custom bot’s parameters, and then running it. We have already begun Phase 1, and so the main focus is beginning the process of archiving all non-crucial channels.
- Yes, I support this application
- No, I do not support this application