Proposal: Forge Working Group for S11

TL;DR

The mission of the Forge Group is to bring together experienced PMs to mine, discover, and polish great public ideas and public goods, to measure and evaluate the progress of working groups, and to drive and assist LXDAO projects and efforts forward to make LXDAO better.

Season 10 Summary

The Forge group, as the main working group driving the project and internal community needs, in S10, the Forge group drove the iteration of the website, the FairSharing product upgrade, the Brutal Learning branding, the MyFirstWeb3 product relaunch and Brainstorming, the launch of the IntensiveCoLearning project, the refactoring of the Community Research Group, and also participated in the devcon 7 conference. Like Coordination day

What did we do last Season?

Internal community needs and projects

The Forge team regularly reports on and promotes internal community projects on a weekly basis.

LXDAO Website: LXDAO has upgraded its branding, and LXDAO will create an infinite cycle of public goods.

CryptoDCA: The fixed investment project has completed its official launch https://www.cryptodca.xyz/

IntensiveCoLearning: Cruelty Together project has launched its branding and the project team has been formally established, the overall progress of Millstone 1: 80%.

PGNode: PGNode official website is online, L1 weekly newsletter is online.

FairSharing: Completed team restructuring, sorted out legacy issues and fixed the blocked Claim Pizza feature, redesigned the overall FS architecture, and pushed forward the iterative incentive pooling programme, which is now 60% complete.

MyFirstWeb3: Started 2 rounds of brainstorming sessions, identified the direction of lightweight + fun education format, and initiated community discussions.

OPCN: Daily operations, published over 12 weekly articles, S10 total over 20 articles published.

On external ecological research

The Forge team has been regularly working on different ecosystems on a weekly basis to collate and advance their needs.

Optimism: Submitted FairShaing Grants application and LXDAO RetroPGF application, and got some feedback on the lack of professionalism.

Gitcion: Submitted GR22 Community Round and OSS Round rounds.

Arbitrum: Completed some Arb profiling.

Public Goods Research

Reorganised the Wild LX group, the Wild LX group has been working too much on translating content and too little on the research system and atmosphere, now it needs to focus more on the research on how Grants are distributed.

PM training mechanism

Some basic SOP mechanisms have been established, and regular dialogues have been held with fixed posts and intern posts to help sort out goals.

What problems exist in S10

Lack of research on the underlying mechanisms.

Focusing too much on external Grants applications and not researching the underlying mechanisms and needs of the project.

Multiple researchers are focusing on Optimism, Arbitrum, Gitcoin, and ignoring the direction that the community needs to move forward and do better. In S10, the Forge team needs to adjust its strategy, complete the community’s internal projects, and emphasise and research the underlying mechanisms of collaboration, and at the same time, it should summarise and collate the external requirements every week, and initially update it in the form of a forum post. At the same time, external requirements should be summarised and collated weekly, and initially updated in the form of a forum post.

Insufficient promotion of PM training mechanisms

Some SOP and dialogue mechanisms have been established, but they have not been spread to the whole community, and there is no obvious mechanism to bring up the old and bring in the new. The main problems are: unclear sense of goal, insufficient initiative, and weak ability to test the Milestone.

Insufficient research on external demand

The research on external needs is more often conducted by applying for Grants, but the exact research needs of the external ecosystem have not been better organised and analysed in a more systematic way.

Season 11 Plan

In S11, we want to focus on iterating on the community’s own products as well as research on the underlying collaboration mechanisms.

On Coordination Day, there were a lot of questions about coordination in the exchange with Vitalik: e.g., coordination and conflicts in standards development, coordination challenges of Layer 2 solutions (independence and cross-Layer 2 standardization), distribution of small businesses to become unicorns, and distribution of funds for public goods.

In S11, we will focus on the problems posed by coordination and systematically analyze specific issues.

Focus on internal community needs

  1. Focus on internal community projects and needs, and help with proposals and product grooming.
  2. groom and drive product iterations to drive the success of core projects
  3. organise regular reporting of projects within LXDAO and Milestone retrieval.
  4. activate important and potential projects in the community

Research on underlying collaboration mechanism

  1. set up a special group to conduct research on the underlying collaboration mechanism. 2.
  2. Collaboration mechanism needs are more on the product side of the transformation, providing product transformation solutions to the whole LXDAO community.

