IssueRaiser

> The way I read it the intent is to ensure there is one sanctioned version of Rus basically that Through it's very annoying that it ne...

> The way I read it the intent is to ensure there is one sanctioned version of Rus basically that Through it's very annoying that it needs refinement _again_ and _again_ every f* time they update the trademark policy. Like why - is there no exception for research (i.e. science) use, as long as explicitly labeled at such - public development forks which are used to prototype directions rust could go into, again if clearly labeled as such and not maintained as forks (through to be fair the line between a public experimental rust development fork and an early rust "full" fork are thin) - wrt. software compatibility allowance why is it limited to the "packaging system of that platform" can't I fork to idk. create compatibility with a code analysis tool, changes I then later want to upstream but first need to test so need to distribute to various people? and sure you will normally get written permission for all the cases above, just the chance that someone could abuse this preventing you from doing very reasonable thing is IMHO an issue. I really don't want to see a headline like "rust forbids <company> from creating a compatible code analysis tool because <some stupid issue>".

Posted by dathinab on Nov 10, 2024, 8:01 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

hackernews (SaaS)

> The way I read it the intent is to ensure there is one sanctioned version of Rus basically that Through it's very annoying that it ne...

dathinabNov 10, 2024, 8:01 PM

> The way I read it the intent is to ensure there is one sanctioned version of Rus basically that Through it's very annoying that it needs refinement _again_ and _again_ every f* time they update the trademark policy. Like why - is there no exception for research (i.e. science) use, as long as explicitly labeled at such - public development forks which are used to prototype directions rust could go into, again if clearly labeled as such and not maintained as forks (through to be fair the line between a public experimental rust development fork and an early rust "full" fork are thin) - wrt. software compatibility allowance why is it limited to the "packaging system of that platform" can't I fork to idk. create compatibility with a code analysis tool, changes I then later want to upstream but first need to test so need to distribute to various people? and sure you will normally get written permission for all the cases above, just the chance that someone could abuse this preventing you from doing very reasonable thing is IMHO an issue. I really don't want to see a headline like "rust forbids <company> from creating a compatible code analysis tool because <some stupid issue>".

Comments (0)

No comments yet. Start the discussion.

Comment on this issue