VS Code is a popular open-source IDE maintained by Microsoft [1] and works especially well for Python and web development. Microsoft maintains their own DNF/Yum repo [2] for the VS Code RPMs and I'd like to include it as an external repo [3] so that developers using Fedora (especially new Fedora users) can easily install it.
What are your thoughts?
1 - https://github.com/Microsoft/vscode 2 - https://code.visualstudio.com/docs/setup/linux#_rhel-fedora-and-centos-based-distributions 3 - https://src.fedoraproject.org/rpms/fedora-workstation-repositories/pull-request/1
Metadata Update from @mclasen: - Issue tagged with: meeting
Some questions and comments:
(We should have an SOP for the process of adding 3rd party repo.)
Some questions and comments: What would it take to get vscode packaged in Fedora?
What would it take to get vscode packaged in Fedora?
I'm not sure, but having this as a third-party repo seems like an easy route since it is maintained by a relatively reputable source. It's less of a maintenance burden by Fedora packagers.
Does Microsoft's repo have appstream data?
I don't know
Is the repo covered by any EULA?
Not that I'm aware of but I wouldn't know how to check.
The package is in flathub (We should have an SOP for the process of adding 3rd party repo.)
The package is in flathub
I am talking to people at Microsoft now, will try to get them to add needed Metadata to the Yum repo.
Metadata Update from @uraeus: - Issue assigned to uraeus
Metadata Update from @catanzaro: - Issue untagged with: meeting
The website says: "By downloading and using Visual Studio Code, you agree to the license terms and privacy statement. " That would be https://code.visualstudio.com/License/ and https://privacy.microsoft.com/en-us/privacystatement
Metadata Update from @catanzaro: - Issue tagged with: meeting
We are somewhat dependent on the MS folks working with us to do something here. @uraeus is pursuing this, but it's not clear whether the effort will be successful. If not done in 30 days, we can close this as cantfix.
Metadata Update from @pfrields: - Issue untagged with: meeting
@uraeus Any update here?
OK then.
Metadata Update from @catanzaro: - Issue close_status updated to: Can't fix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.