Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate away from BadgeKit-api to Badgr #159

Open
1 task
abbycabs opened this issue Mar 1, 2016 · 11 comments
Open
1 task

Migrate away from BadgeKit-api to Badgr #159

abbycabs opened this issue Mar 1, 2016 · 11 comments

Comments

@abbycabs
Copy link
Member

abbycabs commented Mar 1, 2016

Since our MVP, badgekit has been less than stable and is no longer under active development.

  • Roadmap migration plan to Badgr

Issue updated to reflect the decision to move to Badgr

@josmas
Copy link
Member

josmas commented Mar 1, 2016

Leaving a couple of links in here (I am assuming the new badge system should be open source?):

Badgr seems to be the most up to date solution I've found so far. They do hosting too, but all code is available to run your own server.

The nice people at P2PU also worked on an implementation but not sure how up to date it is.

@abbycabs
Copy link
Member Author

abbycabs commented Mar 1, 2016

Thanks @josmas!

Yes, I've talked to Nate Otto about using Badgr here -- leaning towards it!

Open to exploring non-open source solutions, too. I've been thinking about Credly.

@jgmac1106
Copy link

I have used both badgr and credly. I really like badgr.

On Tue, Mar 1, 2016, 1:13 PM Abigail Cabunoc Mayes [email protected]
wrote:

Thanks @josmas https://github.com/josmas!

Yes, I've talked to Nate Otto about using Badgr here -- leaning towards it!

Open to exploring non-open source solutions, too. I've been thinking about
Credly.


Reply to this email directly or view it on GitHub
#159 (comment)
.

@AndreyK729
Copy link

I have set up my own test badgr-server. I studied its API and features and I think it properly suits for the project.

@billymeinke
Copy link

+1 to looking more closely at using Badgr. @ottonomy is one of the few
folks trying to keep the "open" in Open Badges, knows his stuff.

Having seen Credly in use, I'm not convinced it offers anything special.

@dirkcuys would be the one at P2PU to talk to about their badge system, if
you're interested.

On Wed, Mar 23, 2016 at 12:23 PM, Andriy Kopenkin [email protected]
wrote:

I have set up my own test badgr-server. I studied its API and features and
I think it properly suits for the project


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#159 (comment)

Billy Meinke, MEd
@billymeinke https://twitter.com/billymeinke / Web
http://billymeinke.github.io

@abbycabs
Copy link
Member Author

Thanks for the feedback @billymeinke (hi billy!), @AndreyK729 & @jgmac1106!

I think this puts Badgr solidly on our roadmap! I'll update the issue to reflect this

@abbycabs abbycabs changed the title Migrate away from BadgeKit-api Migrate away from BadgeKit-api to Badgr Mar 24, 2016
@dirkcuys
Copy link

https://github.com/p2pu/badges is still used at https://badges.p2pu.org. You can create a badge and users can push badges to their open badge backpack. The process of earning a badge is modelled around giving and receiving feedback on projects. The badges have a peer flavour to them - anyone who earned a badge can give feedback and award that badge - this may not be appropriate for everyone.

@abbycabs
Copy link
Member Author

Ohh, thanks for the info @dirkcuys! Nice to hear about your badges -- this is helpful

@josmas
Copy link
Member

josmas commented May 19, 2016

@dirkcuys you are still alive!!! :D just kidding. Thanks for the info!

A bit of progress: we are going to give Badgr a go. This is a Dockerfile for local installation; hasn't been tested on windows, so help with that appreciated.

Next steps:

  • get all data currently in badgekit into a Badgr local instance
  • write a nodejs module for the Badgr API (this will be subdivided into other issues).

@Wardormeur
Copy link

Also interested in the process, particularly db-wise.
Please write it down somewhere when it happens :)

@josmas
Copy link
Member

josmas commented Oct 2, 2016

hey @Wardormeur it is already happening; most of the db stuff is in the bin folder.
Last time I looked, coderdojo zen used the baking API only, so not sure if the work here would apply, but that was a while ago, and you guys have been very busy lately! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants