Re: [Tiki-devel] [Tiki-users] doc.tiki.org is down?!
Bsfez Tiki via TikiWiki-devel <[email protected]> Sat, 24 Jul 2021 14:00:57 +0300
| Newsgroups | gmane.comp.cms.tiki.devel,gmane.comp.cms.tiki.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Marc, > @Bernard: I tried to explain the best I could. I understand you feel like you explained everything you had to tell about this. But I don’t see where you explain why it is important to keep those datas "alive" in our existing Tiki sites where they require resources, maintenance, monitoring, etc... (or I may have miss it). We have a discussion about this in a few weeks and we will be able to complete and pass missing informations. I’ve added examples of pages I have found that are outdated and can only (IMO) hurt our image when someone land on it + we lost the visitors (we should implement tools to redirect him to other pages). Then from our decisions we will decide what to do (after we agree on a realistic project). Have a nice week-end, Bernard > On 24 Jul 2021, at 08:59 , Marc Laporte <[email protected]> wrote: > > @Bernard: I tried to explain the best I could. > > If you want to propose a plan, I suggest you start a wiki page with the project. > > Marc > > > On Fri, 23 Jul 2021 15:17:47 +0300 Bsfez Tiki [email protected] said > >> Hi Marc, >> I agree with your arguments but not with the conclusion. >> If we are struggling to find resources to publish/manage 15+ years of data >> and if checking those data is an unrealistic project that will take a huge >> amount of hours. >> Why would we try to do it ? >> Monitoring those data will only add extra resources consumption and even if >> monitored, who will analyse and do some kind of action based on those reports >> ? >> It won’t solve the huge amount of time issue to analyse reports, to clean >> pages, to move pages to warn about outdated information, etc. >> I don’t see the point where once we decide a policy actions are turned into >> automatic process done by AI. 😉 >> (while I’ll be very glad to have improvement in the monitoring area on Tiki >> monitoring) >> Unless there is a critical reason (and we should agree on it) to keep this >> heavy inheritance my conclusion is that we should move the data in a read >> only area where they’ll use as less as possible resources AND where it will >> be understandable that this is outdated or none-used data. (publishing those >> data are sometimes damaging Tiki image). >> May be a fresh start (reset) is a but too much, but we can decide simple >> criteria for archiving pages (last visited/edited time). >> Other project did that before us and they didn’t die... >> Bernard >> > On 22 Jul 2021, at 16:51 , Marc Laporte <[email protected]> wrote: >> > >> For all the reasons above, I think we shouldn't keep 15+ years of data >> > online >> >> all the time in a Tiki. We should keep them archived somewhere and available >> > as read only. > > I don't see how this is realistic with the current community and technology. >> > > 1- It would take a huge amount of hours to manage such a project. Determine >> > guidelines, go through content, etc. >> > > 2- If we archive them somewhere, we are just transferring the problem >> > somewhere else. What system? who will manage? what will lifecycle? how will >> > links work? etc. >> > > We could invest hundreds of hours to clean up data that has no impact on >> > performance. >> > > > I repeat my conclusion: >> > "The main issue is that we do not have a proper monitoring system. We are >> > somewhat blind to what are the root causes of issues." >> > > Once we know the root causes, we can determine a sensible plan. >> > > Marc >> > > > > > _______________________________________________ >> > TikiWiki-devel mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > _______________________________________________ TikiWiki-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel