Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×
Software

+ - How to open source a library + maintain ownership?

Submitted by
HenryC
HenryC writes "My company has a closed source webservice that clients submit data to. We were hoping to open source the client, so users can extend it / fit it into their own needs and if that is succesfull, eventually open source everything. However, it sounds like it is very hard to open source a client library and still maintain enough ownership to keep the quality high and keep it consistent with our webservice. For example, we don't want people using it in a way that collects data which would violate the privacy policy. We don't have the funds for an IP lawyer but still want to go through with this. Does anybody have any recommended reading, or case studies, or anything that would be helpful for us to figure out which license to use and how to add any additional info to keep this safe?"

panic: kernel trap (ignored)

Working...