It is proposed to set up a technical expert group within LXDAO. The following is the preliminary idea of its responsibilities, requirements, joining process and remuneration. Everyone is welcome to participate in the discussion.
Responsibilities:
Rank evaluation
Responsible for rating builders (the ratings of some builders may be adjusted periodically). Ratings will affect the points per unit of working hours.
When onboarding, a member of the expert group must participate to rate the builder
In-depth participation and observation in work and projects, and the rating of builder can be dynamically adjusted (need to initiate a proposal public voting adjustment)
Check the project
Join each project team, check products or technical solutions,
Evaluation of personnel needs and working hours (the project needs to provide a convincing task breakdown plan)
If an expert raises an objection, it can be published to the community, and a team of experts will evaluate it together.
Continue to provide technical consulting services in the project.
Technical consultation
lxdao’s internal public technical consultation is available at any time.
Provide technical consultation on cooperation projects or dao, and can deeply track projects and dao community meetings (non-PM). The other party needs to provide remuneration
Participate in the decision-making and evaluation of important matters within lxdao, and provide technical guidance and checks
basic requirements:
Have more than 6 years of work experience in related technical fields, special circumstances can be evaluated by the community
Have successful and mature medium and large project experience, rich practical experience
Have open source community participation and contribution experience, have certain community influence
Awareness of active communication and clear logic and expression
Joining process:
First you must be the builder of lxdao
Apply yourself.
Initiate a proposal to apply to become a member of the expert group, see the proposal template
Members of the expert group must participate in voting, and the pass rate must reach 100%.
More than 2/3 of the votes passed by community members.
You can entrust other members to help you initiate.
daily work:
A member is elected by the members as the group PM to manage daily affairs.
Report to the community every Wednesday, and report to the community every Sunday.
Maintain group work tasks and calendars, etc.
Regularly organize synchronous meetings within the group.
remuneration:
Daily wages.
Group PM 500u per month
Others 400u per month
Internal items.
Calculated based on expert input and working hours.
External projects
Based on the calculation of 1000u per person per week, the working hours per week shall not exceed 10 hours.
Participate in onboarding
Points are assessed according to normal participation
Instead of requiring an expert to participate in the onboarding session, we could come up with a different solution for ranking builders. For instance, builders could submit a request through the website for experts to rank them, and once ranked, they would receive marks to show that they have been verified by experts. This way, PMs can make informed decisions when recruiting members based on the marks.
To conserve resources, we don’t need to follow up on the project in-depth. Experts only need to be involved in the project at key points, such as:
Brainstorming meeting
Solution designing and architecture
Weekly projects’ progress review and provide options for progress (slow, normal, or quick)
Technical support if the PM requires it or if there are blocking issues
Project review after completion and adjust builders’ rankings and skills (by proposal)
For requirements, instead of 6 years of experience in a specific domain, we could change it to general programming or development experience, as this requirement is too strict for blockchain or Web3. However, good communication skills are a must.
In terms of passing rate, we need to clarify the number of votes required, or if we don’t care about the number of votes, but instead focus on the rate.
The salary offered to experts may need to be increased, perhaps even doubled. For example, if the expert isn’t from Core (which has a DAO salary), they could receive 1000u for the Leader role and 800u for another role. This would cover the DAO’s internal project consulting services. For external services, the amount would be evaluated on a case-by-case basis. For instance, if a team needs Layer2 consulting, they could pay an expert team 10000u, and 15% of that would go to LXDAO, while the rest would go to the experts who provided the consulting services. If there are no experts within the DAO to provide the services, we could help find external experts (provided they have the necessary skills to resolve the issue).
Additionally, we need to specify the rules for quitting, such as if an expert doesn’t actively work, misses many calls, or doesn’t provide good ideas or opinions, they could be voted out on a monthly basis.
对于 builder 的技能评级，我初衷是希望可以有一个更公平的评级，而不是大锅饭或者无所谓，因为这会影响 DAO 的支出，项目的开发成本等，当然可以开辟一个新的属性去对 builder 现在的技能评级进行系数调整，不过感觉变得更复杂了，所以我参考了普通公司入职定级和定期调整的机制。这个问题主要是来源于项目中的观察，对于所有人都评为中级以上，对真正的中级以上的 builder 是不公平的。
当然制定定级准则，是专家组最重要的职责，职级调整的流程可以再议。
For the skill rating of the builder, my original intention is to have a fairer rating, not a big pot or nothing, because this will affect the expenditure of DAO, the development cost of the project, etc. Of course, a new attribute can be opened up to compare the builder’s current The skill rating is adjusted by coefficient, but it feels more complicated, so I refer to the mechanism of general company entry rating and regular adjustment. This problem mainly comes from the observations in the project. It is unfair for everyone to be rated above the middle level, and it is unfair to the real builders above the middle level.
Of course, formulating grading criteria is the most important responsibility of the expert group, and the process of rank adjustment can be discussed again.
If onboarding is automated, there may be a process to determine the rating of the builder, because this rating needs to be uploaded to the chain during onboarding, and will affect the number of unit hours for subsequent credits
其实我描述的技术专家跟进项目基本也是做这些事情，就是每个专家会被分配到项目，跟进和回报项目情况。
In fact, the follow-up project of technical experts I described basically does these things, that is, each expert will be assigned to the project, follow up and report on the project situation.
