zlinux: joined #tikiwiki zlinux_: joined #tikiwiki fabricius1: joined #tikiwiki zlinux: joined #tikiwiki zlinux_: joined #tikiwiki zlinux: joined #tikiwiki zlinux_: joined #tikiwiki zlinux: joined #tikiwiki marclaporte: joined #tikiwiki lincolna: joined #tikiwiki Bsfez: joined #tikiwiki marclaporte: joined #tikiwiki marclaporte1: joined #tikiwiki seamymsg: joined #tikiwiki marclaporte: joined #tikiwiki chibaguy: joined #tikiwiki
polom GillesM: hi chibaguy marclaporte: joined #tikiwiki GillesM: salut marclaporte chibaguy: Hi GillesM GillesM: chibaguy, I have again my problem ....
Tikiwiki seems to be dead chibaguy: How do you mean? Your Tiki installation?
Or tiki.org? GillesM: tiki upgrade fro 18.0. to 18.1 chibaguy: Ah, I see. I wish I could help, but I have no expertise there. GillesM: marclaporte is always on the project ? chibaguy: Yes, but the best way to get help is to ask on the developers list, or submit a bug at dev.tiki.org, if you think there is a bug. GillesM: it seems to be a known bug chibaguy: Did you submit a bug report? GillesM: I wrote on list yes chibaguy: But I mean did you submit it at https://dev.tiki.org/Make a wish ? GillesM: a lot of people have thr problem i see chibaguy: I also have some problem with the database in Tiki 18, maybe related. marclaporte: GillesM: you bet!
GillesM: you are always the complainer
GillesM: tying to make people feel guilty into fixing your problems
You have not changed
tying -> trying
How about being a regular contributor who is there to help the community and project? Make regular contributions. Keeping your Tiki instances up to date.
Bug reports go in the bug tracker after searching to see if it has already been reported. In which case, add useful info. And in the ideal world, a patch! GillesM: I love the projects where when you have a problem you are "complainer" .. marclaporte: Here are some teams to get involved in: https://tiki.org/Teams GillesM: marclaporte, how many active people on the teams ?
marclaporte, I am ok to help marclaporte: Super!
Teams have 0 to 3 people active
System is designed so workload of each team is reasonable
We need doers GillesM: 0 to people to each team ? or 0 3 people to all the project ? marclaporte: each team
some teams are dead
some are good
There is a TikiFest soon in France. Would be perfect for you!
https://tiki.org/TikiFestStrasbourg2018
I took the train from Paris to Strasbourg a while back. Nice little trip!
If you really want to get away, there is a TikiFest within a WikiSuite Unconference in Montreal in September: http://wikisuite.org/Unconference1
Activity level on the whole project can be tracked here for committers: https://www.openhub.net/p/tikiwiki/contributors?query=&time_span=&sort=twelve_month_commits
Add to that some good contributors that don't commit, but help a lot in forums, translations, etc.
AFAIK, the Tiki 16-17-18 cycle has actually been the period with the most development in the history of the project. GillesM: ok marclaporte: There has been tons of back-end things done that are not necessarily very visible but that have a huge impact for the future of the project
Tiki is 15 years old, so there was some technical debt
Danger is that we don't take advantage of newest and greatest tools and techniques
Ex.: We now have a Composer Web Installer: https://doc.tiki.org/Packages
This required a revamp of how we use Composer, with some transition pains.
But now, we can cleanly and easily add some code which was very messy before (ex.: ViewerJS)
All the gory details here: https://tiki.org/forumthread67983-About-Tiki-Packages-in-Tiki-18-0-LTS-and-why-I-support-this-project-And-mods-tiki-org-can-now-be-scheduled-for-retirement
Tiki uses over 100 external libs
The danger is: https://blog.versioneye.com/2014/02/18/why-your-software-project-will-slowly-die-without-continuous-updating/
All the external libs have been updated, and are now managed by Composer
This was an incredible amount of thankless work
Ex.: moving Zend Framework 1 to 2, and then, 2 to 3
For most libs, it goes quite well. But for others, they are dead, and we need to find alternatives.
And then, a painful migration
That was all done and cleaned up, and in trunk (upcoming version 19.0), we are pretty much up to date on everything
On another topic: we have implement a Git-SVN 2-way mirror. So committers have the choice now. And it makes it easier to have certain kinds of workflows. And to add certain types of new tools.
We implemented a Continuous Integration system (within GitLab, which is also Open Source) that alerts when a test is broken or some other error is detected
The CI is in soft launch. We are refining, and then, will make the alerts more public.
Then, it will be easy to add new alerts
chibaguy is leading the migration from Bootstrap 3 to 4 in trunk GillesM: wow marclaporte: It's less hard than the initial migration to Bootstrap
Tiki has several hundred templates and they had to be modernized
joined #tikiwiki
joined #tikiwiki Jyhem_: joined #tikiwiki Jyhem_laptop_: joined #tikiwiki Jyhem_laptop: joined #tikiwiki fabricius: joined #tikiwiki Jyhem_laptop_: joined #tikiwiki Tiki|bot: Recent Bug: - http://dev.tiki.org/item6702-Smarty-icon-function-returns-green-question-mark-images-instead-of-intended-icons fabricius1: joined #tikiwiki