Open Sourcery ✨

Development Developer Relations
2

NEAR Open Sourcerers Priorities

  • Priority One: Increase the number of successful apps running on MainNet
  • Priority Two: Increase the number of successful developers deploying and improving their apps on TestNet
  • Priority Three: Support the continued maintenance of the material that will allow devs to self-serve and be successful

Main question:

  • James: Identity management and the CRM integration. As people join, we need to see the updated description.
  • James: How this program for the devrel guild can fit into the NCD. Can we carve out a space in that discord.
  • Peter: How can we get people to stand up key activities?
  • Peter: What goals and numbers can we make public to inspire people to act in this community?

Thoughts + concerns + "How do we accomplish this?"

  • James:“Tokens!”
  • Chloe:“Feeling confident that you’re correct as the person supporting”
  • James:“Certain questions must be answered by the DevRel and NEAR core team”
  • Chloe:“Taking care of community leaders”
  • Dani:“You can work with us, and then you ship an example app.”
  • Chloe:“As many efficient examples is important”
  • Chloe:“A scavenger hunt or developer flow”
  • Sasha:“It’s difficult to get questions answered. The question was sitting there for 72 hours”
  • Sasha:“Zero karma doesn’t allow new users to even ask a question.”
  • James:“the forum is the best place to start. Forum participants, create a request for tokens”
  • Cameron:“He was on stack Overflow, went to Discord, then went to TG and got a quick response”
  • James:“I’m all for rewarding people for contributions on any platform, but we need to consolidate”
  • Dorian:“What mechanisms do we have to track these people? How can we measure credibility?”
    Sidebar
  • Cameron:“The list of devs is in Airtable”
  • James:“How do I add to the AirTable? Can we make a form?”
  • Cameron:“Yep. Next week.”
  • Chloe: “So would Dani’s idea to have grants for tasks/pathways DevRel wants members to go down and those tasks can be sent to the relevant contributors make sense? Tracking and Reputation still important ofc”
  • James:“We need a hands off approach to rewarding devs. I would have other people proposing to tip people.”
    Cameron:“Weighting contributions is difficult to crowdsource. You need to start with a benevolent dictator. It’s beneficial to hear from the community on what should be considered a contribution. It’s important from someone to provide guidance on the pricing.”
    Sasha:"If you like the answer to your question you tip a fraction of near. If you solve my major problem, I tip you a 100 near. I decide by myself. ‘Oh man, this guy just saved my life! Here’s ten cents’ "
    James:“Number one priority is identifying the pathways that are valuable. Then we can have a dry run.”

Process and needs

  • A single place for people to be aware of new issues in docs, new initiatives etc.
  • A wiki where we can explore what developer problems are
  • A documented pathway to getting active for Open Sourcery members
  • Developer kits for devs to present and to take to their friends/communities
  • Onboarding flow into the DevRel guild. (Includes publishing flows that people can get started with). E.g. “Audit of an example app or documentation and writing issues.”
  • A process for answering questions on: Stack Overflow
  • Airtable: the developer list
  • Talk to that list one dev at a time
  • Documentation on “tipping people”
  • A person responsible for each component of the guild
  • A framework for success: Inputs and outputs

Campaigns

  • Next week James will do a dry run of the experience of the themed story-telling activities based on the pathways.
  • These could evolved into text based quests on the forum.

Key activities for Open Sourcery

  • Writing documentation
  • Writing issues in code libraries
  • Writing PRs to the code libraries
  • Dev chat support
  • Presenting workshops
  • Supporting hackathons
  • Educating new members of the dev community
  • Campaigns

Next Steps

  • [ ] James to start talking to the list of devs
  • [x] James picks the place of a single source of truth for this: Private Forum
  • [ ] Y writes the process for answering questions needs owner
  • [ ] Cameron owns list of devs, and will move forward on dev form
  • [ ] DevRel Guild · Issue #31 · near/devrel · GitHub << Update the tasks here.
2 Likes