Tiki is a "big" piece of software with hundreds of niches and used "once in a while" options and parameters.
Aside of this we have "common" features that will be meet by any user of Tiki. Those common features will be the first encounter between a new user/admin and Tiki.
It may have some very positive impact to prioritise testing/monitoring/fixing those features as part of a wider plan or checklist.
Considered as "sacred cow" issues and regression on those features will be considered as critical and should come first in the list.
We have to define features but in my mind, the following, in their basic functions, should be at the top of what is available on the web (comparison to other similar software) and 99% bug free:
Wiki pages
Files gallery
Tiki Admin panel
...
I have more in mind but I think we should start with low "pretention" and get things done.
The first impression count and by extension the install process should look like "going to Mars". 😉
Somehow related...
Tiki is a "big" piece of software with hundreds of niches and used "once in a while" options and parameters.
Aside of this we have "common" features that will be meet by any user of Tiki. Those common features will be the first encounter between a new user/admin and Tiki.
It may have some very positive impact to prioritise testing/monitoring/fixing those features as part of a wider plan or checklist.
Considered as "sacred cow" issues and regression on those features will be considered as critical and should come first in the list.
We have to define features but in my mind, the following, in their basic functions, should be at the top of what is available on the web (comparison to other similar software) and 99% bug free:
I have more in mind but I think we should start with low "pretention" and get things done.
The first impression count and by extension the install process should look like "going to Mars". 😉