Author(s): @luan (lu.an#9388)
Following discussions held during the Team Sync on 15th July - the team have decided to pull the AxisOne Season 1 proposal. In a nutshell, it’s not at the place that it needs to be. I (@luan) am solely responsible for this. Regrettably, I took on the role of Lead on this initiative, much later than that of other projects (such as Onboarding). As a result, it has had much less time to be refined and produce certain deliverables.
Of our own volition, the team will continue to work on the AxisOne Program throughout Season 1 - but will we not have a
$CODE budget allocation.
For further context - please see the two messages I wrote in Discord: Link.
Link to archived version.
Link to the original idea in Discord (27th November, 2021)
You can find previous discussion about this topic in the
#axis-one discord channel within the Community Guild. And for a high-level overview of this, please see the original AxisOne Proposal that I put together back in early-May 2022.
This is the Season 1 budget proposal for the AxisOne Program (formerly called Fellowships). It outlines the high-level goals for the initiative, how we plan to get there, the team working to make this happen and the proposed budget we’re applying for.
The AxisOne Program offers 3 distinct pathways for funnelling people into Developer DAO—all of which are in service of fostering diversity, inclusiveness, and empowerment: scholarships, Club Stellar, and fellowships. For this reason, the proposal I’m making here is that we allow ourselves the flexibility to tailor our motivations to specific seasons; whilst maintaining some overarching structure that is predicated on the Program’s ethos.
AxisOne exists as a public goods initiative, focused on funnelling people into Developer DAO. At both a higher and granular level, this Program is grounded in diversity, equity, and empowerment — and is comprised of the following 3 pathways:
Memberships that are awarded at the individual-level. There will be a 50/50 split between memberships which can be earned, and memberships that are awarded for free.
Memberships that are awarded at the individual-level. For ref. see the Kernel program that was spun up out of Gitcoin — Kernel Community | Kernel.
This pathway serves as an opportunity for people to come into the Developer DAO community in a cohort-based, collective learning format. Fellowships will run for 1/3 of a season (i.e. a period of 4 weeks).
Memberships awarded to people, via organisations that have a mission focused on underrepresented groups within the tech and web3 spaces.
Depending on when Season 1 commences, the 1st and 3rd pathways will be ready to rollout by Week 4 of Season 1. The second pathway (Fellowships) will not. Part of the Season 1 (and potentially Season 2) focus, is to build this out. This includes key partnerships (both internal and external), research & development, drafting grant proposals, and constructing a v1.0 framework.
The intention is that each season, there is an allocation set aside to fund the AxisOne Program. The logistics of which do not have to be defined at this juncture; and thus, are subject to change in future seasons.
As this particular effort is multi-layered, 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. As mentioned, depending on when Season 1 commences, the rollout of the AxisOne Program will not be ready for week 1. To protect the integrity of this initiative, it is important that we do not rush this.
The Developer DAO branding will be used on any 3rd party platforms, such as Google Forms, Typeform etc.
The overarching goal for Season 1 is twofold:
Roll out the Scholarships and Club Stellar pathways in a manner that protects the integrity of the AxisOne Program.
And from there, work to develop a steady cadence around each.
At a granular level, this looks like (but is not limited to):
- Constructing a charter
- Constructing an ethos
- Work on building out a suitable v1.0 framework for the Scholarships pathway
- Building a Season 1 framework of responsibilities for the Elected Committee
- Procuring ENS domains + setting up relevant multi-sig(s)
They are the immediate areas of focus. And thus, give way to the following:
- Refinement of the aforementioned pathways
- Initial development on the Fellowships pathway
- Building out the Axis Fund
In the spirit of fostering a democratic work structure, the initial intention was for the entire Community Guild to get involved in developing this Program. After multiple attempts to engage the community (dating back to November 2021 when this idea was first broached), I’ve concluded that we lack certain elements within the DAO at this juncture, that can adequately facilitate such an approach. What has inevitably occurred at various intervals, is that this effort has experienced delays. Therefore I believe that it is better to follow the format we currently have running on the OKRs Initiative: open up the process for anybody to get involved in, and later establish a working group who can be held accountable.
The Working Group will remain separate from; but still function alongside the Elected Committee.
The requested budget is based on a projected idea of operations that are needed, in order to fulfil the Season 1 scope of work, as laid out above. Team syncs, liaising with external organisations, drafting documents, research & development, as well as other miscellaneous tasks which serve this effort.
The nature of the work that 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 = 𝒙 no. hours per-week X 16-week Season X 15
Buffer (miscellaneous) = 14,480
Total Requested Budget = 20,000
|aakansha||Fellowships Lead, R&D||7hrs||1,680|
|luan||Founder, Team Lead||12hrs||2,880|
|Committee Member||Elected Committee||2hrs||480|
The following people will comprise the initial working group, based on them previously expressing an interest in helping to build out this Program. To reiterate the above: the Working Group will remain separate from, but still function alongside the Elected Committee.
@luan (lu.an#9388): Founder, AxisOne Program Lead
@aakansha12 (aakansha#9163): Fellowships Lead, R&D
@Cannablitch (Canna (She/They)): Partnerships
@Committee Member (x5): season-specific elected contributor role
Construct a Charter for the AxisOne Program prior to its rollout, and get it ratified — the charter focuses on WHO are we? and WHAT do we do?
Create an Ethos for the AxisOne Program prior to its rollout, and get it ratified — the ethos focuses on the HOW i.e the standards by which the Charter is upheld.
Define a process by which the Ethos that is signed on-chain each season by the elected Committee, can be archived and easily referenced.
Hold an election to vote in the Season 1 Committee that will be tasked with deciding who will be awarded memberships, in accordance with the ratified Charter.
Successfully consolidate the scholarships pathway under the AxisOne Program (contingent upon @dabit3).
Establish a framework for fulfilling Season 1 duties between the working group and Elected Committee (asynchronous tasks, regular meetings etc)
Establish a framework for awarding scholarships, selecting organisations, and allocating memberships
Set up multi-sig.
Define a framework around minimum viable credentials (MVC) that members of the elected Committee are to possess, in future seasons (e.g. experience with on-chain voting procedures and governance, anti-bias training etc).
Have a basic outline of this pathway completed, by the end of Season 1
The immediate next steps are focusing on finalizing an initial draft of the Charter and Ethos, electing who will comprise the Committee for Season 1, and continuing research and development into the Fellowships pathway.
- Yes, I support this application
- No, I do not support this application