Foswiki 1.2.0 Beta 1 Ready for Testing!

I’m very pleased to announce that after 4+ years of work by a team of dedicated developers and translators. Foswiki Release 1.2.0 is ready for beta test.   This is a major new release with significant changes and new features.    The download links can be found on A list of areas to focus testing can be found at sure to carefully review the release notes and installation instructions.  A lot of significant changes have been made, including a very different installation process.If you encounter issues, please report new issues at, and you can contact the developers for support on, or on

And as mentioned below, we need help in translation of Foswiki. If you or your colleagues can help, please contact

Happy testing!

George Clark
Release Manager, Foswiki 1.2.0

Highlights of this release

  • Major new Foswiki release
  • 257 bugfixes, and 129 enhancements relative to 1.1.9
  • Incorporates 47 “Feature proposals”
  • After in-depth security review, improvements made in 15 areas.

For users:

  • New “Natural Edit” TML editor helps users learn the Topic Markup Language
  • New “block indent” TML markup ( Multiple of 3 spaces, :(colon) (space) indented text )
  • HomePagePlugin adds individualized homepage on login.
  • More realistic edit “preview” includes active links.
  • SubscribePlugin allows one-click subscribe for topic change notifications
  • Old EditTablePlugin has been replaced by the EditRowPlugin. This plugin provides enhanced capabilities and client-side sorting of tables.
  • Improved support for international character sets.
  • Updated jQuery, with more use of AJAX for crisper performance.

 For administrators:

  • New pluggable Store backend, and Plain File store available: higher performing and eliminates use of RCS.
  • New pluggable ACL processing with Read only and Admin only access settings
  • Simpler initial installation and bootstrap of settings.
  • internal admin login can be eliminated, avoiding use of shared passwords.
  • New configure interface requires JavaScript
  • New command-line configuration tool available
  • UpdatesPlugin alerts admin when updated extensions are available.
  • FastCGI and mod_perl supported “out of the box”.
  • Simpler web server configuration: No need to apply special protection to configure script.

 Translation status Help Wanted!

As of this release,

  • Italian translation is 100% complete
  • French and Czech are >99% complete
  • German is >97%
  • Danish is >90%
  • Other languages are 70% complete or lower, and help is needed to complete the translation.

We especially need help with Bulgarian, Dutch, Finnish, Japanese, Polish, Portuguese, Spanish, Swedish, Russian, and Ukrainian.

For more details on translation status, see Foswiki:Community.TranslationTeam and Foswiki’s Weblate translation server. Foswiki thanks the Translators for their Herculean efforts. If you are interesting in helping with the translation, please contact

Foswiki Camp 2015

Let's pick up breakfast before we get started. Foswiki Camp 2015 - Amsterdam


This will be held again in Amsterdam from Wed 25th – Fri 27th March.

This is a great opportunity to meet the faces behind the WikiNames and IRC nicknames of the project:

It’s also a great time to accelerate Foswiki development and indeed accelerate your own knowledge of how to be involved in developing and contributing to Foswiki and the Foswiki community.

See for details – this includes:

  • Registration
  • How to get there
  • Accommodation

Please get involved now with ideas for the Camp here:

Foswiki 2014 / 2015 Update

Hello Foswiki Community,

As 2014 draws to a close, we are much closer to beta for Foswiki 1.2.0.  This release has been several years in the making, and has an extremely broad list of features.    There are 397 Tasks with checkins and 49 FeatureProposals merged. Everyone’s waited long enough for 1.2.0, and we hope to start the release process early in 2015.

You can see the complete list of major features at   Some of the many accomplishments in 2014:

  • Foswiki source now resides on Github. It’s much easier to contribute to the project.
  • Major restructuring of the Foswiki Store has been completed.
    • Foswiki is now store-agnostic, and can use many different store backends as well as the current RCS.
    • Backends have been written for several database engines, including PostgreSQL, MySQL, SQL Server and MongoDB.
    • Foswiki will default to a new PlainFile store on new installations.
  • Configure has had a huge amount of remodeling and modernization.    It’s now lightweight, javascript / jsonrpc based, and includes a shell interface for configuration changes from the command line.
  • A new completely rewritten PageCache greatly improves performance.
  • There is a new Editor interface,  NatEdit, and an updated TinyMCE.
  • Several other extensions have been modernized.
  • Foswiki now “bootstraps” itself, and will work even with a missing LocalSite.cfg.   unzip and go!
  • Support for Nginx, Lighttpd and other FCGI web servers is all there.
  • We’ve gone through several rounds of security audits and a lot of behind-the-scenes work to make Foswiki more robust and secure.
  • The list of “real” release blockers is down to only a few minor issues:
  • The Foswiki developers have been holding release meetings generally bi-weekly,  minutes at  Everyone is welcome to attend!  Meetings resume on Monday January 12th at 1300Z
  • Or join an impromptu meeting on #foswiki anytime.

