From d9a58cfd8c14a6c2fac44a83ac78776834eb8660 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Maxime=20=E2=80=9Cpep=E2=80=9D=20Buquet?= Date: Thu, 3 Oct 2019 20:06:44 +0200 Subject: [PATCH] Stockholm sprint: Moar spelling fixes. Thanks lool0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Maxime “pep” Buquet --- content/posts/stockholm-sprint.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/content/posts/stockholm-sprint.md b/content/posts/stockholm-sprint.md index ca56843..c3ae71a 100644 --- a/content/posts/stockholm-sprint.md +++ b/content/posts/stockholm-sprint.md @@ -41,7 +41,7 @@ awaiting feedback from the authors. ([Conversations][conversations-commit], [Dino][dino-commit], [Gajim][gajim-commit], [Movim][movim-commit], [Renga][renga-commit], and some initial work in poezio), but will not be used as long as the feature is not -advertized by the server. A new [prosody module][bookmarks-prosody] is also +advertised by the server. A new [prosody module][bookmarks-prosody] is also available for adventurous services operators. [cbg-sprint-bookmarks]: https://bouah.net/2018/08/cambridge-xmpp-sprint/ @@ -75,12 +75,13 @@ The project is far from being over, this is only the tip of the iceberg. Lots of work needs to be done with the "stakeholders", that is mainly users and server operators. -To know what server to recommend to users we first need to get a list a +To know what server to recommend to users we first need to get a list of servers we are confident about and willing to recommend. This would mandate -discussing with server operators to get feedback on a required "feature set" -and policies. All this would then be fed into usability testing sessions for -users to validate all of it. After that, we would need lots of promotion -around it and that's also going to take a significant amount of effort. +discussing the issue with server operators to get feedback on a required +"feature set" and policies. All this would then be fed into usability testing +sessions for users to validate all of it. After that, we would need lots of +promotion around it and that's also going to take a significant amount of +effort. While I am excited about all this I don't think diving in head first is a good strategy and I would rather take it slow. @@ -91,7 +92,7 @@ good strategy and I would rather take it slow. ### And more Pulkomando has been working on implementing IBR support in [Renga][Renga], and -reported with Link Mauve issues to server implementations that weren't +reported with Link Mauve issues about server implementations that weren't respecting the specification. The issue in prosody has been fixed and one has been opened [for ejabberd][IBR_ejabberd].