• 0 Posts
  • 62 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle






  • Note that it speaks of the “official version” in the next sentence, which seems to me like there will be inofficial versions which requires a more permissive license

    It doesn’t necessarily require a permissive license. For example, Winamp could be willing to license the code for non-official versions or for integration into other projects, but at a fee and with limitations set by Winamp. As I’ve said in other comments, the press release is vague, and I think that’s likely to be intentional ambiguity.


  • The article’s text said, “Winamp will remain the owner of the software.” That does not, in fact, preclude giving it a FOSS license, nor does retaining a related trademark. GP was correct. They can make it FOSS and keep the trademark and copyright. I don’t see any reason to think it unlikely.

    It’s possible. However, at no point in the post is that discussed, so it’s pretty wild speculation.

    Forking someone’s copyrighted work does not change ownership of the rights in any jurisdiction that I know of. If you meant “ownership” in a difference sense, like maybe control over a derivative project’s direction, then I think choosing a different word would have made your meaning more clear.

    AFAIK, it doesn’t “change” ownership, but it creates a new property with new ownership. That new ownership may be bound by he terms of the original license, but the original owner has no further control.


  • The open-source licenses that I’ve used don’t require surrendering copyright.

    The creator doesn’t “surrender” their copyright, but someone can fork it and then have ownership of their version. “Winamp will remain the owner of the software” indicates you won’t have ownership of a fork.

    Again, it doesn’t clearly state whether it will be “FOSS” or “Source Available”, but if they were planning to go FOSS, you’d expect them to say something to make that clear. Leaving it vague seems like a strategy to get attention while not actually lying.









  • A solution would be to have a STOP SIGN at the off-ramp to protect cyclists. It’s not ideal for motorists, but it’s a far safer option, and there’s more than enough distance coming off the highway to allow for it.

    Sure, the yield sign could be turned into a Stop Sign (I honestly don’t know why it isn’t one now), but that’s not what’s in the picture, or where most of the conflicts happen. What’s pictured is the an on-ramp and most of the conflicts are drivers drifting across the bike lane to get on to the expressway.


  • Up until 3 years ago, I lived in KW. I agree this is insane and completely avoid biking on these lanes. However, whenever this picture pops up on social media, I always question what would have been a better option?

    • Should they just not have put in bike lanes? They are useful on either side of the overpass.
    • Should the bike lanes be centre running? They could run beside the LRT, but I know centre running bike lanes present a bunch of new problems.
    • Something else?

    Here’s the location on Google Maps, if anyone wants to poke around.

    I would love to see dedicated bike infrastructure to cross the expressway, but I don’t see that happening in the short/medium-term. There aren’t any other nearby crossing, though the next one south of here is okay~ish.