Re: [Savannah-hackers] submission of Another Sound System - savannah.nongnu.org

[Jaime E . Villate]

Hi,
I'm evaluating your project for approval in Savannah. We would like to take a
look at your preliminary implementation to help you solve licensing issues
from the beginning (once the project is more developed changes will be
harder). For example, if you have different modules with different compatible
licenses, the license for the whole project will be the least permissive among
them.

Please register your project again choosing ONE license for your project, and
including a URL where we can find the source code for review (the information
you give at registration is not published in the Savannah webpages; when the
project is approved you will have to give a project description for the general
public). Or if you prefer, you can e-mail me a copy of the source code and
in the registration explain that a copy of the code has been e-mailed
separately.

Cheers,
Jaime

On Mon, Nov 18, 2002 at 04:22:48PM -0500, address@hidden wrote:
> 
> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> 
> Who Cares <address@hidden> described the package as follows:
> License: other
> Other License: portions are going to be MIT style licensed (python bindings 
> to MIT style licensed libs), 
> most of code under GPL
> Package: Another Sound System
> System name: a-ss
> Type: non-GNU
> 
> Description:
> ASS is a project that will develop a protocol for music player back-end and 
> front-end communication - that is to separate player core that is pretty much 
> thesame for all the players and interface that could be anything from 
> command-line to GUI to custom hardware controller. Also dividing player into 
> parts permits one to have dedicated (or whatever) music jukebox and 
> conviniently control it from his desktop. For such a project to succeed it\'s 
> vital to be all-in-one solution and thus be portable and extensible as well 
> as provide solution for all the common tasks users expexts from ANY player to 
> perform. 
> 
> Working plan is like this:
> 1. develop python bindings for the decoding libraries
> 2. develop reference prototype back-end in python
> 3.0 develop the protocol
> 3. develop reference prototype front-end in python as well as library for 
> custom front-ends
> 4 port that library to major languages
> 5 extend back-end to support more features (music shelf, music server (for 
> LANs), \"personal radio\" (autogenerated palylists based on preference), p2p 
> sharing with gateways to other networks, more?)
> a. with port of the backend to C somewhere on the way (if requested by many)
> 
> Other Software Required:
> soft/lib [use] (license)
> python (GPL compatible)
> swig [not used in runtime] (MIT style)
> portaudio [for portable sound output] (MIT style)
> libvorbis [ogg vorbis decoding] (GPL compatible)
> MADlib [mpeg audio decoding] (GPL)
> libmodplug [music modules decoding] (public domain)
> zlib [well..] (GPL compatible)
> 
> Other Comments:
> the preliminary implementation exists but is not available to public - first 
> public release is expected in 2 weeks.
> at the moment this is a one-man project.
> i expect quite a lot of assistance from the community once step 3 is done.