[gmpi] Re: The Master Plan
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Tue, 8 Mar 2005 11:11:39 -0800
On Tue, Mar 08, 2005 at 11:03:59AM -0800, Chris Grigg wrote:
> I truly do dislike having to ask these things I occasionally pop in
> to ask, so please nobody assume I'm trying to be a killjoy with this,
> but: Since everything that's been coded up so far is necessarily
> subject to revision in order to better support whatever further
> coding comes next, what precisely is the purpose of 'releasing' it at
> this stage? Put another way, to whom would it be 'released'? Would
> developers be well advised, or ill advised, to incorporate this
> release into products and call it GMPI?
Sorry, I meant to publish it. So far it's on my hard drive. I'd like
to put it in a place where people (this list, mostly) can look at it and
comment and make changes. A public CVS with bug tracker and doc manager,
preferably.
Remember, at my core I am an open-source guy, so my inclination is to be
as public as possible about all stages of development.
> Also there are the whole licensing and (c) ownership issues to get
> worked out, are there not, before any public release?
Sorry, I don't mean "Issue a press release, 1.0 is done", just putting
it somewhere that you all can get at it.
As for ownership, it is currently owned by Jeff and I :). We're trying
to work within the group here, but (as you can see) we're chomping at
the bit to get work done. Ron asked, a while back, that we not post
this code anywhere, so we haven't. But I want to.
This code is a prototype of the API, and it solves and raises issues
that the group needs to address. If I can't share it...
I hope that clarifies.
> >I've been dodging this email until my tree of the SDK was caught up. I'm
> >caught up. We need to decide what we're going to do with it, in terms of
> >releasing it. Most of the ideas have been posted here, but the complete
> >code has not.
> >
> >Right now I have a C and C++ split, each with host and plugin directories.
> >Each of those 4 trees provides some base code which should not need
> >modification by many developers (but could be if needed) and example code
> >which shows how to use the base code and implement a host/plugin. It's
> >all been tested on Linux, but needs to be re-reworked for Windows and Mac
> >(and others), I am sure.
> >
> >So, until we agree how to release this, that's all you get :) Seriously,
> >I'm dying to share this stuff.
> >
> >
> >On Wed, Mar 02, 2005 at 02:26:34PM +1300, Jeff McClintock wrote:
> >> MIDI, Audio, Parameters, Events, GUI etc being your building blocks..
> >
> >I think the next steps are:
> >
> > - Documenting what we have done (Who "owns" the spec? I owned the reqs
> > doc, I'd rather not do it again, but I can if I have to).
> > - Expanding the host interface (I added IGMPI_Host which is passed to
> > plugins at creation time).
> > - Specifying the metadata interfaces (internal and external)
> > - Arguments to plugins
> > - Defining a plugin "bundle"
> > - Writing a cross-platform GMPI_PLUGIN_PATH walker
> >
> >So really, let's get this code released. Once we release this snapshot,
> >we can freeze it until it is good on all platforms, then start moving
> >forward again. I'm sure there will be plenty of critique on what I've
> >done wrong in C++ and what I've done (somewhat unilaterally) in C.
> >
> >Having fun.
> >Tim
> >
> >
> >----------------------------------------------------------------------
> >Generalized Music Plugin Interface (GMPI) public discussion list
> >Participation in this list is contingent upon your abiding by the
> >following rules: Please stay on topic. You are responsible for your own
> >words. Please respect your fellow subscribers. Please do not
> >redistribute anyone else's words without their permission.
> >
> >Archive: //www.freelists.org/archives/gmpi
> >Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
>
>
> ----------------------------------------------------------------------
> Generalized Music Plugin Interface (GMPI) public discussion list
> Participation in this list is contingent upon your abiding by the
> following rules: Please stay on topic. You are responsible for your own
> words. Please respect your fellow subscribers. Please do not
> redistribute anyone else's words without their permission.
>
> Archive: //www.freelists.org/archives/gmpi
> Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
>
----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules: Please stay on topic. You are responsible for your own
words. Please respect your fellow subscribers. Please do not
redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
Other related posts:
