Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

How to open source a library + maintain ownership?

HenryC (147782) writes | more than 5 years ago

Software 0

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?"

cancel ×

0 comments

Sorry! There are no comments related to the filter you selected.

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>