• 1 Post
  • 27 Comments
Joined 1 year ago
cake
Cake day: July 21st, 2023

help-circle












  • Wow, thanks a lot for this thorough answer. I see I need to dust off the old employment contract and see what it says - I’ve had an assumption that any ownership my previous employer has pertains only to any discovery that could be commercialized through patents and spin-offs - this is not that. This work is academic research, and I was required to make any publication openly accessible (with CC-licenses) due to how the work was funded, and this code base contains all the analysis tools that underpin these publications.


  • The idea that a license added would only apply to code added after the license change is very funny.

    I suppose it makes sense if it originally had a license, and you then change the license to be less permissive.

    What is more difficult is that earlier commits won’t have that license explicitly unless you rewrite git history to make that happen (which is possible but tedious).

    I will probably not do that, but I guess it factors into my second question: That I in that case should make sure to include it in all branches (which are not treated as branches in the common sense, but rather as forks within the repo - they will never be merged to the main branch).



  • Thanks for your answer.

    1. The license change won’t apply retroactively - I am not sure theres a legal way to retroactively change licenses and terms? I am recalling back to the Unity runtime fee, which they wanted to apply retroactively, but there was a lot of noise/discussion on whether it was legal to even do this.

    OK, in that case it may not even make much sense to add a license. There will be no added code to this repo in the future, so there will nothing the new license would apply to.

    1. Once you have main released version of the repo that contains the license you want to use going forward, any branches from that point should contain license by default? Since its just a file in the main branch.

    Yes, you kind of answered this in question 1. Since it is not retroactively applied, it won’t apply to the stale branches that only exist as snapshots of the code.

    1. Since you are using it commercially, and want to change the license for future versions, you will absolutely want to discuss this with whatever entity is using it. You could choose a license they refuse to accept, and end up not being able to use any future releases. My employer will not use copy-left style licenses for example.

    Good point. This is not included in any software that is distributed, it is only a smaller part of an internal codebase used for data analysis. Does that not change things? But to be on the safe side, it would probably make sense to make it as permissive as possible to avoid any issues here. But then again, if it is not applied retroactively then nothing of the code used will be subject to any license. But good thing to remember for the future.



    • I’m using FitoTrack to keep track of running, biking, hiking and walking with GPS-data.
    • I have a Xiaomi Mi Band 7 that’s set up with Gadgetbridge to keep track of especially heart rate and roughly sleep habits (though not very accurate).
    • I use Loop Habit Tracker for various habits I want to keep, not only related to health.
    • openScale to keep track of weight data with my Xiaomi Mi Body Composition Scale 2. I think this can use GadgetBridge as well, but openScale works like I want, so I have not bothered trying it out.

    For the most part, I try to set up automatic data exports from these apps that is synced with my Nextcloud server, and my plan is to eventually develop something of a dashboard that allows me to easily view historical data from all these sources, but as of now it more a backup solution.