• Who
  • People Confirmed
  • People Interested
  • was there?
• When
• Where
• What
• Topics
  • First hour, quick news
  • Second hour, longer topics
• Recording
• Follow-Up
  • 1.1. Synchronous discussions: Decide whether Irc vs other chats (wikisuite.chat, for instance)
  • 1.2. Asynchronous Discussions - Forum Topic Status
  • 1.3. Junior devs helping in Tiki Open Online Hours
  • 1.4. some topics may come back in the next TRM
  • 1.5. Cleaned doc.t.o/Upgrade page
  • 1.6. PluginTogether in t.o - serverurl added
  • 1.7. Mike will submit a 'Wish' regarding the first topic, in the first half (Plugin Tracker / Plugin Tracker List GUI - revise all options into 'Tabs' view)
• Chat log
• Pages related to this one

Volunteering Facilitator: Bernard Sfez / Tiki Specialist

Who plans to attend? (please vote for preferred times below)

• @Bernard Sfez / Tiki Specialist
• @guill
• ...

• @Xavier de Pedro - I'd like to attend but I can't make it the week from August 17th-23rd, but I can almost any day and time the week after: from August 24th to 30th .

According to the tiki logs:

• Alice (anon)
• Bsfez
• chibaguy
• Jyhem
• lindon
• marclaporte
• mikeua
• robertokir
• xavidp

Thu 27 Aug 2020 14:30 UTC

Time in your timezone (when this page was last reloaded): Thursday 18 April 2024 11:02:15 UTC

• https://live.tiki.org

See Roundtable Meetings for a detailed description.

1. Plugin Tracker / Plugin Tracker List GUI - revise all options into 'Tabs' view. Why? It's typically the first impression for new users to Trackers and the list is very, very long (read: not user friendly) Is this a significant amount of work? (Mike FInko)
2. Machine Learning (1- Rubix ML community meeting: recording available soon. Code plan made: Commits by Victor soon)
3. Ma question is: How can I adjust the URLs of the single wiki pages and of the homepage of wiki? (Alisa)
4. ...

put your topic (max. 5-10 minutes) into the list above

Since few versions less and less information are added by developers or people (investors) adding or improving stuff to the version doc and generally at doc.tiki.org while more and more new features and options added.

http://doc.tiki.org/Tiki22 doesn’t reflect at all the mass of improvement and additions in master (https://gitlab.com/tikiwiki/tiki/-/commits/master)