External Requirements Collection

  1. external requirements research, regularly update the requirements of Ethernet ecosystem in the forums.
  2. external product analysis, output product analysis content regularly
  3. analyse the external requirements received by the operation and BD team

Budget Plan

In S11, we will set up 2 fixed-term members and 2 interns.

10,000 LXPU per month, 30,000 LXPU in total, 1 LXPU = 0.8 U + 0.2 LXP.

Forge workgroups are motivated by project management, internal requirements analysis and facilitation, external requirements acceptance and introduction, and project coordination.

Role Duty Worktime Amount Wage Budget
Project Manager Organising weekly meetings, coordinating people, driving existing LXDAO requirements, supporting project development within LXDAO, ecology, project and PM incubation additions, LXDAO Program Promotion 15~20h/Week 1 30LXPU/h 2000
Project Manager Facilitate internal community projects, organise regular weekly project meetings, test project Milestone, external requirements gathering and facilitation. 12~20h/Week 1 20~30 XPU/h 1500
Researcher (internship) Demonstrated initiative to drive community affairs, product analysis and research skills 15h/Week 2 10LXPU/h 1200
Designer Support LXDAO internal and project design requirements 16.25h/Week 1 20LXPU/h 1300
Research Bounty Public Goods Product Sustainability Analysis, Grant Analysis, Collaborative Mechanisms Analysis 20h/Week 15LXPU/h 1500
Other Bounty LXDAO Internal Requirements Development, Project Requirements Development, Project Server Costs, Project Coordination, etc. 35h/Week 15LXPU/h 2500

中文版

TL;DR

Forge Group 的使命是汇集经验丰富的 PM,挖掘、发现和打磨伟大的公共理念和公共产品,衡量和评估工作组的进展,并推动和协助 LXDAO 项目和努力向前发展,使 LXDAO 更好地发挥作用。

Season 10 总结

Forge 小组作为主要推动项目和社区内部需求的工作组,在 S10 中,Forge 小组推动了官网迭代,FairSharing 产品升级,残酷共学品牌的建立,MyFirstWeb3 产品重启和脑暴,定投项目的上线,社区研究小组的重构,同时也参与了 devcon 7 Coordination day

我们在 S10 做了什么?

社区内部需求和项目

Forge 小组每周会定期对各个社区内部项目进行周报汇总和推动项目

LXDAO Website: LXDAO 进行了品牌升级,LXDAO 将打造公共物品的无限循环

CryptoDCA: 定投项目完成了正式上线 https://www.cryptodca.xyz/

残酷共学:残酷共学项目启动了品牌化,项目组正式成立,目前 Millstone 1 整体进度:80%

PGNode:PGNode 官网上线,L1 周刊上线

FairSharing: 完成团队重组,梳理遗留问题,并修复其中阻塞使用的 Claim Pizza 功能, FS 整体架构重新设计,并主要推进激励池迭代方案,该方案目前完成 60%

MyFirstWeb3: 启动了 2 轮脑暴会议,确定了方向为轻量化+趣味化的教育形式,并发起了社区讨论

OPCN: 日常运营,发布超过 12 篇周刊,S10 总计发布超过 20 篇文章

外部生态研究上

Forge 小组每周会定期对不同的生态开展需求整理和推进

Optimism: 提交了 FairShaing Grants 申请和 LXDAO RetroPGF 申请,获得一些专业度不够的反馈

Gitcion: 提交了 GR22 Community Round 和 OSS Round 轮次

Arbitrum: 完成了一些 Arb 资料整理

Research and collation of requirements

公共物品研究

重构了野生 LX 小组,野生 LX 小组在以往的工作过多在于翻译内容上,研究的体系和氛围比较少,目前需要将更多的内容放在对于 Grants 分配方式的研究上

PM 培养机制

建立了一些基本的 SOP 机制,和固定岗和实习岗定期举行一些对话,帮助梳理目标

https://www.notion.so/lxdao/Forge-Working-Group-Sop-12cdceffe40b807ab64ec38b280ae30a

我们在 S10 存在哪些问题?

缺少一些底层机制的研究

将过多的精力放在了外部的 Grants 申请上,而缺少了对一些底层机制和项目需求的研究

