Wojciech Kapcia Application 2020

From XMPP WIKI
Revision as of 15:54, 3 April 2020 by Wojtek (talk | contribs) (Created page with "'''Name''': Wojciech Kapcia <br /> '''e-mail/JID''': wojtek@tigase.org <br /> '''Location''': Poland/Chile <br /> == History == My journey with XMPP started in mid 2000s whi...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Name: Wojciech Kapcia
e-mail/JID: wojtek@tigase.org
Location: Poland/Chile

History

My journey with XMPP started in mid 2000s while looking for alternatives to limited, proprietary solutions available at that time. I stumbled against Jabber/XMPP and after some digging quickly figured out that it was what I was looking for - open, extensible and interoperable. At the beginning I mostly concentrated on user side, promotion of protocol wherever I could as well as providing helping hand to whomever needed such. In 2010 I started working for Tigase. We are now in 2020 and it seems that proprietary walled garden once again made communication difficult and it was never more important to support open communication!

Last year in Tigase/XMPP:

  • promoting Tigase and XMPP wherever possible
  • extensive work on compatibility of Tigase XMPP Server (s2s and clients ecosystem)
  • administration of tigase.im/sure.im servers

XMPP Related Activities

Most of my current activities revolve mostly around server side Tigase:

  • finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability,
  • building, packaging, releasing; nightly builds,
  • promotion and help with XMPP.

Plans for a future

I want to work to improve Tigase XMPP Server compatibility with the most recent extensions and work on aligning Tigase projects with Modern XMPP. It's also essential to make deploying XMPP-based solution as easy as possible and this will be main goal for this year.

XMPP - Why I like it

I like XMPP because of it's openness and flexibility which allows freely choose from abundance of software (both server as well as client) and services without sacrificing interoperability. It also allows contributing back.

I do hope and do my best to convince people to switch from other, closed solutions to XMPP.