[p2pu-dev] Notes tech call 2012-03-14

Wed Mar 14 17:25:15 UTC 2012

Mar 14

   - Status OBI
      - Chloe: looks like there are a lot of updated stuff on
      http://openbadges.org/ and we should be able to move ahead with the
      new obi integration ;)
      - beta.openbadges.org
      - https://github.com/mozilla/openbadges/wiki/Issuer-API
      - Updating https://github.com/zuzelvp/django-obi to support the new
      obi api.
      -
      https://a248.e.akamai.net/assets.github.com/img/94b8e6833e4062c1488e0406d0c3c1942c65ff6b/687474703a2f2f6661726d372e7374617469632e666c69636b722e636f6d2f363036332f363034393439393934395f353937616236333037345f7a2e6a7067
      - >> i think it should be on the profile in future releases, with
      some explanation of what OBI is.
      - http://beta.openbadges.org/share/90ec681ab5160e23dfc2925f75d76eff
   - Community focus
      - What's the best way of doing this? Google group embed?example of
      how it looks?
      - Community page
         - Show RSS feed of latest topics from community list
         - Link to subscribe
         - Join Mozilla -> Join (the) P2PU (community)
         - *TODO:* John to take forward
      - Challenge set metrics - should we show "badges awarded" or "badges
   that exist"?
      - Badges awarded is a "stat", Badges available is a "characteristic"
      - >idea: stat=badges awarded i.e. 1025 / under the stats there is a
      box with the visual of badges
      - Ensure that users know they can earn or not earn badges in a
      particular challenge (maybe use a "badges available" icon - mouse over
      shows you the badges you can earn)
      - Number = skill badges in the challenge +
      - Update the label? -> Badges Awarded (Yes - but that means we have
      to update the logic as well / what's the number we display?) -> or badges
      available don't update logic :) Let's update the logic (it's a "stat")
      - # the badge awards to the participants of this challenges
      restricted to badge awards of the badges of the challenge
      - ana A B*3
      - john C D
      - I think limit to skill badges for now (those are most closely
      associated with a particular challenge) otherwise fine
      - format for numbers 0-999 in digits 1,000 - 10,000 == 1k - 10k
      - *TODO:*
         - Update label of challenge set box -> "Badges awarded"
         - Update logic -> # of skill badges awarded to users of the
         challenge (challenge set)
         - Card - > https://trello.com/c/Fz9eklWv
         -
         https://trello.com/board/challenge-fixes-1-1/4ed8ff4175e6467872117dcc
      - Adding 202 challenges to webcraft home page and feature done
      - Is there no way to add individual groups that are featured on the
      webcraft home page? Yes
      - We have two more awesome 202 challenges that are almost done
      - *TODO:*
         - Zuzel will add a few courses to webcraft home page as featured
         courses
            - Need links of the courses that should be featured.
         - Chloe to tell Jessy's API course ( programming-101) - done (
         emailed Zuzel)
         - http://p2pu.org/en/groups/programming-101/
         - 2 courses made by John's friends
      - P2PU API status
      - Documentation:
      https://github.com/p2pu/lernanta/wiki/API-development-process
      - Demo: http://alpha.p2pu.org:8094/en/api/v1/?format=json
      - Trello:
      https://trello.com/board/p2pu-api-process/4f4fb70ee4ba0e4f098263e9
      - Thoughts about users info available through api
         - http://alpha.p2pu.org:8094/en/api/v1/userprofile/?format=json
         - we will only show information that is already publicly available
         to any visitor to p2pu.org
         - is an option for turning on/off some of the api resources needed?
         - So no problem.
      - Merge current version on next release?
      - *TODO*:
         - Look into setting up a API subdomain (Paul may be able to help)
         - Add cards to the trello board
      - *Community Badges for April 11:*
      - We need to:
         - Collect feedback: done, send survey, but only 12 answers -
         taking into consideration but we make final call.
         - (1) Decide on 3-4 badges to roll out across community.
            - Which badges?
               - Chloe and Philipp to discuss and decide based on
               experience so far, survey, etc.
               - May focus on "role" badges and those awarded by community
               (not automatic) for now (taking into account the
discussion across blogs at
               the moment)
            - (2) Rebrand badges
            - do we have any work going on this? there's a card on the
            design board based on some discsussions with chloe before ->
            https://trello.com/c/k6dYn1Sr
            - i.e. Change images so they don't say mozilla?yes + redesign
            to fit P2PU branding and not Mozilla branding
         - (3) UX improvements to make it easier to get community badges,
         need FB
            - Discussions >
            https://gomockingbird.com/mockingbird/#m5ase18/07SBGq <
            - How does it look when writing a comment >
            https://gomockingbird.com/mockingbird/#m5ase18/85m4ca <
            - Add into project pipeline
         - TODO:
            - Philipp and Chloe to do (1) and share with community
            - Chloe +Aleks? to do (2)
            - Chloe to use input from discussion and get on (3)
         - Jobs / Staff page on a branch?
      - How can we add community members (less separation between
      team/community) to this in the future?
      - jobs page already lists volunteer positions, staff page is about
      staff. we could include people with prominent contributions that have
      committed to the project as volunteers and possible change the
name of the
      page from "staff" to "team"
      - TODO: zuzel to move code to a branch so John can make changes
   - Bugs / Small tasks on development board
      - How do you want us to use this?
      - This is a place for dev tasks that aren't part of a project with
      it's own board. Some big projects warrant their own board, but not all.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20120314/1b6283e2/attachment.html>