lorinab

I get the pointthat some might consider this spamming marketing bs, but in the same time I'd like to underline some aspects: - a lot of us are currently speaking about EU alternatives and OSS - a lot of the discussions are very general and not talking about the actual existing tools - we expect open source to be free to access and use but maintained and developed at the same standards as proprietary tools with (unlimited, by comparison) budgets - if someone talks about alternatives, promoting a webinar or a resource, they are flagged for it (as in my case) For full disclosure: Yes, I do work at XWiki and we do create webinars on a regular basis to educate people and promote our latest developments, updates, and improvements. If someone finds the information useful, they can join the free webinar, ask questions, find out more about our work. If someone wants to support us, they can share the link to a friend or a colleague which might use the information. If someone finds this irrelevant, they can just pass by and keep scrolling to something that appeals their interest.

XWiki and OpenProject are hosting a webinar on 24 June at 15:00 CET about using the two tools together as an open-source alternative stack to Atlassian.

The session will cover:

XWiki as an alternative to Confluence for structured knowledge management and documentation OpenProject as an alternative to Jira for project management deployment options, including cloud, on-premises, and private cloud what teams should consider when moving away from Confluence and Jira how to preserve knowledge, project context, history, and long-term data control

Need a privacy-focused alternative for collaborative work?

Many people care about privacy, but still rely on mainstream tools for shared documents, notes, forms, and planning. That usually means trusting a provider with access to your content and data.

This webinar will show you a different approach.

CryptPad is an open-source, end-to-end encrypted collaboration suite. It lets you work with others online in real time, while keeping your data private.

In this session, you will see how CryptPad works, what you can do with it, and why it is a strong option for individuals or organizations looking for a secure, privacy-focused online office suite.

You will leave with a practical understanding of encrypted collaboration and why CryptPad is the right fit for your everyday needs.

Ludovic Dubost (XWiki CEO, 20 years building open source in Europe without VC funding) submitted a response to the EU's consultation on their European Open Digital Ecosystem Strategy. The core tension: the EU's framing of open source as sovereignty infrastructure is actually correct. The incentive structure underneath it is not. Public procurement still optimizes for lowest bid today, not long-term sustainability. Maintenance, security patches, and reliability work get treated as "community effort" — right up until something breaks and suddenly it's critical infrastructure again. Meanwhile, regulatory compliance costs hit small European maintainers disproportionately hard compared to large vendors who can absorb them. The article makes a few concrete proposals: procurement criteria that reward contribution and sustainability, multi-year funding that reflects how maintenance actually works, and addressing the bundling/lock-in economics that make switching away from proprietary stacks artificially expensive. No ideology here, just 20 years of operational reality about what happens when you try to build and sustain open-source infrastructure in Europe without external investors covering the gap. Curious whether others building in this space see the procurement angle as the main lever, or whether the regulatory burden piece is the bigger friction.

We published an article on why internal documentation matters and how to build it properly: https://xwiki.com/en/Blog/internal-documentation-best-practi... The core issue: "later" usually means "never." Teams lose institutional knowledge, onboarding takes 3x longer than it should, and people keep making the same mistakes because nobody wrote down what worked. What the article covers:

Why documentation decay is structural, not cultural Faster onboarding, fewer repeated errors, better handoffs How to build documentation that survives team turnover Technical architecture that prevents fragmentation

We're also running a webinar (Feb 25, 16:00 CET) on the technical side: structuring, maintaining, and scaling documentation systems using XWiki (LGPL, built since 2004). Live Q&A included.

Running a technical session on why documentation systems fragment at scale and what actually prevents it. The problem: Most tools optimize for writing, not surviving. After 3-4 years, you get 20-30% broken links, orphaned pages, and teams asking "where did we document that?" Navigation breaks around 1k pages because hierarchies reflect how one person thought about the problem in 2022, not how new people need to find it in 2026. What works: Structured content with metadata (so you can rebuild navigation without rewriting), explicit ownership and review cycles (treat docs like code), and content/presentation separation (because how you navigate should evolve as the org grows). I'll cover the technical architecture using XWiki as the reference (LGPL, built since 2004, handles 100k+ page deployments). Real examples: University of Lorraine migrated 145k pages with full history, KIT moved 9,431 pages from Confluence. For: DevOps/sysadmin folks dealing with runbooks, internal wikis, or infrastructure docs that need to outlive team turnover. Free webinar, recording posted after: https://xwiki.com/en/webinars/XWiki-as-a-documentation-tool Interested in what others have seen work at this scale. What's your approach for keeping technical docs usable after years and multiple people leaving?

I work at XWiki, and we’ve been getting a lot of questions from teams that need to stay on-prem after Atlassian Data Center’s end of life. Together with OpenProject, we’ve built a setup that covers most Confluence + Jira use cases, fully open-source and self-hostable.

Next week, we’re doing a live session to show how migrations work, what tools we use for importing spaces, issues, and attachments, and what still needs improvement.

If you’re running on-prem or testing other open stacks after Atlassian, I’d be interested to hear what approaches you’ve tried.

The court will move its internal work environment to Open Desk, a German-developed open source software

For teams looking to stay on-prem or move off Atlassian’s stack, we’ve been working on integrating XWiki (for structured documentation) and OpenProject (for project management).

Both are open-source and can be self-hosted, with integrations for linking tasks, requirements, and project docs. We’re hosting a live demo + Q&A on Nov 19 showing how it works in practice.

