Stockholm sprint: Reword some sections

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2019-10-02 23:07:20 +02:00
parent 85e0bc2b37
commit ffad0c1257

View file

@ -6,12 +6,13 @@ draft: true
---
Another episode of the XMPP sprints series happened this weekend close to
Stockholm in the Nacka prefecture, in a house we rented. We worked together on
improving a new groupchat bookmarks specification, file transfer
interoperability issues, and a future landing page for new XMPP users!
Stockholm in the Nacka prefecture, in a house we rented. Significant
improvements to the sprint infra this time are sauna and crêpes!
As usual, every developer meetup comes up with its share of bug fixes, new
ideas, and improvements.
We worked together on improving a new groupchat bookmarks specification, file
transfer interoperability issues, and a future landing page for new XMPP
users! As usual, every developer meetup comes up with its share of bug fixes,
new ideas, and improvements.
![Stockholm scenery](../stockholm.jpg)
@ -66,22 +67,21 @@ server depending on different factors that would be gathered automatically for
the most part (if not all). This is more or less similar to other portals like
[joinmastodon][joinmastodon], or [nextcloud sign-up process][nextcloud-signup].
While I am no designer at all, building up a website isn't the hardest part,
what is hard is finding a way to convey to the user what "federation" or
"public network" mean. Roel teaches in Interaction Design, and so he was a
great help over the weekend. We came up with a narrative for the project, and
a sketch for a sign-in flow.
Building up the website isn't the hardest part, what is hard is finding ways
to convey to the user what "federation" or "public network" mean. Roel teaches
in Interaction Design, and so he was a great help over the weekend. We came up
with a narrative for the project, and a sketch for a sign-in flow.
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 need to first get a list a
servers we are confident about and are willing to recommend. This would
mandate discussing with server operators to get feedback. And this would then
be fed into usability testing sessions for user 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.
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.
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.