For stocking stuffers and New Year’s resolutions, we need help with several things:

  • There are a large number of tasks in status “New” that still need developer review.  We need help triaging tasks:
    • Assign a Component,   An extension or a core component, so we can find the tasks later
    • Set the status: Confirmed,   Waiting for Feedback,  or No Action Required.  Or a new status: Needs Developer
    • Please try not to leave tasks in status “New”
  • Life moves on,  people change jobs,  and work gets left incomplete / extensions get orphaned.   These are a great opportunity to get some experience in development.   Many of us started with Open Source to “scratch an itch”.  You don’t have to start big.  If you’ve locally patched a bug, please contribute it back.   Anyone can “fork a repository” on GitHub and submit patches with a pull request.
  • We need to reboot the Translation process.  As soon as we can get the translate software rebuilt we’ll be asking the translators to begin their work. If you’d like to be involved, please subscribe to the Foswiki-translations email list at:   If your native language is other than English, we need your help.

In summary, Foswiki is looking forward to a major release in 2015, consolidating the platform for the future. Any open source project lives and breathes through it’s contributors, so please get involved today and help shape the future of this great project!

On behalf of the Foswiki Developers and the Foswiki Association, we wish you all a Happy New Year.


Foswiki update May 2014

Hello Foswiki community, Time for an overdue update of the Foswiki project.   Read on for notes on the Foswiki Association meetings, the upcoming Foswiki 1.2 release,  Foswiki Translations,  the Foswiki Task Teams, and the Foswiki infrastructure and GitHub migration.


Enjoy community.


Foswiki Association

The Foswiki association held its Fifth General Assembly on .17th May 2014.   Oliver Krueger and Crawford Currie have stepped down from the board.  George Clark was reelected as a board member. Lynnwood Brown and Julian Levens were elected into the board. All three accepted their election. The “new” board consists of: Paul Harvey, Michael Daum, Lynnwood Brown, Julian Levens and George Clark. The Board of Directors met on 23rd May 2014.  Lynnwood Brown was elected as Chairman, and Julian Levens  as treasurer. The complete minutes of both meetings can be found at: FifthGeneralAssemblyMinutes and AssociationBoardMinutes20140523

Release 1.2

We are beginning the release process for Foswiki 1.2 and wanted to pass along the news. George Clark agreed to serve as the Release Manager for Foswiki 1.2. There has been a lot of excellent work done on Foswiki 1.2, and it’s time to get it out.   See Development.ReleasePlan for details of what’s in the release. We will be starting regular release meetings to drive forward the release process.   We are still in the early stages of picking a schedule for the meetings.  Given the time zones involved it appears that a weekday around 1200Z seems to be mostly waking hours for many of our developers.  Release meetings will be held in the #foswiki channel on IRC,  and we’ll start off with bi-weekly meetings. Meetings will be limited to 1 hour if possible. Check out your timezones. If you have any opinions regarding the proposed schedule, please speak up!   Everyone is welcome to participate in the release process.  Planned agenda for the meetings:

  • Release blocker review
  • Other task review
  • Testing and usability feedback
  • Feature request review (limited … we are in feature freeze)

In the meantime if you have a favorite task that has not seen much activity, please mark it urgent so it bubbles up to the top of the development effort.


We’ve established a new email list for the translators: We will use this new email list to keep the translators up to date with the efforts.   You can subscribe here:  Please pass along this information to anyone else in your organizations who might be willing to help in keeping Foswiki translations current.

Task Teams

In the annual meeting, the Foswiki Association decided to retire several of our Task Teams.  The Translation team is being split into the Infrastructure and Release task teams.   Translation is integral to each new Foswiki release.   You can see the current and past team information here: you can help with any of the teams, please let us know.

Foswiki Infrastructure

And last but not least, we have some critical decisions to make regarding the Foswiki infrastructure:

  • The infrastructure team is working on migrating from subversion to github as our primary repository.   We’ve been running github in parallel with svn for several years now and we hope to complete the migration to git prior to the branching of Foswiki 1.2 from trunk.
    • We are proposing making github the primary Foswiki repository under the “Foswiki” github account:
      • The current flow   svn -> (git-svn repo) -> github would be reversed.
      • Core + Default extensions would be in one github repository under the Foswiki account.
      • Each non-default extension will be in it’s own github repository under the Foswiki account
      • Users will also be able to release extensions from their own github accounts.
    • The Tasks web would still be used as our tracker for extensions in the Foswiki github account.
      • It is yet to be determined if we will make any effort to support extensions released from other non-Foswiki github accounts using the Tasks web, vs. using the github tracker.
    • We will still maintain a foswiki-owned repository but it will be a mirror of the github environment.
    • We are still working on a way to map the historical svn rev numbers into git commit identifiers.   Because of differences in how git and svn record a change, it’s possible for one svn checkin to result in multiple git commits,  so it’s not a 1:1 relationship.
    • We also need to work out a good mechanism for updating the tasks web with each github commit.
  • The Pootle server ( is down due to an issue encountered during a system upgrade, and we are taking this opportunity to review tools and decide if there might be a better alternative.
    • Pootle integration to scm tools like subversion or git has been difficult, and only translates one branch.
    • Weblate ( appears to be similar to Pootle, but has very tight github integration,  and can translate across multiple branches.
    • Other suggestions are welcome.
    • If anyone here has experience with Weblate and git integration, we need assistance in working though the integration requirements and implementation.

As you can see,  there is much to be done.  Please help if you can! Thanks, George Clark On behalf of the Foswiki Association Board.