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

Jump to navigation Jump to search
Move projects to the top
(Update with providers.xmpp.net)
(Move projects to the top)
 
Line 8: Line 8:
* '''GitHub:''' [https://github.com/wurstsalat3000 wurstsalat3000]
* '''GitHub:''' [https://github.com/wurstsalat3000 wurstsalat3000]
* '''Projects:''' [https://gajim.org Gajim], [https://xmpp.org xmpp.org], [https://providers.xmpp.net providers.xmpp.net]
* '''Projects:''' [https://gajim.org Gajim], [https://xmpp.org xmpp.org], [https://providers.xmpp.net providers.xmpp.net]
== Projects ==
* [https://dev.gajim.org Gajim]: [https://dev.gajim.org/wurstsalat Development, Issue Tracker caretaker]
* Author of [https://gajim.org gajim.org] and Gajim’s [https://gajim.org/post Development News]
* [https://xmpp.org xmpp.org]: Since xmpp.org needed an update for its backend, I took on the challenge and rebuilt the website using Hugo
* [https://providers.xmpp.net/ providers.xmpp.net]: A frontend for the [https://invent.kde.org/melvo/xmpp-providers XMPP Providers project]
* [https://xmpp.org/newsletter.html XMPP Newsletter]: Contributor since 2019
* [https://github.com/pulkomandy/xmpp-doap XMPP DOAP] (Descpripton of a Project): Contributor
* Personal chat bot based on SliXMPP: Development
* Various other XMPP projects


== About Me ==
== About Me ==
Line 20: Line 31:


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.
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 ==
Since xmpp.org needed an update for its backend, I took on the challenge and rebuilt the website using Hugo.
* [https://dev.gajim.org Gajim] ([https://dev.gajim.org/wurstsalat development, Issue Tracker caretaker])
* 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://providers.xmpp.net/ providers.xmpp.net] (website maintenance since 2022)
* [https://xmpp.org/newsletter.html XMPP Newsletter] (contributor since 2019)
* [https://github.com/pulkomandy/xmpp-doap XMPP DOAP] (Descpripton of a Project) (contributor)
* Personal chat bot based on SliXMPP (development)
* Various other XMPP projects
25

edits

Navigation menu