Please tell us a bit about your package and why it requires a bootstrapping exception:
rebar3 is a build tool for erlang: it replaces the now deprecated rebar2 that we still use to build erlang packages in Fedora. Support for rebar2 is gradually disappearing and it's getting tedious to build recent packages with it. Although we should be able to build rebar3 with rebar2, it won't be easy and we don't think it worth the time.
Related RHBZ: #1434779
+1
Metadata Update from @tibbs: - Issue tagged with: meeting
From this weeks log ( https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2018-08-23/fpc.2018-08-23-16.00.txt):
Metadata Update from @james: - Issue untagged with: meeting - Issue assigned to tibbs - Issue tagged with: writeup
As far as I can tell, we don't actually explicitly list the granted exceptions anywhere; the ticket itself acts as the record. So I don't think I actually have anything to write up (or announce).
Metadata Update from @tibbs: - Issue untagged with: writeup - Issue close_status updated to: accepted - Issue priority set to: None (was: Needs Review) - Issue status updated to: Closed (was: Open)
Metadata Update from @tibbs: - Issue tagged with: bootstrap