A user can obtain experience points to unlock new levels.
User should have an experience progress bar to show how many it has to go to next level.

Ideas of advantages having high levels:

• Unlock epic borders for avatars
• Being able to unlock evolutive badges

[WIP]

Quests are created from admins or with a Cron.
They are defined by:

• a fun or epic title
• a nice description of the objective to fulfill
• a nuts amount for reward (see #20 )
• a start date
• a stop date

User can claim a Quest when the have completed it. Admin valid or reject the claim.

Technical

A Quest is tagged, like Users & Badgers.
They must be displayed in the front, in a new tab Quests.
New entity ClaimedQuest to claim succeed Quests
They must be a "claim" button, like Badge system.

And GateBundle to AppBundle

Could be interesting to use PostgreSQL :)

Badger should not be fucked up on mobile :3

A triggered badge is a badge linked to an external application, ie. GitHub, Forum, etc.
A service would check every hour or every night if conditions for the given application is fill fulled then automatically assign badge for the user.

Or this could be a webhook.

As a user, I could access a leaderboard to see users with the most badges.
Example of implementation:

I mean: for those who have no access to the source code.

It would be cool to be able to see the badges available for the other services even if I can't claim them.

Example: I'm a core team member, and I want to see the badges of the sales team.

A badge can evolve to a superior level (with stars or levels or whatever).
So the badge "A" could be "A" level 2, or 3.

It should stay the same badge (it's not an unlock, it's an evolution).

• Badge should be declared as "evolutive" and have a max reachable level (admin side)
• An unlock should take User, Badge, and Level if evolutive
• The image doesn't change, only a "star" system under the name or on the border to distinguish them

User registers with his google account.
Avatar url is saved in DB

Later the user updates he's picture on Google => the old avatar is shown in Badger (because the url changed).

There is no problem with GitHub as they provide always the same avatar url.

User can gain some points, named "nuts" on Badger. 🌰

We should have a page to view a badge:
http://ironforge/badge/24b8d68c-c69e-11e5-aa19-386077d535e5

The badge should be displayed as well as the user list that have unlocked that badge.

User A
User B

Quest 1

A & B can see 1. A completes 1. B can't see 1 anymore, but he should.

• "I once swam in the Mellinet duck pond"
• "I co-opted a new colleague for Akeneo"
• "I gave some internal training for a colleague (2 hours minimum)"
• "I fixed my colleague computer"
• "I lost something during a trip / a convention / at a client #notProud"
• "I had some lunch-hour workout (running, riding, swimming, whatever)"
• "I cooked something for a colleague during lunch time"
• "I achieved some hardware / IoT experiment to enhance Akeneo offices"

Be able to define a tag as "default".
Once a user registers, he's attached to this tag.

For us, it could be "Community".

Create interfaces for model (for inheritance) and change the mapping to use the interfaces

I think we could have one or two more badges for contributors:

• When a PR is merged in PIM community
• When a user posted a bundle to use with Akeneo (on marketplace or not)

We should have user groups.
A user is "tagged" into a group. Everyone in the application has the "Community" tag.

We could have other group tags:

• Core Team
• Professional Service
• Internal Projects
• Sales
• Marketplace team

And so on.
A user belongs to X groups, so does a badge.

Error 500 'cause same email.
We have to handle the same email with 2 different oAuth providers.

For now, a user can't see a Badge if none of his tags belong to the Badge.
We should just forbid the POST request to claim a badge he can't see.

• As a user, claim a badge
• As an admin, accept that claimed badge

=> Error 500. See log for more informations, but I think it's related to slack connector

Be notified in a channel when someone unlocks a badge.

On a badge I can claim, JS hover effect to blur image is activated, it should not on users.

Some dev fixtures would be usefull :

• dummy badges
• dummy users

Adventure

An Adventure is defined by:

• A name
• A description
• Completion nuts reward (fixed amount of user percent)
• Completion badge (can be NULL)
• At least one Step

Step

A Step is defined by:

• A name
• An order (can be NULL if not ordered Adventure)
• Completion nuts reward (fixed amount)
• Completion badge (can be NULL)

Explanation

A adventure is a set of step that can be completed by the user. It defines several steps to fulfill.
Each step, once unlocked, give the user an amount of Nuts and sometimes, a Badge too.
Inspiration display for an adventure:

(Here is a example for 2 adventures. The first is a "Linked" adventure where the progression is linear. The second one is a "Not linked" adventure, each step can be unlocked independently)

Linked or not ? An adventure can defines its steps as linked, or not.

• If linked, steps should be unlocked in the right order, the first, then the second, etc.
• If not linked, steps can be unlocked in any order

URL to Akeneo on README generates a 404 error :(

• Add a notification system to be notified when a badge/quest is obtained.
• Notification in the admin system to be notified when someone claim a badge and when someone register on the application.

Create a tutorial explaining how to use Badger.

• Explain how the quest works
• What is an adventure
• How the nuts reward system works
• ...

I've done this:

https://github.com/akeneo/badger/blob/master/src/Badger/GameBundle/Entity/BadgeInterface.php#L15

But another possibility is to remove "extends TaggableInterface" from this interface, and add "implements TaggableInterface" to "Badge".

I think these 2 implementations are "code-correct", but have not the same "coding sense".

What's your opinion ?

Create an home page with links to all users profile.
And create a /user/profile with badges awarded by user

As a user, be able to "claim" a badge.
As an admin, I can accept a "claim" to deliver the badge. It removes the claim.

The "Game" controllers are used in routes like /admin/xxx/...
This controllers should be renamed in AdminXXXControllers or be placed in a Admin folder, to be able to have a declaration of 2 Controllers managing same entities (one for admin, one for front).

In the dropdown below, we should not see already unlocked badge by the selected user.

So we should select the user first to load the second dropdown (filtered by the user's unlocked).