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.