This is a serious concern as many of the new stuff is known by only a handful of people. In time there is a danger information is lost. IE: the Relation tracker fields was developed a few years ago without serious doc and today it is very hard to find how to use the full power of its options and we can only rely on existing usage (http://doc.tiki.org/Relations-Tracker-Field).

• I've been one the main persons (besides Marc) to create/extend/maintain these pages reporting the new features in any new version of Tiki over the years until Tiki16. My offline duties changed by then and I can't find the time to do that task as before, when I used to "comb" the cvs/svn lists for NEW and ENH tags, and place information in the corresponding doc page for that tiki version. I'm currently mostly focusing in investing my little free time for this task in the LTS versions, which are the ones I use in my day to day life (for personal or professional reasons). Looking at the history of those wiki pages in doc.t.o (Tiki17, 18, 19, 20, 21, 22) I see other people are contributing, beyond Marc, to drop a section and some line to cite the new feature or enhancement added, etc. However, maybe this is not enough, for what you @Bernard Sfez / Tiki Specialist say.

• In addition to that fact, the "Changes Wizard" was added years ago (formerly known as the "Upgrade Wizard", to display in short the main new preferences and settings available since any new tiki version, plus some information of the new changes that you could find there. As far as I know, little additions to this wizard are added by other devs. And since I don't know yet which are the new features and enhancements added to Tiki22, I didn't even find the time to start the new screen for Tiki 22 in there.

• Xavi... wrong direction.
  I’m not talking about "changelog" or a list of new stuff added (whatever you want to call it) but about Tiki online documentation, about documenting how to use new features, options, changes, etc.
  It is pretty obvious (at leat to me) that less and less samples, less screenshot, less explanations are added to our online doc and that’s leave us with a handful of users having a real idea on how to use them.
  The Tiki online documentation is critical for Tiki Admin to understand how to use, how they can improve their existing Tiki or how to use an option they just discovered on their way.
  
  And just to clarify, there are a few people (other than you and Marc) adding a line here and there as they can (thanks).

I have the sensation that we have been too many years not being able to pay enough attention to (1) the user forums in tiki.org, as well as (2) to the bug reports/feature requests in dev.t.o. That might be one of the reasons why we are loosing power and health in our community over the years.

I've seen that some other software communities (Ubuntu, RStudio, ...) included a section in their notifications to users (the equivalent to the notification digests or the Daily reports in Tiki) about the new posts without replies yet. We could do something similar, to prevent cases in which posters receive no feedback at all, and add some way that users willing to help can subscribe to something like:

• forum posts in t.o without any reply yet
• open bug/wish reports in dev.t.o without any comment by any other user, nor any change in the "Lastmod by" field in the last n weeks (n=1?)
• bug/wish reports still open and not triaged (still with the Resolution status = "New") affecting any of the last n tiki versions (n=3?)

We could then add that report by default to the tikiwiki-users email list, for instance, plus allow anyone else to subscribe.

And as a low hanging fruit, a section in the report with "what's new since the last report" (being fed from the content in the "since your last visit" feature in Tiki, might be handy (this is also added in the reports sent by some other software communities, that seem that might be having better health than ours, imho .

• This discussion is more than welcomed (I’ve planned to add this topic to our next TAG meeting)

Also - regarding 'Users', shouldn't there be an option to label your own posts in the Forums as 'resolved, partially resolved, (other?)'? This would help for the 'Since Last Login' report or email list mentioned above by Xavi. This falls under the category of reducing 'single points of failure', or, everyone does a little. (Mike / 15:41EET / 25.08.2020 - I don't have the 'sign' button, could copy/past/edit the code but a bit pointless)

I know this has been discussed before but, if people are ok with it, can we have an update on the best Git workflow, etc. for Tiki? Or if this isn't necessary because there is an up-to-date comprehensive doc page, please put the link(s) here instead. (I'm asking because I haven't committed to Tiki yet via Git, having been busy with other things since the last time I started to set up the workflow - sorry ;-) .)

UPDATE: This topic was withdrawn because time was running short. My questions were answered on the dev mailing list instead.

• View and listen to the recording here.

Problem to view the recording? Read this...

Suggestions of actions to be taken:

proposal: equivalent of wikisuite.chat but for tiki address and scope only.

• create another room like tiki.wikisuite.chat or a new instance chat.tiki.org
• Step1: use tiki.wikisuite.chat ( tiki at conference.wikisuite.chat )
• Step2: use chat.tiki.org ( chat at conference.tiki.org or talk at chat.tiki.org? ).

Proposal to go straight to Step 2 (provided that people will participate and help where needed):

• For: Gary, Xavi, Jyhem, Marc, lindon, Mike, luci
• Against:
• Undecided:

Pending topics about this option:

• Logs of previous days in openfire-based chats (like wikisuite.chat or the potential chat.tiki.org):
  • how to achieve that?
    • (feature added in openfire already)

Xavi sends a message to the devels list, to allow getting feedback for some time before making it happen .

• we discussed adding a field (or using a current field?), where the topic creator can mark the topic as: 'Solved', 'Unresolved', 'Partially Resolved', etc. Maybe the default should be 'New'? If the topic creator is responsible for this, than it will be mostly sustainable without anyone having to do any extra work. Otherwise, we can create a List Execute to change all 'New' answers to 'Unresolved' if no response over 30 days. Opinions?
• it was also suggested to add a 'Resolved' to the title of the topic, like in brackets. While this sounds good, who would do this? While this may not be much work, I suspect it is more than anyone has time to do, and the first option above is simpler and faster to implement
• can we add a search filter to the 'Topic' column
• I created a 'PluginSlider' (but swiper may be better) that we could put on the top of the 'Forums' to 'humanize' them a bit, or encourage community building:

We need a person to coordinate the effort of junior dev work, sponsored by EvoluData.

• About how to improve getting feedback to new users in forums, etc.
  • Asynchronous discussions: User Forums (many) vs Users List (1)
• when / how to automatically change status of long (potentially obsolete) bug reports, etc.
  • Raise the old thread again.

I've cleaned a bit the Upgrade page, after the discussion, moving oldish content to a newly created child page in that wiki strcuture.

As soon as the enhancement commited by kroky6 is backported to 21.x (or we get t.o running on Tiki22), we will be able to use again the PluginTogether in our TRM meetings in t.o

I added the same serverurl param to the equivalent module on dev.t.o so that we can use it there also.

Remember that you have to temporarily disable the highlighter (in case it's on) for the PluginTogether to work as expected with current versions of Tiki.

put your follow up action(s) when you're done into the list above

One page links to Roundtable Meeting 2020 08

• Roundtable Meetings