Skip to content

Content Plan

This document provides details about the different channels that we have within the OpenWallet Foundation and what we expect each to be used for.





  • Real-Time Communication: Chat services facilitate real-time, synchronous communication among users. Messages are sent and received instantly, enabling quick exchanges and conversations.
  • Interactive Collaboration: Chat services are well-suited for interactive collaboration, allowing users to engage in live discussions, share files, collaborate on documents, and even conduct video calls in some cases.

Staff: Administers, creates new channels, and moderates

Community: Sends messages and monitors

Mailing Lists

  • Asynchronous Communication: Mailing lists are primarily used for asynchronous communication. Users send messages to a central email address, which are then distributed to all subscribers. Subscribers can read and respond to messages at their convenience.
  • Broadcasting Information: Mailing lists are effective for broadcasting information to a group of subscribers. They are commonly used for announcements, discussions, and sharing updates within a community or organization.
  • Archiving: Mailing lists typically archive messages, allowing subscribers to access past discussions and reference previous communications. This archival feature can be valuable for maintaining a record of conversations and facilitating knowledge sharing.

Staff: Administers, creates new lists, and moderates

Community: Sends messages and monitors


  • Project-Based Source Code and User Documentation: Any source code for projects should utilize GitHub. GitHub pages should be used for hosting user documentation.
  • TAC Governance Documentation and Other Relevant Information: Governance documentation for the TAC must be version controlled. As such, GitHub is the appropriate place to store this information in addition to other relevant TAC materials. Currently is generated from markdown files in GitHub.
  • SIG or Task Force Deliverables: A separate repo can be set up for SIGs and Task Forces so that they can have versioned control support for their deliverables.

Staff: Administers, creates new repos and teams

Maintainers: Reviews and handles issues and pull requests

Community: Use source,create issues, fork code, and contribute


  • Blogs
  • Announcements
  • Native content
  • Events and Conferences

Staff: Administers and determines contents

Community: Visit and contribute blog posts


  • Project Meeting Minutes
  • SIG Meeting Minutes
  • Task Force Meeting Minutes
  • Collaborative Editing

Staff: Administers and creates new spaces

Community: Creates and edits pages

LFX Meetings (Zoom)

  • Project, SIG, and TAC meetings: All project, SIG, and TAC meetings must be held using LFX meetings. This ensures that a recording of the meeting is captured and available for people to catch up on what they may have missed. Send an email to to get your meetings scheduled.

Staff: Administers and creates new meetings

Community: Attends meetings and listen to recordings


  • Community meeting recordings
  • Webinar recordings
  • Event recordings

Staff: Administers and adds videos and playlists

Community: Watch videos

Social Media

  • Posts about activities and events that the community may be interested in
  • Posts to announce new projects, SIGs, Task Forces, blog posts

Staff: Administers and posts content

Community: Reads content

Content Plan Mindmap