Foundation Mission Request: TechNERDs S7 [CONTRIBUTIONS]

[Nicca42]

Proposed Foundation Mission Request: This Mission Request is to maintain and expand the existing techNERD program. TechNERDs provide developer support for the Optimism Collective in the [Developers Support repo](https://github.com/ethereum-optimism/developers/discussions). This Mission will introduce a TechNERD Lead, and cover up to 6 techNERDs providing developer support for the duration of S7, as well as incentives for techNERDs to provide support to Optimism organized hackathons.

Intent: Interoperability (developers across the Superchain need technical support).

Total grant amount: 23,000 OP (excluding hackathons and performance bonus)

• 3,000 OP per TechNERD x 6 (max)
• 5,000 for TechNERD Lead x 1 (max)
• 250 OP bonus per nerd per hackathon (see Hackathon Support).
• 4,000 OP bonus reward for high issue turnaround (500 OP per TechNERD, 1,000 OP for Lead, see critical milestones for details).

Should this Foundation Mission be fulfilled by one or multiple teams: Multiple

OP Labs or Optimism Unlimited Sponsor: Soyboy @sbvegan, Vee @Nicca42 , Zak Ayesh Github: @ZakAyesh Discord: @zakattak88

Submit by: Applications are accepted on a rolling basis

Selection by: 21 Jan 2025

Start date: 21 Jan 2025

Completion date: 24 Jul 2025 (start of S8)

---

How will this Foundation Mission Request help accomplish the above Intent?

In order for Interop to work, developers will need technical support. The TechNERDs are decentralizing support, allowing the developer community to help itself. The TechNERD program enables this by decentralizing the knowledge needed to debug, build, and deploy on the Superchain. TechNERDs are also spread over the major timezones, ensuring quicker responses and consistent monitoring.

What is required to execute this Foundation Mission Request?

TechNERDs:

Applicants need to meet the following criteria:

• Complete and pass KYC. This is a requirement to get the TechNERD role.
• Have a web3 technical background (ideally one directly related to the development or deployment of production systems).
• Have a solid understanding of the OP Stack and the Optimism ecosystem as a whole. Understanding of Smart Contract deployment process and tooling, debugging, and common troubleshooting. Some resources have been provided.
• Successfully close a discussion in the Developer support repo.

TechNERDs Requirements:

• Create or update their “Contributor” page in the support repo.
• Attend bi-weekly techNERD calls in Discord.
• Maintain a minimum of 18 active weeks. Only active weeks are considered for rewards. If a nerd has less than 18 active weeks at the end of the mission they will not receive rewards.
  • Activity is defined as at least 5 tickets closed a week or 5 t-shirt points worth of tickets. For more info see the Developer Support GitHub Discussions.

Hackathon Support:

• TechNERDs will be informed of upcoming hackathons during TechNERD calls and will be able to sign up to support hackathons.
• Hackathons may be online or in person. Hackathon support is optional, and as they are outside of regular support channels, these bonuses will be at the discretion of the Optimism Foundation. Activity is roughly defined as 5 questions or t-shirt ticket sizes per 24-hour period. This may be different for IRL or longer-form hackathons.
  • For online hackathons support may be in a different discord/github, depending on the hackathon. Support locations and expectations will be set during calls.
  • For IRL hackathons TechNERDs may be flown to the event (expenses covered) to provide support to developers.

TechNERD Lead:

TechNERD Lead applicants need to meet the TechNERD criteria as well as:

• Have some experience leading a team or managing contributors.
• Have exceptional organizational skills, able to track and maintain data.
• Good people skills, able to give critical feedback in a supportive way to fellow TechNERDs.
• Only existing TechNERDs will be considered for the Lead role this season.

TechNERD Lead Requirements:

• Operations: Manage day-to-day issue management (ensuring each issue has a techNERD, closing issues once a sufficient answer has been provided, combining and closing duplicate questions, ensuring issues have the correct tags, etc).
• Community engagement: Gather feedback from developers getting support, encourage devs to join relevant community platforms, and foster collaboration between TechNERDs and the developer community.
• Strategic: Work with Mission Sponsor to improve the TechNERDs program, and improve performance metrics and quality standards for TechNERDs.
  • Attend a bi-weekly call with the Mission Sponsor to relay any common questions, missing resources, weekly issue count and topics, and fellow TechNERD performance.
• Hackathon support is not optional for the TechNERD lead. Lead will need to collaborate with volunteered TechNERDs to ensure consistent hackathon support (especially for longer-form hackathons), and collaborate with the Optimism team to support workshops or other live resources.
  • Before hackathons, the Lead will work closely with the team to ensure that sufficient resources are available, and resources (tutorials, guides, docs, etc) catered to the theme or goal of the hackathon are available and tested.

Please list a critical milestone.

The critical milestone should be a measure of whether an applicant has made the best efforts to execute what is outlined in this proposal or not. If an applicant fails to achieve the critical milestone, their grant may be clawed back.

• Each TechNERD must:
  • Meet the minimum activity requirements: 18 active weeks. Only active weeks are considered for rewards. If a TechNERD has less than 18 active weeks at the end of the mission they will not receive rewards.
    • Activity is defined as at least 5 tickets closed a week or 5 t-shirt points worth of tickets. For more info see the Developer Support GitHub Discussions.
  • Attend bi-weekly TechNERD calls.
  • There is an additional reward of 500 OP to each TechNERD should they manage to get 80% of issues closed or resolved within 48 hours for 8 nonconsecutive weeks.
• TechNERD Lead:
  • Must meet the TechNERD minimum activity requirements.
  • Produce a weekly report of issues, join team calls, and manage hackathons (outlined in TechNERD Lead Requirements).
  • Lead must ensure that 60% of new issues are closed or resolved within 48 hours. 80% of issues must be closed or resolved within 72 hours.
  • There is an additional reward of 1,000 OP available to the Lead and 500 OP to each TechNERD should they manage to get 80% of issues closed or resolved within 48 hours for 8 nonconsecutive weeks.

How should the Foundation measure progress toward this Mission Request?

Token House milestones are mostly about accountability, so they should measure progress toward completion.

• Hackathon(s) require less team time on assistance than previous hackathons.
• Testimonials from developers helped by techNERDs.
• Weekly ticket close times recorded by TechNERD Lead (goal is 60% closed or resolved within 48 hours).

Please note: All of the contributor roles and associated rewards described here are intended for independent and engaged community members who volunteer to provide their knowledge and expertise to the Collective and receive an honorarium in the form of OP. These volunteers are not employees of the Collective, the Foundation, or any of its affiliates for any purpose.

---

Application Instructions

TechNERDs:

To apply for this Foundation Mission, please complete the linked form. Existing TechNERDs MUST reapply through the same link (even if you have filled this application form in before).

TechNERD Lead:

Those wishing to apply for the TechNERD Lead role please fill in the same form as well as posting the following template filled in as a comment on this issue thread.

• Discord Handle:
• Experience Leading a team or contributors: (this can include other NERD roles or contributions in DAOs or non-traditional leadership roles)
• Relevant experience tracking contributions or tasks: (data tracking, data tracking automation and interpretations, etc)
• Why do you think you would make a good lead: (why are you the right person for this role?)

Note that the TechNERD lead will also need to pass a camera on interview with the team before selection. Should no acceptable TechNERD Lead applications be submitted before the start of this Mission proposal, a TechNERD may volunteer during the course of the Mission.

[fujianggara10]

The link is broken @Nicca42 Developer Support GitHub Discussions.

[opfocus]

Discord Handle:
simple8720
Experience Leading a team or contributors:
I have worked in the supply chain department of a manufacturing company for many years and have extensive experience in supplier management.
Relevant experience tracking contributions or tasks:
I have a basic understanding of Python’s Pandas for data analysis and TypeScript’s d3.ts for data visualization.
Why do you think you would make a good lead:
I am responsible, fair, and focused on achieving work objectives.

[Nicca42]

Update:

TechNRD Lead:

• simple8720

TechNERDs:

• @j8j
• t1p1
• .keroro520
• hashigo
• chomtana

Note that new TechNERDs can apply throughout the season, but rewards will be limited to active weeks. Listed NERDs have successfully completed KYC.