LiquidFeedback Frontend

To provide web based user access to the core, there is LiquidFeedback Frontend. It contains a web based frontend for users with access to almost any of the functions of the core and a priliminary API for mobile applications and other purposes including automatic processing of the data. The software is based on  WebMCP, a framework implemented by some of the authors of LiquidFeedback. Currently the LiquidFeedback Frontend is basically a one-to-one view on the data structures and the corresponding actions and forms which are available for the user.

The frontend is beta, but there are already organisations using it in productive environments. There are currently no show stoppers, but a lot of improvements to do.

Get the source

We are using  mercurial as revision control system. In most distributions it's available as a package named mercurial.

Official beta releases

Official beta releases are provided at  http://www.public-software-group.org/liquid_feedback_frontend.

Repository liquid_feedback_frontend

This repository contains only patches reviewed by a maintainer and scheduled for the next release. Official beta releases are tagged with the corresponding tag. Public read access is available  via the Web or by cloning the repository:

hg clone http://www.public-software-group.org/mercurial/liquid_feedback_frontend

You can update it at any time with the following sequence (from within the directory):

hg pull -u

Repository liquid_feedback_frontend.devel

All contributors have write access to this repository to commit patches. It may contain completely untested features. Public read access is available  via the Web or by cloning the repository:

hg clone http://www.public-software-group.org/mercurial/liquid_feedback_frontend.devel

You can update it at any time with the following sequence (from within the directory):

hg pull -u

If you register as contributor, you will get all needed information to get write access to this repository.

Roadmap

• Support for disabling voting weights of inactive users (done, scheduled to release)
• Support for units (attached)
• Split API into public/private (open)
• Full read/write access via API (open)
• Useability: rework user views, navigation, menus, forms (open)

There are many more bugs and wishes in the bug tracker.