[p2pu-dev] Tech call notes 2013-05-23

[Dirk Uys]

***Progress*

   - Sent email to previous users of Python Mooc
      - had a small problem (100 users * 25 emails = %$#%)
   - User on badges can delete badge that does not have any projects
   - Other Python MOOC updates?
      - Improved the unsubscribe feature (previously, users would
      unsubscribe from mailgun, but would still be in our local DB / now
      unsubscribes sync both)
   - Discourse
      - http://thepeople.p2pu.org (please update DNS)
   - Course UX improvements
      - Call with School of Open to go through course organizer feedback
      - See email from Jane on community list with (excellent) summary

*Priorities*

   - Upgrading p2pu.org linode DU to let community know about planned
   upgrade and 3h downtime on Monday the 27th
   - Plan implementation of feedback from SOO & SOE
   - Confirm that single signon with disqus is possible (for free accounts)
   - Grouping users for the Python MOOC. We need to talk with June about
   the grouping
   - Next steps: DU to send a email to community list, June and VMG about
      grouping
   - Badges partner badge implementation
      - there was a wireframe presented today to Vanessa and Dirk
   - Get Discourse hosting set-up
      - DNS -> http://thepeople.p2pu.org
      - [Optional] Set-up P2PU OAuth
      - Heroku (explore DB size first, evaluate if move to Digital Ocean or
      AWS makes sense now)
   - Course UX
      - Next step: DU to schedule and prioritize the work (tentatively week
      after June 1st) and inform SOO + community

*Problems*

   - Email hickup (how can we avoid these in future, can we?)
      - For things with high risk, use a second set of eyes
   - Better deploy process (Staging servers are needed)
      - Let's discuss how much time (cost?) is required to do this, before
      we set it up

*Process*

   - How can we improve tech updates in the community call? (People don't
   know what is cooking)
   - Lets try markdown format for tech call notes so that we can copy and
   paste the notes in discourse
   - doing some research about fabric for the Badges testing and deployment
      - we could use it instead of ansible (ansible misses a lot of stuff
      for real production)
      - EP havs some experiences with it, has been using it before
      - It would not be time consuming as much bcs EP have experience
   - Deployment process (too complicated?)
      - you have to be sudo user to pull
      - after you have to restart apache manualy
      - what happens if migration breaks
      - all of those are very dangerous operations to do them without
      testing on staging servers first
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20130524/b0489330/attachment.html>