Type of contribution

• code review
• merge requests/issue
  • bugs
  • feature
• research - document
• Dev ops
  • IPFS setup
  • recurring task setup
  • analytics setup

Factors that contribute to points

• Knowledge/skill required
• effort required
• research required
• Merged code - scaling factor
  • code quality
    • test cases
    • comments
    • var names
    • security
    • structure of code
      • reusability of code
      • use of standard libraries
      • organization of files
  • documentation

Points

• Merge Request
  • L1: 10 - 5 hour effort
  • L2: 25 - 15 hour effort
  • L3: 50 - 30 hour
  • L4: 100 - 60 hour
  • There can be higher points decided by guild leaders in rare cases
• Code review:
  • base points: 10% of MR points
  • multiplier
    • suggestions(minor bugs, code improvements) - 2x
    • critical bug finding - 5x
  • Process for base review:
    • leaders assign who is going to review
    • reviewed acknowledges after completing the review
• Nonissue research:
  • low: 25 - 10 hours
  • high: 50 - 20 hours
• dev ops - subjective

Process of assigning points:

• An issue is created, and MR points are assigned