Request License Clarification for Rust-Based Derivative #48

Hello @SethBling and cbscript contributors,

Thank you for creating and sharing cbscript. It's an impressive project, and I’ve learned a lot by exploring the code. I’m interested in creating a Rust-based transpiler inspired by cbscript to address some performance challenges and add more comprehensive documentation for the community. This aligns with feedback previously raised in #1, and I’d like to take on this effort myself.

However, I noticed there is currently no explicit license provided for cbscript, and there is an open issue (#3) regarding the license. To proceed, I’d like to request some clarifications:

1. License Clarification
   a. Since the repository does not currently have a license, it’s unclear whether creating and distributing derivative projects is permitted.
   b. Are there any updates on which license you plan to adopt for cbscript?
   c. Would you consider a permissive license like MIT or Apache 2.0, or do you have a preference for a copyleft license like GPL?

2. Permission to Create a Derivative Work
   a. I’m interested in creating a Rust-based transpiler that draws inspiration from some of the concepts and code patterns of cbscript.
   b. To ensure proper attribution and legal use, I’d like to ask for your explicit permission to use, modify, and redistribute code from this repository once an official license is in place.
   c. I will, of course, credit the original project and link back here.
   d. Are there any additional conditions or requirements you’d like me to follow?

My goal is to help grow the cbscript community and make it more accessible for those who prefer a faster, compiled approach. I greatly appreciate any guidance or feedback you can provide and look forward to hearing your thoughts.