Re: [Jsynthlib-devel] Separating the synth drivers from JSL (Was: Name for refactored branch)

[Vladimir A. <vl...@gm...>]

On 09/02/2011 09:38 AM, Joe Emenaker wrote:
> 1 - Will we want to manage the source for JSL and the drivers
> *separately*  at that point? Would we have a branch for every driver, or
> have a branch for*all*  of the drivers? Or is there a better way to do
> this than to use branches?

I would think synthdrivers would move to the top level of repository and 
each driver will get its own build.xml. Whether to use branches in 
development would be up to maintainer of each driver.

I just took a look at jedit repository structure, they actually have 
trunk, branches and tags inside each individual plugin folder. That 
probably make much sense, as each plugin can be project on its own, can 
be taken straight to different repository, or brought to SF repo from 
outside

> 2 - How do we want to*distribute*  the drivers? What I'm getting at here
> is that I think Brian still has control over jsynthlib.org, but he's
> hardly ever here, so I think there's little chance of us being able to
> store the drivers on his server. Do we want to store them on
> SourceForge? Do we want to store them on my server or someone else's? If
> we store it on someone's server, do we want to use some descriptive
> domain name (like jsldrivers.org or something)?

I would think in the application itself that shall be made user 
configurable through preferences. That way independent developers would 
be able to publish their drivers on their own websites.

As for how to handle the projects repository, I donno, maybe that is too 
early to ask this question.

Hey, please do not hide you development. The branch does not need to be 
tidy and compilable. You could dump your work in progress freely on it. 
This way other developers would be able to plug in early. I for one is 
looking forward to get into this development. Looks exciting

-- 
Vladimir