[p2pu-dev] notes tech call April 11, 2012

Zuzel VP zuzel at p2pu.org
Wed Apr 11 15:30:56 UTC 2012


 April 11


   - Status Report:


   - Migration to django 1.4 still on progress


   - Setup of google analytics, adwords' conversion tracking moved to next
   release


   - https configured on production


   - Background on using https for entire session after log-in:


   - https://docs.djangoproject.com/en/dev/topics/security/#ssl-https


   - In the process of detecting and fixing pages that import non-https
   resources (images, css, js, ...)


   - There was a small problem with missing avatars but fixed


   - Needed to change to https://secure.gravatar...


   - This causes the https:// on the url bar of chrome to be displayed in
   red or with an exclamation mark


   - Problem with embed.ly - if you embed content through embedly the
   browser shows that there are non-safe resources on the page


   - no solution yet for pages with embed.ly resources because even if the
   user embeds a video with an https link the code embedly sends has
http://links


   - planning to serve files from old drupal site (e.g., images of courses
   appearing on users profiles) under p2pu.org so they can be included with
   an https:// url


   - todo: automatically redirect admin site to https:// since http:// does
   not allow login


   - some performance improvements rolled out which should improve page
   loading time when posting comments


   - defered a bigger part of the sending and creating of notification
   emails logic to async celery tasks


   - clear improvement


   - OBI integration rolled out


   - Question: What are we doing about the badges that were issued in the
   past?


   - Users can manually send badges into the OBI (from their badges admin
   page) https://p2pu.org/en/profile/edit/badges/


   - Wait until other OBI UI fixes are rolled out - then consider how to
   communicate the feature to our users.


   - TODO: mark/create the badges that are going to be global to all
   challenges (neccesary code is on production)


   - we decided to go with Helpful Feedback in a past tech call


   - http://pad.p2pu.org/p/communitybadges


   - http://p2pu.org/en/badges/helpful-feedback/


   - Need to update description to the one on
   http://pad.p2pu.org/p/communitybadges


   - We need to deside if wave should included or not (see feedback on
   http://help.p2pu.org/discussions/questions/52-what-should-be-done-to-make-someone-my-peer)


   - Next steps:


   - Add the wave badge to Laura's challenge as a quick fix [Zuzel] - then
   consider making wave a global badge separately


   - Philipp to chime in on help discussion


   - Sill on my [Zuzel] TODO list: prepare screencast about lernanta code
   overview


   - Automated tests to be added during this release:


   - Test course, study group creation still works as expected


   - Test new challenge creation page works ok


   - On apps/projects/tests.py and SauceLab tests



   - Status report (Dirk)


   - Busy changing "Introduction to contributing to Lernanta" course to
   challenge


   - Added two optional tasks:


   - Getting to know Python (probably good to add a link to
   https://p2pu.org/en/groups/?all_languages=on&tag=python)


   - Getting to know Django


   - Considering adding a task for "Basic linux usage"?


   - Maybe Cheat Sheet style?


   - Rename challenge to "Contribute to Lernanta" - what about "Learn to
   hack the P2PU code"?


   - Merged support for multiple reviews/awards for badges like Supper
   Blogger given one submission


   - multiple reviews, but one badge


   - Philipps feedback: check if it works that way. keep it like that


   - Maybe add tests


   - allow people to add "evidence" to a badge, but keep one badge for now
   (not multiple badges for the same submission)


   - Still busy familiarising myself with the codebase


   - Some random notes: http://pad.p2pu.org/p/dirk_thoughts (still have to
   add a few from my paper notebook)


   - Added comments there


   - Q: what is the state of badges on the live site?


   - Only for certain courses or for any course someone creates


   - Only certain challenges (badge creation is still manual and UI changes
   in courses are needed to display badges there)


   - Q: Do we have any wireframes/(dont know what to call it) showing how
   site navigation should work?


   - Almost like a user story: home -> badges -> view submissions -> review
   appropriate -> award badges?


   - nope


   - may be useful, with the badges I'm not completely certain how someone
   should work with them?


   - Or maybe something showing how the site comes together (like a graph
   showing possible navigation?)


   - where is the mockups Chloe left? - see trello board for challenges


   -
   https://trello.com/board/challenge-development-sprints/4ed8ff4175e6467872117dcc


   - John may have moved some cards into other places when he took over
   "ownership" from Chloe


   - No badge creation on current mockups to create challenges


   - Allowing users to add badges to challenges will be implemented in
   future (as part of our DML work)


   - Next step:


   - Dirk to review challenge creation trello boards (ask John for pointers
   if necessary)


   - Hire learning lead who will "own" badge creation UX


   - http://hastac.org/competitions/winners/peer-2-peer-university-p2pu



   - Badges issuer project


   - Background: openbadge.org (OBI)


   - P2PU won DML competition grant to build a badge issuer platform


   - http://hastac.org/competitions/winners/peer-2-peer-university-p2pu


   - Adaptable, customizable, fully-documented platform


   - Need to confirm how much it is integrated into Lernanta


   - Next steps:


   - Philipp to double-check with DML team to make sure we agree on
   deliverables


   - Zuzel to check with Les Orchard how django apps we are building are
   different - then make recommendation if we should combine core code
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20120411/4bed0fe3/attachment-0001.html>


More information about the p2pu-dev mailing list