Difference between revisions of "Main Page"
(Add note about antispam service) |
(Weekly calls) |
||
Line 73: | Line 73: | ||
* Fediverse (Mastodon, GNU Social, Hubzilla, etc.): [https://kosmos.social/@kosmos kosmos@kosmos.social] | * Fediverse (Mastodon, GNU Social, Hubzilla, etc.): [https://kosmos.social/@kosmos kosmos@kosmos.social] | ||
* Twitter: [https://twitter.com/KosmosHQ @KosmosHQ] | * Twitter: [https://twitter.com/KosmosHQ @KosmosHQ] | ||
+ | |||
+ | === Public weekly calls === | ||
+ | |||
+ | New: weekly calls to sync our team (and whoever else is interested) on development progress. Every Wednesday, 9am UTC/GMT, in [https://zoom.us/j/414901303 https://zoom.us/j/414901303]. | ||
+ | |||
+ | '''09:00''' Kosmos Chat<br> | ||
+ | '''09:10''' Kosmos Infra<br> | ||
+ | '''09:20''' Kredits<br> | ||
== Events == | == Events == |
Revision as of 03:50, 13 March 2019
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 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.
Contents
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).
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 IRC 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
- Chat
- Incoming notifications / (web)hooks
- Audio/video communication
- File sharing
- Migration from existing systems
- Guest communication
- Themes
- Offline support
- Onboarding / Setup
- Design
- Multi-backend support
- Accessibility
- Encryption
Development Roadmap
See Roadmap.
Kredits
See Kredits.
Notes
See Notes.
Community / Getting in touch / Getting involved
Code
Chat
- IRC: #kosmos and #kosmos-dev on Freenode
- XMPP: kosmos, kosmos-dev, and kredits on chat.kosmos.org
Social
- Fediverse (Mastodon, GNU Social, Hubzilla, etc.): kosmos@kosmos.social
- Twitter: @KosmosHQ
Public weekly calls
New: weekly calls to sync our team (and whoever else is interested) on development progress. Every Wednesday, 9am UTC/GMT, in https://zoom.us/j/414901303.
09:00 Kosmos Chat
09:10 Kosmos Infra
09:20 Kredits
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
- Kosmos Mini Hack Days (March 5-11, 2019, Chiang Saen, Thailand)
- Chaos Communication Camp 2019 (August 21-25, 2019, Germany)
Past
- Hacker Beach #7 - Jan 2019, Coron, Philippines
- HCPP - Oct 2018, Prague (lio17, raucao)
- Kosmos Hackdays 2018/1 — Tuscany (Italy) in April (~11-end)
- Hacker Beach #6 (January 2018, Petite Côte, Sénégal)
- SHA2017 (August 4-8, 2017, Zeewolde, NL)
- Kosmos Hackdays 2017/1 (May 2-5, 2017 | during WWWTF Berlin)