Issue: Launch a Community Leaderboard and Rewards System #129411

New Issue

Nidhi-kuntal · 2024-10-26T15:29:54+02:00

Nidhi-kuntal commented

2024-10-26 15:29:54 +02:00

Overview

To enhance community engagement and celebrate the work of Blender’s contributors, I am proposing a Community Leaderboard and Rewards System. This feature will recognize top contributors, including artists, tutorial creators, developers, and community helpers, by providing them with visible rewards for their dedication and impact.

Objective

The goal of this system is to make Blender’s community contributions more visible and rewarding. By introducing a leaderboard and a badge system, members can gain recognition, build their reputation, and receive acknowledgment within the community.

Proposed Solution

1. Designing the Leaderboard

Leaderboard Page: Create a dedicated, visually engaging leaderboard page accessible from the main website navigation.
Contribution Categories: Organize leaderboards by different types of contributions to showcase the diverse talents in our community:
- Artists: Ranked based on shared artwork, gallery features, and positive community feedback.
- Tutorial Creators: Recognized for popular tutorials, hosted either on Blender’s platform or other community channels.
- Developers: Acknowledging code contributions, bug fixes, feature suggestions, and active GitHub participation.
- Community Helpers: Highlighting members who actively provide support by answering questions and assisting in forums.
Leaderboard Options: Display monthly and all-time leaderboards to reward both ongoing and sustained contributions.

2. Profiles and Contribution Tracking

Personalized Profiles: Enable contributors to view their achievements, badges, and leaderboard ranking on their profiles.
Automated Tracking: Capture contributions across Blender’s platforms, including forums, GitHub, and tutorial pages.
Shareable Profiles: Allow contributors to share their profile and achievements to promote their expertise.

3. Rewarding Contributions with Badges and Recognition

Badges for Milestones: Develop badges for achievements like “Top Artist of the Month,” “Tutorial Pro,” or “Code Contributor.”
Achievements: Add recognitions for meaningful contributions, such as highly rated tutorials or significant code contributions.
Community Spotlight: Feature top contributors on the homepage or a dedicated “Community Spotlight” page.

4. Incentives and Event Recognition

Event Recognition: Mention top contributors at Blender conferences or online events, giving them public recognition.
Exclusive Perks: Offer perks like early access to new Blender versions, beta invites, or merchandise discounts as appreciation.

5. Engagement Tools

Achievement Notifications: Notify members when they earn a new badge, reach a milestone, or move up on the leaderboard.
Gamified Progress: Include progress bars or other gamified elements on profiles to encourage ongoing contributions.

Considerations

Opt-Out Option: Allow members to opt out of the leaderboard if they prefer privacy.
Accessibility: Ensure the feature is accessible and responsive, following web accessibility standards.
Moderation: Set up basic moderation to verify contributions and maintain a fair and reliable system.

Expected Outcome

The Community Leaderboard and Rewards System will:

Foster a more engaged community by publicly celebrating contributions.
Encourage ongoing contributions, recognizing members for their expertise and support for the Blender project.
Make Blender’s community spirit visible, reinforcing the collaborative and creative culture that defines the Blender ecosystem.

Labels
enhancement, community, engagement, feature request, frontend, UI/UX

## Overview To enhance community engagement and celebrate the work of Blender’s contributors, I am proposing a **Community Leaderboard and Rewards System**. This feature will recognize top contributors, including artists, tutorial creators, developers, and community helpers, by providing them with visible rewards for their dedication and impact. ## Objective The goal of this system is to make Blender’s community contributions more visible and rewarding. By introducing a leaderboard and a badge system, members can gain recognition, build their reputation, and receive acknowledgment within the community. ## Proposed Solution ### 1. Designing the Leaderboard - **Leaderboard Page**: Create a dedicated, visually engaging leaderboard page accessible from the main website navigation. - **Contribution Categories**: Organize leaderboards by different types of contributions to showcase the diverse talents in our community: - **Artists**: Ranked based on shared artwork, gallery features, and positive community feedback. - **Tutorial Creators**: Recognized for popular tutorials, hosted either on Blender’s platform or other community channels. - **Developers**: Acknowledging code contributions, bug fixes, feature suggestions, and active GitHub participation. - **Community Helpers**: Highlighting members who actively provide support by answering questions and assisting in forums. - **Leaderboard Options**: Display monthly and all-time leaderboards to reward both ongoing and sustained contributions. ### 2. Profiles and Contribution Tracking - **Personalized Profiles**: Enable contributors to view their achievements, badges, and leaderboard ranking on their profiles. - **Automated Tracking**: Capture contributions across Blender’s platforms, including forums, GitHub, and tutorial pages. - **Shareable Profiles**: Allow contributors to share their profile and achievements to promote their expertise. ### 3. Rewarding Contributions with Badges and Recognition - **Badges for Milestones**: Develop badges for achievements like “Top Artist of the Month,” “Tutorial Pro,” or “Code Contributor.” - **Achievements**: Add recognitions for meaningful contributions, such as highly rated tutorials or significant code contributions. - **Community Spotlight**: Feature top contributors on the homepage or a dedicated “Community Spotlight” page. ### 4. Incentives and Event Recognition - **Event Recognition**: Mention top contributors at Blender conferences or online events, giving them public recognition. - **Exclusive Perks**: Offer perks like early access to new Blender versions, beta invites, or merchandise discounts as appreciation. ### 5. Engagement Tools - **Achievement Notifications**: Notify members when they earn a new badge, reach a milestone, or move up on the leaderboard. - **Gamified Progress**: Include progress bars or other gamified elements on profiles to encourage ongoing contributions. ## Considerations - **Opt-Out Option**: Allow members to opt out of the leaderboard if they prefer privacy. - **Accessibility**: Ensure the feature is accessible and responsive, following web accessibility standards. - **Moderation**: Set up basic moderation to verify contributions and maintain a fair and reliable system. ## Expected Outcome The Community Leaderboard and Rewards System will: - Foster a more engaged community by publicly celebrating contributions. - Encourage ongoing contributions, recognizing members for their expertise and support for the Blender project. - Make Blender’s community spirit visible, reinforcing the collaborative and creative culture that defines the Blender ecosystem. **Labels** `enhancement`, `community`, `engagement`, `feature request`, `frontend`, `UI/UX`

