Difference between revisions of "Daniel Brötzmann Application 2022"

From XMPP WIKI
Jump to navigation Jump to search
(Create application page for 2022)
 
(Update with providers.xmpp.net)
Line 7: Line 7:
* '''E-Mail:''' daniel.broetzmann [ät] posteo [dot] de
* '''E-Mail:''' daniel.broetzmann [ät] posteo [dot] de
* '''GitHub:''' [https://github.com/wurstsalat3000 wurstsalat3000]
* '''GitHub:''' [https://github.com/wurstsalat3000 wurstsalat3000]
* '''Projects:''' [https://gajim.org Gajim], [https://xmpp.org xmpp.org]
* '''Projects:''' [https://gajim.org Gajim], [https://xmpp.org xmpp.org], [https://providers.xmpp.net providers.xmpp.net]


== About Me ==
== About Me ==
Line 19: Line 19:
Giving people the ability to communicate freely and in a decentralized way sounds like a good idea to me. But there have to be good XMPP chat clients in order to be able to compete with proprietary chat clients. My main goal in contributing to Gajim is to make it easier to use. The client has been around since 2004, and it shows. In the past years, I helped redesigning various areas, including the most critical bit for first time users: account creation. At the moment, I'm involved in rewriting Gajim's core features, which is really exciting for me, looking back at where I started.
Giving people the ability to communicate freely and in a decentralized way sounds like a good idea to me. But there have to be good XMPP chat clients in order to be able to compete with proprietary chat clients. My main goal in contributing to Gajim is to make it easier to use. The client has been around since 2004, and it shows. In the past years, I helped redesigning various areas, including the most critical bit for first time users: account creation. At the moment, I'm involved in rewriting Gajim's core features, which is really exciting for me, looking back at where I started.


Having good clients is step one, step two is promoting them. In order to provide new users with an overview of available clients in the XMPP ecosystem, I believe using Compliance Suites and establishing XMPP DOAP are the way to go. On the other hand, users have to make a decision about the service provider they want to use. [https://invent.kde.org/melvo/xmpp-providers XMPP Providers] started to gather infos about various providers, offering a machine-readable file for XMPP clients to use. In order to give a better overview and to raise visibility, a user-friendly website is planned. This is what I want to work on in the future.
Having good clients is step one, step two is promoting them. In order to provide new users with an overview of available clients in the XMPP ecosystem, I believe using Compliance Suites and establishing [https://xmpp.org/extensions/xep-0453.html XMPP DOAP] are the way to go. On the other hand, users have to make a decision about the service provider they want to use. [https://invent.kde.org/melvo/xmpp-providers XMPP Providers] started to gather infos about various providers, offering a machine-readable file for XMPP clients to use. In order to give a better overview and to raise visibility, we launched a user-friendly website at [https://providers.xmpp.net/ providers.xmpp.net]. This is what I want to work on in the future.


== Current projects ==
== Current projects ==
Line 28: Line 28:
* Author of [https://gajim.org gajim.org] and monthly [https://gajim.org/post Development News]
* Author of [https://gajim.org gajim.org] and monthly [https://gajim.org/post Development News]
* [https://xmpp.org xmpp.org] (website maintenance since 2021)
* [https://xmpp.org xmpp.org] (website maintenance since 2021)
* [https://providers.xmpp.net/ providers.xmpp.net] (website maintenance since 2022)
* [https://xmpp.org/newsletter.html XMPP Newsletter] (contributor since 2019)
* [https://xmpp.org/newsletter.html XMPP Newsletter] (contributor since 2019)
* [https://github.com/pulkomandy/xmpp-doap XMPP DOAP] (Descpripton of a Project) (contributor)
* [https://github.com/pulkomandy/xmpp-doap XMPP DOAP] (Descpripton of a Project) (contributor)
* Personal chat bot based on SliXMPP (development)
* Personal chat bot based on SliXMPP (development)
* Various other XMPP projects
* Various other XMPP projects

Revision as of 08:53, 14 April 2022

Summary

About Me

I'm a PhD student at University of Oldenburg. My research topics include Dragonflies and their habitat use, sphagnum farming, and landscape fragmentation. This has nothing to do with XMPP, but it's what I do. I have studied Environmental Sciences and Landscape Ecology, and I've always been a computer enthusiast. For my bachelor's thesis, I had the opportunity to combine both topics. I developed an Android App which helps users to determine certain insect species. So much about my background.

In search of an alternative solution for proprietary chat apps, I found XMPP and started to look at various clients. Gajim caught my interest, because it's available on both Linux and Windows, thus enabling most of my friends to use it on their computers. I started helping the project by contributing translations, small fixes, and by taking care of Gajim's issue tracker. Being written in Python, it promised an easy entry into client development, which it was. Thanks to patient and helpful maintainers, I was able to learn many things from this project (git, python, and much more).

Motivation

Giving people the ability to communicate freely and in a decentralized way sounds like a good idea to me. But there have to be good XMPP chat clients in order to be able to compete with proprietary chat clients. My main goal in contributing to Gajim is to make it easier to use. The client has been around since 2004, and it shows. In the past years, I helped redesigning various areas, including the most critical bit for first time users: account creation. At the moment, I'm involved in rewriting Gajim's core features, which is really exciting for me, looking back at where I started.

Having good clients is step one, step two is promoting them. In order to provide new users with an overview of available clients in the XMPP ecosystem, I believe using Compliance Suites and establishing XMPP DOAP are the way to go. On the other hand, users have to make a decision about the service provider they want to use. XMPP Providers started to gather infos about various providers, offering a machine-readable file for XMPP clients to use. In order to give a better overview and to raise visibility, we launched a user-friendly website at providers.xmpp.net. This is what I want to work on in the future.

Current projects

Since xmpp.org needed an update for its backend, I took on the challenge and rebuilt the website using Hugo.