Brice, Please forget messing with code and finish building and shipping the modules. The code, right now, means nothing to most of us. Thank you. ac On 01/03/06, synthmodules <synthmodules@synthmodules.com> wrote: > Bob, > > I believe this is unnecessary. I have already re-opened the "Files" > section of this group to members so everyone can upload/download code > again. The files there are in their original form without change. > They are as the authors uploaded them. I have also noted that *all* > PSIM-1 programs are PUBLIC DOMAIN... so I believe this addresses all > the issues you stated. > > I'm working on cleaning up the code to make sure all the programs are > consistant with the header including the PUBLIC DOMAIN statement. I > am looking for input from the community on the wording of the header > as I stated in my previous message. > > I hope this clears up issues regarding availability of code. At one > point I was working on a better way to share the code, but this site > is the easiest for everyone to use. > > Take care, > > Brice > http://www.SynthModules.com > > --- In SynthModules@yahoogroups.com, "rdrake" <rdrake@...> wrote: > > > > Brice, > > > > I am in the process of setting up a site where users of your product > can discuss and share code. To avoid some of the current issues > regarding ownership and licensing, I propose that the actual authors > of the individual programs post their own code, and will leave it to > their discretion what licensing restrictions (if any) they wish to > include. > > > > This site is not intended to compete with the resources you have set > up, nor is an attack on you personally. I'm trying to constructivly > address a couple of the issues (code ownership, availability & > licensing) we've been discussing. Perhaps by alleviating the burden > of "managing" PSIM programming code, you'll have more time to devote > to fulfilling your hardware committments. I hope that you'll choose > to contribute your own PSIM code to the site when you have time > (licensed as you see fit), but obviously that will be your choice. > > > > If you have any concerns regarding this project (potential > infringement, etc.), please let me know in the next couple of days so > that I can address them. Best of luck with all. > > > > regards > > Bob Drake > > rdrake@... > > > > > > > > > >Message: 19 > > > Date: Wed, 01 Mar 2006 08:09:07 -0000 > > > From: "synthmodules" > > ><synthmodules@...> > > >Subject: SynthModules PSIM-1 Programs - PUBLIC > > >DOMAIN > > > > > >Gary makes a good point. My intentions were good > > >and I was trying to > > >make it in the best interest of the community > > >(although it seems that > > >was misunderstood). Anyway, I am in the process of > > >changing the > > >headers on all the code to reflect ALL PSIM-1 code > > >is PUBLIC DOMAIN. > > > > > >Please note, the code many of you were seeing that > > >was still on the > > >Web site (although the link didn't work on purpose, > > >some managed to > > >find old code sitting around from last year with a > > >very early form of > > >the GPL header inserted as a test) is NOT the code > > >that was supposed > > >to be seen or used. It has been removed so there > > >will be no further > > >confusion until I can get all the programs fixed > > >with the PUBLIC > > >DOMAIN header. Also, my wording in the header may > > >have been > > >confusing. I was in no way trying to imply the > > >CODE was my > > >intellectual property. I did design the PSIM-1 > > >(and yes, as you all > > >know Grant did help some, but he did not design > > >it). I think I still > > >deserve credit for the idea and design and would > > >like something in the > > >header that states it. Is that so wrong? If not, > > >any suggestions as > > >to the wording so no one gets upset? > > > > > >- Brice > > >http://www.SynthModules.com > > > > > > > > > > > > > > > > Be sure to check out the primary Web site at: > http://www.SynthModules.com > > Yahoo! Groups Links > > > > > > > >
Message
Re: [SynthModules] Re: Digest Number 272
2006-03-01 by ac
Attachments
- No local attachments were found for this message.