Nidhi-kuntal added the

Type

Design

label 2024-10-26 15:29:54 +02:00

Alaska commented

2024-10-27 01:59:44 +02:00

Do you plan to implement this feature yourself? Or are you just suggesting it as a idea?

Alaska commented

2024-10-27 03:00:19 +01:00

I will close this design task as I believe it is a feature request/spam.

Reasons I believe it's a feature request:

I do not believe you will implement this yourself and would prefer others to implement it for you.
You don't appear to be a Blender employee, but I could be wrong.

Feature requests are not suitable for the Blender bug tracker and are instead better suited for https://blender.community/c/rightclickselect/

Reasons I believe this is spam:

Some information is inaccurate. Here are some examples:

Developers: Acknowledging code contributions, bug fixes, feature suggestions, and active GitHub participation.

Developers are already recognized for thier contributions through Blender's credits (It lists every person who has contributed, and how many contributions they have made in which time frame).
Plus Blender does not use GitHub for contributations.

Automated Tracking: Capture contributions across Blender’s platforms, including forums, GitHub, and tutorial pages.

Once again Blender does not use GitHub for contributations.

Exclusive Perks: Offer perks like early access to new Blender versions, beta invites, or merchandise discounts as appreciation.

Everyone already has early access to new and beta versions of Blender. This is done to help with bug testing and development. Limiting new versions of Blender to a select few will make Blender worse.

I will close this design task as I believe it is a feature request/spam. Reasons I believe it's a feature request: - I do not believe you will implement this yourself and would prefer others to implement it for you. - You don't appear to be a Blender employee, but I could be wrong. Feature requests are not suitable for the Blender bug tracker and are instead better suited for https://blender.community/c/rightclickselect/ Reasons I believe this is spam: - Some information is inaccurate. Here are some examples: > - **Developers**: Acknowledging code contributions, bug fixes, feature suggestions, and active GitHub participation. Developers are already recognized for thier contributions through Blender's credits (It lists every person who has contributed, and how many contributions they have made in which time frame). Plus Blender does not use GitHub for contributations. > - **Automated Tracking**: Capture contributions across Blender’s platforms, including forums, GitHub, and tutorial pages. Once again Blender does not use GitHub for contributations. > - **Exclusive Perks**: Offer perks like early access to new Blender versions, beta invites, or merchandise discounts as appreciation. Everyone already has early access to new and beta versions of Blender. This is done to help with bug testing and development. Limiting new versions of Blender to a select few will make Blender worse.

Alaska closed this issue

2024-10-27 03:00:23 +01:00

Blender Bot added the

Status

Archived

label 2024-10-27 03:00:26 +01:00

Nidhi-kuntal commented

2024-10-27 16:53:42 +01:00

Hi @Alaska
No, this is not a spam. I would absolutely love to implement this and yes i am capable of doing that.
I am not a BLENDER-EMPLOYEE but hey, isn't this open source?
I would love to help out if you want me to.
Also, I agree with you. I know we don't use github but we use this platform. We could track it here, but since you said that you do track them, then maybe we can open the leaderboard publicly so that developers can become more motivated.
I believe that this idea is worth the try and i know that you think the same as i do not see you guys replying everyone's issues.
Thankyou for considering.

