Fwd: Mozilla Backpack is now Badgr Backpack
by Miro Hrončok
JFYI:
-------- Forwarded Message --------
Subject: Mozilla Backpack is now Badgr Backpack
Date: Tue, 27 Aug 2019 13:14:22 +0000
From: badges(a)mozillafoundation.org
Mozilla Backpack is now Badgr Backpack
Mozilla Backpack is now Badgr Backpack
Mozilla is retiring its Open Badges Backpack platform and helping users move
their badges to Badgr.
We're immensely proud of the work we've done on Open Badges over the years, and
Mozilla will continue to be an Open Badges champion. Going forward, we believe
Concentric Sky and the free and open-source Badgr platform are the best stewards
for the community. Mozilla will shutdown the Backpack platform by August 22,
2019. You can read more about the change here
<https://support.badgr.com/portal/kb/articles/mozilla-backpack-transition-...
>.
What's Next?
*Here's what's changing:* We are retiring the Mozilla Backpack and transitioning
to Badgr Backpack.
*How will this impact you?* You will need to follow these three steps to make
the transition to Badgr:
*1.* Download the attached zip file. It contains all of the badges awarded to
your Mozilla account.
*2.* Access Badgr. It's free and easy.
Access Badgr <https://issuerjs.backpack.openbadges.org.badgr.io/#/select-server>
*3.* Earn your first Badgr badge in less than 5 min. Promise.
Earn a Badge <https://explore.badgr.io/>
Why Badgr?
Badgr has all the same features as Mozilla Backpack, plus more. Badgr gives
users complete control over their achievements and data, so they can organize
and share all their badges from one place. Users can even create and award
badges for free. For more information, visit Badgr.com <https://badgr.com/>.
4 years, 8 months
Future of Badges
by Clement Verna
Hi all,
Today a few of us had a productive meeting to discuss the future of
the Badges application.
As a summary we have agreed on the following :
1 - No outreachy intern for this winter, but starting to prepare a
plan for next summer round.
2 - A new Front end for the application based on a JavaScript
framework and independent from the back end will be written bases on
the user trials and mock-ups. (Current plan is to have the inter work
on this next summer)
3 - Backend is hard, different possibility depending on how developer
time we have. Following are different options that need to be
discussed before moving forward.
1 - Focus on the current pain point and fix them. Hope is to improve
the current application performance
2 - Modify the back end so that it serves only JSON, consumed by the
new Front end
3 - Use the current code base and move it to Django
4 - Restart from scratch
5 - Move away from the message bus driven actions to award badges to
make the application
more generic and attract other community than Fedora.
Feedbacks are welcome, also there is Virtual Hack-fest happening
September 13-15th where it would be good to start coordinating some of
the backend work.
Thanks all
Following are the minutes:
## Attendees
Clément
Michal
Marie
Sayan
pingou
## Notes
* Frontend will be rewritten
* Backend ? is this worth the rewrite ?
* Pyramid as a framework does not have a strong community and adoption
* Django is the industry standard for Python based web application
* Current application is very slow
* Badges image are big
* Needs to download a lot of data to load a page
* If rewrite this need to be kept in mind
* Python2 dependencies not maintained
* Rewrite could also be porting current app to Django and slim down
the number of pages/feature
* maybe 1 user page and 1 admin page.
* Start with the frontend --using a JS framework and let the backend
with pyramid but just serve JSON instead of templates.
* Refactoring Backend is difficult --> need experienced developer
there and a specification
* Focusing in on the pain point first will give improvement performance
* Moving off the message driven backend would be good in order to make
the application more generic and not only Fedora centric.
* Potential to get more contributors from other communities.
* Virtual Hackfest - September 13-15th
* Idea to sit down and look at the technical pain point. Slow
Requests, Exception in the consumer etc
* Write these down and come up with a plan to improve these.
4 years, 8 months