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.