多个研究员将注意力分布在 Optimism,Arbitrum, Gitcoin 上,而忽略了社区本身需前进和做好的方向,在 S10 中,Forge 小组需调整战略,完成社区内部的项目推进,强调和研究协作的底层机制,同时,应每周对外部需求进行汇总整理,初步以论坛帖子的形式发布在论坛进行更新

PM 培养机制推进不足

建立了一些 SOP 机制和对话机制,但是并未扩散到整个社区,也并未形成明显的老带新的机制,主要问题在于:目标感并不清晰,主动性不够强,Milestone 检验能力弱

外部需求研究不足

外部需求的研究更多推进是以申请 Grants 的方式去进行,而并未更好的整理到外部生态的确切研究需求,也并未对需求进行更系统性的分析

Season 11 的计划

在 S11 中,我们希望把重点放在社区内部本身产品的迭代以及底层协作机制的研究上

在 Coordination Day 中,和 Vitalik 的交流中,我们收集到很多关于协调的问题:如标准制定中的协调和冲突问题,Layer 2 解决方案的协调挑战(独立性和跨 Layer2 标准性),小企业成为独角兽的分配问题,公共物品的资金分配问题等

在 S11 中,我们将重点关注协调所带来的问题以及对具体问题进行系统性分析

关注社区内部需求

  1. 关注社区内部项目和需求,帮助进行提案和产品梳理
  2. 梳理和推动产品迭代,推动核心项目的成功
  3. 定期组织项目在 LXDAO 内的汇报以及 Milestone 检索
  4. 激活社区重要和潜在项目

底层协作机制研究

  1. 成立专项组,开展关于底层协作机制的研究内容
  2. 协作机制的需求更偏向于产品侧改造,给 LXDAO 整个社区提供产品改造方案

外部需求收集

  1. 外部需求调研,在论坛定期更新以太坊生态的需求
  2. 外部产品分析,定期输出产品分析的内容
  3. 对运营和 BD 小组接受到的外部需求进行整理分析

预算计划

在 S10,我们将设立 2 名 固定岗成员 和 2 名 实习成员

每月 10000 LXPU,总计 30000 LXPU,1 LXPU=0.8 U+0.2 LXP

Forge 工作组的激励范围包括:项目管理,内部需求分析和推动,外部需求接受和引入,项目协调等

Role Duty Worktime Amount Wage Budget
Project Manager 组织周会,协调人员,推动 LXDAO 现有需求,支持 LXDAO 内部项目发展,生态,项目及 PM 孵化新增, LXDAO 项目推进 15~20h/Week 1 30LXPU/h 2000
Project Manager 推动社区内部项目,定期组织项目周会,检验项目 Milestone,外部需求收集和推动 12~20h/Week 1 20~30 XPU/h 1500
Researcher (internship) 具有推动社区事务主动性,产品分析能力和研究能力 15h/Week 2 10LXPU/h 1200
Designer 支持 LXDAO 内部和项目设计需求 16.25h/Week 1 20LXPU/h 1300
研究 Bounty 公共物品产品可持续性分析,Grant 分析,协作机制分析 20h/Week 15LXPU/h 1500
其他 Bounty LXDAO 内部需求开发,项目需求开发,项目服务器成本,项目协调等 35h/Week 15LXPU/h 2500
3
1 Like

我的感觉确实比较野生,似乎没有特别明确的职责和方向,比较随机的翻译一些内容。但是内容的选择还是很不错的。这块经历了半年了,我觉得是时候有一个更加明确的结论了。

确实不应该太多的精力放在这上面,应该是搞清楚我们要做什么,然后再去匹配相应的基金会和 Grants 以及 VC 等。

这个分析或许应该是在整个 DAO 的层面,而 Forge 可能需要关注应用和开发部分的。

Forge 绝对不是老好人,是需要有更强的 push 和监督的作用,对一些项目形成一定的压力和推动力,不然整个 DAO 会趋向于慢慢消亡,人性就是这样的。

这个为什么成为了 Forge PM 的工作内容之一?这个应该是具体项目的预算和内容。

研究这块的内容还是应该剥离出来,Forge 组本身还是应该专注项目相关事项推进,涉及研究的内容可以给其他研究组提需求,一起来研究

2 Likes

似乎很多工作组都有研究的需求,我在想直接各个工作组抽一部分预算出来,由 Forge 小组领投,来成立一个专项研究组,开始由虚拟小组的模式启动,在后期出产一部分研究内容后,成立正式工作组