= Progress call: 17:00 UTC =

 * Stable images & release announcement (jvalleroy)
   * http://ftp.freedombox.org/pub/freedombox/stable-2017.06/
   * RPi image build problem https://github.com/freedombox/freedom-maker/issues/107
   * RPi2 random MAC issue https://github.com/freedombox/freedom-maker/issues/108
 * GNU Social update (sunil)
   * ITPs filed for all dependencies
 * Mobile app update (sunil)
   * Issues/tasks: https://github.com/freedombox/android-app/issues
 * Communications & Outreach updates (Danny) -->  email: dah2180 at columbia dot edu
   * User Guides proposals (Danny)
     * What the technology is
     * The context in which to use it
     * Proposed List of User Guides (Danny)
       * 1. Browse the net privately and freely
         * a) Private browsing with no browser data collected and stored and no tracking (Tor, Dynamic DNS, !PageKite)
         * b) Ad-free clean browsing (Privoxy)
         * c) Network neutrality protection: If your ISP starts limiting or interfering with your access to services in the Net, your Freedom Box can communicate with your friends to detect and route traffic around the limitations. Network censorship is automatically routed around, for your friends in societies with oppressive national firewalls, or for you
       * 2. Communicate securely
         * a) Email that protects privacy and resists eavesdropping (!RoundCube)
         * b) Emergency communication network in times of crisis
         * c) Medium for anonymous conversation between whistleblowers and media
         * d) Mesh routing to talk to other boxes
         * e) Private voice communications (Mumble VoIP)
       * 3. Organize activism safely
         * a) A publishing platform that resists oppression and censorship (Ikiwiki)
         * b) Mesh routing when the Internet is shut down
         * c) Safe social networking, in which, without losing touch with any of your friends, you replace Facebook, Flickr, Twitter and other centralized services with privacy-respecting federated services
     * Feedback: 
       * Concentrate on the synergy of how things work together instead of describing each piece of software individually. 
       * We can replace the entire cloud service
       * Use cases are still interesting to the end users
       * There may be a danger of creating high expectations with the guide and then having the users have bad experiences. If one configuration error makes a service fall, then users may not come back. 
       * If we get a new contributor, then we can assist him/her in getting an idea of the format and depth of a how-to guide
     * How to access to freedombox.org for content posting (Danny)
       * Documentation at the Git repository https://github.com/freedombox/freedombox.org
     * Video development (Danny)
       * 3 minute promotional video that shows the !FreedomBox in action 
       * could be good content for the main landing page
     * Idea: How to outreach to developers
     * Idea: How-to guide for set-up of a !FreedomBox
       * This is a first important step and can be a big barrier for new users
       * there is potentially one new researcher who is working on how-to guide (Danny)
     * Idea: Usability study to engage new users in the product and see where the problems arise
       * Tool for surveying users: https://www.limesurvey.org/
       * Questions: 
         * What do you use !FreedomBox for? 
         * What are the technical details of a !FreedomBox?
 * Information on community networks https://code.swecha.org/freedombox/networks/wikis/home