[For full disclosure] I’m part of the XWiki team, and I'd be happy to answer any questions about this.

Together, XWiki and OpenProject provide a powerful open-source alternative to Atlassian’s Confluence and Jira. XWiki delivers a flexible, extensible knowledge management platform that serves as a true alternative to Confluence in collaborative documentation and team knowledge sharing. When it comes to OpenProject, its full-featured project management and issue tracking capabilities act as a strong Jira alternative. This partnership will offer organizations an integrated, open-source stack. It's a privacy-respecting, vendor-neutral solution for teams seeking to move away from proprietary tools without compromising on functionality or user experience.

The Historical Dictionary of Switzerland runs their entire multilingual encyclopedia (all 36,500+ articles across 4 languages) on XWiki. This is more than a customized wiki. It’s a platform that supports multilingual publishing, complex editorial workflows, Jira integration, and fast content discovery. All built on open-source software, developed in Europe.

The Historical Dictionary of Switzerland (HLS) needed to move beyond outdated tools, tangled workflows, and rigid systems. They made the switch to a flexible, open solution, and they’re sharing what that looked like.

This release introduces important improvements for the definition of wiki macro parameters and provides a new mechanism for faster macro execution. It also contains a redefinition of the real-time editing toolbar for better user experience. Further, it is now possible for users to resize the panel columns on the right and left of the content. This release contains security fixes, with the highest severity being 9.3/10.

Could part of this budget be redirected toward Free/Libre and Open-Source Software (FLOSS) to support national digital sovereignty?

With digital transformation accelerating, your organization’s control over its data and workflows is more critical than ever. While many collaborative platforms seem convenient, they often come at a steep price: vendor lock‑in, a one-size-fits-all approach where customization and deployment are limited, and data management practices remain unclear.

XWiki offers a different approach. It offers a flexible, open-source platform that you can shape to fit your company's specific workflows and security requirements. It puts you in control.

This is indeed obvious for weeks, no questions here. However, the even more accelerated developments in the last 2 weeks, as well as what happened in France with the Ministry of Education opting for a Microsoft solution, even if there are so many good French options out there (Suite Hexagonne to name at least one), made it even more obvious and stringent.

"Europe loves to talk about sovereignty but keeps handing its digital future to American companies. If we’re serious about this, we need to stop outsourcing our entire tech stack to Silicon Valley." Ludovic Dubost, CEO of XWiki

You can also try https://tuta.com/ and see if it works for you.

Most online collaboration tools ask you to trust them with your data. Google Docs and Microsoft 365 store your files on their servers, scan your content, and build profiles on users. CryptPad does the opposite. It’s a real-time document editor where everything is encrypted—only you and your team can see what you write. Not even the server can read your files.

Now, we’re bringing that same privacy-first approach to businesses with CryptPad Enterprise. It’s a self-hosted, end-to-end encrypted alternative to Big Tech’s office suites, designed for teams that care about privacy, security, and data sovereignty. With governments and companies across Europe looking for ways to move away from US-based cloud services, solutions like this are becoming more relevant.

We’re hosting a webinar to talk about how it works, the technical challenges of scaling encrypted collaboration, and what’s next. If you’re interested in privacy-first infrastructure, join us:

If you’ve ever had to migrate data off Confluence, you know it’s not as straightforward as it looks. Broken links, lost metadata, and keeping workflows intact can make the process a nightmare—especially if you’re dealing with large-scale or complex setups.

XWiki is hosting a free webinar, A hands-on guide to migrating from Confluence, that dives into practical strategies for tackling these challenges.

What’s interesting about this session:

It’s based on real-world migrations, so you get insights from actual projects, not just theory. They cover both technical and organizational challenges, like keeping the process smooth for teams using the data. They highlight where automation helps—and where manual intervention is unavoidable. If you’re in the middle of a migration or thinking about one, it might save you some headaches.

The most noticeable change of this release is a revamp of the notifications watch button. In addition, the notification email contrast has been improved. This release also contains a few bug fixes, as well as improvements for developers, but most importantly it contains security fixes, with the highest severity being 10.0/10.0.

This happened to me twice in the last week — for a Kickstarter project I was collecting shipping fees via Backer Kit. I had 2 backers that “decided” they do not want to pay for the shipping, and they started disputes after the product was already shipped. I sent screenshots and proof of service to Stripe, but I still lost the dispute with no appeal option.

I use LinkedIn for news, being connected to the industry leader and also for job search. However, lately is seems to be a more polished Facebook. However, I still keep my profile up to date and sometimes I peek on others profiles/ job changes/ updates.

I do agree with you, they will explode in usage. But where do we stop and is this the universal panacea for the modern obesity pandemic? In my country, Ozempic is highly regulated and is free via prescription for diabetics. You can only get Saxenda otherwise, for weight-loss purposes. I tried it myself after years of infertility, high doses of hormones and pregnancies that made my body (and mind) suffer. I will not deny that it took a mixture of therapy, diet, and exercise to lose the weight. However, I do firmly believe that the magic of Saxenda was putting my “mind hunger” to rest and allowing me the space to make choices not influenced by cravings and hunger.

For more details about the Analytics App (Pro) you can also check: Blog:https://xwiki.com/en/Blog/Analytics-Application-Pro/ GitHub:https://github.com/xwikisas/application-analytics