On 9/2/2011 5:22 AM, frankster wrote: > It seems to me that as there are several extra synths supported since > version 0.20, it would be worth getting some kind of release out > (perhaps alpha quality / unstable version), so that people can make use > of the work people have done over the last 6 years! And you never know, > it might attract a bit more interest in the project as well.
Once I finish this refactor, the next thing I want to set to work on is making it so that drivers can be loaded as plugins. This will allow us to *not* have to make a new release of JSL in order to get a new driver out to the world. This brings up two questions: 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? 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)? - Joe ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
