#9557 Open Firefox for commits by provenpackagers group
Closed: Fixed 6 days ago by kevin. Opened 18 days ago by stransky.

Describe what you would like us to do:

Please enable commits to Firefox package by provenpackagers group, I don't think we need such protection there.


Please also enabled commits for thunderbird package (if there's such restriction).

The current list is:

    'exclude': ['rpms/xulrunner', 'rpms/thunderbird', 'rpms/firefox']

rpms/xulrunner is a dead package.

I mean, you can remove rpms/xulrunner too.

These packages have had this restriction set for legal reasons a while back.
We may want to clear this by legal first before lifting the restriction.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on External (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

17 days ago

Which legal restrictions?

To be clear, I don't expect that provenpackagers do whole package rebases and issue updates, that's rather complicated and time consuming task.

Such change may help to deliver easy-to-fix patches like second arch fixes, spec tweaks, rebuilds for new libraries/compiler updates and so on.

Which legal restrictions?

IIRC they had to do with the trademarks of these projects and the wish to not
see people add patches to these packages that were not released (iirc, firefox's
trademark forbids to call the software firefox if it contains patches that have
not been released).

Note that I am not 100% sure here, this is the recollection that I have of
something that I was told quite a few years ago.
All I know for sure is that we have always had these restrictions, from pkgdb1
to pkgdb2 to pagure on dist-git and I'm pretty sure they were for legal reasons.

Which legal restrictions?

IIRC they had to do with the trademarks of these projects and the wish to not
see people add patches to these packages that were not released (iirc, firefox's
trademark forbids to call the software firefox if it contains patches that have
not been released).

Note that I am not 100% sure here, this is the recollection that I have of
something that I was told quite a few years ago.
All I know for sure is that we have always had these restrictions, from pkgdb1
to pkgdb2 to pagure on dist-git and I'm pretty sure they were for legal reasons.

Ah, Yes. As the package is actively maintained I don't expect such massive patching from wide audience and as a package maintainer I can always remove offensive commits or close the package again if it turns out to be troublesome.

Commit 0741be6d2afb3c116a78307a0d32e7063e1c8a66 in ansible fixes this request.

Thanks!

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 days ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog