pep/blog.bouah.net
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Stockholm sprint: Moar spelling fixes. Thanks lool0

Browse source 
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2019-10-03 20:06:44 +02:00
parent 1661231bf7
commit d9a58cfd8c
Signed by: pep
GPG key ID: DEDA74AEECA9D0F2
1 changed files with 8 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
content/posts/stockholm-sprint.md
View file

@ -41,7 +41,7 @@ awaiting feedback from the authors.
([Conversations][conversations-commit], [Dino][dino-commit], ([Conversations][conversations-commit], [Dino][dino-commit],
[Gajim][gajim-commit], [Movim][movim-commit], [Renga][renga-commit], and some [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 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. available for adventurous services operators.
[cbg-sprint-bookmarks]: https://bouah.net/2018/08/cambridge-xmpp-sprint/ [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 of work needs to be done with the "stakeholders", that is mainly users and
server operators. 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 servers we are confident about and willing to recommend. This would mandate
discussing with server operators to get feedback on a required "feature set" discussing the issue with server operators to get feedback on a required
and policies. All this would then be fed into usability testing sessions for "feature set" and policies. All this would then be fed into usability testing
users to validate all of it. After that, we would need lots of promotion sessions for users to validate all of it. After that, we would need lots of
around it and that's also going to take a significant amount of effort. 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 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. good strategy and I would rather take it slow.
@ -91,7 +92,7 @@ good strategy and I would rather take it slow.
### And more ### And more
Pulkomando has been working on implementing IBR support in [Renga][Renga], and 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 respecting the specification. The issue in prosody has been fixed and one has
been opened [for ejabberd][IBR_ejabberd]. been opened [for ejabberd][IBR_ejabberd].