Participants: Harald, Mario, Emanuel
- Harald and Mario agreed on joining forces on implementing an interactive helper which guides new users
- Also joint forces between Harald and Mario with regards to testing. If others want to join, they just have to say "I want to join" here in the Hubzilla Boost Team Forum channel.
- Association: Bylaws are not written yet, to be done. Emanuel proposes to register the association in Switzerland. No objection by the others present. But all agree that there should be more than just us three to be willing to join the association and contribute to it. Otherwise all the work would be in vain. What it means to join should be clarified in the bylaws before the founding.
- New install or Migration of hubzilla.org: Not wait until the association is founded. Should be done as soon as possible because waiting with it hinders so many ideas for improving the hubzilla-related communication. We need heartPhonix to hand over the Domain to Mark. Mario will see with HeartPhonix and Mark how this can be done soon. Emanuel who has access to the two channels hubzilla@hubzilla.org and contribute@hubzilla.org will make clones of them for backup reasons. Mario favours a New install over a Migration. The others present have no objections. The important content to save is the websites of hubzilla@hubzilla.org. It's ok for all present if contribute@hubzilla.org is given up. We can link to the support@zotadel.net for that purpose. After New install or Migration of hubzilla.org, support@zotadel.net should be cloned to hubzilla.org.
Third Online Meeting
Wed, 01 Mar 2023 11:00:00 CET
Participants: RockyIII, Emanuel
German translation below.
In order to fulfil this purpose, decisions must be made jointly and recorded in a binding manner.
Online meetings are the preferred medium for decision-making.
The Hubzilla Boost channel should be used as a further communication channel for the Boost team as well as for exchanges with the developers. Special care should be taken to ensure that communication does not get bogged. There needs to be uniform handling of the forum channel as well as the wiki and article pages. The communication tools provided by the Hubzilla technology should be used in such a way that they actually serve the communication and that the communication serves the overarching purpose. The accumulation of different communication options is to be explicitly avoided so that communication can take place efficiently. Meeting minutes are prepared in a wiki and then copied into an article. The version in the article is then binding.
Fixed categories are needed in the channel for the purpose of retrieval. These categories are still to be defined. Also, only one topic should be discussed per thread. If new topics appear in the comments, a new thread should be opened for this -> In one of the next meetings, this moderation should be assigned to a sub-team, see next point.
Sub-teams are to be assigned to each of these areas of responsibility. Individuals will be asked whether they are prepared to do this or whether they can suggest other people. Of course, people can volunteer themselves. If someone wants to withdraw from a sub-team, the sub-team first looks for a successor to ensure that the minimum number of participants is not fallen short of. If the sub-team does not find a successor, it informs the entire Hubzilla Boost team, which then jointly searches for a successor.
The organisational structure is then characterised by clear binding responsibilities. This is not about introducing hierarchies within the organisation.
The following people have already announced that they are not available for any function:
Hans, Heart, Haakan
German:
Um diesen Zweck erfüllen zu können, müssen Entscheide gemeinsam gefällt und verbindlich festgehalten werden.
Das bevorzugte Gefäss für die Entscheidungsfindgung sind Online-Meetings.
Als weiteres Kommunikationsgefäss für das Boost-Team wie auch für den Austausch mit den Entwicklern soll der Hubzilla-Boost-Kanal genutzt werden. Dort ist insbesondere Acht zu geben, dass die Kommunikation sich nicht verzettelt oder versandet. Es braucht eine einheitliche Handhabung des Forum-Kanals wie auch der Wiki- und Artikelseiten. Dabei sollen die von der Hubzilla-Technologie zur Verfügung gestellten Kommunikationswerkzeuge so verwendet werden, dass sie der Kommunikation tatsächlich dienen sowie die Kommunikation dem übergeordneten Zweck dienen. Das Anhäufen von verschiedenen Kommunikationsmöglichkeiten soll explizit vermieden werden, so dass die Kommunikation effizient erfolgen kann. Meeting-Protokolle werden in einem Wiki vorbereitet und dann in einen Artikel kopiert. Die Version im Artikel ist dann verbindlich.
Im Kanal braucht es festgelegte Kategorien, zwecks Wiederauffindung. Diese Kategorien sind noch festzulegen. Auch soll pro Thread nur ein Thema besprochen werden. Wenn in den Kommentaren neue Themen auftauchen, soll dafür ein neues Thread eröffnet werden -> In einem der nächsten Meetings ist diese Moderation einem Unterteam zuzuweisen, siehe nächster Punkt.
Diesen Aufgabenbereichen sollen jeweils Unterteams zugeordnet werden. Dazu werden einzelne Personen gefragt, ob sie dazu bereit wären, oder ob sie andere Personen vorschlagen können. Natürlich können sich Personen von sich aus melden. Wenn sich jemand aus einem Unterteam zurückziehen will, sorgt zuerst das Unterteam mit einer Suche nach einer Nachfolge dafür, dass die Mindestteilnehmerzahl nicht unterschritten wird. Wenn das Unterteam nicht fündig wird, informiert es das gesamte Hubzilla-Boost-Team, welches gemeinsam eine Nachfolge sucht.
Die Organisationsstruktur zeichnet sich dann durch klare verbindliche Zuständigkeiten aus. Es geht hier nicht darum, Hierarchien innerhalb der Organisation einzuführen.
Folgende Personen haben schon gemeldet, für keine Funktion zur Verfügung zu stehen:
Hans, Heart, Haakan
Wed, 01 Mar 2023 11:00:00 CET
Participants: RockyIII, Emanuel
German translation below.
Purpose and communication structure of the Hubzilla Boost Team
The purpose of the Hubzilla Boost Team is to do infrastructure management and public relations for Hubzilla. To do this, this team needs to be in active communication with the Hubzilla developers in order to know and be able to communicate development intentions on the one hand and implemented innovations on the other.In order to fulfil this purpose, decisions must be made jointly and recorded in a binding manner.
Online meetings are the preferred medium for decision-making.
The Hubzilla Boost channel should be used as a further communication channel for the Boost team as well as for exchanges with the developers. Special care should be taken to ensure that communication does not get bogged. There needs to be uniform handling of the forum channel as well as the wiki and article pages. The communication tools provided by the Hubzilla technology should be used in such a way that they actually serve the communication and that the communication serves the overarching purpose. The accumulation of different communication options is to be explicitly avoided so that communication can take place efficiently. Meeting minutes are prepared in a wiki and then copied into an article. The version in the article is then binding.
Fixed categories are needed in the channel for the purpose of retrieval. These categories are still to be defined. Also, only one topic should be discussed per thread. If new topics appear in the comments, a new thread should be opened for this -> In one of the next meetings, this moderation should be assigned to a sub-team, see next point.
Tasks of the Hubzilla Boost Team
- managing the hubzilla.org domain (ownership; paying the domain holder and web hosting costs): The idea is to set up an association for this.
- server administration of hubzilla.org: approx. 3 people (always at least 2)
- hub administration of hubzilla.org: approx. 3 people (always at least 2)
- maintenance and update of the websites of hubzilla@hubzilla.org: approx. 3 persons (always at least 2)
- moderation of the forum channel hubzilla-boost@hub.hubzilla.de incl.: approx. 3 persons (always at least 2)
Sub-teams are to be assigned to each of these areas of responsibility. Individuals will be asked whether they are prepared to do this or whether they can suggest other people. Of course, people can volunteer themselves. If someone wants to withdraw from a sub-team, the sub-team first looks for a successor to ensure that the minimum number of participants is not fallen short of. If the sub-team does not find a successor, it informs the entire Hubzilla Boost team, which then jointly searches for a successor.
The organisational structure is then characterised by clear binding responsibilities. This is not about introducing hierarchies within the organisation.
The following people have already announced that they are not available for any function:
Hans, Heart, Haakan
Next Hubzilla Boost Meeting
A different time should be chosen for the next meeting so that more people can attend. When the date is published, it should be asked to comment if participation is unfortunately not possible because the date does not fit. This will help us find better dates in the future.To Do
- Formation of the sub-teams
- Migration hubzilla.org from Heart's server to Mark's server (in progress)
- Decide whether hubzilla.org websites should be offered in different translations, and if so, with which technical solution
- Decide wheter we use an e-mail hubzilla@hubzilla.org and if so, assign the responsabilities.
German:
Zweck und Kommunikationsstruktur Hubzilla-Boost-Team
Das Hubzilla-Boost-Team hat zum Zweck, Infrastrukturverwaltung und Öffentlichkeitsarbeit für Hubzilla machen. Dazu muss dieses Team in regem Austausch mit den Entwicklern von Hubzilla sein, um einerseits die Entwicklungsabsichten und andererseits die Neuerungen zu kennen und kommunizieren zu können.Um diesen Zweck erfüllen zu können, müssen Entscheide gemeinsam gefällt und verbindlich festgehalten werden.
Das bevorzugte Gefäss für die Entscheidungsfindgung sind Online-Meetings.
Als weiteres Kommunikationsgefäss für das Boost-Team wie auch für den Austausch mit den Entwicklern soll der Hubzilla-Boost-Kanal genutzt werden. Dort ist insbesondere Acht zu geben, dass die Kommunikation sich nicht verzettelt oder versandet. Es braucht eine einheitliche Handhabung des Forum-Kanals wie auch der Wiki- und Artikelseiten. Dabei sollen die von der Hubzilla-Technologie zur Verfügung gestellten Kommunikationswerkzeuge so verwendet werden, dass sie der Kommunikation tatsächlich dienen sowie die Kommunikation dem übergeordneten Zweck dienen. Das Anhäufen von verschiedenen Kommunikationsmöglichkeiten soll explizit vermieden werden, so dass die Kommunikation effizient erfolgen kann. Meeting-Protokolle werden in einem Wiki vorbereitet und dann in einen Artikel kopiert. Die Version im Artikel ist dann verbindlich.
Im Kanal braucht es festgelegte Kategorien, zwecks Wiederauffindung. Diese Kategorien sind noch festzulegen. Auch soll pro Thread nur ein Thema besprochen werden. Wenn in den Kommentaren neue Themen auftauchen, soll dafür ein neues Thread eröffnet werden -> In einem der nächsten Meetings ist diese Moderation einem Unterteam zuzuweisen, siehe nächster Punkt.
Aufgabenbereiche des Hubzilla-Boost-Teams
- Verwaltung der Domain hubzilla.org (Eigentümerschaft; Bezahlen der Domain-Halter- und der Webhosting-Kosten): Hierfür besteht die Idee, einen Verein zu gründen.
- Server-Administration von hubzilla.org: ca. 3 Personen (immer mind. 2)
- Hub-Administration von hubzilla.org: ca. 3 Personen (immer mind. 2)
- Pflege und Update der Webseiten von hubzilla@hubzilla.org: ca. 3 Personen (immer mind. 2)
- Moderation des Forum-Kanals hubzilla-boost@hub.hubzilla.de inkl.: ca. 3 Personen (immer mind. 2)
Diesen Aufgabenbereichen sollen jeweils Unterteams zugeordnet werden. Dazu werden einzelne Personen gefragt, ob sie dazu bereit wären, oder ob sie andere Personen vorschlagen können. Natürlich können sich Personen von sich aus melden. Wenn sich jemand aus einem Unterteam zurückziehen will, sorgt zuerst das Unterteam mit einer Suche nach einer Nachfolge dafür, dass die Mindestteilnehmerzahl nicht unterschritten wird. Wenn das Unterteam nicht fündig wird, informiert es das gesamte Hubzilla-Boost-Team, welches gemeinsam eine Nachfolge sucht.
Die Organisationsstruktur zeichnet sich dann durch klare verbindliche Zuständigkeiten aus. Es geht hier nicht darum, Hierarchien innerhalb der Organisation einzuführen.
Folgende Personen haben schon gemeldet, für keine Funktion zur Verfügung zu stehen:
Hans, Heart, Haakan
Nächstes Hubzilla-Boost-Meeting
Für den nächsten Termin soll eine andere Zeit gewählt werden, damit mehr Leute teilnehmen können. Bei Veröffentlichung des Termins soll darum gebeten werden, zu kommentieren, falls die Teilnahme leider nicht möglich ist, weil der Termin nicht passt. Dadurch können wir in Zukunft bessere Termine finden.To Do
- Bildung der Unterteams
- Migration hubzilla.org von hearts Server zu Marks Server (in Arbeit)
- Entscheid, ob Webseiten von hubzilla.org in verschiedenen Übersetzungen angeboten werden sollen, und falls ja, mit welcher technischen Lösung
- Entscheid, ob wir eine E-Mail hubzilla@hubzilla.org nutzen, und wenn ja, Zuweisung der Verantwortlichkeiten
Participants: Harald, Emanuel
-> next step: write the bylaws for association
Then let's help out each other until we find enough people for all tasks and sub-teams.
2. Another new task (sub-team of Hubzilla Boost Team):
Create sort of guidance for beginner users (some sort of wizard).
Harald is interested in that sub-project.
Possible helpers:
scott
dan
jupiter rowland
3. Website translation:
Later. First improve the content of the website.
4. When server is migrated and the association is formed, we should create 2 e-mail accounts:
Regularity of meetings: at least every month, like that it's easier to become a habit. We will try every last friday of the month, that's easy to remember. Emanuel will create the event.
We'll write the UCT time into the event description, for less time confusion.
Association
We need the association, if it is just for the domain ownership.-> next step: write the bylaws for association
Migration of hubzilla.org
Harald knows how to migrate from mariadb do postgres and is willing to help. He will reach out to Mark.Forming sub-teams
1st thing to do is migration of hub.Then let's help out each other until we find enough people for all tasks and sub-teams.
Tasks for the Hubzilla Boost team
1. We need better website and better documentation.2. Another new task (sub-team of Hubzilla Boost Team):
Create sort of guidance for beginner users (some sort of wizard).
Harald is interested in that sub-project.
Possible helpers:
scott
dan
jupiter rowland
3. Website translation:
Later. First improve the content of the website.
4. When server is migrated and the association is formed, we should create 2 e-mail accounts:
- hubzilla@hubzilla.org -> we will need a receiving team for the inbox or a mailing list.
- security@hubzilla.org: if somebody finds security vulnerability, it can be sent to this e-mail. It could be forwarded to the developer team.
Next meeting
Regularity of meetings: at least every month, like that it's easier to become a habit. We will try every last friday of the month, that's easy to remember. Emanuel will create the event.
We'll write the UCT time into the event description, for less time confusion.
1. Zot vs. Nomad
?tbc
To-Do:
- Ask Mike about benefits of Nomand over Zot
2 Facilitate a project support team / increase the project team
How can we expand the dev team?
Which other functions would be supportive? Documentation of use / administration / code, P.R.., concept development, infrastructure (more public hubs, etc.).
We agreed to create a Hubzilla group as a base for this group and ~monthly Video calls to keep the collaboration dynamic and grow together by getting to know each other better. For better compatibility we will try a Matrix channel with Video call, supported by a turnserver. Fallback is Mark's company's Zoom instance (hosted in Europe, so GDPR(EU)-respecting in spite of Zoom.)
To-dos:
- Create Hubzilla group channel for supporting the project on hub.hubzilla.de (Witcraft)
- Create Matrix channel (Witcraft)
- meeting minutes (Emanual + all)
3 Zotlabs Website
Is the domain name Zotlabs still relevant?
As all other Zot-ware except Hubzilla were more or less a playground to develop (streams) and were announced to be End-of-Life by 2023-01-01, the "brand" Zotlabs makes little sense for the future. Zolabs (2023) = Hubzilla.
Can the website be relaunched?
Witcraft had created a rough draft of a new website and had discussed implementation with HeartPhoenix. RockyIII, and Emanuel were asked to join, and Emanuel created a new website based on this, with generous funding for graphics from a professional designer. RockyIII and Emanuel pursued this draft and demonstrated it in the meeting. It was welcomed and positively received, so it would be could to go for a relaunch.
However, there are some questions left regarding the domain and the existing webiste. There can only be clarified with HeartPhoenix as the domain owner (See nect agenda point).
4 Security Concept for Administration of Critical Infrastructure
How can we make sure that critical domains, websites, "official" support channels, etc. can be maintained independent of indivual availability?
netzgemeinde.eu and hub.hubzilla.de are set up with multiple admins (including root access to the unterlying VPS). This is a model for other infrastructure. We should ask the owner of zotum (owner of the Support channel, apparently not running smoothly) if the Support channel can be moved or cloned to another server with better fallback solutions (hub.hubzilla.de). Actually, he already had made this offer himself, but it was not pursued further.
The website (and eventually the domain) hubzilla.org could also be hosted on the VPS behind hub.hubzilla.de (as a separate instance). It could be run on a separate hub - But to reduce the barrier for website contributers, it should actually not be done using Hubzilla: Responsive design and CSS takes advanced webdesigning skills that would be a barrier for possible contributors, and Code execution must be allowed (except for very simple looking pages in the standard Hubzilla design).
Current admins of hub.hubzilla.de:
Mark Nowiasz
Marcus Wissmann
Heart Phoronix
Hilmar Runge
To-do (Mark):
- clarify with heartphoenix:
-- if the website can be re-launched, and eventually what elements should be kept
-- if it should be hosted on the VPS behind hub.hubzilla.de
-- if we can use the domain hubzilla.org for that, and how to ensure access to it in case of emergencies.[/share]
?tbc
To-Do:
- Ask Mike about benefits of Nomand over Zot
2 Facilitate a project support team / increase the project team
How can we expand the dev team?
Which other functions would be supportive? Documentation of use / administration / code, P.R.., concept development, infrastructure (more public hubs, etc.).
We agreed to create a Hubzilla group as a base for this group and ~monthly Video calls to keep the collaboration dynamic and grow together by getting to know each other better. For better compatibility we will try a Matrix channel with Video call, supported by a turnserver. Fallback is Mark's company's Zoom instance (hosted in Europe, so GDPR(EU)-respecting in spite of Zoom.)
To-dos:
- Create Hubzilla group channel for supporting the project on hub.hubzilla.de (Witcraft)
- Create Matrix channel (Witcraft)
- meeting minutes (Emanual + all)
3 Zotlabs Website
Is the domain name Zotlabs still relevant?
As all other Zot-ware except Hubzilla were more or less a playground to develop (streams) and were announced to be End-of-Life by 2023-01-01, the "brand" Zotlabs makes little sense for the future. Zolabs (2023) = Hubzilla.
Can the website be relaunched?
Witcraft had created a rough draft of a new website and had discussed implementation with HeartPhoenix. RockyIII, and Emanuel were asked to join, and Emanuel created a new website based on this, with generous funding for graphics from a professional designer. RockyIII and Emanuel pursued this draft and demonstrated it in the meeting. It was welcomed and positively received, so it would be could to go for a relaunch.
However, there are some questions left regarding the domain and the existing webiste. There can only be clarified with HeartPhoenix as the domain owner (See nect agenda point).
4 Security Concept for Administration of Critical Infrastructure
How can we make sure that critical domains, websites, "official" support channels, etc. can be maintained independent of indivual availability?
netzgemeinde.eu and hub.hubzilla.de are set up with multiple admins (including root access to the unterlying VPS). This is a model for other infrastructure. We should ask the owner of zotum (owner of the Support channel, apparently not running smoothly) if the Support channel can be moved or cloned to another server with better fallback solutions (hub.hubzilla.de). Actually, he already had made this offer himself, but it was not pursued further.
The website (and eventually the domain) hubzilla.org could also be hosted on the VPS behind hub.hubzilla.de (as a separate instance). It could be run on a separate hub - But to reduce the barrier for website contributers, it should actually not be done using Hubzilla: Responsive design and CSS takes advanced webdesigning skills that would be a barrier for possible contributors, and Code execution must be allowed (except for very simple looking pages in the standard Hubzilla design).
Current admins of hub.hubzilla.de:
Mark Nowiasz
Marcus Wissmann
Heart Phoronix
Hilmar Runge
To-do (Mark):
- clarify with heartphoenix:
-- if the website can be re-launched, and eventually what elements should be kept
-- if it should be hosted on the VPS behind hub.hubzilla.de
-- if we can use the domain hubzilla.org for that, and how to ensure access to it in case of emergencies.[/share]
Meeting date, time, location, participants
Wed Jan 11th 11h-12h CET
Location: https://noris.zoom.us/j/4289953766?pwd=UXo2TDRFbkpMQmFUdDhvbHFUUFg1QT09 , later meet.jit.si/hubzilla
Participants: mario, rockyiii, hilmar, emanuel
Agenda
Protocols
Documentation
Which forum channels should be hosted on which hub?
Website hubzilla.org
Website zotlabs.org
Dev team increase
Minutes
Protocols
Currently, moving Zot to Nomad would only be a renaming. Mario sees the future of Zot/Nomad perhaps as an extension to ActivityPub. How it will develop is not yet known. Protocols do not have to be prominently mentioned on the website for this reason. Mario's wish: No abandonment of the term Zot, wait and see. Further development of AP is discussed here: https://codeberg.org/fediverse/fep
Documentation
/help: needs to be updated. Idea: Collaboratively develop the English-language (lead) version in a Hubzilla wiki, then import it back into code on GIT.
Translations are developed to different degrees. They could also be built up in a wiki on the basis of the lead version.
Mario thinks the idea of a wiki is good.
Direct help (app) (direct access to doc/context for each module; app is no longer updated) will be removed in v8.0.
To do: Set up a team which updates the /help documentation after each software update
New idea: A link to the documentation wiki should appear on every help page. ("If you want to improve this documentation, please do so on hubzilla.org/wiki/hubzilla/documentation"). Like this, non-git-affine people can finally contribute to the documentation.
Which forum channels should be hosted on which hub?
Was not discussed. Postponed to next meeting.
Website hubzilla.org
Mario thinks the new site (which is under construction) is good.
Updating of the website content should also be done in a Hubzilla wiki. (hubzilla.org/wiki/hubzilla/website)
Still to do: create multiple admin accesses to the web hosting of hubzilla.org and to Hubzilla admin.
Both documentation wiki and website wiki to be hosted on hubzilla.org itself under wiki.
Website zotlabs.org
From Mario's point of view, this URL is redundant. (see topic "protocols" above).
Dev team increase
Current contributors: Max, Mario, Mike (for questions), Harald, Manuel (Spanish translation). More people should join! But such people should read deeply. (Source code + ask questions)
Mario said that a good start to contribute as a coder would be issue tracker: feature request; bug reports To do: Formulate in road map which looks at the big picture (where is the journey going) (i.e. hubzilla.org/wiki/hubzilla/roadmap)
Mastodon API: Question open whether it is worth putting much energy into it.
Next steps:
create multiple admin accesses to web hosting of hubzilla.org and to Hubzilla admin. Who is in charge beside HeartPhonix? The admins of hubzilla.de?
Rocky will organise the next session.
Problem is that ideas raised in the channel by the Hubzilla Boost Team are quickly lost from view again.
In the Hubzilla Boost Team, add categories to the top level posts.
Wed Jan 11th 11h-12h CET
Location: https://noris.zoom.us/j/4289953766?pwd=UXo2TDRFbkpMQmFUdDhvbHFUUFg1QT09 , later meet.jit.si/hubzilla
Participants: mario, rockyiii, hilmar, emanuel
Agenda
Protocols
Documentation
Which forum channels should be hosted on which hub?
Website hubzilla.org
Website zotlabs.org
Dev team increase
Minutes
Protocols
Currently, moving Zot to Nomad would only be a renaming. Mario sees the future of Zot/Nomad perhaps as an extension to ActivityPub. How it will develop is not yet known. Protocols do not have to be prominently mentioned on the website for this reason. Mario's wish: No abandonment of the term Zot, wait and see. Further development of AP is discussed here: https://codeberg.org/fediverse/fep
Documentation
/help: needs to be updated. Idea: Collaboratively develop the English-language (lead) version in a Hubzilla wiki, then import it back into code on GIT.
Translations are developed to different degrees. They could also be built up in a wiki on the basis of the lead version.
Mario thinks the idea of a wiki is good.
Direct help (app) (direct access to doc/context for each module; app is no longer updated) will be removed in v8.0.
To do: Set up a team which updates the /help documentation after each software update
New idea: A link to the documentation wiki should appear on every help page. ("If you want to improve this documentation, please do so on hubzilla.org/wiki/hubzilla/documentation"). Like this, non-git-affine people can finally contribute to the documentation.
Which forum channels should be hosted on which hub?
Was not discussed. Postponed to next meeting.
Website hubzilla.org
Mario thinks the new site (which is under construction) is good.
Updating of the website content should also be done in a Hubzilla wiki. (hubzilla.org/wiki/hubzilla/website)
Still to do: create multiple admin accesses to the web hosting of hubzilla.org and to Hubzilla admin.
Both documentation wiki and website wiki to be hosted on hubzilla.org itself under wiki.
Website zotlabs.org
From Mario's point of view, this URL is redundant. (see topic "protocols" above).
Dev team increase
Current contributors: Max, Mario, Mike (for questions), Harald, Manuel (Spanish translation). More people should join! But such people should read deeply. (Source code + ask questions)
Mario said that a good start to contribute as a coder would be issue tracker: feature request; bug reports To do: Formulate in road map which looks at the big picture (where is the journey going) (i.e. hubzilla.org/wiki/hubzilla/roadmap)
Mastodon API: Question open whether it is worth putting much energy into it.
Next steps:
create multiple admin accesses to web hosting of hubzilla.org and to Hubzilla admin. Who is in charge beside HeartPhonix? The admins of hubzilla.de?
Rocky will organise the next session.
Problem is that ideas raised in the channel by the Hubzilla Boost Team are quickly lost from view again.
In the Hubzilla Boost Team, add categories to the top level posts.
Who are the admins of hub.hubzilla.de?This info is missing in the minutes, should be added
They're added.