C4GT - Community Revamp - Tech Scoping

[karntrehan]

Sheet: https://docs.google.com/spreadsheets/d/1-S6WpjYnQw3yrCysHcUr0WSHEL55C5HpI77RRG9DgS0/edit?gid=0#gid=0

Flow:

Requirement
(On Githubt ticket)

• Pull issues with different labels - Design, Advisory, Programming, Mentorship

View
(on C4GT website)

• Filter for type of project basis labels added above
• Expand issue for details
• Support for 2 more complexities

Assignment
(On Github Ticket)

• We do not handle actual assignment process, that is owned by org owner.
• Pull assignee from description following a template

Points
(On github ticket)

• Maintain a metrix of complexity and role to award points on ticket closure.
• On closure of ticket, read description and give points basis roles and difficulty to github ids marked above.
  (On BE)
• Maintain a transaction table with each type of closure, complexity, issue id, etc..

Rewards

• New badge to mentor when mentorship ticket is closed

[karntrehan]

Database requirements:

• Issues - id, link, org, labels(String[]), complexity, skills, technology, status, etc..
• Issue_Contributors - id (pk), user_id (fk), issue_id (fk), role
• point_transactions - id (pk), user_id (fk), issue_id (fk), point, type (credit / debit / lapse)
• User - id (pk), name, discord, github, points, level
• User_certificates - id, user_id, certificate_link
• user_badges - id, user_id (fk), badge_id (fk)
• user_activity - id, user_id (fk), issue_id (fk), activity
• Badges - id, image, text, description
• points_mapping - id, role, complexity, points

Created_at, updated_at in all tables.

[karntrehan]

Source: https://drive.google.com/file/d/1CgisMYd9mxkP96hiIJknb2CNCuRa5ncp/view?usp=sharing

[MohitNSamagra]

• Dev tickets to be added