fesco

Clone
Source Code
GIT

#1774 Treat Developer-only Stream for Fedora Atomic Host as non-Released Fedora artifacts
Closed: Fixed 6 years ago Opened 6 years ago by stefw.

Closed: Fixed
Reopen Issue

Background and Premise:

  1. Fedora Requirements for CI/CD explicitly allow for CI/CD pipelines not run on Fedora infrastructure (section 3) and outline requirements for Fedora delivery of artifacts from those pipelines (section 5)
  2. Fedora Requirements for CI/CD require recording (via content generators) all output artifacts delivered as Fedora content (section 5 clauses 5 and 6)
  3. Fedora has an Objective for CI/CD of Atomic Host which intends to deliver exactly those artifacts that are integration tested by a CI pipeline.
  4. The CI pipeline currently composes Atomic Host artifacts several times a day.

Plan:

  • The CI/CD Objective plans to produce a Fedora Atomic Host Developer-only Stream which always includes the latest OSTree/QCow2 artifacts that passed the pipeline.
  • This Fedora Atomic Host Developer-only Stream should be hosted at a non-mirrored *.fedoraproject.org URL.
  • This Fedora Atomic Host Developer-only Stream will not be signed with a Fedora release key, but with another Fedora Atomic Host Developer Stream key.
  • This Fedora Atomic Host Developer-only Stream is not targeted at Fedora users and will not be treated as Fedora “delivered” content.

FESCO Request for Waiver:

The CI/CD Objective would like to treat this Developer-only stream for Fedora Atomic Host as non-released Fedora artifacts, while still hosted at a fedoraproject.org URL. As non-released artifacts it would not be signed with a Fedora release key. It would also not be subject to the usual Fedora requirements for recording and archival of content/input/outputs for Fedora released artifacts.

Metadata Update from @maxamillion:
- Issue tagged with: meeting
6 years ago

I'm not sure I understand all the implications of this waiver (especially from the rel-eng perspective), but I guess I'm OK with it, given my current understanding. Please consider me +1 for this in today's meeting.

What is the reason to host it under a *.fedoraproject.org URL? In general this sounds ok, so +1 in case I will have no Internet later.

@till Good question. I realized I forgot to include the "Why" in this waiver request:

The CI/CD objective aims to:

  • Help packagers start to accept testing as part of their packaging and development workflow.
  • Help Fedora packagers and developers work on Fedora Atomic Host as an always integrated and verified whole ... rather than something that comes together just before a release.

Hence:

  • Making the composed artifacts always available (for each change several times a day) helps us meet the these goals of the objective.
  • Making it available at a fedoraproject.org URL prevents forking of the distribution during development but focus packaging and development efforts around the Fedora brand.
Edited 6 years ago by stefw

We lost in-meeting quorum, but the current proposal is +4 (from @maxamillion, @bowlofeggs , @sgallagh, and @kevin). If we get one more in-ticket +1 to it, consider it passed.

proposal: ask for feedback from infra (re resources/load) and legal (re: keeping srpms that the ostrees were built from)
Edited 6 years ago by maxamillion

Did you not count the +1 from my comment earlier in this ticket?

@stefw Has reached out to both legal@fedoraproject.org and infrastructure@lists.fedoraproject.org teams on this. Will summarize responses received.

Received response from Fedora Legal that the following meets the legal source code distribution requirements:

  • The developer stream will only contain sources stored and curated in Fedora dist-git (the usual source repository for Fedora).

  • The developer stream will contain full source RPMS for every single artifact delivered.

No response has been received from infrastructure@lists.fedoraproject.org.

AGREED: wavier granted for 6 months, will revisit then. Logs should be added to artifacts (+6,0,0) (nirik, 18:43:06)

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

No response has been received from infrastructure @lists.fedoraproject.org.

FTR, I do not see your message on the archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/2017/9/

The message bounced both at infrastructure@fedoraproject.org and infrastructure@lists.fedoraproject.org. I then sent it to @kevin directly.

Login to comment on this ticket.

Metadata
None

meeting

None
None
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.