Description of problem: I'd like to see this program added to either non-free or tainted as I'm unsure of what the license form is. If you download the src.rpm made by PCLinuxOS and browse the teams.tar.gz inside of it the file LICENSE that's under /usr/share/teams shows that it's free of charge, but as the program is made by Microsoft I can't really tell if this has a GPL license or something else. Someone here might know better. I took the liberty of successfully porting this program from the previously mentioned PCLinuxOS src.rpm, the program builds using go-lang and it installs without any visible error/s and it also runs perfectly fine. The repo to find the deb packages is here: https://packages.microsoft.com/repos/ms-teams/ Version-Release number of selected component (if applicable): 1.3.00.5153
Created attachment 11895 [details] Proposal spec file
Here's the link to the PCLinux OS src.rpm: https://ftp.nluug.nl/pub/os/Linux/distr/pclinuxos/pclinuxos/srpms/SRPMS.pclos/teams-1.3.00.5153-2pclos2020.src.rpm
The official Microsoft RPM (available from https://teams.microsoft.com/downloads) shows that the license is the Microsoft End User License Agreement. The license can be found in /usr/share/teams/resources/ReadmeFirstTermsofUse.txt. The license found in /usr/share/teams/LICENSE looks to be the license for the Electron framework that the Teams app is built on. The Microsoft RPM installs and runs OK on Mageia 7 (albeit I've not used the latest version), so I don't see a pressing need to repackage it.
CC: (none) => mageia
(In reply to Martin Whitaker from comment #3) > The official Microsoft RPM (available from > https://teams.microsoft.com/downloads) shows that the license is the > Microsoft End User License Agreement. The license can be found in > /usr/share/teams/resources/ReadmeFirstTermsofUse.txt. > > The license found in /usr/share/teams/LICENSE looks to be the license for > the Electron framework that the Teams app is built on. > > The Microsoft RPM installs and runs OK on Mageia 7 (albeit I've not used the > latest version), so I don't see a pressing need to repackage it. Sure, but I do wish that we could at it to Cauldron and every new version contains bug or performance fixes plus I know a couple of people that would consider using Mageia as a main operating system IF for example Teams could be found in rpmdrake. I'm not trying to be rude, just helpful in making more programs ported. I like to port programs, but I'm by far NO expert in fixing bugs. There should be a job title for that when someone wants to help out with Mageia. I believe that it's called being a PACKAGER. I have managed (with help of course) to port packages to Mageia before, but I didn't add them to Cauldron as I don't want to get sued if I add a package that clearly isn't allowed to be added. What I COULD do is to create a non official repo for people to add to their mirrorlist so that they can install whatever package I've ported. I think that exists in OpenSUSE if I'm not mistaken.
(In reply to Kristoffer Grundström from comment #4) > Sure, but I do wish that we could at it to Cauldron and every new version > contains bug or performance fixes plus I know a couple of people that would > consider using Mageia as a main operating system IF for example Teams could > be found in rpmdrake. As I understand it, the Microsoft EULA does not permit redistribution. So the only way to make it available though the Mageia repositories would be to do as was done for the Adobe Flash Player plugin - create a meta-package that automatically downloaded and installed the latest version. > I'm not trying to be rude, just helpful in making more programs ported. > > I like to port programs, but I'm by far NO expert in fixing bugs. > There should be a job title for that when someone wants to help out with > Mageia. > > I believe that it's called being a PACKAGER. Yes, that's what it's called. See https://wiki.mageia.org/en/Becoming_a_Mageia_Packager. As it says there, all you need is enthusiasm and a willingness to learn. You don't need the skills to fix bugs yourself - just pass bug reports on upstream, and update your packages when the bugs are fixed. > I have managed (with help of course) to port packages to Mageia before, but > I didn't add them to Cauldron as I don't want to get sued if I add a package > that clearly isn't allowed to be added. > > What I COULD do is to create a non official repo for people to add to their > mirrorlist so that they can install whatever package I've ported. Why do you think that makes you any less likely to get sued? If you create official Mageia packages, the other packagers are likely to warn you if you are doing something that isn't allowed. If you create your own unofficial repo, you're on your own.
https://docs.microsoft.com/en-us/microsoftteams/ links to https://docs.microsoft.com/en-us/legal/termsofuse which states ... Personal and Non-Commercial Use Limitation Unless otherwise specified, the Services are for your personal and non-commercial use. You may not modify, copy, distribute, transmit, publicly display, perform, reproduce, publish, license, create derivative works from, transfer or sell any information, software, products or services obtained from the Services (except for your own, personal, non-commercial use) without prior written consent from Microsoft. So unless you have written permission from Microsoft permitting Mageia to redistribute it or as above using a getflash type package, closing the bug request as wontfix. As a member of the board of directors for Mageia, which is responsible for handling legal issues, I have no desire to be sued.
Resolution: (none) => WONTFIXStatus: NEW => RESOLVEDCC: (none) => davidwhodgins