<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-us">
  <title type="text">WikiSuite blog</title>
  <subtitle type="text">WikiSuite is the most comprehensive and integrated Free / Libre / Open Source enterprise software suite ever developed.</subtitle>
  <logo>https://wikisuite.org/img/tiki/Tiki_WCG.png</logo>
  <updated>2026-07-08T22:34:35+00:00</updated>
  <generator uri="https://getlaminas.org" version="2">Laminas_Feed_Writer</generator>
  <link rel="alternate" type="text/html" href="https://wikisuite.org/"/>
  <link rel="self" type="application/atom+xml" href="https://wikisuite.org/tiki-blogs_rss.php"/>
  <id>https://wikisuite.org/</id>
  <entry>
    <title type="html"><![CDATA[WikiSuite Celebrates 15 Years: 2011 - 2026, the Adventure Continues!]]></title>
    <summary type="html"><![CDATA[<p>WikiSuite Turns 15: 2011 - 2026, the Adventure Continues!
</p>

<p>	<a href="dl1265?display" class="internal"  data-box="box">		<img src="dl1265?display&scale=1"  alt="WIkiSuite Anniversary" class="regImage pluginImg1265 img-fluid" />	</a>
</p>

<p><strong>March 11, 2026</strong> marks 15 years since WikiSuite was first announced by <strong>Marc Laporte</strong> at the Confoo conference in 2011. The goal from the beginning has been to bring Free/Libre and Open Source software together into a functional, interoperable suite.
</p>

<p>Over the past 15 years, as the need for organizations to keep control over their data has grown, the WikiSuite project has focused on acting as the "glue" between independent projects. Making different systems communicate smoothly requires consistent effort. By combining these projects under a unified brand, WikiSuite provides an integrated experience that helps organizations deploy tools on their own infrastructure, ensuring data sovereignty and avoiding vendor lock-in.
</p>

<p>WikiSuite does not exist in a vacuum. Our 15-year milestone is an opportunity to celebrate the continued improvement of the individual projects that compose it. We want to sincerely thank the developers, contributors, and users of <strong>Tiki, Cypht, Syncthing, Dolibarr, Converse.js, and</strong> <a href="Software-Components" title="Software Components" class="wiki wiki_page">all the other vital Open Source tools we integrate</a>. Their continuous improvements and dedication over the years are what make WikiSuite possible.
</p>

<p>As we celebrate these 15 years, our commitment remains the same: to continue improving the interoperability of these fantastic Open Source projects. Our priority is to keep adapting and refining this integrated ecosystem to meet the enterprise needs of tomorrow.
</p>

<p>We are celebrating 15 years of digital independence, collaboration, and the power of the Open Source community.
</p>

<p>On behalf of the whole team: <strong>Happy 15th Anniversary, WikiSuite!</strong>
</p>
]]></summary>
    <published>2026-03-10T23:00:00+00:00</published>
    <updated>2026-03-10T23:00:00+00:00</updated>
    <link rel="alternate" type="text/html" href="https://wikisuite.org/blogpost18-WikiSuite-Celebrates-15-Years-2011-2026-the-Adventure-Continues"/>
    <id>https://wikisuite.org/blogpost18-WikiSuite-Celebrates-15-Years-2011-2026-the-Adventure-Continues</id>
  </entry>
  <entry>
    <title type="html"><![CDATA[🎉 Happy 23rd Anniversary, Tiki Wiki CMS Groupware!]]></title>
    <summary type="html"><![CDATA[<p>🎉 Happy 23rd Anniversary, Tiki Wiki CMS Groupware!
</p>

<p>	<a href="dl1238?display" class="internal"  data-box="box">		<img src="dl1238?display&scale=1"  alt="TikiAnniversary" class="regImage pluginImg1238 img-fluid" />	</a>
</p>

<p>October 9, 2025, marks 23 years of innovation, collaboration, and resilience for Tiki Wiki CMS Groupware. What began in 2002 as a vision by Luis Argerich to create a completely free, fully featured CMS has grown into one of the most robust, flexible, and community-driven Open Source platforms in the world.
</p>

<p>In the years since that first release, Tiki has evolved from a "wiki with extras" into a modular all-in-one web application, powering everything from enterprise intranets to public portals, project management systems, collaboration platforms, and more. And all of this, without ever relying on external plugins Tiki includes everything in one package, staying true to its unique, self-contained design philosophy.
</p>

<p>🚀 A Year of Steady Growth and Meaningful Contributions
</p>

<p>Over the past year, Tiki’s development has continued at full throttle:
</p>

<ul><li> Over 1,200 commits pushed to the core repository <a target="_blank" class="wiki external"  href="https://gitlab.com/tikiwiki/tiki">https://gitlab.com/tikiwiki/tiki<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
</li></ul><p>
</p>
<ul><li> Dozens of new contributors joined the project, with a warm welcome to those making their first-ever Open Source contributions through Tiki <a class="wiki external" target="_blank" href="https://openhub.net/p/tikiwiki/contributors" rel="external">https://openhub.net/p/tikiwiki/contributors</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>
</li></ul><p>
</p>
<ul><li> Continuous refinements to UI/UX, security, and performance
</li></ul><p>
</p>
<ul><li> Active testing and deployment in diverse environments, proving once again how adaptable Tiki is across industries and use cases
</li></ul><p>
<br />Behind every fix, feature, and improvement is a community of dedicated developers, testers, documenters, and users. Whether you're writing code, reporting bugs, translating strings, or just giving feedback you are part of what makes Tiki thrive.
</p>

<p>🔄 Built by Many, Belongs to All
</p>

<p>Tiki stands out not just because of its size and feature set, but because of its values: openness, transparency, and inclusion. It's no accident that Tiki remains in the top 2% of Open Source project teams tracked by Open Hub. The collaborative model it champions is more than just a development strategy it's a philosophy.
</p>

<p>Looking back, Tiki has powered tens of thousands of websites, been translated into dozens of languages, and helped communities and organizations across the globe build their digital presence without vendor lock-in or license restrictions.
</p>

<p>🔮 The Road Ahead
</p>

<p>As we celebrate 23 years, we look forward to the future with the same energy that fueled Tiki's early days. From embracing emerging technologies to strengthening our governance and community engagement, Tiki’s journey is far from over.
</p>

<p>In a world increasingly shaped by proprietary ecosystems and fragmented tools, Tiki continues to prove that a unified, free, and Open Source platform is not only possible it’s powerful.
</p>

<p>So, from all of us in the Tiki community:
</p>

<p>🥳 Happy 23rd Anniversary, Tiki!
</p>

<p>Here’s to the next chapter of building, learning, and growing together.
</p>

<p> #TikiWiki #OpenSource #Groupware #BuiltToLast</p>
]]></summary>
    <published>2025-10-09T05:25:00+00:00</published>
    <updated>2025-10-09T05:25:00+00:00</updated>
    <link rel="alternate" type="text/html" href="https://wikisuite.org/blogpost17--Happy-23rd-Anniversary-Tiki-Wiki-CMS-Groupware"/>
    <id>https://wikisuite.org/blogpost17--Happy-23rd-Anniversary-Tiki-Wiki-CMS-Groupware</id>
  </entry>
  <entry>
    <title type="html"><![CDATA[WikiSuite will now support all major Linux distros]]></title>
    <summary type="html"><![CDATA[<p>To the WikiSuite community,
</p>

<p>Today, we announce that, going forward, WikiSuite will become supported on all major Linux distros (CentOS, Ubuntu, Debian, etc.) building on the experience gained with ClearOS. This has been happening for several months now, and it's time to make it official.
</p>

<p>Founded in 2011, WikiSuite has become <a href="The-most-comprehensive-and-integrated-Open-Source-enterprise-solution" title="The most comprehensive and integrated Open Source enterprise solution" class="wiki wiki_page">The most comprehensive and integrated Open Source enterprise solution</a>.
</p>

<p>Key components of WikiSuite started about a decade earlier, with Tiki Wiki CMS Groupware (2002) and Openfire (2002)
</p>

<p>The feature set already being very extensive, the WikiSuite leadership team decided the time had come to increase focus on deployability and manageability. This transition will manifest itself in two ways:
</p>
<ol><li> Make it easier to deploy WikiSuite on popular "Infrastructure as a Service" (IaaS) offerings. The main goal is to be agnostic to the service provider and maintain easy portability &mdash; AWS, MS Azure, Linode, Digital Ocean, etc.
<ul><li> Our primary focus is to collaborate with the Virtualmin/Webmin community. The code is here: <a class="wiki external" target="_blank" href="https://gitlab.com/wikisuite/virtualmin-installer/" rel="external">https://gitlab.com/wikisuite/virtualmin-installer/</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</li><li> We will further invest in <a class="wiki external" target="_blank" href="https://doc.tiki.org/Manager" rel="external">Tiki Manager</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span> to facilitate various use cases:
<ul><li> Make it easier to provide Tiki instances within a classic shared hosting scenario
</li><li> Advanced projects which require dev-qa-production workflow
</li><li> Etc.
</li></ul></li></ul></li><li> When appropriate and when it does not cause a vendor lock-in, we'll embark on a process to leverage  <a class="wiki external" target="_blank" href="https://en.wikipedia.org/wiki/Cloud_native_computing" rel="external">Cloud Native</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span> capabilities.
</li></ol><p>
</p>
<h2 class="showhide_heading" id="What_is_the_historical_context_here_"> What is the historical context&nbsp;here?<a href="#What_is_the_historical_context_here_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p>WikiSuite was founded in 2011. In February 2012, we chose ClearOS as our operating system and built several ClearOS apps.
</p>

<p>The goal was (and still is) to make a system which is fully self-hostable. Some of the early WikiSuite instances were running on repurposed old laptops!
</p>

<p>About ClearOS: ClearOS is a derivative of RHEL, with a great selection of tools and a great unified web admin interface. It eases server management and covers use cases such as Gateway and Networking...
</p>

<p>Although it's possible to convert a CentOS to a ClearOS, this is unsupported.
</p>

<h2 class="showhide_heading" id="What_is_changing_"> What is&nbsp;changing?<a href="#What_is_changing_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p>We will:
</p>
<ul><li> Expand support to other distros (Such as CentOS, Debian and Ubuntu) as per the <a class="wiki external" target="_blank" href="https://www.virtualmin.com/os-support/" rel="external">Virtualmin support policy</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>
</li><li> And cease support for ClearOS-specific apps (They are all Open Source and we'll welcome new maintainers)
</li></ul><p>So, for example: Openfire is supported, <a href="Why-Openfire" title="Why Openfire" class="wiki wiki_page">Why Openfire</a> but the Openfire app for ClearOS ( <a target="_blank" class="wiki external"  href="https://github.com/WikiSuite/app-openfire">https://github.com/WikiSuite/app-openfire<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a> ) is no longer supported. Each WikiSuite component will be installed as per their operating system (via regular packages .rpm/.deb, or Docker) with potential automation (ex.: via Bash/Ansible/etc. scripts).
</p>

<h2 class="showhide_heading" id="Won_t_this_mean_losing_some_functionality_"> Won't this mean losing some&nbsp;functionality?<a href="#Won_t_this_mean_losing_some_functionality_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p>In some cases, unfortunately, yes. Over time, we will reimplement the functionality in another way, aiming to support all main Linux distros.
</p>

<h2 class="showhide_heading" id="What_about_deprecation_of_CentOS_8_vs_CentOS_Stream_"> What about deprecation of CentOS 8 (vs CentOS&nbsp;Stream)?<a href="#What_about_deprecation_of_CentOS_8_vs_CentOS_Stream_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p>We will go along with what the Virtualmin community decides:
<br /><a class="wiki external" target="_blank" href="https://forum.virtualmin.com/t/centos-8-lifecycle-end-2021/108483" rel="external">https://forum.virtualmin.com/t/centos-8-lifecycle-end-2021/108483</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>
<h2 class="showhide_heading" id="Why_are_you_making_this_change_"> Why are you making this&nbsp;change?<a href="#Why_are_you_making_this_change_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p>We want to make it as easy as possible to adopt and deploy WikiSuite.
</p>

<p>Many organizations and hosting providers have a short list of supported operating systems. When ClearOS was not an option for them, we needed to set up WikiSuite components like Tiki Wiki CMS Groupware and Openfire. Sometimes on RHEL. Sometimes Ubuntu, etc. And even on <a href="How-to-install-WikiSuite-on-Windows-Server" title="How to install WikiSuite on Windows Server" class="wiki wiki_page">Windows</a>.
</p>

<p>So we are doing most of the work, but are not getting the benefits.
</p>

<p>Also, there is overhead to keeping apps updated. That diverts energy from adding features and improving the integration.
</p>

<p>Also, while some community users want to install locally, more want to install on cloud providers. Thus, we will make it easier.
</p>

<h2 class="showhide_heading" id="Should_this_have_been_done_since_the_beginning_"> Should this have been done since the&nbsp;beginning?<a href="#Should_this_have_been_done_since_the_beginning_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p>That is an interesting question. Since we can't go back in time and compare two universes, it's really just an opinion.
</p>

<p>Focusing on one distro provides many benefits: Predictability, standardization, lower complexity / overhead / etc. It's like speaking a common language. No question that selecting ClearOS has provided many benefits. However, in other cases, it has added extra work for little benefit; for example, the Elasticsearch app for ClearOS.
</p>

<h2 class="showhide_heading" id="Will_it_still_be_possible_to_run_WikiSuite_components_on_ClearOS_"> Will it still be possible to run WikiSuite components on&nbsp;ClearOS?<a href="#Will_it_still_be_possible_to_run_WikiSuite_components_on_ClearOS_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p>Yes, but without Virtualmin. The WikiSuite components (Tiki, Openfire, etc.) can run on all Linux distros so they can be installed on ClearOS (usually with the CentOS recipe). However it will be more of a manual process because there will no longer be ClearOS apps. So you install Tiki as you would any web app: <a class="wiki external" target="_blank" href="https://documentation.clearos.com/content:en_us:app_web_server" rel="external">https://documentation.clearos.com/content:en_us:app_web_server</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<h2 class="showhide_heading" id="Why_have_a_web_panel_"> Why have a web&nbsp;panel?<a href="#Why_have_a_web_panel_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p>If you are an experienced sysadmin, you may prefer to just install a fresh Linux and configure LAMP. We want a consistent recipe and to make it easier to manage servers. Virtualmin was selected to do this.
</p>

<h2 class="showhide_heading" id="How_will_you_replace_the_functionality_provided_by_ClearOS_"> How will you replace the functionality provided by&nbsp;ClearOS?<a href="#How_will_you_replace_the_functionality_provided_by_ClearOS_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p>
</p>
<h3 class="showhide_heading" id="Identity_Provider">1.1.1.  Identity&nbsp;Provider<a href="#Identity_Provider" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>ClearOS has a very nice integration of OpenLDAP. This is designed for a small organization context where each user is added by the Administrator. However, in an open community context, we also need self-serve capabilities (registration, change email, reset password, etc.) Tiki offers all this. And there is a recipe for SAML (to be improved &mdash; see <a class="wiki external" target="_blank" href="https://dev.tiki.org/SAML-SSO-Authentication" rel="external">https://dev.tiki.org/SAML-SSO-Authentication</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>).
</p>

<p>We will add any missing features to Tiki. As an example, here is a recipe for Tiki to be an identity provider to Openfire: <a href="How-to-install-Openfire-using-Tiki-for-its-userlist" title="How to install Openfire using Tiki for its userlist" class="wiki wiki_page">How to install Openfire using Tiki for its userlist</a>.
</p>

<h3 class="showhide_heading" id="Firewall_Dynamic_Firewall_and_2FA">1.1.2.  Firewall, Dynamic Firewall and&nbsp;2FA<a href="#Firewall_Dynamic_Firewall_and_2FA" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>ClearOS has a nice GUI to manage the firewall. And when an app is installed, it conveniently warns the server admin about ports to be opened.
</p>

<p><a target="_blank" class="wiki external"  href="https://www.clearos.com/products/clearos-editions/clearos-7-home/marketplace/network/Dynamic_Firewall">https://www.clearos.com/products/clearos-editions/clearos-7-home/marketplace/network/Dynamic_Firewall<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
<br /><a target="_blank" class="wiki external"  href="https://www.clearos.com/products/clearos-editions/clearos-7-home/marketplace/system/2FA_for_Webconfig">https://www.clearos.com/products/clearos-editions/clearos-7-home/marketplace/system/2FA_for_Webconfig<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
</p>

<p>We will soon release "Tiki Firewall" which will be an extra layer of protection over Tiki. Written in PHP, it will be usable with all distros:
<br /><a class="wiki external" target="_blank" href="https://doc.tiki.org/Firewall" rel="external">https://doc.tiki.org/Firewall</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<p>As for server management and 2FA, we use an Open Source distro-agnostic solution: <a href="MeshCentral" title="MeshCentral" class="wiki wiki_page">MeshCentral</a>.
</p>

<h3 class="showhide_heading" id="Attack_Detector_Fail2ban">1.1.3.  Attack Detector /&nbsp;Fail2ban<a href="#Attack_Detector_Fail2ban" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>ClearOS also has a nice app to detect and report attacks (a GUI on Fail2ban):
<br /><a class="wiki external" target="_blank" href="https://www.clearos.com/products/clearos-editions/clearos-7-home/marketplace/gateway/Attack_Detector" rel="external">https://www.clearos.com/products/clearos-editions/clearos-7-home/marketplace/gateway/Attack_Detector</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<p>We will use Fail2ban for Virtualmin:
<br /><a class="wiki external" target="_blank" href="https://doxfer.webmin.com/Webmin/Fail2Ban_Intrusion_Detector" rel="external">https://doxfer.webmin.com/Webmin/Fail2Ban_Intrusion_Detector</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<p>
</p>
<h3 class="showhide_heading" id="Domain_names_PHP_Apache_SSL_Let_s_Encrypt_multiple_version_of_PHP_MariaDB_MySQL_shared_hosting_use_case_">1.1.4.  Domain names / PHP / Apache / SSL / Let's Encrypt / multiple version of PHP / MariaDB / MySQL (shared hosting use&nbsp;case)<a href="#Domain_names_PHP_Apache_SSL_Let_s_Encrypt_multiple_version_of_PHP_MariaDB_MySQL_shared_hosting_use_case_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>ClearOS has a great tool to create websites and databases:
<br /><a class="wiki external" target="_blank" href="https://documentation.clearos.com/content:en_us:7_ug_web_server" rel="external">https://documentation.clearos.com/content:en_us:7_ug_web_server</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>
<br /><a class="wiki external" target="_blank" href="https://documentation.clearos.com/content:en_us:7_ug_mariadb" rel="external">https://documentation.clearos.com/content:en_us:7_ug_mariadb</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<p>And the WikiSuite project contributed:
<br /><a class="wiki external" target="_blank" href="https://news.clear.co.com/lets-encrypt-app-live-in-the-clearos-marketplace/" rel="external">https://news.clear.co.com/lets-encrypt-app-live-in-the-clearos-marketplace/</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>
<br /><a class="wiki external" target="_blank" href="https://news.clear.co.com/php-engines-app-now-live-in-the-clearos-marketplace/" rel="external">https://news.clear.co.com/php-engines-app-now-live-in-the-clearos-marketplace/</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<p>ClearOS is designed so that each project has its own virtual machine (which has many benefits). There is no strong segmentation between various websites on a same ClearOS server. Virtualization permits each ClearOS instance to have the proper resources allocated. The same is possible with Virtualmin. However, Virtualmin additionally permits to have multiple clients and projects on the same server with strict segmentation since its core business is the shared hosting use case.
<br /><a class="wiki external" target="_blank" href="https://www.virtualmin.com/documentation" rel="external">https://www.virtualmin.com/documentation</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<h3 class="showhide_heading" id="Elasticsearch">1.1.5.  Elasticsearch<a href="#Elasticsearch" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>We will deprecate <a target="_blank" class="wiki external"  href="https://github.com/WikiSuite/app-elasticsearch">https://github.com/WikiSuite/app-elasticsearch<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a> and <a target="_blank" class="wiki external"  href="https://github.com/WikiSuite/adminer-elasticsearch">https://github.com/WikiSuite/adminer-elasticsearch<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>, and use a standard upstream recipe for each distro (Docker, RPMs, etc.).
</p>

<p>Unfortunately, Elasticsearch is no longer Open Source:
</p>
<ul><li> <a target="_blank" class="wiki external"  href="https://www.elastic.co/blog/licensing-change">https://www.elastic.co/blog/licensing-change<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
</li><li> <a target="_blank" class="wiki external"  href="https://www.elastic.co/blog/license-change-clarification">https://www.elastic.co/blog/license-change-clarification<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
</li></ul><p>
<br />Thus, research is ongoing to pick an Open Source alternative: <a class="wiki external" target="_blank" href="https://avantech.net/Elasticsearch-Alternatives" rel="external">https://avantech.net/Elasticsearch-Alternatives</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<h3 class="showhide_heading" id="Openfire">1.1.6.  Openfire<a href="#Openfire" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>We will deprecate <a target="_blank" class="wiki external"  href="https://github.com/WikiSuite/app-openfire">https://github.com/WikiSuite/app-openfire<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a> and use a standard upstream recipe for each distro (Docker, RPMs, etc.).
</p>

<p>We already have:
</p>
<ol><li> <a href="How-to-install-Openfire-using-Tiki-for-its-userlist" title="How to install Openfire using Tiki for its userlist" class="wiki wiki_page">How to install Openfire using Tiki for its userlist</a>
</li><li> <a target="_blank" class="wiki external"  href="https://github.com/igniterealtime/openfire-tikitoken-plugin">https://github.com/igniterealtime/openfire-tikitoken-plugin<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
</li></ol><p>
</p>
<h3 class="showhide_heading" id="IMAP_and_SMTP_server">1.1.7.  IMAP and SMTP&nbsp;server<a href="#IMAP_and_SMTP_server" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>ClearOS has a very easy set up for email, using Postfix and Cyrus IMAP:
<br /><a class="wiki external" target="_blank" href="https://documentation.clearos.com/content:en_us:7_ug_imap" rel="external">https://documentation.clearos.com/content:en_us:7_ug_imap</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>
<br /><a class="wiki external" target="_blank" href="https://documentation.clearos.com/content:en_us:7_ug_smtp" rel="external">https://documentation.clearos.com/content:en_us:7_ug_smtp</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<p>Tiki has support for CalDAV and CardDAV, and integrated Cypht Webmail: <a class="wiki external" target="_blank" href="http://dev.tiki.org/Email-as-a-first-class-citizen" rel="external">http://dev.tiki.org/Email-as-a-first-class-citizen</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<p>Virtualmin is designed for shared hosting and has a mature email feature set, using Postfix and Dovecot. So we'll support the commonly used standard email protocols (SMTP and IMAP). As for <a href="JMAP" title="JMAP" class="wiki wiki_page">JMAP</a>, it's on <a class="wiki external" target="_blank" href="https://dovecot.org/pipermail/dovecot/2019-May/115972.html" rel="external">the roadmap for Dovecot</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>. Since this will likely take a while, we will explore using a <a class="wiki external" target="_blank" href="https://github.com/barnslig/jmap-proxy" rel="external">Proxy</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<p>We have also started experimenting for email users to be provided by Tiki (like we can do for Openfire): <a class="wiki external" target="_blank" href="https://gitlab.com/fabiomontefuscolo/kube-tiki/-/commit/e5d6ef06f036ab5307825cfbb1598a15cb998123" rel="external">https://gitlab.com/fabiomontefuscolo/kube-tiki/-/commit/e5d6ef06f036ab5307825cfbb1598a15cb998123</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
<br />So Tiki will be able to create ad hoc email addresses via the Virtualmin API. Example: create a mail address for a project.
</p>

<h3 class="showhide_heading" id="Syncthing">1.1.8.  Syncthing<a href="#Syncthing" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>We will deprecate <a target="_blank" class="wiki external"  href="https://github.com/WikiSuite/app-syncthing">https://github.com/WikiSuite/app-syncthing<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a> and use a standard upstream for each distro (Docker, RPMs, etc.).
</p>

<p>What we have: <a href="How-to-install-Syncthing-on-Virtualmin" title="How to install Syncthing on Virtualmin" class="wiki wiki_page">How to install Syncthing on Virtualmin</a>.
</p>

<p>Our goals: <a href="Syncthing-in-WikiSuite" title="Syncthing in WikiSuite" class="wiki wiki_page">Syncthing in WikiSuite</a>.
</p>

<h3 class="showhide_heading" id="Tiki_Manager">1.1.9.  Tiki&nbsp;Manager<a href="#Tiki_Manager" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>We will deprecate <a target="_blank" class="wiki external"  href="https://gitlab.com/tikiwiki/app-tiki-manager">https://gitlab.com/tikiwiki/app-tiki-manager<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a> and focus on a distro-agnostic approach. We will investigate via <a target="_blank" class="wiki external"  href="https://packagist.org/">https://packagist.org/<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a> or Docker or just create .rpm/.deb.
</p>

<p>Tiki Manager will detect if it's running within Virtualmin and offer appropriate paths as defaults.
</p>

<h3 class="showhide_heading" id="Monitoring_and_Logs">1.1.10.  Monitoring and&nbsp;Logs<a href="#Monitoring_and_Logs" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>This aspect is still to be determined. Candidates include:
</p>
<ul><li> Zabbix
</li><li> <a target="_blank" class="wiki external"  href="https://github.com/netdata/netdata">https://github.com/netdata/netdata<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
</li><li> Explore more with the Virtualmin community
</li><li> See also: <a target="_blank" class="wiki external"  href="https://dev.tiki.org/Monitoring">https://dev.tiki.org/Monitoring<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
</li></ul><p>
</p>
<h3 class="showhide_heading" id="Kimchi_and_KVM">1.1.11.  Kimchi and&nbsp;KVM<a href="#Kimchi_and_KVM" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>We will deprecate <a target="_blank" class="wiki external"  href="https://github.com/WikiSuite/app-kimchi">https://github.com/WikiSuite/app-kimchi<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a> and use a standard upstream for each distro (Docker, RPMs, etc.).
</p>

<h3 class="showhide_heading" id="FusionPBX_and_FreeSWITCH">1.1.12.  FusionPBX and&nbsp;FreeSWITCH<a href="#FusionPBX_and_FreeSWITCH" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>We had not created an app yet, so nothing to deprecate. We will use and use a standard upstream for each distro (Docker, RPMs, etc.).
</p>

<h3 class="showhide_heading" id="Xibo">1.1.13.  Xibo<a href="#Xibo" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>We had not created an app yet, so nothing to deprecate. We will use a standard upstream for each distro (Docker, RPMs, etc.).
</p>

<p>
<br />Please keep informed and participate to the the developments here:
<br /><a target="_blank" class="wiki external"  href="https://gitlab.com/groups/wikisuite/-/activity">https://gitlab.com/groups/wikisuite/-/activity<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
</p>

<p>Thanks!
</p>

<p>Marc Laporte, founder</p>
]]></summary>
    <published>2021-07-20T04:06:00+00:00</published>
    <updated>2021-07-20T04:06:00+00:00</updated>
    <link rel="alternate" type="text/html" href="https://wikisuite.org/blogpost16-WikiSuite-will-now-support-all-major-Linux-distros"/>
    <id>https://wikisuite.org/blogpost16-WikiSuite-will-now-support-all-major-Linux-distros</id>
  </entry>
  <entry>
    <title type="html"><![CDATA[WikiSuite just received a grant from Grant for the Web to integrate Coil Content Monetization and ILP (Interledger) payments]]></title>
    <summary type="html"><![CDATA[<p><img src="dl985?display"  width="1010" height="720" alt="Grant   Congrats2" class="regImage pluginImg985 img-fluid" />
</p>

<p>In April 2020, Grant for the Web announced a public call for web monetization project proposals eligible for one of three levels of funding: Spark, Mid-Level, and Flagship. In less than two months, applications were received from 286 applicants. The applications were analyzed and evaluated by an independent and diverse panel of judges.
</p>

<p>We at WikiSuite are delighted to have received a Mid-Level grant for the submission "Tiki ILP Integration & Monetization" as it will accelerate our integration of ILP and Coil web monetization features into the Tiki Wiki CMS Groupware component of WikiSuite.
</p>

<p>ILP — Interledger protocol — is an Open Source technology for connecting all types of ledgers, from e-wallets to blockchains. The purpose is to smoothly execute financial transactions with anyone, regardless of the location or currency or transaction amount. Interledger, or as one may call it, "The new Internet of Money," allows you to receive money from any ledger, without setting up accounts in multiple systems.
</p>

<p>Coil — a new approach to web monetization that we are also implementing in Tiki — replaces paid advertisements with the ability to "experience web monetized content in your browser while supporting sites you love in real time." This is a perfect solution for every company or organization that may have had issues with being treated equitably in a marketplace stifled by corporate domination. And with Coil, web content can be monetized without having to display advertisements from other companies on our websites, mobile apps or videos.
</p>

<p>WikiSuite, "the most comprehensive and integrated Free / Libre / Open Source enterprise software suite," is especially suited to knowledge-centric organizations and offers most of the data and information management features all organizations need. This mid-level grant will facilitate the integration of Interledger and Coil with WikiSuite components, thus enhancing WikiSuite’s capabilities for website monetization and sending/receiving payments via Interledger. As Open Source software, this enhanced multi-component suite will of course be available to the general public at no cost. And organizations using WikiSuite for their Information Management Systems will be able to deploy this new monetization and payments functionality.
</p>

<p>We are overjoyed to be among the pioneers of these Open Source monetization technologies alongside outstanding established organizations, and very pleased to be granted this opportunity.
</p>

<p><a target="_blank" class="wiki external"  href="https://www.grantfortheweb.org/blog/2020-mid-grantees">https://www.grantfortheweb.org/blog/2020-mid-grantees<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
</p>

<p>Stay tuned for more updates from us!</p>
]]></summary>
    <published>2020-10-15T18:43:00+00:00</published>
    <updated>2020-10-15T18:43:00+00:00</updated>
    <link rel="alternate" type="text/html" href="https://wikisuite.org/blogpost15-WikiSuite-just-received-a-grant-from-Grant-for-the-Web-to-integrate-Coil-Content-Monetization-and-ILP-Interledger-payments"/>
    <id>https://wikisuite.org/blogpost15-WikiSuite-just-received-a-grant-from-Grant-for-the-Web-to-integrate-Coil-Content-Monetization-and-ILP-Interledger-payments</id>
  </entry>
  <entry>
    <title type="html"><![CDATA[Budgeting practices for major software initiatives by Waldo Jaquith (18F) at the Michigan Senate Appropriations Committee.]]></title>
    <summary type="html"><![CDATA[<p>Filmed on February 26th, 2020
<br /><iframe src="//www.youtube.com/embed/g-h6CtSwk30?" frameborder="0" width="425" height="350" allowfullscreen="" referrerpolicy="strict-origin-when-cross-origin"></iframe>
</p>

<p>Here is the handbook mentioned in the video:
<br /><a target="_blank" class="wiki external"  href="https://18f.gsa.gov/2019/08/05/budgeting-handbook/">https://18f.gsa.gov/2019/08/05/budgeting-handbook/<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
</p>

<p>You can join the discussion here: <a target="_blank" class="wiki external"  href="https://twitter.com/waldojaquith/status/1233134423710871553">https://twitter.com/waldojaquith/status/1233134423710871553<span class="icon icon-link-external fas fa-external-link-alt "   ></span></a>
</p>

<p>See also
</p>
<ul><li> <a class="wiki external" target="_blank" href="https://www.cigref.fr/cigref-report-open-source-alternative-major-it-providers-en-2018" rel="external">Cigref published a report “Open source, an alternative to major IT providers”</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span></li></ul>]]></summary>
    <published>2020-02-28T10:13:00+00:00</published>
    <updated>2020-02-28T10:13:00+00:00</updated>
    <link rel="alternate" type="text/html" href="https://wikisuite.org/blogpost14-Budgeting-practices-for-major-software-initiatives-by-Waldo-Jaquith-18F-at-the-Michigan-Senate-Appropriations-Committee"/>
    <id>https://wikisuite.org/blogpost14-Budgeting-practices-for-major-software-initiatives-by-Waldo-Jaquith-18F-at-the-Michigan-Senate-Appropriations-Committee</id>
  </entry>
  <entry>
    <title type="html"><![CDATA[Get the most out of your digital signage - Manage it with XIBO]]></title>
    <summary type="html"><![CDATA[<p><img src="dl841?display"  width="1103" height="394" alt="Xibo Blog" class="regImage pluginImg841 img-fluid" />
</p>

<p>Digital signage is a form of electronic display that shows information, advertising and other messages. Digital signs (such as LCD, LED, and plasma displays, and projected images) can be found in public and private environments such as retail stores and corporate buildings. Nowadays digital signage plays a vital role in our industry as it is replacing traditional printed catalogs, menus and product listings in restaurants, shopping centers, and other community places.
</p>

<p>Most of the time people use a USB flash drive to feed individual screens, to display the desired media and, whenever they have to update the media, they manually update the contents of the USB flash drive and plug it back in. This can be very inconvenient when managing a large number of displays and especially when you have to manage displays at multiple locations. That’s where XIBO can help manage all of your digital displays with a centralized media management system equipped with scheduling and other features. With XIBO you can keep all your digital displays up to date automatically.
</p>

<h2 class="showhide_heading" id="What_is_XIBO_">What is&nbsp;XIBO?<a href="#What_is_XIBO_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p>Xibo is a powerful open source digital signage platform with a web-based content management system and Windows, Android and webOS signage player applications. Xibo helps you to create your dynamic content for digital signage.
</p>

<div class="card bg-light"><div class="card-body">
<p>Xibo enables the user to upload media and arrange it in a layout which is then scheduled for one or more authorized displays.
</p>
</div></div>
<p>
<br />The interface of this powerful software is very simple and user-friendly and based on five core points:
</p>
<ol><li>User Control
</li><li>Display Management
</li><li>Layouts (Screen Sizes)
</li><li>Media Management
</li><li>Scheduling Media
</li></ol><p>
<br />This image shows how XIBO works:
</p>

<p><img src="dl297?display"  width="792" height="612" alt="Simple Network" class="regImage pluginImg297 img-fluid" />
</p>

<h2 class="showhide_heading" id="Xibo_Introductory_Video">Xibo Introductory&nbsp;Video<a href="#Xibo_Introductory_Video" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p><iframe src="//www.youtube.com/embed/gncIbFlEBZI?&fs=1&rel=0" frameborder="0" width="425" height="350" allowfullscreen="true" referrerpolicy="strict-origin-when-cross-origin"></iframe>
</p>

<h1 class="showhide_heading" id="What_are_the_benefits_of_using_XIBO_">What are the benefits of using&nbsp;XIBO?<a href="#What_are_the_benefits_of_using_XIBO_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h1>
<ol><li>Open source (FREE)
</li><li>User friendly interface web interface
</li><li>Easy to make media layouts
</li><li>Create and change your content and it displays dynamically
</li><li>Schedule upcoming content
</li><li>Control and design your content from anywhere using a web browser through a CMS
</li></ol><p>
</p>
<h2 class="showhide_heading" id="Where_to_get_XIBO_">Where to get&nbsp;XIBO?<a href="#Where_to_get_XIBO_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h2>
<p><a class="btn btn-absolute_path " target="" data-role="button" data-inline="true"  title="Download XIBO" href="https://xibo.org.uk/cms"><span class="icon icon-download fas fa-download "   ></span> Download XIBO</a>
</p>

<p></p>
]]></summary>
    <published>2019-03-27T19:55:00+00:00</published>
    <updated>2019-03-27T19:55:00+00:00</updated>
    <link rel="alternate" type="text/html" href="https://wikisuite.org/blogpost13-Get-the-most-out-of-your-digital-signage-Manage-it-with-XIBO"/>
    <id>https://wikisuite.org/blogpost13-Get-the-most-out-of-your-digital-signage-Manage-it-with-XIBO</id>
  </entry>
  <entry>
    <title type="html"><![CDATA[Affirmation of the Open Source Definition]]></title>
    <summary type="html"><![CDATA[<p><img src="dl821?display"  width="1103" height="394" alt="Osi Blog" class="regImage pluginImg821 img-fluid" />
</p>

<p>In 1799 the kilogram was defined as the mass of a litre of water. In 1889, metal cylinders of the precise identical mass were created as reference objects.
</p>

<p>In the hundreds of years since, the physical nature of the metal caused those cylinders no longer to reflect the identical mass as defined. In order to ensure the integrity of a vital unit of measurement, the kilogram was redefined as the same mass but simply expressed in terms of fundamental and invariable physical constants.
</p>

<p>Without this single, standard definition of this or other fundamental units, commerce as we know it would not be possible. There is no trust in a world where anyone can invent their own definition for units, items, and concepts on which others rely, and without trust there is no community, no collaboration, and no cultural or technological development.
</p>

<p>In exactly the same way, the term "open source software" was coined in 1998 as software that provides a set of precise freedoms and benefits, including but not limited to the freedoms to run, study, redistribute, and improve the software on which you rely . These benefits are codified in the Open Source Definition (OSD), which is based on the Debian Free Software Guidelines. The Open Source Initiative, its members, affiliates, and sponsors, promote and protect this fundamental definition through software license review and approval.
</p>

<p>Without this single, standard definition of "open source," software development as we know it would not be possible. There is no trust in a world where anyone can invent their own definition for open source, and without trust there is no community, no collaboration, and no innovation.
</p>

<p>Recently there have been efforts to undermine the integrity of open source by claiming there is no need for a single, authoritative definition. These efforts are motivated by the interests of a few rather than the benefit of all, and are at odds with the principles that have so demonstratively served us  well in the past decades. If allowed to continue, these efforts will erode the trust of both users and contributors, and hinder the innovation that is enabled by open source software, just as surely as having multiple definitions of a kilogram would erode and undermine commerce.
</p>

<p>We, the undersigned, affirm our commitment to the Open Source Definition. We acknowledge its importance to the development of the software on which we rely to operate our businesses and organisations. We pledge to guard and maintain the Open Source Definition and we recognize the Open Source Initiative as the steward of the Open Source Definition.
</p>

<p>Open Source Initiative, Board of Directors
</p>

<p>American International University West Africa, The Gambia
<br />Apereo Foundation
<br />Association Francophone des Utilisateurs de Logiciels Libres
<br />Associazione LibreItalia
<br />BigBlueButton, Inc.
<br />California Association of Voting Officials
<br />Creative Commons
<br />Debian Project
<br />DemocracyLab
<br />Drupal Association
<br />Eclipse Foundation
<br />Journal of Open Source Software
<br />Kaiyuanshe
<br />KDE e.V.
<br />Linux Australia, Inc.
<br />Linux Professional Institute
<br />LinuxFest Northwest
<br />Mozilla Foundation
<br />New Zealand Open Source Society
<br />Odoo Community Association
<br />Open Source Matters, Inc. (Joomla)
<br />Open Source Sweden
<br />OpenProject GmbH
<br />OW2 Consortium
<br />Plone Foundation
<br />Powering Potential
<br />Puerto Rico Python Interest Group
<br />Python Software Foundation
<br />Rensselaer Center for Open Source
<br />Snowdrift.coop
<br />sysarmy
<br />The Document Foundation
<br />The Perl Foundation
<br />Tiki Wiki CMS Groupware
<br />TYPO3 Association
<br />Xerte Project
</p>

<p>Note: This post is originally published by <a class="wiki external" target="_blank" href="https://opensource.org/node/966" rel="external">Open Source Initiative</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span></p>
]]></summary>
    <published>2019-02-06T01:08:00+00:00</published>
    <updated>2019-02-06T01:08:00+00:00</updated>
    <link rel="alternate" type="text/html" href="https://wikisuite.org/blogpost12-Affirmation-of-the-Open-Source-Definition"/>
    <id>https://wikisuite.org/blogpost12-Affirmation-of-the-Open-Source-Definition</id>
  </entry>
  <entry>
    <title type="html"><![CDATA[Tiki 19 - Keeping you ahead]]></title>
    <summary type="html"><![CDATA[<p><img src="dl816?display"  width="1103" height="394" alt="Blog Images1" class="regImage pluginImg816 img-fluid" />
</p>

<p><a class="wiki external" target="_blank" href="https://tiki.org/Download" rel="external">Tiki 19</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span> was recently released by the Tiki Community (<a class="wiki external" target="_blank" href="https://tiki.org" rel="external">Tiki.org</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>). A number of significant feature upgrades insure that Tiki remains future-proof and stays current with rapidly advancing technology. Key discussions were held among Tiki developers during <a class="wiki external" target="_blank" href="http://wikisuite.org/Unconference1" rel="external">WikiSuite Unconference 1</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span> to hone the details of this release and guide the ongoing progress of the project.
</p>

<p>Major upgrades in this version include an update from Bootstrap 3 to 4, which is good news for front end developers who can now take advantage of Bootstrap 4 power, such as SCSS pre-compiling and Flexbox layout, in Tiki templates and pages. Much attention was paid to the front end aspects of the project in this release, with Font Awesome updated from 4 to 5, Reveal.js slideshow integrated along with PDF export, menus enhanced with SmartMenus, and much more. The presentation features have been enhanced to enable building powerful and mobile-friendly displays such as <a class="wiki external" target="_blank" href="https://wikisuite.org/tiki-slideshow.php?page=Presentation-Defi-Montreal-2018-12-04&amp;fbclid=IwAR10ILEgWHCrFF2tP1KhJ9D_1iSxl0KLBm671gMJixRAWYgWGfVRpNr7UyU" rel="external"> this one</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<p>Key new features include <a class="wiki external" target="_blank" href="https://doc.tiki.org/PluginDiagram" rel="external">Plugin Diagram</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span> for easy building of flowcharts. XMPP chat rooms can now be embedded in a wiki page. Out of the box special-layout landing pages can be quickly created by using <a class="wiki external" target="_blank" href="https://doc.tiki.org/PluginLayout" rel="external">Plugin Layout</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span> in a wiki page. For a complete list of changes, please see <a class="wiki external" target="_blank" href="https://doc.tiki.org/Tiki19" rel="external">Tiki 19</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<p>Tiki 19.x is a Standard Term Support (STS) version and will be supported until Tiki 20.1 is released.
</p>
]]></summary>
    <published>2018-12-21T10:52:00+00:00</published>
    <updated>2018-12-21T10:52:00+00:00</updated>
    <link rel="alternate" type="text/html" href="https://wikisuite.org/blogpost11-Tiki-19-Keeping-you-ahead"/>
    <id>https://wikisuite.org/blogpost11-Tiki-19-Keeping-you-ahead</id>
  </entry>
  <entry>
    <title type="html"><![CDATA[WikiSuite - the business operating system]]></title>
    <summary type="html"><![CDATA[<p><img src="dl649?display"  width="1103" height="394" alt="Wikisuite Bos" class="regImage pluginImg649 img-fluid" />
</p>

<p>WikiSuite is a modern enterprise suite with such broad and deep capabilities that it can truly be called a "business operating system" &mdash; an enterprise suite  that encompasses most of the business processes found in typical diversified companies and organizations. To meet its objectives,  every enterprise, large or small, requires a digital platform strategy that addresses its business and IT needs.  WikiSuite is composed of specialized technologies designed precisely to meet the digital needs of today's organizations.
</p>

<p>Here is an overview of WikiSuite - the business operating system.
</p>

<h3 class="showhide_heading" id="Underlying_OS"> Underlying OS<a href="#Underlying_OS" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>WikiSuite runs on a Linux-based open source operating system especially built for server, network and gateway systems. It can be installed to power your local intranet and/or your presence on the Internet, depending on your connectivity requirements. It provides a secure platform for all of the WikiSuite applications. For details, please visit <a class="wiki external" target="_blank" href="https://wikisuite.org/OS-and-Network" rel="external">https://wikisuite.org/OS-and-Network</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<h3 class="showhide_heading" id="Communication"> Communication<a href="#Communication" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>One of the first and most basic requirements of any business is effective communication, through multiple channels and in real time. WikiSuite provides solutions from traditional email to advanced video conferencing. Find out more about WikiSuite <a class="wiki external" target="_blank" href="http://wikisuite.org/Chat-and-Video-Conference" rel="external"> Chat and Video Conferencing</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span> and <a class="wiki external" target="_blank" href="http://wikisuite.org/Email-and-Calendar" rel="external">Email and Calendar</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span> features.
</p>

<h3 class="showhide_heading" id="Collaboration"> Collaboration<a href="#Collaboration" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>Teams with a superior ability to collaborate and integrate naturally work more smoothly and produce better results. WikiSuite offers features ranging from automated file syncing to real-time collaborative content development for your teams in a secure and controlled environment. With WikiSuite, you can set up user group and category areas to provide appropriate user access to specific segments of the system. Multiple group and object-level user rights enable the management of many people in the system.
</p>

<h3 class="showhide_heading" id="Knowledge_Sharing"> Knowledge Sharing<a href="#Knowledge_Sharing" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>Information created can be shared by setting up public and private web portals. WikiSuite builds websites equipped with modern features such as a CMS (for news and announcements), blogs, forums, e-commerce solutions and more. For an extensive list of the WikiSuite web application features, please visit <a class="wiki external" target="_blank" href="https://doc.tiki.org/Features" rel="external">https://doc.tiki.org/Features</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<h3 class="showhide_heading" id="Business_Processes"> Business Processes<a href="#Business_Processes" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>WikiSuite can help you design and control your business operations management. Optimize your performance with centralized and integrated management features. No matter if it's manufacturing, retail, marketing or research, or other field, WikiSuite offers flexible tools and technologies to manage and improve processes with statistical data and other information. Analyze and make better decisions informed by actual data available in real time. Find out more at <a class="wiki external" target="_blank" href="http://wikisuite.org/BPM-and-Analytics" rel="external">http://wikisuite.org/BPM-and-Analytics</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>.
</p>

<p>Choosing the right technologies for any organization is a critical decision. All WikiSuite apps are industry-leading open source technologies and are being actively developed by their respective teams and communities. The WikiSuite team itself works directly with other relevant open source projects and brings them together within the WikiSuite platform as the most comprehensive and integrated Free / Libre / Open Source enterprise software suite.
</p>

<h3 class="showhide_heading" id="What_can_this_business_operating_system_do_for_you_"> What can this business operating system do for&nbsp;you?<a href="#What_can_this_business_operating_system_do_for_you_" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>Once configured and deployed for your organization, it will become an invaluable and important asset for your organization. Here are some abilities you have with WikiSuite that make it the best option for any small or medium organization, especially one that is knowledge-centered.
</p>

<ul><li> Take advantage of all the benefits of100% open source software.
</li><li> Keep control of your data and manage it securely.
</li><li> Optimize and streamline your business.
</li><li> Build your business knowledge base.
</li><li> Save hardware and software costs to do all that WikiSuite does.
</li><li> Take comfort in the availability of paid support and management if needed.
</li></ul><p>
</p>
<h3 class="showhide_heading" id="Where_we_are_headed">Where we are&nbsp;headed<a href="#Where_we_are_headed" class="heading-link"><span class="icon icon-link fas fa-link "   ></span></a></h3>
<p>
<br />WikiSuite is working directly with the teams behind the spectacular open source systems integrated with it. Forming a unique set of features and tools to manage data in any organization. Founded in 2011, WikiSuite is the most comprehensive and integrated open source enterprise suite available today for Free. Our mission is to empower organizations better manage, secure and use their information, to become data-driven, and achieve their optimal performance.
</p>

<p>Getting started &mdash; :  <a class="wiki external" target="_blank" href="http://wikisuite.org/How-to-install-WikiSuite" rel="external">How to Install WikiSuite</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>
</p>

<p>Do get in touch with us, comment or contact us, and we will be glad to assist you.
</p>
]]></summary>
    <published>2018-09-22T19:32:00+00:00</published>
    <updated>2018-09-22T19:32:00+00:00</updated>
    <link rel="alternate" type="text/html" href="https://wikisuite.org/blogpost9-WikiSuite-the-business-operating-system"/>
    <id>https://wikisuite.org/blogpost9-WikiSuite-the-business-operating-system</id>
  </entry>
  <entry>
    <title type="html"><![CDATA[Now you can call into an online video conference with a phone]]></title>
    <summary type="html"><![CDATA[<p><img src="dl636?display"  width="1103" height="394" alt="Jitsi Call" class="regImage pluginImg636 img-fluid" />
</p>

<p>WikiSuite focus on team connectivity in real time using top open source Jitsi Meet. The new feature a participant can join the conference by calling to a phone number and provide a code to connect. That’s not all, you can even call out to a person and connect him in the conference call.
</p>
<table class="wikitable table table-striped table-hover"><tr><td class="wikicell" ><img src="dl635?display"  width="707" height="578" alt="Screenshot1" class="regImage pluginImg635 img-fluid" /></td><td class="wikicell" ><img src="dl634?display"  width="550" height="318" alt="Screenshot3" class="regImage pluginImg634 img-fluid" /></td></tr></table>
<p>
<br />Jitsi Meet video conferencing solutions is already packed with powerful features and now it is even more flexible to accept participants over a phone line. It will help professionals traveling and having no internet access for any reason to join online meetings.
</p>

<p><strong>Some other key features of WikiSuite Jitsi Meet video conferences are as under:</strong>
</p>

<ul><li> Share desktop presentations and more
</li><li> Invite users to conferences with a simple web URL
</li><li> No desktop software required, completely web based
</li><li> Integrated chat in the video conferences
</li><li> Administration control to mute or ban users
</li></ul><p>
<br />Fully encrypted information, makes Jitsi Meet conferences secure and available round the clock in a few clicks. Try it out today at <a class="wiki external" target="_blank" href="https://meet.jit.si/" rel="external">Jitsi Meet</a><span class="icon icon-link-external fas fa-external-link-alt "   ></span>
</p>

<p></p>
]]></summary>
    <published>2018-08-15T22:01:00+00:00</published>
    <updated>2018-08-15T22:01:00+00:00</updated>
    <link rel="alternate" type="text/html" href="https://wikisuite.org/blogpost6-Now-you-can-call-into-an-online-video-conference-with-a-phone"/>
    <id>https://wikisuite.org/blogpost6-Now-you-can-call-into-an-online-video-conference-with-a-phone</id>
  </entry>
</feed>
