Added value for the open source / open data community

Who can work with the code you made? What happens to the data? Who else can benefit, or build later? Through the created Slack channel the communication can continue after osoc20. The current team members are part of this channel and anyone (technical/ non-technical) who is interested in WiseBadges can become a part. In terms of developing, the Github page is open for anyone who feels like contributing.

https://wisebadges.slack.com/home https://github.com/Wise-Badges

Fixes & Bugs

Not any bugs at the moment, if so, these will be mentioned in the Github page.

Future features and ideas

1. Let users make their own badge classes:

• Make the API accept POST requests for making new badge classes
• Add a page to the front-end to allow people to make their own badge class. This could be on the same website or could be a whole other website/project. (There could be the ability to design the images for the badge classes.)

1. The community page could be expanded: either by geographical maps, graphs, … It would also be nice to add to the assertions the tweet / reason why someone got a badge.
2. Now there is only a twitter bot, the ideal would be that people can issue badges through many platforms. If not already done by the open source community, there could be a facebook bot, linkedin bot, .. added.
3. Make a (twitter/facebook/..) button available that developers can just add to their page and it gives a pop-up of issuing a badge (so kind of like the website, but in pop-up version).
4. Possibility to save badges to badgr backpack, or any other way of saving them.
5. When there will be lots of badges / assertions: it would be handy if users could search for badges / assertions or an easy way to navigate through them.
6. Front-end now only shows last 50 assertions (per badge it shows 50, and when selecting "all" it also shows 50), this should make use of the pagination of the API. So there are "next" and "previous" buttons needed to go through the assertions. This can also be integrated with (5.), a search functionality and multiple pages.
7. Right now we're struggling with Twitter: the account giving out the badges sometimes loses its rights to give notifications to recipients. Probably because we're sending out to many tweets. Trying to look for a solution for this problem is also very important.
8. Global styles for frontend: defining our global colors, spacers, and so on to maintain consitency.