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

help-circle





  • Not legal advice, just an idea.

    Publish early and frequently (e.g. on github with a license statement) and encourage others to clone it. Now the code is out there. You can’t take it back. Even better if the funding agency explicitly approves this.

    You can still dual-license, later, i.e. use a more permissive (or different) license if the agency or a research partner requires this. Just make sure the repo with your preferred licence stays available and uptodate.

    The license is less important than you think. OSS projects live as long as there is at least one maintainer.


  • Not an expert, not an insider. Just commenting to inform about what i know.

    When wayland was designed, security was a concern and it was handled differently than in X decades ago. That is good.

    Under X any application can be a screenreader and see your data. This was okay when you trusted everything on your machine, but is a problem today.

    Under wayland’s original design, no application could be a screenreader. That’s bad. It took way too long to agree on how to make exceptions to the rule, e.g. for screen readers, screen sharing in video calls, etc.