Volunteering Facilitator: Jean-Marc Libs
When
The time is now:
Time in your timezone (when this page was last reloaded): Friday 27 September 2024 05:48:47 UTC
Votes
The time will be set by the participants vote:
Where
What
See Roundtable Meetings for a detailed description.
Topics
First hour, quick news
- Progress reports on new features in Tiki 25 (https://dev.tiki.org/Tiki25)
- Quick report on usability improvements and concerns for Tiki as a knowledge base from people who use Tiki… as a wiki 😊
- Quick follow-up on February 2022 Roundtable meeting discussion about assigning a class or rating to themes. A preliminary theme quality and classification checklist is up at themes.t.o, and the next step will be to make a tracker based on that and start entering the relevant theme information.
- Working with new Tiki users/admins, I've found there's a lot of confusion about "site icon" and "site logo" — why two files needed and why two admin config locations. I'd like to propose that there be just one image that's used for all navbar-brand/site identity instances. This is standard practice these days as far as I know, with sites using image types that scale to suit the purpose. This can also be part of a mini-revamp to consolidate the site identity configuration that's now spread between module admin and look and feel admin. Any opinions?
- Quick update about the Unified Admin Backend: various layout and theme compatibility fixes
- ...
put your topic (max. 5-10 minutes) into the list above
Second hour, longer topics
- Provide fewer packages in composer.tiki.org
Our caching repo grows uncontrollably. Possible solutions:
- We can remove dev packages from satis config and save space. I think this one is obviously a good idea.
- Some packages have way too many versions as files on the disk compared to the versions listed on composer.tiki.org - I think these are cached assets that probably disappeared later and are no longer supported. Do you think that we can do the following?
- clean up satis config from dev packages
- delete the whole directory holding packages on composer.tiki.org
- deploy and run satis again to download only the ones that are currently in use
I'd like to discuss consequences of doing the above
- Merge strategy for the Kanban feature (https://doc.tiki.org/PluginKanban)
A lot of preliminary work went into making sure we can merge this into tiki 24. Unfortunately, there was some unexpected difficulties in the data model, requiring some refactoring. I kinda froze, affraid to violate the process for a point release.
- As of now the feature in tiki 24 is non-functional, and was never meant to be announced.
- The functional work is in a feature branch based on 24, is functionnal, but is mising some refactoring to support more enumeratable fields. There are 3 options
- Merge as is, with very limited support for enumerable fields, and missing refactorings to make backporting fixes from tiki 25 realistic.
- Finish enumerable fields support and merge.
- Finish enumbarble fields support and minimal additions to Tiki apis to allow code simplification and future backports.
- I am willing to do the work, but don't want to go behind anyone's back, as this touches core parts of tiki, albeit with a very low risk of regressions.
put your topic (max. 15 minutes) into the list above
Recording
Follow-Up
put your follow up action(s) when you're done into the list above
Chat log
Pages related to this one
2 pages link to Roundtable Meeting 2022 06