#114 [Talk-50] What's new in Copr and Mock
Closed: Resolved 4 years ago by riecatnor. Opened 4 years ago by msuchy.

CfP Submission for Flock 2019 is now open

= Instructions

  1. Fill out the issue answering the questions.
  2. Leave the issue public.
  3. Solicit and consider feedback. Don't assume people will just come to this repo - actively solicit feedback!
    If you want to make changes, just edit the initial comment.
    That is what the CfP committee will read.
  4. Submissions will be considered in rounds.
    Submissions not selected in one round continue to the next one.
    Therefore you can keep on iterating :)
    1. Round 1 selection starts on: 1 June 2019
    2. Round 2 selection starts on: 15 June 2019
    3. Final selection starts on: 1 July 2019

= Questions/Requested Information

  1. What is your proposal?

Go through recent changes in Copr: CI/CD improvements, change in the retention policy, new architectures.
Go through recent changes in Mock: force-arch, Jinja2 templating system, dynamic build requires, mockchain changes.

  1. Who in addition to the speaker needs to be in the room for this to succeed? This could be the audience you need to reach, other participants in the conversation, or other stakeholders.

List each person by their name and FAS ID, as shown below:

  • Person One: praiskup (Pavel Raiskup) will give the talk together with me.

Target audience is Fedora package maintainers and users of Fedora who are building 3rd party packages on top of Fedora/CentOS.

  1. Is this a…
  • 50 minutes: Talk
  1. Anything else we need to know?

Projector with HDMI od DP is just fine.

  1. Who are you?
  • Name: Miroslav Suchý
  • FAS ID: msuchy
  • IRC Nick, if not FAS ID:

I'm definitely interested (to hear about feature I was working on, Dynamic BuildRequires). :)

As someone who is often working on this type of tooling, I'm interested as well.

Metadata Update from @mattdm:
- Issue tagged with: Talk In Consideration

4 years ago

I see this is still in consideration. To help you with the decision:

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

4 years ago

Login to comment on this ticket.

Metadata