Weekly progress updates from team

mozilla / mozbadging

where we track progress on mozilla-wide badging infrastructure

Mozilla Public License 2.0

2 stars 3 forks source link

Weekly progress updates from team #22

Closed emgollie closed 10 years ago

emgollie commented 10 years ago

We mentioned doing an asynchronous check-in towards the tail end of the week. I can kick it off each Thursday (and am open to email updates if we don't want these in GitHub).

[X] Grow Mozilla roadmap sharing and feedback solicitation
[ ] Surveys and interviews with internal stakeholders to plan badges.m.o. site pages
[ ] Badge studio design brief for issuers brainstorm
[ ] Determining UI process with @zzzndr

Over to you @andrewhayward @christensenep @adamlofting @davidascher.

emgollie commented 10 years ago

Also, we can make part of our check-in on Tuesday a retro about our first heartbeat milestone tomorrow.

adamlofting commented 10 years ago

Thanks for the reminder :+1:

[x] Review @christensenep 's PR that counts badges issued in adhoctribution
[x] #6 Decide how to integrate contribution dashboards into mozbadges metrics
[x] Start process for adding Google Analytics to badges.m.o

Missed the (heart)beat:

[ ] Decide how to allocate a badge to a particular team or contribution type for reporting purposes #8

emgollie commented 10 years ago

@christensenep @andrewhayward Friendly check-in on this. Tomorrow we will also discuss live via https://openbadges.etherpad.mozilla.org/mozbadges.

ghost commented 10 years ago

Hello! Sorry I am late on this.

[x] Adhoctribution PR that logs earners of specified badges as contributors
[x] Staging version of badges.m.o deployed
[ ] Refactor badges.mozilla.org to use the django badgekit client

I'm working on getting the staging version of badges.m.o up and running in heroku, should be done by our meeting tomorrow. badges.mozilla.org using the django badgekit client will miss the heartbeat, unfortunately.

andrewhayward commented 10 years ago

Sorry, missed this.

[ ] BadgeKit API python client
- [x] Testing framework
[ ] Working through VPN/Chief setup

The API client has proven to be a lot more legwork than I was anticipating. The hard work is done, but it might be a case of filling in bits as and when we need them.

I'm also quite confused as to what the Webmaker guys are waiting on us for. This bug is asking that we "move to action [it] ASAP", but I don't know what they're actually after.

Finally, slowly wading my way through what I need to do to get access to the badges.m.o chief config.