• 4 Posts
  • 48 Comments
Joined 2 years ago
cake
Cake day: June 26th, 2023

help-circle

  • Glitterkoe@lemmy.worldtoCoMaps@sopuli.xyzName Ideas
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    8 days ago

    The one that lives within or is in the living. It’s alive in all of us (the community) and the other way around: our contributions live within the app and OSM. Also, its supposed to be the fork that lives on. I think this would be a subtle nudge without carrying a scarred name like phoenix/revival with the project forever.















  • Before I forget: many thanks for your response! It’s nice to discuss this.

    That distinction is important indeed. I could always add a notice to the README to underline that for potential users.

    I’m going to make a dependency map of our own libs and license the language tools and their dependencies as LGPL such that they can be relatively freely embedded in other products. The post-processing and analysis libs/applications will then be licensed under the AGPL (dual licensing). We had other libraries under the GPL before, but in the current landscape it seems wise to cover the hosted/embedded variations as well.





  • Hmm, I don’t know of many widespread (programming) languages with an AGPL-alike license, but would love to see examples! Wouldn’t a language have a better chance of adoption with an easy to integrate licensed library?

    As for some full featured visualization and analysis applications that accept the language’s data format: those might be a good fit for AGPL as they generate valuable insights.

    With non-core stuff I meant a tiny wrapper around some 2D data or some color palette management. I’m fine with MIT/Apache there and would consider LGPL to keep the landscape simpler.