Hi @Alaska No, this is not a spam. I would absolutely love to implement this and yes i am capable of doing that. I am not a BLENDER-EMPLOYEE but hey, isn't this open source? I would love to help out if you want me to. Also, I agree with you. I know we don't use github but we use this platform. We could track it here, but since you said that you do track them, then maybe we can open the leaderboard publicly so that developers can become more motivated. I believe that this idea is worth the try and i know that you think the same as i do not see you guys replying everyone's issues. Thankyou for considering.

Nidhi-kuntal reopened this issue

2024-10-27 16:53:46 +01:00

Blender Bot added

and removed

labels 2024-10-27 16:53:49 +01:00

Guillermo Venegas commented

2024-10-27 17:44:57 +01:00

Labels
enhancement, community, engagement, feature request, frontend, UI/UX

This already states that is a feature request.

Also, I agree with you. I know we don't use github but we use this platform

To me this sounds like this is a generic text and you put "Blender" in it

> Labels > `enhancement`, `community`, `engagement`, `feature request`, `frontend`, `UI/UX` This already states that is a feature request. <br> >Also, I agree with you. I know we don't use github but we use this platform To me this sounds like this is a generic text and you put "Blender" in it

Iliya Katushenock commented

2024-10-27 18:00:23 +01:00

Half of the task seems like this is already such here, other part seems like anti-features or something that does not look like the this that is suitable, not sure.
Even more, not sure this should be here, probably next conversation can be in the chat of the triaging module: https://chat.blender.org/#/room/#module-triaging:blender.org

Half of the task seems like this is already such here, other part seems like anti-features or something that does not look like the this that is suitable, not sure. Even more, not sure this should be here, probably next conversation can be in the chat of the triaging module: https://chat.blender.org/#/room/#module-triaging:blender.org

Iliya Katushenock closed this issue

2024-10-27 18:00:26 +01:00

Blender Bot added

and removed

labels 2024-10-27 18:00:27 +01:00

Alaska commented

2024-10-28 02:57:32 +01:00

Just to clarify some things. I intially closed your report as a feature request or spam based on the points above, plus the fact it was a bit suspicious this was the first thing you did with your brand new Blender ID.

Since you actually want to implement this feature (and it's not a feature request or spam?), then I want to detail the correct approach for something like this:

If you have a small feature you want to implement in Blender, then generally you can code up the feature, submit it as a PR for review with relevant reviewers, and go from there.
If you have a large feature (like this one) you want to implement into Blender, or the wider Blender "community" (E.g. Blender websites), then the best practice is this:
- Find the module in charge of the area you want to make changes to and discuss the broad concept with them, see if they want it, etc. Generally this is done in Blender chat, and then usually you're invited to the bi-weekly module meetings to further discuss the idea.
  - I'm not sure we have a module for website/community stuff. But I believe @fsiddi @dfelinto and @pablovazquez would be the relevant people to talk to.
- Once the module agrees that they want this, create a design task like this one and get full approval.
- Then proceed with implementing it.

If there is something you want in Blender or on the Blender website, and do not want/plan to implement it yourself, then just go straight to Right Click Select and make your feature request there.

Just to clarify some things. I intially closed your report as a feature request or spam based on the points above, plus the fact it was a bit suspicious this was the first thing you did with your brand new Blender ID. Since you actually want to implement this feature (and it's not a feature request or spam?), then I want to detail the correct approach for something like this: - If you have a small feature you want to implement in Blender, then generally you can code up the feature, submit it as a PR for review with relevant reviewers, and go from there. - If you have a large feature (like this one) you want to implement into Blender, or the wider Blender "community" (E.g. Blender websites), then the best practice is this: - Find the module in charge of the area you want to make changes to and discuss the broad concept with them, see if they want it, etc. Generally this is done in Blender chat, and then usually you're invited to the bi-weekly module meetings to further discuss the idea. - I'm not sure we have a module for website/community stuff. But I believe @fsiddi @dfelinto and @pablovazquez would be the relevant people to talk to. - Once the module agrees that they want this, create a design task like this one and get full approval. - Then proceed with implementing it. If there is something you want in Blender or on the Blender website, and do not want/plan to implement it yourself, then just go straight to [Right Click Select](https://blender.community/c/rightclickselect/) and make your feature request there.

Alaska commented

2024-10-28 08:11:04 +01:00

Nidhi-kuntal has shifted the discussion to the triaging module room of Blender chat. It's generally a better platform for real time discussions.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Issue: Launch a Community Leaderboard and Rewards System #129411

Overview

Objective

Proposed Solution

1. Designing the Leaderboard

2. Profiles and Contribution Tracking

3. Rewarding Contributions with Badges and Recognition

4. Incentives and Event Recognition

5. Engagement Tools

Considerations

Expected Outcome