[WLANware] Radiomate Ninux-Freifunk-GSOC project status update

[clauz at ninux.org]

Hello, everybody.

This e-mail has already been sent to the radiomate mailing list a couple
of weeks ago, so sorry for the cross-posting.

I am glad to announce that we have a new webradio engine. Its source
code can be checked out from the repository [1].

The current revision will be the one that will be submitted to
Google. There are still some things to do, especially a web interface
that interacts with the CGI (see below), implemented as a wordpress
plug-in or whatever (a website in django?).

Other things to be done are in the TODO file in the repository. This
makes sense for a single-developer project, but perhaps it would be
better to exploit trac tickets, also to organize suggestions from you
and from users.

I here copy and paste an extract from the README file:
"""
RadioMate is a Free Engine for Distributed Web Radios, i.e. Web Radios
in which the users can broadcast from home or wherever there is a
connection to the Internet.

While Savonet Liquidsoap [http://savonet.sourceforge.net] already
provides a scriptable language and engine for Web Radios with a
centralized schedule, RadioMate wraps and extends it to be used for Web
Radios in which the schedule is managed in an horizontal and distributed
way.

Website: http://radiomate.org
Mailing List: https://lists.subsignal.org/mailman/listinfo/radiomate


Structure
=========

At the moment, RadioMate has two main components: the radiomate.cgi CGI
script and the radiomated daemon.

radiomate.cgi accepts JSON requests, made with the POST method,
interacts with the database, and returns JSON responses, as described in
the JsonAPI.txt file.

Through the JSON API, the user can:
- manage roles, i.e. groups of users, with different level of permissions
- manage users, each user must have a role, created in advance
- manage mediafiles, i.e. audio (for the moment) files, which must be
already present in the server's filesystem
- manage playlists, which are collections of mediafiles
- manage timeslots. Each timeslot represents a time interval reserved
for a  transmission. The slottype parameter must correspond to a defined
JukeSlot type (described later).

The radiomated daemon retrieves the reserved timeslots from the database
and schedules the transmissions, launching the appropriate JukeSlots.

JukeSlots are an abstraction for liquidsoap instances: the main JukeSlot
manages the global fallback playlist, the actual transmission stream and
the takeover stream. The global fallback playlist is played when there
are no scheduled transmissions, while the takeover stream can be used to
override the normal webradio schedule.

A LiveJukeSlot (slottype:"simplelive") istance represents a transmission
in which a WJ can connect with her client and transmit/perform live,
while in a PlayListJukeSlot (slottype:"simpleplaylist") a predefined
playlist (or a prerecorded transmission) is played.

New JukeSlots can be added, plug-in-wise, as described below.

"""

Ciao!
Clauz

[1] svn co http://svn.radiomate.org/trunk



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.freifunk.net/pipermail/wlanware-freifunk.net/attachments/20100830/f86d31b3/attachment.pgp>