Wiki

• FrontPage
• RecentChanges
• FindPage
• HelpContents
• 2015.0524

May 24th, 2015

These are the notes for the May 24, 2015 call, originally recorded at: https://pad.riseup.net/p/dokIP2GeA1KCG

Previous Actions

• [ ] Release 0.4
  • [ ] Releases of Plinth and freedombox-setup (James)
    • Updates made to alioth.
    • Sunil reviewed updates, proposed packages.
    • Waiting on DM/DD to upload.
    • Sunil still going through DM process.
    • Should be good to go, no blockers.
  • [ ] Building images and release-testing (Sunil)
    • Blocked by package uploads.
    • Can't test cubietruck or dreamplug.
    • Two types of release testing:
      • 1. Thorough testing: stress-testing every available option.
      • 2. Basic sanity testing: does it boot? Can I access it?

  • [ ] Write release notes & announce (Sunil)

    • waiting on testing
• [X] Sumbit patch for network-manager with python3-gi and libnm-glib (Sunil)

  • Added Networks module

• [X] Consider python3-gi with libnm-glib and decide (James)

Agenda

0.4 release status

• waiting on announcement
  • waiting on release testing
    • waiting on plinth, fbx-setup uploads

Recent progress

• implementing the Plinth landing page and dashboard
  • overview of installed apps, enable/disable those apps.
  • links to each app/service
  • Sunil:
    • make the default Plinth page a service overview/landing page.
    • anonymous users should have read-only access if configured in LDAP.
    • firewall and other low-level system services should not be directly accessible from Plinth.
    • the landing page should be reserved for daily-use services (blogging, wiki).
    • also list non-installed apps: install them when user selects them.
    • if service is web-accessible, connect user directly to it. otherwise, should show info on how to access.
    • should alert user to required user-configuration or user-attention ("Service disabled until you set a password.")
    • Overview of purpose:
      • 1. Connect user to service (or show connection info).
      • 2. Install/Enable/Disable services.
      • 3. Notify user of required alerts: also G/Y/R overall box-health status.
    • The better built the applications are, the more the system can use other more-basic services to do management.
  • fonfon:
    • Don't show not-installed applications/services, as we have a whole bunch and will have more.
    • Sort-by-usage (Sunil), add filters to show/hide not-installed?
    • Start small and add features over time.
  • Nick:
    • There're a few requirements for a well-configured services.
      • LDAP
      • (others)
    • The system is slowly working its way toward LDAP and freeing up Plinth/home for higher-level purposes.
  • A couple different pull requests:

    • https://github.com/freedombox/Plinth/pull/20

    • https://github.com/freedombox/Plinth/issues/71

    • https://github.com/freedombox/Plinth/issues/72

    • https://github.com/freedombox/Plinth/issues/109

Low-Hanging Fruit

• See "Leaving the Cloud Page."
• TTRSS
  • Already packaged for Debian.
  • Google Reader Replacement
• Asterisk
  • Already packaged.
  • SIP Server, very serious.
  • Could have these meetings via FBX?
• Community Cube
  • LAFS?
  • Similar Project to FBX

• ?RoundCube

  • Webmail, can use third-party services, don't need to include a full mail stack.
• Gnu Social
• Gnu Media Goblin
  • Under Packaging
  • Talk to Chris Webber.
• Stuff needs polish.

Add basic router capabilities to FBX

• Network manager (thanks, James/Sunil!) makes this easy.
• James adding firewall zones.

Django testing framework added to fbx-setup

• Can do lots of testing during development, not deployment.
  • Provide link to travis-ci page during development.
    • Add travis last-build-status link-button to Github FBX readme.
• User should be able to see Plinth status report though.

How does the box monitor its own health?

• Each service should have a status report that reports whether the service is configured, working, and available.

bobg: New Service: Coveralls

• coveralls.io: Publishes unit-test code coverage.
• coveralls runs tests for you and recording status-reports over time.
• can they pick up the HTML Travis is currently generating?

Actions

• [ ] Complete Roadmap Draft (Nick)
• [X] Update Call time to 6 PM GMT (Nick)
• [ ] Upload plinth and fbx-setup packages (Nick).
• [ ] Release-test Dreamplug (Nick)
• [ ] Release-test cubietruck (fonfon)
• [ ] Coordinate GMG call, when necessary (Nick)
• [ ] Make PGP-Client Certificates easy (Marc, Nick)
• [ ] Add Travis-CI Last-Build-Status button to FBX Readme (bobg)
• [ ] Investigate Coveralls (bobg)