You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This meeting involves reviewing the current competition status and discussing strategies for enhancing our approach.
This meeting touches on scoring criteria, leaders assigned to each submission category, and what transparency into the entire GoR grading system looks like.
We are going to have leaders for each challenge in order to check the issues and PRs
Michael + Second lead (TBD) lead for Governance
Milos & Jon lead for Tutorial
Lead TBD - Evaluation
Make a disclaimer that the participants can remind leaders to review their issues
transparency on what we think would score
Recurring reminder for the leaders to update the results with a report
Results are in form of proposal to the participants
We are not going to publish score card as it lowers flexibility and closes doors - We can have something internally
Clarify profiles for each challenge in the issues - e.g, Tinkerers, Technical Writers, Philosophers, writer and not limited to - Golang developers - to be listed by Marketing team and Jon, to be passed on to Core team for approval
Leader Board to be structured by top 10 contributors - Intermediary way to measure the contribution
An Office Hour to be lead for Jon + Johnny + Valeh
thehowl
changed the title
Recurring - GoR Weekly Updates
Minutes: GoR Weekly Updates
Nov 24, 2023
This meeting involves reviewing the current competition status and discussing strategies for enhancing our approach.
This meeting touches on scoring criteria, leaders assigned to each submission category, and what transparency into the entire GoR grading system looks like.
Related: DevRel #6.
The text was updated successfully, but these errors were encountered: