Skip to content
This repository has been archived by the owner on Mar 27, 2022. It is now read-only.

Roadmap

Tim Morgan edited this page Apr 9, 2016 · 20 revisions

General Strategy

Thanks for being interested in where we're going. At a 10,000 foot view, here's the broad categories of functionalty that we're going to be looking at:

  1. Social (we've mostly got this, but need some improvements)
  2. Office (people database, attendance/check-in, reporting, giving?)
  3. Engagement (connecting volunteers, organizing leadership communication with congregation)

1. Social

  • Usability Improvements
  • Integration with Twitter and Facebook (at least for login, but maybe more) - [x] Login - [ ] post status updates
  • Check-in
  • Add invite functionality (invite people to join the community)

2. Office

3. Engagement

  • Calendaring (possibly integrate with Google Calendar)
  • Follow-up/Pastoral Care/Shepherding
  • Onboarding/Membership
  • Prayer Event Sign-up (pick a slot for continuous prayer)
  • Book a meeting with someone in the church staff.
  • Ability for admins to pin a news post to the top of the home page.

Other ideas to be considered

  • Feeding the Hungry (Community meals)
  • Manage Post Sunday Content and Engagement (need example)
  • Add the Apocrypha
  • A forum type function (maybe that's just an extension of a group?)
  • Highlight Service Times
  • Statistics Gathering (monitor which events people go to, to see which ones lead to the most conversions, then optimize these)
  • Integration with Planning Center Online (PCO) - http://get.planningcenteronline.com/
  • Multi-Church Collaboration (possibly via sharing one installation, or otherwise connecting churches for communication, event planning, etc.)

Things We Won't Do

  • Sunday Service Management (use something like PlanningCenterOnline.com)
  • Record Service Statistics (eg. for CCLI tracking)
  • Change from the AGPL License.
  • Room/resource reservation.

Caveats

This page is intended to outline a map for future features of OneBody. It is really a scratch page to support dialog about what might be useful to develop in the future, and it does not represent a commitment by anybody to do anything to OneBody, at any time, at all :)