Difference between revisions of "Main Page"

From Kosmos Wiki
Jump to navigation Jump to search
m
Line 1: Line 1:
−
'''Kosmos''' (ex ''Codename 67P'') is a team communication application based exclusively on open protocols, standards, APIs, and data formats. All of its components are free software, published under open-source licenses. User-facing programs are built upon the [https://platform.html5.org/ Web Platform], communicating with server components via HTTP and WebSockets.
+
'''Kosmos Chat''' (ex ''Codename 67P'') is a team communication application based exclusively on open protocols, standards, APIs, and data formats. All of its components are free software, published under open-source licenses. User-facing programs are built upon the [https://platform.html5.org/ Web Platform], communicating with server components via HTTP and WebSockets.
  
 
''Please note: this wiki is protected by an anti-spam service, which can be a bit overzealous in blocking registrations and edits. If your signup or edit is blocked, please contact us and we'll get you sorted! See below for various contact options.''
 
''Please note: this wiki is protected by an anti-spam service, which can be a bit overzealous in blocking registrations and edits. If your signup or edit is blocked, please contact us and we'll get you sorted! See below for various contact options.''

Revision as of 18:00, 3 September 2019

Kosmos Chat (ex Codename 67P) is a team communication application based exclusively on open protocols, standards, APIs, and data formats. All of its components are free software, published under open-source licenses. User-facing programs are built upon the Web Platform, communicating with server components via HTTP and WebSockets.

Please note: this wiki is protected by an anti-spam service, which can be a bit overzealous in blocking registrations and edits. If your signup or edit is blocked, please contact us and we'll get you sorted! See below for various contact options.

Building blocks

Kosmos consists of several components, all of which can be configured separately, and thus be either hosted by a provider or self-hosted by the user/organization. These are:

  • Sockethub server for facilitating client/server communication between the Web client and the multiple protocols/backends/APIs it needs to talk to (e.g. IRC, SMTP, OStatus, Twitter, GitHub, SMS gateways, TURN etc.)
  • RemoteStorage server for storing all user data in a user-defined/controlled storage backend
  • IRC or XMPP server for private communication servers (not needed for personal usage on public servers)
  • Web client, written in Ember.js, using sockethub-client.js and remoteStorage.js
  • Daemon for logging channels, handling incoming notifications (e.g. Webhooks), sending push notifications (e.g. for offline mentions). Functionality is currently being prototyped with Hubot scripts (running on botka and hal8000).

Technical overview

Goals

  • Provide users/organizations/businesses with a modern, full-featured team communication solution, which is easy to set up and use
  • Eventually provide a fully hosted, one-click-setup solution for private team communication (keeping the possibility to exchange any component at will, e.g. storing all data on user-controlled remoteStorage servers
  • Use common, open, documented data formats for storing all data, thus making it possible to use/manage/input stored data from other apps (no matter if new or existing). This is where the remoteStorage protocol really shines compared to all other personal data storage protocols made for the Web.
  • Make it possible for users to be part of and use both public and private channels/spaces/servers at the same time and in the same window (no more Campfire/HipChat/Slack for work and clients, and IRC only for open-source and hobby, all in different apps)
  • Always keep the whole application in a state that can be deployed by anyone (with the necessary skills) who wishes to self-host the whole system. That explicitly includes documentation for doing so.
  • Enable *anyone* to join the conversation on public servers by offering a great Web client, making it easy to connect, register nicks, auto-log and replay messages while away — all the nitty-gritty details that even software developers struggle with these days
  • Be backwards-compatible to plain text chat/clients
  • Have an excellent mobile client (or multiple)
  • Make use of the latest Web Platform standards, not caring about backwards-compatibility in Web runtimes (much). Kosmos is a modern Web application, and people not running modern Web runtimes can use plain IRC clients.

We also summarized our goals for a grant application with the Prototype Fund in German language on 31/03/2017: see Prototype Fund

Features

Development Roadmap

See Roadmap.

Kredits

See Kredits.

Notes

See Notes.

Community / Getting in touch / Getting involved

Code

Chat

Social

Weekly conference calls

New: weekly calls to sync our team (and whoever else is interested) on development progress. Every Wednesday, 10am UTC/GMT, in https://zoom.us/j/414901303. Usually 30 to 60 minutes long.

Topics:

  • Kosmos Chat
  • Kosmos Kredits
  • Kosmos Infra/Ops

Events

This is a list of events with Kosmos activities going on. Please add more, in case you're working on something related somewhere.

Upcoming

Past

Code of Conduct

Contributor Code of Conduct

Retrieved from "https://wiki.kosmos.org/index.php?title=Main_Page&oldid=574"