search

ctsstc / typio-form-recovery-reboot

This is a fork of the Typio Form Recovery Chrome Extension from Bitbucket: https://bitbucket.org/nicklassandell/chrome-form-recovery
Other
20 stars 6 forks source link

Could you please change the Typio license from Creative Commons to MIT, so that we can make and publish changes to Typio? #6

Open unforgettableid opened 1 year ago

unforgettableid commented 1 year ago

Dear @nicklassandell:

Introduction

Thank you for writing Typio Form Recovery! It doesn't work anymore, due to changes to Google Chrome. @ctsstc hopes to fix it and get it working again.

The problem

Unfortunately, you licensed Typio as "Creative Commons Attribution-NonCommercial-NoDerivatives 4.0". This means that we are legally forbidden from compiling and distributing a fixed version to the public.

Proposed solution

Would you be willing to please relicense Typio under a more-liberal license, such as the MIT license?

Legally, the best way to do so might be to edit https://bitbucket.org/nicklassandell/chrome-form-recovery/src/master/license.txt so that it holds the new license.

Conclusion

I'd be curious to hear your thoughts.

Thank you for reading this!

ctsstc commented 1 year ago

Yeah it seems that there's no response from Nick from what I've seen. I knew I needed to dig through and understand the license better, but it does seem that maybe the best thing to do is start something from scratch in memory of Typio unfortunately. The code is quite dated, I was still running into issues trying to get it all running and rendering properly, although there was a large effort put in on updating it and getting it to run in the first place. I'm not very experienced with Vue and updating it from v2 to v3 as well as the manifest from v2 to v3 was a bit of a lift. Typio is a great extension, but it seems that the best route may be to start something fresh unfortunately. At this point I'm not sure if the owner is still around. I had ambitions of carrying the torch, but it didn't feel right to swap out or close some attributions nor would it be valid in the current license. For all we know, people are donating to a black hole currently which isn't great either.

dumblob commented 1 year ago

We can at least cement the Nick's code under CC and everything new under MIT (both are compatible AFAIK). And later once (if at all) Nick appears around, we can ask him to relicense also his work under MIT to not have this repo dual-licensed.

unforgettableid commented 1 year ago

@dumblob:

I found this discussion on Creative Commons NoDerivatives clauses. They're very restrictive, and they seem to me at least to strongly discourage forking.

I think the best thing to do would be for us to keep trying to contact Nicklas, with maybe one ping every 4-12 months at first. There are multiple ways to contact him. I think it'd best to try a variety of different contact methods.

A good email subject line might be: "Typio relicensing request: CC-BY-NC-ND > MIT. Fine with you?"

unforgettableid commented 1 year ago

@dumblob:

A possible alternative to Typio which we could use for now is Formalizr. It uses the Apache License 2.0, according to its license declaration.

dumblob commented 1 year ago

Hm, interesting, the license was actually added by @nisansei in https://github.com/ctsstc/typio-form-recovery-reboot/commit/39cf142754428ed3076c832caa8812575737b485 .

ctsstc commented 1 year ago

I think the original two comitters are the same person.