[p2pu-dev] Notes tech call 2012-02-29

[zuzel.vp]

 * Status of etherpad migration preparation for this Friday
   * email sent to the community mailing list
   * http://etherpad.p2pu.org will replace http://pad.p2pu.org (i.e.,
pad.p2pu.org will serve etherpad litle)
   * etherpad.p2pu.org/tech redirects to etherpad.p2pu.org/p/tech so
no links get broken (without breaking other url patterns used by
etherpad little)
     * the /p/ part is hardcoded on several places of the code so
adding a bit of javascript code to etherpad-litle/node/server.js was a
cleanest solution i found
   * etherpad little does not has an admin dashboard so at the moment
api calls need to be used for most admin stuff including creating
groups, creating pads in a group, setting password and visibility of
groups pads (https://github.com/Pita/etherpad-lite/wiki/HTTP-API)
     * if the creation of password protected pads is only going to
happen from time to time I can do it manually
       * test at http://etherpad.p2pu.org/g.G9I8LjqVPdvZ1fPl$protected
       * no email is involved in the process
         * also as far as i have discovered etherpad little only sends
email when safeRun.sh restarts the etherpad and 'mail -s' is used for
this (not available at the dev server at the moment since we have not
installed postfix or exim or ...)
   * padsearch.p2pu.org/etherpadsearch.php (searching pads on
etherpadlittle) will replace padsearch.p2pu.org (searching pads on the
current etherpad) when the migration occurs
   * Replaced favicon.ico
   * TODO: etherpad embeds?
     * https://github.com/Pita/etherpad-lite/wiki/Embed-Parameters
     * https://github.com/johnyma22/etherpad-lite-jquery-plugin
     * https://github.com/devjones/PyEtherpadLite
     * note that there is nothing apart from the pad itself on
http://etherpad.p2pu.org/p/testing so it can be pretty much embedded
as it is
       * possible easy contribution: enable etherpad little embed's on tasks
 * Hiring report
 * Learn page
   * Zuzel implementing mockup
   * We've been working on the design for this page, we're basically
going to stick to the wireframe that we proposed before.
       * Spending some time on three different types of pages at P2PU
         * Application Pages
           * Learn, Contribute, Profile
           * The style is a smaller functional header that gets out of your way
         * Landing Pages
           * Staff, Jobs, About, Get Involved, etc
           * The style is a large image heavy header and a simple
message with some additional static content
         * External Pages
           * blog, help
           * Inconsistent styles (for now) but would like to bring
these closer to the p2pu look in the future
 * Community Badge Survey : send to all users, any other items to add?
   * who is going to help with the text/content of the email (maybe
cc. alison and bekka in case there is anything else to share in that
email)
     * links to blog posts
     * categories of newsletter
     * the newsletter goes out every week -- bekka sends it (through sendgrid?)
 * Hackasaurus: when should we expect a pick in visits to those pages?
   * I was going through the google analytics yesterday
   * We don't know who will be coming to the site (small launch
followed by bigger launch?)
 * Ideas for organizing content + teams (Cohorts, playlists)
   * cohorts (team is a better name): if there is signup, dates, ...
     * you have 3 options : open team, by invitation, by application?
   * challenges (can we name it course?): content
   * Lets refine those wireframes add this idea of "teams">> and send
them to list?
 * Since we have time, do you want to review my ideas for stealth
community badges? http://pad.p2pu.org/communitybadges