Please read the Code of Conduct that applies for this forum:
Click to open/close
Different ways to contribute:The Code of Conduct of Hubzilla.org (Version 22 June 2024)
In all publications and interactions on Hubzilla.org, we ask you to cultivate and demand respectful interaction with one another and to be aware of the consequences of your actions (in relation to the world and the future).
Your'e asked to behave in a way that enables all users and visitors of Hubzilla.org to participate (to inform, to get informed, to discuss, to develop, to create) without harassment, regardless of age, body size, disability, ethnicity, gender characteristics, gender identity and expression, level of experience, education, social status, nationality, personal appearance, race, caste, skin colour, religion or sexual identity and orientation.
We ask you to act and interact in a way that contributes to an open, welcoming, diverse, inclusive and healthy community.
These are examples of behaviours that contribute to a positive environment for the community:
- Show empathy and kindness towards everyone
- Respect different opinions, points of view and experiences
- Give constructive feedback
- Accept constructive feedback with dignity
- Take responsibility
- Apologise to those affected by your mistakes
- Learn from experience
- Focus on what is best not only for you as an individual, but for the community as a whole
The following behaviour will result in your channel being blocked:
- You use sexualised language, images or symbolism
- You make an unwanted sexual advance
- You make offensive or derogatory comments
- You attack someone personally or politically
- You engage in trolling
- You harass someone, whether publicly or privately
- You publish other people's private information without their express permission
- You display behaviour that could reasonably be considered inappropriate in a professional environment
The board of directors of the Hubzilla Association will remove posts and comments that do not comply with this Code of Conduct and block their author.
This Code of Conduct applies to all content published in a channel which is hosted on hubzilla.org, even if the channel is a private one (a closed circle).
Click to open/close
At hubzilla.org/page/info/get_involved you will find an overview of the different ways to contribute to the project.
This forum here is the right place to collaboratively discuss improvements to the user documentation, its translations and the creation of user tutorials.
If you are looking for support as an admin, you will find the right forum at hubzilla.org/channel/adminsforum
If you want to help develop the code, you can find the right forum at hubzilla.org/channel/development
I have removed the DRAFT marker for this MR now, so it's ready for Mario to review, and merge when he has the time.
I'm still hoping we can get the strings and updated docs translated before it's released though. Let me know if you'd like to contribute, but wants some help to get started.
I'm still hoping we can get the strings and updated docs translated before it's released though. Let me know if you'd like to contribute, but wants some help to get started.
Looks like a good plan!
I agree that keeping the focus on developing addons, themes and widgets is the most important. To be fair, most of core is built using the same patterns and functions as well.
Finding a good way of documenting the hooks is probably going to be the most challenging. There's a ton of them, and they're a bit unwieldy to handle automatically. At least with doxygen. We may perhaps want some custom tooling for that.
I agree that keeping the focus on developing addons, themes and widgets is the most important. To be fair, most of core is built using the same patterns and functions as well.
Finding a good way of documenting the hooks is probably going to be the most challenging. There's a ton of them, and they're a bit unwieldy to handle automatically. At least with doxygen. We may perhaps want some custom tooling for that.
While installing my node I had some difficulties with the initial login. I think there is a circular dependency where the installation is not yet finished, not at the point where the email service configuration may take place - so the registration info for the first (admin) account cannot be sent. You can hack the MariaDB table which is what I did, but I believe email verification should be at least suspended during the first registration.
I use a MTA not anything PhP, so for those who use PhP Mail this might not be an issue at all.
I use a MTA not anything PhP, so for those who use PhP Mail this might not be an issue at all.
I use my own stack for everything, from DNS all the way to the top. Sendmail, php mail works, I know. But its a hassle to use them then turn them off once you switch to the MTA. In either case the installation is not user friendly with the very first account creation interrupted by mandatory verification. This is an old issue, by the way, and if I recall it correctly it remains an issue on the Streams fork as well.
@Hubzilla Documentation Team I’ll have a look. But that’s not really "my area of responsibility". I’m not entirely sure how the help texts are displayed. I formatted the German documentation so it could be integrated (following @Harald Eilertsen 's instructions). The different layout in the sidebar seems to be more a matter of the template.
@Hubzilla Documentation Team @Ema エマ
I’ll have a look at the best way to integrate this (I’ve quickly saved the page locally for now, as Scott’s pages aren’t always accessible).
I’ll have a look at the best way to integrate this (I’ve quickly saved the page locally for now, as Scott’s pages aren’t always accessible).
The attachment is not showing in the post. This issue needs to be fixed, @Mario Vavti. I posted by visiting the @Hubzilla Documentation Team channel.
@Der Pepe (Hubzilla) ⁂ Here's the attachment: #^https://hubzilla.org/attach/c5d0b3ad-054b-4600-b65a-a108340e8d3e
@Der Pepe (Hubzilla) ⁂ Here's the attachment: #^https://hubzilla.org/attach/c5d0b3ad-054b-4600-b65a-a108340e8d3e
@Hubzilla Documentation Team OK, I’ll do that right away.
@Hubzilla Documentation Team @Ema エマ
Should I also insert my graphic for the various regions at the appropriate place in the document?
regions.webp
Should I also insert my graphic for the various regions at the appropriate place in the document?
regions.webp
@Hubzilla Documentation Team I can't believe it! 😂
I requested this exact feature a long time ago. They said that undeliverable entries would be deleted after a certain amount of time and unreachable instances would be added to the ‘unreachable list’ after an even longer period of time.
I had asked for exactly that because I knew it from (streams) – when I had installed such a hub – from the queue view there.
queue1.png
That's brilliant! I'll add it to the documentation and my KnowledgeDB.
You've made my day with this discovery.
I requested this exact feature a long time ago. They said that undeliverable entries would be deleted after a certain amount of time and unreachable instances would be added to the ‘unreachable list’ after an even longer period of time.
I had asked for exactly that because I knew it from (streams) – when I had installed such a hub – from the queue view there.
queue1.png
That's brilliant! I'll add it to the documentation and my KnowledgeDB.
You've made my day with this discovery.
Hubzilla is when even the main devs keep discovering hidden features they knew nothing about.
@Hubzilla Documentation Team the documentation can be searched with a
? prefix from the search bar.
Powered by the Hubzilla Fediverse Server. Celebrating 15 Years of Innovation.