@Friendica Support
Hi there.
As the new friendica stable version has come out recently and apparently there aren't mayor problems with the updates I wanted to ask you to consider some suggestions about the helpers/coders/admins etc pp setup we have on forum.friendi.ca
In general terms speaking when ever someone comes up with some bug report or feature request some comment show up saying "go to github and ..".
There are several reasons I consider this is not to helpful and that we should find at least some work around. First of all we all know and are aware by whom github is owned and that there are more than one of us out here who don't like to go to that site for that very reason. At the same time it is where the coding community is, where cross over communication between the fedeVerse platforms can happen and where in any case recruitment and help request for none friendica specific issues can be found or can be published. So even as we have git.friendi.ca as a a very important back up plan and backup tool it most likely will not become part of our production scheme in the near future.
Than there is the friendica community itself, a whole lot of people that are using friendica and have access to the forum.friendi.ca server with the few forum pages that do exist as of now. These are people that might not be skilled in coding itself but could do bug research, publish bug reports, have feature requests or ideas, could help out with standard helpers Q&A or even translation hints or pointing out missing translations.
I do guess that we might have more than one community member out there that is not available to sign up to another site like github or transifex (I guess that's still our translation site?) but would help out if we'd had some more forumpages like @bugresearch, @tutorial, @featureRequests. I could envision even people who love to dedicate some time to administer a forumpage like @tutorial that once some text has been created by the community in such a forum could republish such a text from that very forum page sorting that text into a given category of that forumpage.
Like to say, there is lot's of information that get's discussed or explained and than just "goes down the drain" and get's lost in the stream instead of being pushed into some category of the helpers page where it could be found easily by others.
A bugResearch forumpage for example could have a pinned post containing a bug research template like the following so people could post there findings in the first place and every once in a while someone who does have a github account and signs "responsible" to port those reports to github simple copy-pastes those reports to github with a link to the respective forum post.
Example bug research template for a @bugResearch froumPage on forum.friendi.ca:
#bugResearch
Platform Info: 2023.05 - old stable | VIER | firefox
Friendica Version: 2023.05 - old stableTheme: VIER
Browser: firefox
Friendica Source: gitHub
PHP version: 8.1.2-1ubuntu2.14
SQL version: MySQL / MariaDB
memory_limit 256M
4 Core CPU, 8 GB Ram with 300GB NVME Disk
I did/n't have a look at gitHub
Short bug description:
Overall summary of the issue.Replace the texts inside this and the following spoilers with your description.
Details of the buggy behavior:
Try to explain in short sentences and with precise wording what happens.¿Possible to reproduce, if so how:
step one to reproduce the problemstep two
step three
Expected result:
¿what should be the correct behavior?¿what did you expect?
Screenshots:
information for dev and server team:
php.error.log
LEAVE THIS AS IS, the server team will use this report if possible/necessary---------------------------------------------------------------------------
code of this example bug report
#bugResearch
[spoiler=Platform Info: 2023.05 - old stable | VIER | firefox]Friendica Version: 2023.05 - old stable
Theme: VIER
Browser: firefox
Friendica Source: gitHub
PHP version: 8.1.2-1ubuntu2.14
SQL version: MySQL / MariaDB
memory_limit 256M
4 Core CPU, 8 GB Ram with 300GB NVME Disk[/spoiler]
I [b]did/n't[/b] have a look at gitHub
[spoiler=Short bug description:]Overall summary of the issue.
Replace the texts inside this and the following spoilers with your description.
[/spoiler]
[spoiler=Details of the buggy behavior:]Try to explain in short sentences and with precise wording what happens.[/spoiler]
[spoiler=¿Possible to reproduce, if so how:]step one to reproduce the problem
step two
step three
[/spoiler]
[spoiler=Expected result:]¿what should be the correct behavior?
¿what did you expect?[/spoiler]
[spoiler=Screenshots:]
[img=]the better and dedicated the screenshot and the info involved the better[/img]
[img=]don't include unnecessary or compromising details in the screenshot[/img][/spoiler]
[hr][hr]
information for dev and server team:
[spoiler=php.error.log]LEAVE THIS AS IS, the server team will use this report if possible/necessary[/spoiler]
Diese Webseite verwendet Cookies. Durch die weitere Benutzung der Webseite stimmst du dieser Verwendung zu. https://inne.city/tos
Michael Vogel
Als Antwort auf utopiArte • • •We need to have the issues in our repository, since we link them with our coding. Also this is needed for the milestone planning. We need to have an overview of pending tasks.
The problem is the opposite: I guess that many good ideas or bug reports got lost in the past, when they only had been published in the forum, since it is hard to keep track of all them here.
utopiArte
Als Antwort auf Michael Vogel • • •That's in part exactly what I'm talking about when I say:
"there is lot's of information that get's discussed or explained and than just "goes down the drain" and get's lost in the stream"
My proposal is to create specific forumpage for bugs and have specific people in charge of keeping track of those bugResearches and posting them to github.
That is obvious, the idea is not to evade or skip the tool github.
This is about pre-sorting (Vorsortieren) on our own communication platform the issues and publish them than on github, actually in a more precise and standardized way.
OldKid ⁂
Als Antwort auf utopiArte • • •utopiArte
Als Antwort auf utopiArte • • •@Tobias
Who is administering forum.friendi.ca right now?
Do the specif forum-pages have specific people in charge?
Steffen K9 🍮
Als Antwort auf utopiArte • • •utopiArte
Als Antwort auf Steffen K9 🍮 • • •utopiArte
Als Antwort auf utopiArte • • •Steffen K9 🍮
Als Antwort auf utopiArte • • •Sorry, I didn't get any DM.
Concerning the need for moderation on the groups node forum.friendi.ca: If I remember correctly, I took over the hosting and administration of our community node in 2016. In all these years there were only one or two cases where moderation was necessary. The administration is not a big deal, either.
From my point of view the best way to advance and improve community support is having people answering questions and giving hints how to use and run Friendica. We have made much progress in that. Some years ago there were only a few active supporters in our groups/forums. These days I see much more people who are helping others.
utopiArte
Als Antwort auf Steffen K9 🍮 • • •With moderation of our forum pages I didn't mean resolving conflicts, not at all, but doing some active stuff as or for the profiles themselfs.
I tried to address those options in the beginning of this post.
On one hand I consider that the help requests to the helpers forum reflect a variety and amount that allows to split that forum up into several forums, something like:
... mehr anzeigenI find it not only a pity but a waste of energy and loss of information that conversations, hints and descriptions how to solve issues or problems vanish in the stream and consider that there should be possibilities to prevent this by splitting up the helpers forum, adding some improvements by pinning some help, like in the case of eventual bugs the proposed layout for bug descriptions, and doing some active sorting in case of discussions or content that's worth it.
With moderation of our forum pages I didn't mean resolving conflicts, not at all, but doing some active stuff as or for the profiles themselfs.
I tried to address those options in the beginning of this post.
On one hand I consider that the help requests to the helpers forum reflect a variety and amount that allows to split that forum up into several forums, something like:
I find it not only a pity but a waste of energy and loss of information that conversations, hints and descriptions how to solve issues or problems vanish in the stream and consider that there should be possibilities to prevent this by splitting up the helpers forum, adding some improvements by pinning some help, like in the case of eventual bugs the proposed layout for bug descriptions, and doing some active sorting in case of discussions or content that's worth it.
Not sure to what extent we would need access to profiles on the forum server itself or if we just can address those things by granting permissions to profiles that are hosted somewhere else. Looking at profile options I guess we should be able to do that, it's just that I never actually used it.It looks like the best way to do something like that would be to create some profiles located on the forum server itself and grant them delegate status for the pages they want to take care of. Those profiles should be used only for that very purpose and not for any form of standard use of profiles like personal posts.