-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Naming problem - name is in use #58
Comments
@AmyrAhmady |
Yes, and they've literally said what you can do instead of opening issues on github: |
The legal name is ".NET Multi-platform App UI" as @davidortinau stated, #35 (comment) I don't think naming discussions should be on GitHub. |
If the legal name is ".NET Multi-platform App UI", why is this repository at "/dotnet/MAUI"? It's called "MAUI" literally EVERYWHERE in this repository. You can't really be serious here... |
@dhindrik I think naming discussions should be on GitHub and should be public. |
aside of this religious conversations, I am sure the team can come up with something much better, I love the new approach, I've been waiting for it for 20 years, or let's say 15 if we think Silverlight was the first glance at something like this. the new MVU approach looks mint, specially in light of SwiftUI and Flutter, great work team and lets give it a better name, lets not be Microsoft for once ;) |
I think GitHub should be for technical discussions related to the code. The reason I linked to the comment is that he said that he wanted to take naming discussions via email. Probably to point them to the right persons on Microsoft. I guess it is not the developers that are responsible for the legal aspect of the naming. And I don't defend them I just want to help to share the information that are available. And I don't understand how a big company like Microsoft missed that Maui is a registered trademark. I don't think that is good for the product. So hopefully there will be an easy solution to this, that all will be happy with! |
ppl, be kind... I don't like it either. It can make think ppl that the name was taken like that in a malicious way... But maybe they even didn't know the MAUIKIT... but still, there is no need begin a gihub war ;) we are all developers ;) |
@dhindrik well yeah, I can agree on that. I can't understand that too. It's the first result when you enter in Google or DuckDuckGo query "Maui Framework" -> https://mauikit.org/ And such company as Microsoft really could do a small research before picking a name for a product. |
duplicate of #35 |
@adojck can i please ask you to read this comment We belive this is not the forum for this discussion. If there are ongoing concerns, please email [email protected] and we can loop in the appropriate teams. Also please don't create a new issue. Thanks |
This is why Linux products are the way they are, and why noone had ever heard of KDE MAUI until now -- you lot just argue about inane stuff instead of getting work done. |
Description
Could not find any open issue on this topic. Others are closed, but still not solved. That is why I open a new issue.
MAUI is a registered trademark in European Union. It is registered by Blue Systems which also employes KDE developers.
Here is a link about trademark status: https://euipo.europa.eu/eSearch/#details/trademarks/013410601
These news struck me like a lightning in early morning when I was drinking my coffee. This happening again? It was similar issue that Microsoft made in the past, I think it was GVfs (GNOME Virtual file system), and now this MAUI, which for the past idk maybe 6-8 years was a KDE project for front-end UI framework based on QQC2 and Kirigami. It is really nice project, free and open-source. How can someone just come and take the name of the project for some another project? Maybe my next project should be called .NET or Microsoft? I don't get it...
Solution to the problem would be simple: rename your project, as it is already registered trademark and these actions are illegal.
Oh, and one more thing. Stealing is bad. Microsoft should be ashamed of themselves.
The text was updated successfully, but these errors were encountered: