• 210 Posts
  • 1.25K Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle








  • The CLA can never override the code license. It handles the transition of your code into their code, and what they can do with it. But once it’s published as AGPL, you or anyone else can fork it and work with it as AGPL anyway. The CLA can allow them to change the license to something different. But the AGPL published code remains published and usable under AGPL.

    I’m usually fine with contributing under CLA. A CLA often make sense. Because the alternative is a hassle and lock-in to current constructs. Which can have its own set of disadvantages.

    A FOSS license and CLA combination can offer reasonable good to both parties: You can be sure your contribution is published as FOSS, and they know they can continue to maintain the project with some autonomy and choices. (Choices can be better or worse for others, of course.)




  • That /unsaved/{id} path with a unique server-assigned identifier means your diff content was transmitted to and stored on their servers.

    Not necessarily. URLs can be changed client-side, within the browser, through JavaScript. The fact that the URL changed to unsaved alone is no proof. It could very well be browser-local, labeled unsaved and held in session store for example, ready to be saved.

    With the other indications, you can of course make a guess and/or consider it a strong indication.

    It should be pretty obvious/observable when observing interaction and network requests within the browser. A network request with the content as body would be much better proof.