Closed Bug 974836 Opened 10 years ago Closed 10 years ago

Explore how to integrate training accomplishments in the profile

Categories

(Webmaker Graveyard :: Profile, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: laura, Assigned: cassie)

References

Details

(Whiteboard: [profile][r2][allhands][training][future])

We're building a new platform/app for webmaker training with P2PU. We've tried to spec it in a way that it can be fully integrated with webmaker.org later, by making things modular and using stuff we already have (eg makeapi, sso login, etc)

The user stories for the platform are here: https://docs.google.com/a/zythepsary.com/spreadsheet/ccc?key=0Aku8434q8_LPdHBHaFp3bHBFaGViMmxVQzdwSXdTLUE#gid=0 

But I especially want to call your attention to "Notify Webmaker profile that a user has created or participated in a course". Can this happen through the MakeAPI (P2PU is asking)?

This bug is so that when we get to redesigning/leveling up the profiles, the training piece shain't be forgotten ;)
We haven't done a scoping excerise yet for our next rev of profile, so it's still premature to answer that question.

Something I'm sure will be involved in at least that discussion is how the profile displays a users earned badges.  I think we want to look to hook the profile into a either our own badge backpack instance or the current mozilla backpack.
Assignee: nobody → cassie
Status: NEW → ASSIGNED
Whiteboard: [profile][r2]
Blocks: 978940
Whiteboard: [profile][r2] → [profile][r2][allhands][training]
Whiteboard: [profile][r2][allhands][training] → [profile][r2][allhands][training] [may30]
This is a great bug, partly solved already by badge integration. Removing the May30 deadline but let's definitely not lose this.
Whiteboard: [profile][r2][allhands][training] [may30] → [profile][r2][allhands][training][future]
I'm closing this because I think badge integration and the MVC badge work solves this.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.